Getting started

Get FlyDex running in one session

The public path is intentionally short. Start on the desktop that already runs Codex, install the helper if needed, scan with your phone, and wait for codex_ready before treating the machine as live.

Target: under 2 minutes Desktop starts first QR-only pairing

Reference map

Public docs sections

Getting started

Desktop install, QR handoff, and first health checks.

Authentication

Account auth, QR claims, local-connect tokens, and machine continuity.

Agent control

Thread access, send/resume turns, and remote approvals.

WebSocket API

Bridge lifecycle, documented endpoints, and status model.

Security

Threat model, data boundaries, and transport safeguards.

Architecture

Control plane, connector, and local Codex runtime topology.

Examples Competitive comparison

Step 1

Install the local helper

If the helper is not already running, use the documented one-line desktop install.

npx -y --prefer-online flydex@latest

Step 2

Scan with your phone

Open FlyDex on the desktop, let the page generate the QR claim for that machine, then complete sign-in on the phone browser.

Validation

First health checks

Check	Expected result	Why it matters
`http://127.0.0.1:48163/v1/health`	Helper responds locally	Confirms the connector is alive on localhost only.
QR claim scan	Phone browser reaches account handoff	Confirms the desktop is issuing a live claim for the right machine.
Machine state	`codex_ready`	Confirms cloud session routing and local runtime readiness are both healthy.

curl http://127.0.0.1:48163/v1/health