PocketWorkers Overview

How the web app, AgentGateway, Supabase, clients, and FRP fit together.

PocketWorkers lets a signed-in client control AI workers that remain on the user's own machine or cloud box.

The system has five moving parts:

  1. Web app - account, team, gateway, and pairing management.
  2. Supabase - Auth, team membership, gateway records, and FRP lease metadata.
  3. AgentGateway - local runtime gateway and source of live worker truth.
  4. Client - mobile or desktop control surface that selects a gateway by name.
  5. FRP server - independent cloud relay for public access to registered gateways.

Current MVP boundary

The first worker target is Codex. The web app already has account and team foundations, and PocketWorkers adds gateway registration and route discovery on top.

The client and gateway both authenticate before they can access worker routes.

Core flow

  1. User creates an account.
  2. User opens or creates a team workspace.
  3. User creates a gateway pairing path.
  4. AgentGateway signs in and registers to that team.
  5. Backend assigns FRP endpoint data.
  6. Client signs in and selects the gateway by name.

The client should never need to type IP or port information.