Running coding agents from a phone — what breaks, and what to do about it.
Yes, you can run Claude Code from your phone. A short map of every approach — the official app, CloudCLI, SSH + tmux, and PocketShell — each linking to the full deep dive.
Remote Control shows connected but nothing happens, or it drops after ~10 minutes — the network timeout and the research-preview limits explained, plus what to do instead.
Why closing your laptop or losing Wi-Fi kills a running Claude Code session, why `nohup` doesn't save it, and what actually keeps a TUI process alive across a dropped connection.
Four ways to find out Claude Code is done or stuck without staring at the terminal — from the built-in mobile push toggles to hook-based self-built alerts.
Yes, but it goes through something else first — the official app, an SSH client plus a multiplexer, or a remote desktop. What each path actually feels like.
Two known mobile issues in CloudCLI, their GitHub issue numbers and root causes, and where a self-hosted tmux-based architecture takes a different approach.
Every mobile option side by side, freshly re-verified — Cloud sessions, Remote Control, Dispatch, CloudCLI (self-hosted and Cloud), a bare SSH client, and PocketShell — plus three cases where you shouldn't self-host anything.
tmux and SSH already solve the hard part — the process survives. What's left is touch input, notifications, and network switching, and what people reach for to close each gap.