[BUG] Desktop creates empty bridge-session records that appear as '(session) · 267 bytes' in /resume and dead '<host>-local-x-y' entries in the sidebar
Status Open
Reported on v2.1.269
Maintainer reply None cached
Activity 1 comment · opened Sep 12, 2026
Summary
The Desktop app creates a session record the moment a local Code session is opened (New / open folder), before anything is typed. If the user never sends a message, that record persists as:
- an empty 267-byte file in
~/.claude/projects/<project>/containing only{"type":"bridge-session","sessionId":"…","bridgeSessionId":"cse_…","lastSequenceNum":0,…}, which shows up in the terminal/resumepicker as a row titled(session)with267 bytesand no content; - an entry in the Desktop / claude.ai sidebar named
<hostname>-local-<word>-<word>that opens to "No messages yet" and, once the process is gone, shows "Remote Control disconnected" and cannot be resumed from Desktop at all.
Over a day, these outnumber real sessions. In the attached-style screenshot the Desktop sidebar has 12 such empty entries next to 8 real ones. Both toggles "Connect new sessions to Remote Control" (Desktop) and remote-control auto-connect (CLI, remoteEnabled: false) are OFF, so this is not the auto-connect feature.
Steps to reproduce
- In Desktop, Settings → Claude Code → "Connect new sessions to Remote Control" = off.
- Click New (local session) in Desktop, do not type anything, close it.
- In the terminal, run
/resumein that directory: a(session) · 267 bytesrow appears. catthat file: a singlebridge-sessionline.- The Desktop sidebar now shows a
<hostname>-local-xxx-yyyentry with "No messages yet".
Expected
- No session record until the first message is sent (or empty records are pruned automatically).
bridge-session-only files should never appear in the/resumepicker.- Empty / dead Desktop entries should be hidden or auto-archived rather than listed as sessions the user can neither open nor continue.
Environment
- Claude Code 2.1.269
- Claude Desktop 1.52386.3
- macOS 26.6.2 (Darwin 25.6.0)
This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗