The whole promise of running agents in parallel is that you stop being the bottleneck. Then you dispatch three sessions, stand up to make coffee, and realize the promise has a radius of about two meters: the moment you leave the desk, you're blind. Did the refactor finish? Is an agent sitting on a permission prompt, burning nothing but your patience?
So we built the thing that was obviously missing: a phone app that is a real window onto your desktop's agents. Not a dashboard of stale summaries — the actual sessions, streaming live, with enough control to keep work moving from wherever you are.
What you can do from the phone
- Watch sessions as they run. Every project, every session, transcripts streaming token-for-token with the same rendering discipline as the desktop — and an offline cache, so the app opens instantly to the last known state.
- Unblock agents that need you. A "needs you" badge means a session is waiting on an answer. Open it, reply, and the agent on your Mac resumes. You can send prompts, attach images, switch models, and adjust permission modes mid-session — with a context gauge showing how full the session's window is.
- Review the diff from the couch. The per-session diff review comes along, comments included — and a comment you leave becomes the agent's next prompt, the same review loop the desktop runs.
- Start new work. New session, any project, any of your agents. The Mac does the spawning; the phone is where the idea happened to strike.
Notifications that respect you
Push is where remote tools usually turn obnoxious, so the rules are strict: a push fires when a turn finishes or an agent needs you — never for progress. If you saw the result on your desktop, the phone stays silent (there's a short grace window, and "seen" syncs across every device, so nothing nags you twice). Tapping a push deep-opens that exact session. And if the desktop dies, the app says so plainly instead of dressing up stale data as live — a dead bridge looks dead.
The architecture is the privacy policy
hang4r's founding constraint doesn't bend for mobile: your code and your subscriptions never leave your machine. The desktop app remains the only thing that talks to the CLIs. The phone is a remote surface, and between the two sits the smallest possible relay — a Cloudflare Worker that shuttles frames it cannot read:
-
End-to-end encrypted. Pairing happens by scanning a QR code (or a
hang4r://link) shown by your desktop; the two devices exchange keys directly and every frame after that is ciphertext to the relay. No account, no password, nothing to breach. - Nothing stored in the cloud. Transcripts, diffs, and code live on your Mac and your phone's local cache. The relay holds a mailbox, not a database.
- The desktop is the source of truth. The phone can't drive a session behind the desktop's back — every action flows through the same session manager, which is what keeps two frontends from corrupting one CLI conversation.
The fine print
iOS is in TestFlight today, iPhone and iPad (split view and all); an Android build exists for the adventurous but doesn't get push yet. Your Mac has to be awake and running hang4r — the phone is a window, not a second computer, and that's the design: the machine you trusted with your code and your subscriptions is still the only one doing the work.