[Bug] Remote Control: orphaned server-mode hosts cannot be removed and show false "Connected" state

Status Open
Reported on v2.1.220
Maintainer reply None cached
Activity 0 comments · opened Jul 29, 2026

Bug Description
Remote Control: orphaned server-mode hosts cannot be removed, and show a false "Connected" state Environment: Windows 11 Pro 26100, Claude Desktop 1.22209.0, Claude Code CLI 2.1.220 (Desktop bundles claude-code 2.1.209). Plan: Max. Repro: 1. Run claude remote-control --name "X" --spawn worktree --permission-mode bypassPermissions from two directories. 2. Close both terminals. The local processes die, as documented under Limitations. 3. Reboot the machine. Bug 1 — orphaned hosts, no way to remove them. Both hosts remain listed in the environment picker under "Remote Control" ("D: / KostyaPC" and "Second Brain / KostyaPC", each "0 of 32"). They survive terminal close and a full reboot, because the registration is server-side. There is no way to delete them: - no CLI command in the CLI reference - right-clicking the entry in the Desktop picker only yields the generic Electron text menu (Copy / Select All) - the docs' Troubleshooting section has no entry for this case The only documented timeout is the ~10-minute network-outage one, which does not apply to a process that has already exited. Bug 2 — false "Connected" state, then a 5-minute silent hang. Selecting one of these dead hosts and sending a task shows "Connected to KostyaPC via remote control" with a live status dot. The task then spins with no feedback for about five minutes before finally showing "Remote Control disconnected / The bridged Claude Code process stopped responding mid-turn". Expected: the picker should not present a host with no live process as connectable, and the failure should surface immediately. The suggested remedy in that error ("you may need to run /login") is misleading here — authentication is fine, the bridged process simply no longer exists. Suggested fixes: a delete/disconnect action on entries in the picker, a server-side TTL for hosts with no live process, and an immediate error instead of a five-minute wait.

Environment Info

  • Platform: win32
  • Terminal: null
  • Version: 2.1.220
  • Feedback ID: 88a1169d-77ba-4c85-8c9c-289e32470b11

Errors

[]

View original on GitHub ↗