Desktop install, QR handoff, and first health checks.
WebSocket API
Bridge and relay protocol notes
FlyDex is not publishing a full public SDK here. This page documents the observable relay surfaces and lifecycle milestones operators need for troubleshooting or architecture review.
Reference map
Public docs sections
Account auth, QR claims, local-connect tokens, and machine continuity.
Thread access, send/resume turns, and remote approvals.
Bridge lifecycle, documented endpoints, and status model.
Threat model, data boundaries, and transport safeguards.
Control plane, connector, and local Codex runtime topology.
Documented endpoints
Known public and localhost surfaces
| Surface | Endpoint | Purpose |
|---|---|---|
| Local helper | GET /v1/health | Readiness and presence check on localhost. |
| Local helper | POST /v1/connect | Starts local connector session work once the browser and cloud side are ready. |
| Control plane | POST /api/local-connect/start | Starts the authenticated local-connect lifecycle. |
| Control plane | POST /api/local-connect/:id/agent-status | Lets the connector report lifecycle status transitions back to the control plane. |
created
-> awaiting_browser_finalize
-> codex_readyOperational note
How the event path behaves
Modern FlyDex clients send shard hints such as user and machine identifiers so the worker can route authenticated traffic directly to the right per-user durable object shard on the hot path.