Connect Codex App
Let ReignHub and the desktop App share one Codex app-server.
Why launch through ReignHub?
Other clients may read Codex history, but the corresponding backend owns running sessions. Reading a record does not connect to that backend.
ReignHub starts a shared Codex app-server and passes connection settings when launching Codex App. Both clients connect directly to the same backend, sharing session state and live output.
Steps
- Install Codex App, sign in and confirm it works locally.
- Find Codex App in the ReignHub local dashboard and check readiness.
- If it is running independently, wait for the task to finish and quit it.
- Use Enable / Launch through ReignHub, and wait for ready status.
- Connect from a controller and open an existing session or create one.
Protect running tasks
Do not terminate a working Codex App or app-server just to enable remote control. Integration may require restarting the App; wait for the current task to finish.
Independent launch and quitting ReignHub
An App opened directly through the OS may not use the shared backend and can require reintegration. Follow the dashboard instructions and wait for Ready before sending remote instructions.
The shared backend has an independently managed lifecycle. The shared backend continues to manage local Codex tasks after ReignHub closes. Killing the backend, logging out or losing connectivity can still disrupt connections.
Compatibility boundaries
This integration depends on Codex App connection and launch capabilities, which may change with upgrades. If the shared backend fails, restore normal local use first, then report the App and CLI versions.