Repository navigation
keep the chat agent to one sub-agent per question, and quiet about how it works - #160
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
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.
The chat agent split simple questions into one sub-agent per account, told the person about each one it started, and passed on partial reports while the others were still running. The main agent's prompt and the delegate tool now say to hand one question to one sub-agent, which can look in several accounts, and to start more only for separate pieces of work. They also say to hold reports until the whole picture is in, unless one changes what the person should know now. While it waits, the agent says what it is looking into rather than how it works: no sub-agents, briefs or searches.
Open workspace in Conductor