{"version":"2.1.248","anchor":"error-detail-is-withheld-when-a-session-s-output-leaves-the-","canonical_anchor":"error-detail-is-withheld-when-a-session-s-output-leaves-the-","heading":"Error detail is withheld when a session's output leaves the machine","tier":"notice","area":"Error Handling","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/error-detail-is-withheld-when-a-session-s-output-leaves-the-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Error detail is withheld when a session's output leaves the machine\n\nWhen your transcript leaves this machine, many error messages print redacted and log detail locally.\n\n**What**\n\nWhen 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.\n\n**Details**\n\n- Redacted messages carry the phrase \"detail withheld on this connection\".\n- Config writes now classify their outcome as `kind: \"save-failure\"` or `kind: \"refusal\"` rather than one generic failure.\n- Skill and command names and arguments are run through a sanitizer before being echoed into `<local-command-stdout>` and warning text.\n- 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.\n\n**Evidence**\n\n`detail withheld on this connection`\n\n- Area: Error Handling\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5"}