Claude Code Binary Crashes Immediately When Spawned from VS Code — Works Fine in Terminal.app

What this error means

error: An unknown error occurred (Unexpected) — exit code 1, crash ~8ms after spawn from VS Code parent process is a Claude Code failure pattern reported for developers trying to fix claude code binary crashing on startup when run from vs code integrated terminal or extension, while working fine in standalone terminal.app. Based on the imported evidence, treat this as a tool-specific troubleshooting page rather than a generic API error.

Why this happens

GitHub Issue #60436 in anthropics/claude-code, opened May 19 2026 (yesterday). Very detailed report showing v2.1.144 darwin-arm64 binary crashes immediately in any VS Code context. Extensively tested — ruled out env vars, TTY differences, binary corruption, auth issues. Crash tied specifically to VS Code Electron process tree. Claude Max subscriber with Opus model affected. High commercial value as Claude Max is a paid tier. Category mapped to AI Coding Tools.

Common causes

• GitHub Issue #60436 in anthropics/claude-code, opened May 19 2026 (yesterday). Very detailed report showing v2.1.144 darwin-arm64 binary crashes immediately in any VS Code context. Extensively tested — ruled out env vars, TTY differences, binary corruption, auth issues. Crash tied specifically to VS Code Electron process tree. Claude Max subscriber with Opus model affected. High commercial value as Claude Max is a paid tier. Category mapped to AI Coding Tools.

Quick fixes

1. Confirm the exact error signature matches error: An unknown error occurred (Unexpected) — exit code 1, crash ~8ms after spawn from VS Code parent process.
2. Check the Claude Code account, local tool state, and provider configuration involved in the failing workflow.
3. Reduce request pressure, check quota or plan limits, and retry with backoff instead of immediate repeated requests.

Platform/tool-specific checks

• Verify the command, editor, extension, or API client that produced the error.
• Compare local settings with CI, deployment, or editor-level settings when the error appears in only one environment.
• Avoid deleting credentials, local model data, or project settings until the failing scope is clear.

Step-by-step troubleshooting

1. Capture the exact error message and the command, editor action, or request that triggered it.
2. Check whether the failure is account/auth, quota/rate, model/provider, local runtime, or deployment configuration.
3. Review the source evidence below and compare it with your environment.
4. Apply one change at a time and rerun the smallest failing action.
5. Keep the working fix documented for the team or deployment environment.

How to prevent it

• Keep provider/tool configuration documented.
• Record non-secret diagnostics such as tool version, provider name, model name, and command path.
• Add a lightweight check before CI or production workflows depend on the tool.

Sources checked

• https://github.com/anthropics/claude-code/issues/60436

Evidence note: GitHub Issue #60436 in anthropics/claude-code, opened May 19 2026 (yesterday). Very detailed report showing v2.1.144 darwin-arm64 binary crashes immediately in any VS Code context. Extensively tested — ruled out env vars, TTY differences, binary corruption, auth issues. Crash tied specifically to VS Code Electron process tree. Claude Max subscriber with Opus model affected. High commercial value as Claude Max is a paid tier. Category mapped to AI Coding Tools.

Related errors

• AI Coding Tools

FAQ

What should I check first?

Start with the exact error: An unknown error occurred (Unexpected) — exit code 1, crash ~8ms after spawn from VS Code parent process text and the smallest action that reproduces it.

Can I ignore this error?

No. Treat it as a failed Claude Code workflow until the root cause is understood.

Is this guaranteed to have one fix?

No. The imported evidence supports the troubleshooting path above, but tool behavior can vary by account, plan, version, provider, and local configuration.

How do I know the fix worked?

Rerun the same command, editor action, or request. The fix is working when that action completes without error: An unknown error occurred (Unexpected) — exit code 1, crash ~8ms after spawn from VS Code parent process.