Credentials never leave the Mac
Every task runs through the provider CLI already signed in on its owner’s machine. No token, key or session is copied to a phone, to the relay or to another person’s Mac.
Enforced by the local brokerINTERACTIVE PROTOTYPE · 2026
The whole product,
state by state.
Thirty mobile screens, ten Mac menu-bar states and the orchestration architecture behind shared goals. Every state here is the real intended behaviour, including the ones where the answer is no.
30Mobile screens
10Mac states
6Architecture layers
5Invariants
M01 · IPHONE
Welcome
1 / 30
9:415G ▮▮▯ 82%
Don’t stay
at your desk.
Your coding agents keep running on your Mac. This app is the remote for them.
1Pair one MacScan a short-lived code. No account sharing, ever.›
2Pick a routeProject and provider preset are chosen before any run.›
3Keep movingWatch, unblock and review from wherever you are.›
ARCHITECTURE INVARIANTS
Five rules that
hold in every state.
These are not aspirations. If a screen in this prototype appears to break one of them, the screen is wrong, not the rule.
A friend is not access
Friendship is verified identity and nothing more. Capability comes only from an explicit grant naming a Mac, a project, presets, a budget and an expiry — and it can be revoked mid-run.
Grant table is the only authorityModels are approved preset IDs
Mobile and circles choose from preset IDs that the owning Mac published. Raw model strings, temperatures and shell flags never cross the wire, so a model cannot escalate itself.
Rejected by deterministic validationThe manager proposes, code decides
The AI manager emits a plan document and has no dispatch capability. A deterministic coordinator, not a model, checks grants, dependencies, presets and budgets before any owner is asked.
No model in the control pathRelay transports, never orchestrates
The relay moves signed envelopes between devices. It holds no plan state, schedules nothing, and its control schema is designed without chat-content columns.
Opaque by schema design