Gateway-first control
A control room for the computers that actually do the work. The web app handles identity, gateway discovery, and access leases while AgentGateway stays the source of runtime truth.
Gateway pairing
Create a short-lived token, sign in from AgentGateway, and watch the machine appear in your team.
No IP ritual
Clients pick a connected gateway by name. FRP ports, endpoints, and device tokens stay behind the curtain.
FRP spine
A worker beside frps allocates public ports, records mappings, and keeps leases visible in Supabase.
Codex-ready
Start with Codex and a local AgentGateway, then grow into richer worker fleets without changing the client flow.
Account-owned machines
Every gateway belongs to a team account with permissions, audit logs, and clean session boundaries.
Pocket to workstation
A phone becomes the remote control; the real work stays on your computer or cloud box.
Not a cloud IDE. A remote nervous system for your own workers.
The frontend manages identity and selection; the gateway remains the runtime authority; FRP opens a precise, revocable path when a client needs to reach the machine.
