{"version":"2.1.274","anchor":"startup-now-fails-gracefully-with-a-structured-result-when-c","canonical_anchor":"startup-now-fails-gracefully-with-a-structured-result-when-c","heading":"Startup now fails gracefully with a structured result when cwd is unavailable","tier":"internal","area":"Startup","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274\/e\/startup-now-fails-gracefully-with-a-structured-result-when-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.274","markdown":"### Startup now fails gracefully with a structured result when cwd is unavailable\n\nClaude Code now exits with a structured JSON error, not just a printed message, when its working directory is unavailable at startup\n\n**What**\n\nIf Claude Code starts up and finds that its current working directory is missing or unreadable, it now produces a structured result with the reason `cwd_unavailable` before exiting, instead of just printing an error message. This puts it in line with other startup failure reasons like `temp_dir_unusable` (temporary directory can't be used) and `shell_tool_missing` (required shell tool not found).\n\n**Why**\n\nA structured, machine-readable failure result makes it easier for scripts, integrations, or tools that launch Claude Code to detect exactly why startup failed and react accordingly, rather than having to parse free-form error text.\n\n- Area: Startup\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 1\/5"}