1
Install Runmote local or desktop
A local client runs near your Codex workspace and reports safe presence metadata.
How it works
A safe route from web AI intent to local Codex.
Runmote is being assembled in layers: local clients report safe state, the web app decides what can be routed, and real broker dispatch remains future work.
2
Pair your device
The web control plane issues a bounded pairing flow and device credential contract.
3
Send an action intent
A compatible AI tool can eventually send a normalized request through the future fixed Action endpoint.
4
Route safely
Runmote checks ownership, lifecycle state, active reservations, and safe broker envelopes.
5
Return results
Future broker work will carry results back after real dispatch exists. Today this remains deferred.
What exists now
Accounts, pairing UI, devices, releases, admin control-plane views, and safety verifiers.
What stays local
Codex workspaces and local commands stay on the user's machine behind the device credential boundary.
What is deferred
The official fixed Action endpoint, OAuth, billing, live relay mutation, and real broker dispatch.