{"version":"2.1.321","anchor":"exit-reasons-are-recorded-on-print-mode-and-startup-failures","canonical_anchor":"exit-reasons-are-recorded-on-print-mode-and-startup-failures","heading":"Print mode and startup failures now record why Claude Code exited","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/exit-reasons-are-recorded-on-print-mode-and-startup-failures","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Print mode and startup failures now record why Claude Code exited\n\nWhen Claude Code exits early in print mode or at startup, it now records a reason, not only an exit code\n\n**What**\n\nPrint mode runs Claude Code once without the interactive screen. Exits from print mode now carry a reason, not only a number. Reasons include:\n\n- `no_input`\n\n- `invalid_flags`\n\n- `rewind_files_failed`\n\n- `last_turn_failed`\n\n- `writes_lost_to_full_disk`\n\n- `auto_mode_unchecked_refusals`\n\nWhen Claude Code cannot change into a worktree folder at startup, the error text is now recorded too. A worktree is a separate checkout of a repository in another folder.\n\n**Why**\n\nThis is for diagnosing failures. What you see when Claude Code exits does not change.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}