{"version":"2.1.242","anchor":"crash-reports-hold-back-messages-from-errors-thrown-outside-","canonical_anchor":"crash-reports-hold-back-messages-from-errors-thrown-outside-","heading":"Crash reports hold back messages from errors thrown outside Claude Code","tier":"notice","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242\/e\/crash-reports-hold-back-messages-from-errors-thrown-outside-","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.242","markdown":"### Crash reports hold back messages from errors thrown outside Claude Code\n\nCrash reports replace messages from errors thrown entirely outside Claude Code, so your data stays out.\n\n**What**\n\nWhen every frame of a crash comes from somewhere other than Claude Code's own code (native frames, dependencies, Node or Bun internals) and the error carries no code, the message is replaced with a fixed phrase naming the kind of error, so text that might contain your data is not sent.\n\n**Details**\n\n- Applies always in the error report builder; stack frames, the fingerprint and the tags block (platform, OS release, entry point, model, session kind, renderer mode) are unchanged.\n\n**Evidence**\n\n`thrown outside the Claude Code bundle`\n\n- Area: Telemetry\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}