tokenstat
tokenstat

iPhone and iPad · In review

Your machines, from wherever you are

The agent you left running does not care that you went to lunch. It finishes, or it stalls, or it stops to ask you something, and until now finding out meant going back to the desk. This puts the machine itself in your hand, close enough to answer the question and let the work carry on.

App StoreIn reviewGoogle PlayIn build

No date to promise. The macOS app and the CLI ship today, and everything the phone shows is already in both. Get those instead.

tokenstat on iPhone: today and this week, the activity heatmap, and plan limits per harness
HomeToday, this week, the heatmap, and plan limits per harness.
tokenstat on iPhone: one day opened up, with every model that produced its tokens
A dayHold a day to see every model that produced its tokens.
tokenstat on iPhone: the hosts on an account, their folders, and every running session
WorkspacesEvery host on the account, its folders, and what is running.
tokenstat on iPhone: a live agent session attached in a terminal, with the keyboard up
SessionAttach to a live agent and type into it, keyboard up.

Captures from the iPhone build v0.6.7 · 20 August 2026, the same release the Mac app shipped on. Screens change between builds; the app is right when it disagrees with this page.

Why it matters

An agent does not stop working when you leave

That is the whole problem the phone solves. You start something long, close the lid, and for the next three hours the only way to know whether it finished, stalled, or is asking you a question is to go back to the desk. Now you look.

Answer the question it is stuck on, from the sofa

Attach to a running agent in a real terminal and type into it. A prompt it has been waiting on for an hour takes ten seconds to clear, and the work carries on without you walking back. The keyboard row has shift and back-tab, because a phone keyboard has neither and a terminal needs both.

Know before you start whether you can afford to

Today, this week, the full year, and how much of each plan window is left. Worth checking before you kick off a long run from a train, and worth knowing when something has been running since breakfast.

Read the change, not just the notification

Open the folder it has been working in, read the diff, and see what it actually did. Edit the one line that is wrong in a real editor, keep a note on the folder, and move the card. Deciding whether to keep the work does not have to wait for you to get home.

Reach the dev server you left running

Forward a port from any connected machine and open it in the phone's browser. The thing running on your desk is a tap away, which is the difference between showing someone what you built and describing it.

Start it from anywhere

The work can begin before you get back

Think of the job on the way home and it can be running by the time you arrive. Kick off an automation or a workflow from the phone, watch its output land, and let the budget stop it rather than finding out what it cost afterwards. Your Mac runs it, so nothing depends on the phone staying awake or the lid staying open.

With a keyboard, the iPad is close enough to the desk to work from: the same folder tree in a real sidebar, the same shortcuts, and a workspace laid out for the screen instead of a phone layout pulled wide.

The connection

End to end encrypted, including from us

Reaching your Mac from a phone means the connection has to pass through a server in the middle. Ours is a relay and nothing more: what you type, what comes back, and any file you open are encrypted on one of your devices and decrypted on the other, so the server in between is passing along something it cannot read. We could not show you your own session if you asked us to.

The keys are short-lived and renewed on their own, and the connection can only reach services running on that machine, never the rest of the network it sits on.

Remote reach is a paid tier. Everything local, on every platform, is free and always will be. See pricing.