What does PocketWorkers actually connect?
It connects an authenticated client to an authenticated AgentGateway. The gateway registers with the backend, receives an FRP lease, and then appears as a selectable worker lane for the user's team.
Do clients need to type IP addresses or ports?
No. The client selects a gateway by name. Public endpoint and port information is allocated by the backend and read through account-owned APIs.
Where does the AI work run?
The work runs on the user's own computer or cloud box through AgentGateway. The web app manages identity, pairing, and discovery; it does not become the runtime authority.
Why does the gateway also log in?
A gateway is a device with access to a real worker environment. Requiring gateway login lets us bind that device to an account before exposing any route to clients.
Where will FRP run?
FRPS runs on an independent cloud server. A PocketWorkers FRP worker allocates public ports, stores leases in Supabase, and keeps those details available to authorized clients.
Which AI agent is supported first?
The first target is Codex through AgentGateway. The architecture keeps the client and gateway contracts ready for additional worker types later.