chore: add configuration points #30
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
L-u-k-e
changed the title
L-u-k-e
changed the title
* fix: fix more agent name/type checks * fix: make sure to trigger clear_message_history (#32)
L-u-k-e
added a commit
that referenced
this pull request
Jan 20, 2026
* fix: fix episodic memory ID bug * core: format * chore: add configuration points and fix a bunch of bugs (#30) * feat: make MAX_CHAINING_STEPS configurable * feat: make it possible to turn off meta agent chaining * fix: fix more agent name/type checks (#31) * fix: fix more agent name/type checks * fix: make sure to trigger clear_message_history (#32)
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.
PLEASE REVIEW BUT DO NOT MERGE!
I will merge it, once approved. (There's a few PR's that I want to coordinate merging).
Summary
It's now possible to configure
MAX_CHAINING_STEPSvia an environment variable (was previously a constant) and it's also now possible to turn off meta agent chaining entirely via a newCHAINING_FOR_META_AGENTenvironment variable