claude-code - 💡(How to fix) Fix [BUG] 1.3036.0: CoWork sessions crash with "Claude Code process exited with code 1" on first message — terminal CLI works fine [4 comments, 5 participants]

Source: ~/Library/Logs/Claude/main.log

2026-04-16 13:23:29 [info] [LocalAgentModeSessionManager] Using system prompt (122259 chars, 1 segments) 2026-04-16 13:23:29 [info] [LocalAgentModeSessionManager] SDK version 2.1.111 will be used 2026-04-16 13:23:29 [info] Using Claude VM spawn function for session 2026-04-16 13:23:29 [info] [Lifecycle] Session local_XXXX: initializing → running 2026-04-16 13:23:30 [error] Session local_XXXX query error: Claude Code process exited with code 1 2026-04-16 13:23:30 [info] [Lifecycle] Session local_XXXX: running → idle 2026-04-16 13:23:30 [info] [CycleHealth] Unhealthy cycle: { session_id: 'local_XXXX', vm_instance_id: 'XXXX', model: 'claude-opus-4-6', cycle_health: 'unhealthy', had_first_response: false, seconds_to_outcome: 1, is_resume: true, unhealthy_reason: 'system_error', error_category: 'process_crashed', error_message: 'Claude Code process exited with code 1', transcript_size_bytes: 336477 }

TL;DR

The issue is likely due to a regression in the Desktop app's process-spawn path introduced in version 1.3036.0, causing the Claude Code process to exit with code 1, and a potential workaround could be to revert to a previous version of the Desktop app.

Guidance

• The error message "Claude Code process exited with code 1" suggests that the issue is related to the spawning of the Claude Code process, which works correctly when invoked directly from the terminal.
• The fact that the issue reproduces 100% of the time on new and resumed sessions, both inside and outside projects, indicates a systematic problem with the Desktop app's process-spawn path.
• Comparing the behavior with the terminal invocation of the Claude Code binary may help identify the root cause of the issue.
• Checking the main.log file for any additional error messages or clues may provide more insight into the problem.

Example

No code snippet is provided as the issue seems to be related to the Desktop app's configuration or binary rather than a specific code snippet.

Notes

The issue seems to be specific to the macOS (Apple Silicon) platform and the Claude Desktop 1.3036.0 (cf521c) version. The fact that it worked correctly in a previous version suggests a regression.

Recommendation

Apply workaround: Revert to a previous version of the Desktop app, if possible, until the issue is fixed in a future update, as the current version (1.3036.0) seems to have introduced a regression in the process-spawn path.