prevent literal truncation markers corrupting tool outputs
Cluster 83714 · agent. Data as of
Nothing open on GitHub. Fix merged in #116169 on 19 Sep 2026. Check it covers your case.
The short answer
- Known?
- Yes. 4 related items grouped here, 1 issue already closed.
- Fix event
- A fix was merged to main in PR #116169. Check it covers your case. No release data is tracked.
- Tracker
- The maintainers' tracker marks this
unresolved. That is separate from the fix event. - Still open
- Nothing open on GitHub.
These issues and fixes address a bug where truncation placeholder text (e.g., '...[truncated]') was being emitted literally into tool call arguments, file writes, and compacted context replays instead of being handled transparently. The work focuses on stopping these markers from propagating into actual content.
Open issues0
Open PRs0
Fixes on record
-
#116169 fix(context-compressor): replayed tool-call args stop carrying a marker models copy (#83714, salvage #83843)
files:
agent/context_compressor.py,contributors/emails/[redacted:email],tests/agent/test_context_compressor.py
2 PRs closed without merging
From the close comments: done elsewhere 1 · superseded by another PR 1
Closed issues · 1
- Closed#83714[Bug]: patch tool truncates new_string content with literal '...[truncated]' text
How this cluster was grouped
-
Link evidence (
structural links throughout): every member is connected by structural evidence: shared changed files, or a closing/superseded reference. -
Pairwise link density
0.50: the share of item pairs that carry a link, counting a structural link in full and a relevance-only link at 0.36.1.00means every pair is linked.
Pick up a Lab task
Check whether a fix covers the open issues here, with your own agent. Bring back evidence for maintainers.
Open the LabAt a glance
- Subsystem
- agent
- Merged PRs
- #116169
- Closed issues
- 1
- Attempts
- 2 PRs closed without merging
- Fix link checked
- 19 Sep 2026