Remote Control: session on my PC becomes permanently unreachable (environment_deleted) after the desktop app was closed for a few hours

Status Open
Reported on v2.1.284
Maintainer reply None cached
Activity 1 comment · opened Oct 1, 2026

What happened
A session started from the Android app and running on my Windows PC (bridge environment, own worktree) stopped opening after I closed Claude on the PC and reopened it about 6 hours later. On reopen the PC registered a new bridge environment id, and the session stayed bound to the old one.

The session now reports:
last_init_error: error_kind=environment_deleted, error_type=not_found — "The environment this session was running on has been deleted; its state cannot be recovered."

I never deleted any environment. The row does not open and does not respond to messages.

Why I think this is a bug / bad UX

  • The message blames a deleted environment and says the state cannot be recovered, but the local transcript, branch and worktree were intact. claude --resume <local-id> from the worktree restored the whole conversation (as a new row).
  • The docs say sessions can be brought back for about four hours after the server stops. Past that window the old row is simply dead, with no hint on how to recover the conversation.

Expected
Reopening Claude on the same machine should re-attach its existing sessions, or at least the error should say the session can be resumed locally and how.

Details

  • Affected session: session_01Rh3wmDN8jok2tQ3Qu4rJwM
  • Lost environment: env_012bydCw1WUqjhK2tjVciu6K
  • Claude Code 2.1.284, Windows 11 Pro

View original on GitHub ↗

This issue has 1 comment on GitHub. Read the full discussion on GitHub ↗