When your transcript leaves this machine, many error messages print redacted and log detail locally.
What's wrong with this entry?
When the session's transcript or output persists off this machine, many error messages now print without their detail and log the real detail locally instead. Slash-command dispatch, config key=value writes, MCP add/enable/reconnect, shell substitution in prompt commands, bash spawn failures, heap dumps, restarts and background session start all gained a redacted variant.
- Redacted messages carry the phrase "detail withheld on this connection".
- Config writes now classify their outcome as
kind: "save-failure"orkind: "refusal"rather than one generic failure. - Skill and command names and arguments are run through a sanitizer before being echoed into
<local-command-stdout>and warning text. - Which sessions count as persisting off-box is decided by a per-session predicate whose definition is minified in the bundle, so remote, desktop and cloud coverage is not readable from the build.
detail withheld on this connection
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.219
Credentials scrubbed from summarized error text
Both mention error handling
-
v2.1.228
API rejections are classified from a structured marker instead of prose alone
Both mention error
-
v2.1.228
Oversized media in a request is now its own rejection class
Both mention error