Your agents, on your phone: why Ember's mobile app talks to your own computer
In shortEmber's phone app connects to Ember running on your own computer, not to a cloud copy of your code. It shows what needs you, ranked, with one button each, and every tap is checked against the branch as it is at that moment.
Why not a cloud agent
Our agents run on our own machines, in our own checkouts, with our own tools, credentials and local services. We did not want a second environment in the cloud to keep in step with that. We wanted to walk away from the desk and still unblock the agents already running there.
So one Ember window runs a small hub on 127.0.0.1, every other window joins it, and the phone reaches that hub the way you choose: Tailscale, your local network, ngrok, a Cloudflare tunnel or your own URL.
Now comes first
The app opens on Now: how many things need you across every Ember window, as a card each, in the Dashboard's order. Each card has one big button, the branch's next step. When a chat asks one question with a few short choices, the card shows the choices as buttons.
From the phone you can answer a question, approve a command, merge a pull request, open a pull request, remove a merged branch's worktree, stop an agent, continue a chat that was interrupted, and start a new chat. A chat on the phone is its transcript, condensed, with the send button where your thumb expects it.
Questions are asked where you are
An early rule we set: a question raised by something you did on the phone is asked on the phone, never as a dialog on a desktop nobody is sitting at. Merging asks once on the phone after reading the pull request again. Removing a worktree asks on the phone after naming what is in it.
Ember also checks each tap against the branch as it is right now. If the branch changed since your phone last showed it, nothing happens and the phone says so. An answer counts only for the question the chat is asking at that moment.
What pairing protects
The hub listens on your computer only. A device pairs with a 6-digit code that lasts 5 minutes, with a limited number of tries. Each device then gets its own token; Ember keeps only a hash of it, and you can revoke a device at any time.
Some things are never reachable from the phone: Ember's settings, sign-in, terminals and rule edits. Window screenshots are off by default, because taking them needs a debugging port open on your computer, and we would rather explain that than turn it on quietly.