Claude Code Desktop SSH session unresponsive on macOS — ccd-cli exits with code 1
Resolved 💬 3 comments Opened Mar 23, 2026 by janekver Closed Mar 26, 2026
Preflight Checklist
- [x] I have searched existing issues and this hasn't been reported yet
- [x] This is a single bug report (please file separate reports for different bugs)
- [x] I am using the latest version of Claude Code
What's Wrong?
Claude Code Desktop app SSH session does not respond to messages. After sending any message, there is no response and no loading indicator. The session appears connected but is completely unresponsive.
What Should Happen?
SSH session should respond to messages normally, same as Claude Code CLI works in Terminal.
Error Messages/Logs
From ~/Library/Logs/Claude/main.log:
Session local_dffa50c2-b8ac-4149-b2d8-666510262abc query error: Claude Code process exited with code 1
[CCD CycleHealth] unhealthy cycle for local_dffa50c2 (1s, hadFirstResponse=false, reason=no_response)
From /root/.claude/remote/remote-server.log:
[process.Manager] Process started, PID=2956572, command=/root/.claude/remote/ccd-cli
[process.Manager] Process exited with code 1
Steps to Reproduce
- Add SSH connection in Claude Code Desktop (user@host, port 22, ed25519 key)
- Select remote working directory
- Send any message in the Code session
- No response, no loading indicator — session hangs
Claude Model
Sonnet (default)
Is this a regression?
Yes, this worked in a previous version
Last Working Version
_No response_
Claude Code Version
2.1.79
Platform
Anthropic API
Operating System
macOS
Terminal/Shell
Terminal.app (macOS)
Additional Information
- Claude Code CLI works fine in Terminal via SSH
- git is installed and working on remote server (/usr/bin/git, version 2.43.0)
- ccd-cli is present and executable (/root/.claude/remote/ccd-cli, version 2.1.78)
- Tried: reinstalling desktop app, clearing ~/Library/Application Support/Claude, restarting remote server processes, deleting and recreating SSH connection, reinstalling ccd-cli
- Nothing resolved the issue
This issue has 3 comments on GitHub. Read the full discussion on GitHub ↗