{"version":"2.1.290","anchor":"headless-turn-loop-crash-is-reported-with-a-sanitized-error","canonical_anchor":"headless-turn-loop-crash-is-reported-with-a-sanitized-error","heading":"Crash reports from headless sessions leave out the error message","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/headless-turn-loop-crash-is-reported-with-a-sanitized-error","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Crash reports from headless sessions leave out the error message\n\nWhen a headless session crashes, Claude Code now reports the error type or code but not the message, which may hold private data\n\n**Unclear.** When and where this crash report is produced is not known.\n\n**What**\n\nA headless session is one that runs without the interactive screen. When the loop that handles each turn in such a session crashes, Claude Code now reports the kind of error or its code, but leaves out the error message because it may hold private data. For a local session, the full message is still in the session's result.\n\n**Why**\n\nThis changes what logs and usage reports contain after a crash, keeping possibly private details out of them.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}