Redact sensitive fields in terminal error results
Cluster 38073 · agent. Data as of
Nothing open on GitHub. Fix merged in #81686 on 8 Aug 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 #81686. 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 pull requests address redacting sensitive or security-relevant fields from terminal error results, exception outputs, and stderr logs. The work spans multiple attempts and related fixes targeting the terminal tool's error handling output.
Open issues0
Open PRs0
Fixes on record
-
#81675 fix(security): redact terminal exception results and ACP stderr logs (#77484)
files:
acp_adapter/entry.py,tests/acp_adapter/test_acp_logging_redaction.py,tests/tools/test_terminal_tool_exception_redaction.py,tools/terminal_tool.py -
#81686 fix(terminal-tool): redact remaining terminal error result fields (salvage #38074)
files:
tests/tools/test_terminal_error_redaction.py,tools/terminal_tool.py
1 PR closed without merging
From the close comments: merged via another change 1
-
#38074 fix(terminal-tool): redact terminal error result fields · merged via another change →
#81686,#81675
Closed issues · 1
- Closed#38073fix(terminal-tool): redact terminal error fields before tool results
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 Lab