Remote Control: Multiple stability and usability issues make autonomous use unreliable

Summary

Claude Code's remote control feature is marketed as enabling autonomous use ("go get coffee"), but multiple issues make it unreliable for users who need to step away from their computer and manage sessions from a phone or tablet.

Issues

1. No auto-compaction warning

When auto-compaction is about to happen, there is no notification to the user. Remote control users (on phone/tablet) have no way to see it coming -- the UI just spins with no indication of what's happening. Users should be warned before compaction occurs so they can prepare or save context.

2. No escape button on remote control

There is no way to interrupt or cancel operations when using remote control. If Claude is stuck in a long operation or doing something unwanted, the remote user has no way to stop it.

3. Remote control connection drops repeatedly

The connection is unstable and drops frequently during normal use. This directly contradicts the "go get coffee" autonomous workflow -- you can't step away if the connection dies every few minutes.

4. No way to reconnect through Claude

When remote control drops, the only way to get back to the terminal is through a third-party tool (e.g., RustDesk, TeamViewer). There should be a way to request a new remote control connection from within Claude itself, or an automatic reconnection mechanism.

5. No direct terminal access through remote control

Users should be able to connect directly to the terminal session, not just the chat interface. This would allow recovery from connection issues without third-party tools.

6. Remote control sends duplicate messages

When the connection is unstable, user messages get sent to Claude multiple times. This wastes context window space and causes confusion, as Claude tries to respond to the same message repeatedly.

Impact

These issues combined mean that remote control is not usable for its intended purpose. Users who rely on Claude Code for long-running autonomous tasks (pipeline runs, code generation loops, etc.) cannot reliably manage sessions remotely. Every connection drop requires physical access to the computer or a third-party remote desktop tool, which defeats the purpose of the feature.

Environment

• OS: Windows 11
• Claude Code: latest
• Remote control used from: iPhone/mobile browser