claude-code - 💡(How to fix) Fix [Bug] Desktop app fails to launch Claude Code process with exit code 1 [1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
anthropics/claude-code#54258Fetched 2026-04-29 06:32:06
View on GitHub
Comments
0
Participants
1
Timeline
4
Reactions
0
Participants
Timeline (top)
labeled ×3cross-referenced ×1

Code Example

[]
RAW_BUFFERClick to expand / collapse

Bug Description Claude Code in the desktop app (v1.4758.0) fails with "Claude Code process exited with code 1" every time I start a new session from the Code tab. The app uses its bundled binary at /Users/alexandra/Library/Application Support/Claude/claude-code/2.1.119/claude.app/Contents/MacOS/claude. Steps already completed: fresh CLI install (2.1.121), login via Terminal, PATH fix, sign out/in from the app, full restart. The CLI works perfectly from Terminal - /doctor shows no issues. The bundled binary also responds correctly when called directly from Terminal. The crash happens only when the desktop app launches a session. OS: macOS, MacBook Air (darwin-arm64). Plan: Pro personal.

Environment Info

  • Platform: darwin
  • Terminal: Apple_Terminal
  • Version: 2.1.121
  • Feedback ID: 2cf72a87-b8ae-48a0-aecb-4abe1e192bd0

Errors

[]

extent analysis

TL;DR

The issue may be related to the interaction between the desktop app and the bundled binary, and verifying the environment variables and permissions when launching a new session could help identify the cause.

Guidance

  • Check the environment variables set by the desktop app when launching a new session to ensure they match the ones set when running the CLI from Terminal.
  • Verify the permissions of the bundled binary and its dependencies to ensure they are correctly set and accessible by the desktop app.
  • Compare the command line arguments used by the desktop app to launch the bundled binary with those used when running the CLI from Terminal to identify any differences.
  • Consider running the desktop app from the command line with increased verbosity or debugging flags to gather more information about the crash.

Notes

The issue seems to be specific to the desktop app's interaction with the bundled binary, and the fact that the CLI works correctly from Terminal suggests that the problem may not be with the binary itself, but rather with how it is being launched by the app.

Recommendation

Apply workaround: Try running the desktop app with a clean environment or with explicitly set environment variables to see if it makes a difference, as this may help identify if the issue is related to the environment or the app's configuration.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING