Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix [BUG] Code tab: local sessions crash immediately (exit code 1) — ccd_session/ccd_directory IPC failure [3 comments, 3 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#53281•Fetched 2026-04-26 05:19:43
View on GitHub
Comments
3
Participants
3
Timeline
12
Reactions
0
Author
ib-miaib-mia
Participants
Ed4nEd4ngithub-actions[bot]github-actions[bot]ib-miaib-mia
Timeline (top)
labeled ×6commented ×3cross-referenced ×3

Error Message

Session <blob> query error: Claude Code process exited with code 1 interaction without an error

Error Messages/Logs

Root Cause

Root cause identified The desktop app passes two internal MCP servers — ccd_session and ccd_directory — to the binary on startup. The binary tries to connect to these IPC channels, fails immediately, and exits with code 1. From main.log:

RAW_BUFFERClick to expand / collapse

Preflight Checklist

  • I have searched existing issues and this hasn't been reported yet
  • This is a single bug report (please file separate reports for different bugs)
  • I am using the latest version of Claude Code

What's Wrong?

Environment

  • Claude desktop app: v1.4758.0
  • Claude Code binary: 2.1.119
  • macOS: 14.1 (Darwin 24.1.0)

What happens
Every session started from the Code tab crashes in under 1 second with "Claude Code process exited with code 1", no output. Has been broken since at least
April 19, 2026. Chat and Cowork (VM) sessions work fine.

Root cause identified The desktop app passes two internal MCP servers — ccd_session and ccd_directory — to the binary on startup. The binary tries to connect to these IPC channels, fails immediately, and exits with code 1. From main.log:

[CCD] [replaceRemoteMcpServers] Calling SDK with 9 total servers { serverNames: ['ClickUp', 'Google Drive', 'Slack', 'Claude in Chrome',
'mcp-registry', 'Claude Preview', 'ccd_session',
'ccd_directory', 'scheduled-tasks']
}
Session <blob> query error: Claude Code process exited with code 1
[CCD CycleHealth] unhealthy cycle (0s, hadFirstResponse=false,
reason=no_response)

After the crash, subsequent IPC calls fail:
[account] Account details not yet available, waiting for IPC... [account] User logged out during IPC wait, stopping early

What confirms it's the IPC, not the binary Running the binary manually with any combination of flags (including
--permission-mode acceptEdits, --setting-sources=user,project,local,
--plugin-dir, from the worktree directory) works perfectly. The binary only
crashes when the desktop app spawns it — the only untestable difference is the ccd_session/ccd_directory socket arguments passed internally.

What Should Happen?

interaction without an error

Error Messages/Logs

Steps to Reproduce

Steps to reproduce

  1. Open Claude desktop app
  2. Click the Code tab (</>)
  3. Open or create any session in any folder
  4. Session immediately shows "Claude Code process exited with code 1"

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.119

Platform

Anthropic API

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

No response

extent analysis

TL;DR

The issue is likely caused by the desktop app passing internal MCP servers to the binary on startup, which fails to connect to these IPC channels, resulting in the binary exiting with code 1.

Guidance

  • Verify that the ccd_session and ccd_directory servers are properly configured and accessible.
  • Check the main.log for any error messages related to the IPC connection.
  • Try running the binary manually with the same flags and settings as the desktop app to isolate the issue.
  • Investigate the difference in behavior between running the binary manually and through the desktop app, focusing on the ccd_session and ccd_directory socket arguments.

Notes

The issue seems to be related to the interaction between the desktop app and the binary, specifically with the IPC channels. The fact that running the binary manually works perfectly suggests that the issue is not with the binary itself, but with how it is being spawned by the desktop app.

Recommendation

Apply workaround: temporarily remove or disable the ccd_session and ccd_directory servers from the desktop app's startup configuration to see if it resolves the issue, as this will help determine if the problem is indeed related to these IPC channels.

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…
#api#runtime error#dependency conflict#environment setup#docker error

Still need to ship something?

×6

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

Back to top recommendations

TRENDING

claude-code - 💡(How to fix) Fix [BUG] Code tab: local sessions crash immediately (exit code 1) — ccd_session/ccd_directory IPC failure [3 comments, 3 participants]