Resilient Sessions: Terminal That Survives Phone Sleep
We've solved one of the biggest pain points of using terminals from mobile devices. Phone sleep, Wi-Fi to cellular handoffs, brief signal loss — your terminal session now automatically recovers from all of these.
What Changed
Previously, when a WebSocket connection dropped, your terminal session was lost. Running a long task in Claude Code and putting your phone in your pocket meant losing everything in seconds. That's now a thing of the past.
This update introduces a 4-layer resilience architecture that automatically and seamlessly recovers your connection.
Key Features
- Server-side output buffer — Terminal output is preserved during disconnection and replayed on reconnect. When you open your screen, everything is right where you left it.
- Unlimited reconnection retries — Even if you pull your phone out 30 minutes later, it's still trying to reconnect.
- Instant wake detection — The moment your screen turns on, reconnection starts immediately without waiting for backoff timers.
- Visual connection feedback — A reconnecting overlay appears during recovery, and a "Reconnected" toast shows for 2 seconds once restored.
- Automatic tab recovery — If you had multiple tabs open, each one automatically reattaches to its original session.
Behavior by Plan
On paid plans, sessions stay alive on the server during disconnection, enabling full session restoration on reconnect.
- Starter — Sessions persist up to 30 minutes
- Pro — Sessions persist up to 60 minutes
- Team — Sessions persist up to 120 minutes
- Free — Fresh sessions auto-spawn on reconnect
In all cases, there's no confirmation dialog. It just works.
Real-World Recovery Times
- Wi-Fi → 5G handoff: 1-3 seconds
- 30-second screen lock: 2-3 seconds
- 5-minute sleep (paid plan): 2-3 seconds
All of this without tmux — pure application-layer resilience. A major experience improvement for anyone coding from their phone.