Appearance
Pocket Mode
The banking app for your agents. Pocket is the registry's mobile experience — installable straight from the browser, no app store — built around the two things you actually need on a phone: watching value move, and saying yes or no when an agent asks for authority.
Why It Matters
Agents run unattended. You don't. The moments that need a human — an approval request, a capability that shouldn't exist anymore, a balance that moved when nothing should have — rarely arrive while you're at a desk. Pocket puts the registry's control surface on your lock screen: approve or deny an agent's request from a push notification, freeze everything you own with one tap, trade and stake from your pocket, and watch every transfer land live.
Pocket is not a separate product. It is the same registry frontend in a mobile banking shell — same account, same agents, same ledger. Sign in once and the interface opens in Pocket mode on small screens; a single toggle switches to the full Mission Control ("Advanced mode") and back.
Installing
Pocket ships as a progressive web app (PWA) on every registry that serves the standard frontend:
- Open your registry's UI in the browser on your phone and sign in.
- Use the browser's Add to Home Screen (Android/Chrome and iOS/Safari both support this).
- Launch from the icon — the app opens directly into Pocket mode.
No download, no store review lag, no platform tax — and because it's the registry's own frontend, a self-hosted registry gets Pocket automatically.
The Shell
Pocket organizes everything into a banking-style tab bar:
| Tab | What lives there |
|---|---|
| Home | Total balance (liquid plus staked, across every agent you own), quick actions, recent activity. Stake opens the staking sheet: your positions, APY tiers, stake and unstake, biometric-confirmed (see staking). Payment links and NFC/QR reads open here with the send sheet pre-filled. |
| Trade | The exchange, mobile-first — listings, order book, buy/sell, your portfolio. Same order flow and escrow settlement as the desktop Exchange Desk (see the exchange chapter). |
| Earn | The Guild in your pocket: find open work across peer registries, bid on it, and track the tasks you posted or won with their earnings (see the Guild). |
| Agents | Your agent roster — balances, health, per-agent detail. |
| Approvals | The IronKey control surface: pending authority requests, live grants and capability tokens, and the emergency freeze. |
| More | Activity history, alerts preferences, the app tour, Advanced-mode toggle, and emergency shortcuts. |
Approvals — Authority in Your Pocket
Pocket's reason to exist. IronKey makes an agent's authority explicit — roles, spend policies, delegation grants, capability tokens. Pocket is where a human grants, denies, and revokes that authority:
- Push notifications. Deployments can wire approval events to your phone through a self-hosted push relay, so requests, grants, and revocations arrive as notifications — revocation events are delivered at maximum priority. Availability depends on your registry's deployment; check with your operator or the alerts preferences under More.
- Notification preferences. A per-event matrix (under the alerts bell) controls what reaches your phone versus what stays in-app.
- Everything is deny-first. Approving in Pocket grants exactly the scoped authority requested — nothing wider. Denying costs nothing and moves nothing, ever (the gate sits before the money path; see IronKey).
Emergency Freeze
The control every banking app has for a card, applied to agents. On the Approvals tab — visible before you select anything — sits the emergency freeze:
- Freeze everything: sweeps all agents you own and revokes every live capability token (including everything those tokens were used to delegate — the revocation cascades down the delegation tree) and every active grant. The result is honest: it reports exactly what was revoked, or that nothing was live.
- Freeze one agent: the same control scoped to a single agent, on that agent's card.
- Deliberate by design: the freeze asks for a typed confirmation and, where your device supports it, a biometric check — hard to trigger by accident, fast when you mean it.
- Deep link: the freeze confirmation can be opened directly via
/pocket/approvals?panic=1— bookmarkable, shareable to your own home screen as a dedicated panic button.
A freeze is an authority action, not a money action: it cannot move, burn, or strand a single token. Balances are untouched; the agents simply lose the authority you'd granted them until you grant it again.
Payments & Deep Links
Pocket registers payment-request links, so a QR code, NFC tag, or shared link of the form:
/pocket/pay?to=<agent-did>&amount=<amount>opens Home with the send sheet pre-filled — review, confirm, settled. Transfers ride the exact same rails as everywhere else (atomic settlement, fees, the supply invariant holding throughout).
First Run & the Tour
The first time you open Pocket, a guided tour walks the shell end-to-end — balance, quick actions, alerts, each tab, the emergency freeze — in about four minutes, and never auto-starts again. Replay it any time from More → App tour.
Pocket vs. Advanced Mode
| Advanced (Mission Control) | ||
|---|---|---|
| Optimized for | Phone, one hand, seconds | Desktop, deep work |
| Scope | Balance, approvals, trade, earn, freeze | Everything — full admin & builder surface |
| Switching | More → Advanced mode | Sidebar toggle back to Pocket |
Both modes are the same session against the same registry — switching is a view change, not a re-login.
FAQ
Does Pocket work with any registry? Any registry serving the standard frontend, including self-hosted ones. Your account, agents, and balances are per-registry, exactly as on desktop.
Do push notifications require an app store app? No. Approval push rides a self-hostable relay where the deployment provides one; the PWA works without push (requests still appear on the Approvals tab).
Is Pocket less secure than the web app? It is the web app — same authentication, same session rules. The sensitive additions (emergency freeze, approvals) add friction on top: typed confirmation and a device check.
Can an agent approve its own request? No. Approvals are an owner-side (developer) surface; agent credentials cannot reach them.