fix: Fix Agent Thread.fork() RecursionError caused by circular references in Message objects #299
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.
Fix Agent Thread.fork() RecursionError from circular references
Key Changes:
references in rigging Message objects
circular references
Added:
N/A
Changed:
instead of deepcopy() for each message
history, each fork should track its own)
When messages contained tool calls or parsed models with back-references,
Pydantic's deepcopy() would traverse circular object graphs in
pydantic_private attributes, causing infinite recursion. The
serialize/deserialize approach breaks these circular references and creates
truly independent Message instances.
Testing:
The forking example in
agents/how-to/build-multi-agent-workflows.mdxnowworks without RecursionError when exploring multiple branches in parallel.
Test code:
Generated Summary:
forkmethod to:This summary was generated with ❤️ by rigging