Connect Codex CLI
Connect the CLI backend to work with projects and sessions across devices.
Installation and readiness
Install Codex CLI and sign in on the host. ReignHub discovers installations and compatible backends, marking the provider ready when it can connect. Otherwise, enable it from the local dashboard.
Installing the CLI does not mean a connectable app-server is always running. Codex App, a ReignHub-managed runtime or other clients may start one; check actual backend ownership.
Controlling existing sessions
Readable history and writable sessions are different scopes. A session owned by an independent CLI process or another app-server cannot always be taken over from a different backend.
For active-writer or read-only errors, follow the dashboard instructions to connect the corresponding backend. If the original task is still running, wait for it to finish before reconnecting.
App and CLI relationship
They can share some history storage but remain separate provider routes in ReignHub, keeping source and controllable backend distinct. Sessions in the same directory can share a project group while retaining source icons.
Official quotas count both as one Codex product, not two agent-product slots.