Repository navigation
Reuse named agents within recipe flows - #96
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.
Recipes now reuse the existing instance when they invoke the same named agent again within a flow. Each agent's first invocation still uses
spawn_agentwithfork_turns="none", and every invocation receives its specified inputs.Update invocation wording and diagnosis freshness to match. Same-name fullstack calls run sequentially. Keep the rules at their existing entry points and bump
package.jsonfrom1.6.0to1.7.0.Validation:
npm test(23 passed), agent TOML parsing, unchanged quoted input/result contracts and required skills, andgit diff --check.node bin/cli.js --versionreturns1.7.0.