Issue Station
Sign In
Tools hereToolbox

claude-code - 💡(How to fix) Fix SSH sessions: "This session could not be found" for ~5 min after creation, then self-resolves [1 comments, 2 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#51638•Fetched 2026-04-22 07:56:53
View on GitHub
Comments
1
Participants
2
Timeline
4
Reactions
0
Author
evan-lovaltoevan-lovalto
Participants
evan-lovaltoevan-lovaltogithub-actions[bot]github-actions[bot]
Timeline (top)
labeled ×3commented ×1

When starting a new session in the desktop app with an SSH connection selected as the environment, the session does not appear in the session list until ~5 minutes after it's created. Local sessions are unaffected — they show up immediately. Started happening on or around 2026-04-20.

Error Message

Error Messages/Logs

Root Cause

When starting a new session in the desktop app with an SSH connection selected as the environment, the session does not appear in the session list until ~5 minutes after it's created. Local sessions are unaffected — they show up immediately. Started happening on or around 2026-04-20.

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?

Summary

When starting a new session in the desktop app with an SSH connection selected as the environment, the session does not appear in the session list until ~5 minutes after it's created. Local sessions are unaffected — they show up immediately. Started happening on or around 2026-04-20.

Environment

  • OS: Windows 11 (x64)
  • Claude Code Desktop version: <PASTE VERSION FROM Settings → About>
  • Remote host OS: Debian/Ubuntu (Hetzner VPS)
  • Remote ccd-cli version on host: 2.1.116

What Should Happen?

Expected

The new SSH session appears in the session list immediately, same as local sessions do.

Error Messages/Logs

Steps to Reproduce

Steps to reproduce

  1. Open the desktop app.
  2. Start a new session and select a pre-configured SSH connection as the environment.
  3. Observe the session list.

Claude Model

None

Is this a regression?

Yes, this worked in a previous version

Last Working Version

No response

Claude Code Version

2.1.116

Platform

Anthropic API

Operating System

Windows

Terminal/Shell

Other

Additional Information

Actual

The session takes roughly 5 minutes to appear. During that window it's fully running on the remote host but invisible in the app.

Evidence the session is live on the remote host during the lag

ps aux on the remote host while the session is "missing" in the app shows:

  • The per-user RPC daemon ~/.claude/remote/server --socket ~/.claude/remote/rpc.sock is running
  • A ~/.claude/remote/ccd-cli/2.1.116 ... --output-format stream-json ... process is running for the new session, with a fresh --resume <uuid> or freshly-spawned PID

So the session is being created and launched promptly on the remote host — the lag is in the desktop app's discovery / listing, not in remote session startup.

Impact

Breaks the feedback loop for SSH-based development. Multiple users on the same host (shared dev VPS) are all affected.

Notes

  • Local sessions on the same machine are not affected.
  • Issue reproduces across multiple Linux users on the same remote host.
  • Restarting the app does not shorten the delay.

extent analysis

TL;DR

The desktop app's session list update is delayed for SSH connections, likely due to an issue with the app's discovery mechanism.

Guidance

  • Verify that the ccd-cli version on the remote host is compatible with the Claude Code Desktop version, as the issue started happening recently.
  • Check the desktop app's configuration and logs for any errors or warnings related to SSH connections or session discovery.
  • Investigate the possibility of a network or firewall issue causing the delay in session discovery, as the session is created promptly on the remote host.
  • Test the app with a different SSH connection or remote host to isolate the issue.

Example

No code snippet is provided as the issue is related to the desktop app's behavior and not a specific code snippet.

Notes

The issue is specific to SSH connections and does not affect local sessions, suggesting that the problem lies in the app's handling of remote sessions. The fact that the session is created promptly on the remote host but takes time to appear in the app's session list suggests a discovery or synchronization issue.

Recommendation

Apply a workaround, such as manually refreshing the session list or using a different method to verify the session's existence, until the root cause of the issue is identified and fixed.

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#search optimization#API routing#API middleware#SSR setup

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 SSH sessions: "This session could not be found" for ~5 min after creation, then self-resolves [1 comments, 2 participants]