TokenFuse's gateway enforces the budget in the request path your agent runs on. Pocket is the control that lives outside that path: it watches every run's burn rate live and pulls the kill switch with a command signed by hardware the agent's host never touches. iOS · watchOS · no Android, no web: the whole security story rests on the Secure Enclave, a chip only Apple ships.
This is a simulation, but it replays a shape the app is built for: a run drifts from baseline to 2.4x its burn rate, crosses a budget, and gets killed from an Apple Watch before anyone opens a laptop. The signature that authorizes the kill never leaves the Secure Enclave; the gateway only has to trust the result.
An interactive design mock of the iPhone and Watch apps, running here as a web page. Five iPhone screens and five Watch screens, all live: the burn ticks, the segmented control filters, the kill is a breaker you drag to arm, and a kill from the wrist updates the phone. Drive it with the steps, the tab bar, or the Watch switch.
The app pairs to TokenFuse Cloud, not to the gateway your agent talks to. A kill or a budget change is signed on-device by the Secure Enclave, sent to Cloud, and pushed out to every gateway in the fleet from there. The request path and the kill path never share a wire.
Mint under budget, amber warming, ember at the cap. The run list, the Dynamic Island, and the watch face all read the fuse the same way, so nothing needs translating between screens.
Every kill and every budget change is signed on-device by the Secure Enclave. A fully compromised server cannot forge that order, and it cannot block it from reaching your side either.
The phone talks to TokenFuse Cloud, not through the gateway or the agent's own network path. If the request path is exactly what's compromised, the kill still lands.
Every run with its spend, its burn rate in dollars per minute, and how close it sits to a budget break, sorted hottest first, red once it's over.
Scan a QR code against your own Cloud plane. The app generates a key inside the Secure Enclave on the spot; the key never leaves it, not even to the app.
No screenshots dressed up as a product. The interactive design mockups are public and run live at taipanbox.github.io/tokenfuse-mobile.
PagerDuty tells a human there's a fire. SSH lets a human put it out, if the human, the laptop, and the VPN all cooperate at 2am. Pocket skips the coordination problem: the hand that can pull the Breaker is already on your wrist.
| PagerDuty alert | SSH from a laptop | ||
|---|---|---|---|
| Time to stop a runaway | Seconds, from a wrist | Minutes, if someone's awake | Minutes, if the laptop is near and the VPN cooperates |
| Works when the server path is compromised | Yes, out of band | Alert maybe arrives | No, you're in the same path |
| Can spend be cut by accident | Hold-to-confirm, cost-bound | n/a | One wrong kill -9 |
| Audit trail | Every kill logged as an incident | Alert history | Shell history on a laptop |
Pocket is the human end of TokenFuse: the gateway enforces the budget in the request path, Pocket lets you watch it happen and pull the kill switch from somewhere else entirely. Every kill lands as an incident on the same event bus the rest of the Platform reads. What actually gets enforced was decided upstream, by Wardryx and the budgets you set. Pocket doesn't make that call; it gives you a fast, honest way to see it and override it.
Clone the repo and run the SwiftUI app from Xcode against your own Cloud plane; or poke the live interactive mockups first: taipanbox.github.io/tokenfuse-mobile