Repository navigation
fix(agent): exclude child workflow traces from model tool context - #9326
Closed
mzxchandra wants to merge 1 commit into
Closed
mzxchandra wants to merge 1 commit into
mzxchandra wants to merge 1 commit into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub. |
This branch was previously deployed
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.
Summary
Agent workflow tools return internal child execution spans alongside their final result. Passing those spans into the next model request can exhaust the context window or make secret projection withhold an otherwise small, usable result.
Remove executor-owned child trace metadata from the model-facing copy before secret projection, including canonical workflow tools selected through wire aliases and replayed tool responses. Preserve the raw response for traces, billing and execution records. Nested business fields and unrelated tools are unchanged; secret checks still apply to all functional output.
Type of Change
Testing
git diff --checkpass.Rollout verification
No schema or created-before default changes. Before/after deployed verification should use the same synthetic child workflow with a large intermediate payload and a tiny final output, checking model consumption, retained activity traces, secret redaction and unchanged child billing. A replay must not execute or charge the child again. Existing persisted chat history is not rewritten.
This fixes diagnostic transport, not oversized business results or the need for bounded/paged tool contracts.
Checklist