Connect Codex CLI
Use your installed Codex CLI as a text provider in Aerenium. Understand what this connection can do.
What this connection does
Aerenium supports Codex CLI as a local provider. You do not need to create an MCP server or paste a Codex login token into Aerenium.
It sends a text turn through the installed Codex CLI and returns text. Aerenium tools, skills, swarm actions and optional prompt layers are off for CLI turns. This is not a way to give Codex control of the app.
Before you begin
- Install Codex CLI using the official OpenAI instructions. In a terminal on the same machine as Aerenium, check that the codex command is available.
- Sign in using Codex itself. Run codex login and complete its sign-in flow. Aerenium uses the sign-in already present on this machine; do not copy login files or credentials into the app.
codex --version
codex loginChoose how the model runs
- Open Aerenium, then Control Room → Models → Provider → Codex CLI. If the choice is unavailable, follow the reason shown next to the provider.
- Read “Your Codex CLI sign-in and CLI limits”, then select “Acknowledge and use Codex CLI”. Choosing the provider alone does not enable it.
- In Control Room → Models, expand “Role tuning — temperature, endpoints, per-role keys”. Under “Global Model (Fallback)”, use “Model ID” to choose from the current Codex suggestions. Check any per-role provider and model overrides, then send a short message in Chat.
Which account pays?
Usage counts against the subscription or API account used by your Codex CLI, not Aerenium Credits. Aerenium’s dollar ceiling cannot enforce the CLI vendor’s spending limits. Check the limits in your OpenAI account.
How is MCP different?
The MCP Servers page connects Aerenium to external tool servers. It is a separate feature from choosing Codex CLI as a provider. The current app does not expose a documented MCP server that lets Codex call Aerenium’s tools.