Repository navigation
Lesson 04 agent loop - #6
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Lesson 4 writes the agent loop by hand so I understand what RubyLLM's chat.ask does inside. It is a small loop: ask the model, run the tools it asks for, add the results, repeat until it answers. It has a step limit, handles unknown tools and bad JSON arguments, and keeps a trace of each run.
To check it, I asked the same question through this loop and through SupportAgent, and both made the same tool call. The app keeps using RubyLLM from here on, and the hand-written version stays as a documented lesson.
Tests use a fake client for the loop logic, plus one recorded run against the real model.