Bug Description
After successfully connecting to a Remote Control session (from the Claude mobile app or claude.ai/code), the session does not appear in the session list. If you navigate away from the session (e.g., swipe away, close the app, or press back), there is no way to reconnect to it.
Renaming the session also does not make it appear in the list.
Impact
This makes the Remote Control feature essentially unusable for anything beyond a single uninterrupted viewing session. Any accidental navigation away from the session means the connection is permanently lost.
Expected Behaviour
- The remote control session should appear in the session list like any other session
- Navigating away and back should allow reconnecting to the active remote session
- The session should remain accessible as long as the CLI side is still running
Environment
- OS: Windows 11 Pro 10.0.22631
- Claude Code: 2.1.55
- Client: Claude mobile app (iOS)
Related
This was discovered alongside #28401 (remote-control fails on npm installs). After applying the workaround for that issue, the connection works but session persistence does not.
Bug Description
After successfully connecting to a Remote Control session (from the Claude mobile app or claude.ai/code), the session does not appear in the session list. If you navigate away from the session (e.g., swipe away, close the app, or press back), there is no way to reconnect to it.
Renaming the session also does not make it appear in the list.
Impact
This makes the Remote Control feature essentially unusable for anything beyond a single uninterrupted viewing session. Any accidental navigation away from the session means the connection is permanently lost.
Expected Behaviour
Environment
Related
This was discovered alongside #28401 (remote-control fails on npm installs). After applying the workaround for that issue, the connection works but session persistence does not.