add cross_service flag to trace tool#256
Merged
Merged
Conversation
Agents expected trace to cross service boundaries but couldn't control it. Add `cross_service: bool = False` parameter — when True, BFS continues through HTTP_CALLS/ASYNC_CALLS boundaries into downstream services. EXPOSES is auto-added as scaffolding (exempt from fan_out_cap) so Route -> Handler is followed automatically. Default preserves existing boundary-stop behavior. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
HumanBean17
added a commit
that referenced
this pull request
May 31, 2026
…256) Agents expected trace to cross service boundaries but couldn't control it. Add `cross_service: bool = False` parameter — when True, BFS continues through HTTP_CALLS/ASYNC_CALLS boundaries into downstream services. EXPOSES is auto-added as scaffolding (exempt from fan_out_cap) so Route -> Handler is followed automatically. Default preserves existing boundary-stop behavior. Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
This was referenced May 31, 2026
Open
HumanBean17
added a commit
that referenced
this pull request
May 31, 2026
…256) Agents expected trace to cross service boundaries but couldn't control it. Add `cross_service: bool = False` parameter — when True, BFS continues through HTTP_CALLS/ASYNC_CALLS boundaries into downstream services. EXPOSES is auto-added as scaffolding (exempt from fan_out_cap) so Route -> Handler is followed automatically. Default preserves existing boundary-stop behavior. Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>
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.
Summary
cross_service: bool = Falseparameter totracetool — when True, BFS continues through HTTP_CALLS/ASYNC_CALLS boundaries into downstream servicesfan_out_cap) so Route → Handler is followed automatically in downstream servicesFalse) preserves existing boundary-stop behavior with no regressionContext
During battle testing, agents expected
traceto cross service boundaries seamlessly but had no way to control it. A description wouldn't fix this — the agent needs to control the behavior, not just read about it. The boolean flag is the smallest change that solves the problem.Changes
mcp_trace.py— new param, effective scaffolding set, frontier continues through boundaries when enabledserver.py— register param, update description, wire throughmcp_hints.py— emit lightweight advisory instead of action hint when seamlesstests/test_mcp_trace.py— 4 new tests (seamless HTTP, async, budget, scaffolding exemption)skills/explore-codebase/SKILL.md— updated decision table and tool referenceTest plan
ruff checkclean on all modified files🤖 Generated with Claude Code