Remote connection disconnects too frequently for mobile/away-from-desk use

Problem

Claude Code's remote connection disconnects far too frequently. The promise of the remote/mobile experience is that you can leave your desk, go get coffee, work from your phone while out — but the connection timeout is too short to support that workflow.

Expected Behavior

If the product is designed for mobile/remote use, the connection should stay alive for at least a couple of hours without requiring constant interaction. Users need to be able to step away, run errands, or work from their phone without coming back to a disconnected session.

Actual Behavior

The connection drops regularly, requiring reconnection. This makes the "work from anywhere" experience unreliable and frustrating. Session context is lost on disconnect, which compounds the problem.

Impact

• Users can't trust the connection to stay alive while away from their desk
• Defeats the purpose of mobile/remote access
• Lost context on disconnect wastes time and money (especially for users running AI pipelines)

Suggestion

Extend the connection timeout significantly (2+ hours minimum) for remote sessions, or implement a more robust reconnection mechanism that preserves full session state.

---
Submitted on behalf of a user via Claude Code.