Skip to main content
Codex is OpenAI’s open-source CLI coding agent. Route your Codex traffic through Edgee to cut token costs by 15-20% with lossless compression, and gain full observability over every coding session. (Our SWE-bench Lite benchmark measures 50% with all three strategies on: see what you’ll actually save.) Edgee works with your existing subscription for Codex. The fastest way to connect Codex to Edgee is through the CLI, no config files to edit manually.
1

Install the Edgee CLI

2

Launch Codex through Edgee

Choose how you want to launch. Both options route requests through Edgee.
With aliases installed in the previous step, use your usual command:
The alias runs edgee launch for you, so requests go through Edgee.
If you are not signed in, Edgee starts sign-in automatically at launch. Follow the prompts and select your organization when asked.The CLI authenticates, writes the Codex config, and starts Codex, all in one command. Token compression is enabled automatically.
After the session ends, the CLI prints a link to view token usage, compression savings, and cost breakdown in the Edgee Console.

​
Manual setup (advanced)

​
Get your coding-agent key

Manual setup uses the key of your enrolled Codex agent, not a standard API key created for LLM Router applications.
  1. Open the Edgee Console and select your organization.
  2. In the header, click Set up coding agent or +, select Codex, and click Enroll. If your agent is already enrolled, use its existing icon.
  3. Click the agent’s icon, then Advanced settings → Advanced.
  4. Under Edgee API key (for manual setup), click Reveal key, then the copy icon.
Use this key wherever the configuration below shows <YOUR_CODING_AGENT_KEY>.

​
Configure Codex

If you prefer to configure Codex without the CLI, update your Codex configuration file at ~/.codex/config.toml:
Replace <YOUR_CODING_AGENT_KEY> with the coding-agent key copied above. Manage token compression from the Codex icon in the console header.

​
Usage

Keep launching through Edgee so the request uses your configured gateway:
Arguments after the agent name are forwarded to the installed agent. Use that agent’s current help for its supported flags. A bare codex command routes through Edgee only if you have installed an alias.

​
Verify the connection

Send one request from the configured client, then open Logs in the same Edgee organization. Check the served model, provider, and key. For a CLI-launched coding agent, also inspect its session report. If the request is missing, check that you launched through Edgee or saved the client’s gateway URL and coding-agent key. If it appears with an error, inspect the error before changing settings. See Troubleshooting and Gateway errors.