Codex

The way you connect Codex to Catena depends on where Codex runs:

Connect the Codex CLI

1. Paste our setup prompt from Connect an agent.
2. Codex runs commands in its own sandbox, which is separate from your Catena sandbox. Its default sandbox refuses network access to the Catena API (api.catena.com) and keychain writes, and the CLI needs both:
   • When the CLI's error names the Catena API host, approve the request for network access.
   • When catena link fails to store its key, approve the sandbox escalation when Codex asks, and run the command again.
3. Open the approval link, choose the organization and policy, and approve.
4. Tell Codex you approved. It will run catena link again, which prints Done.

If your sandbox settings cannot allow keychain writes, we recommend a secret key instead. Set it as CATENA_SECRET_KEY in the environment Codex runs in, and skip catena link.

Note

No file fallback

When the keychain refuses a key, the CLI does not save it to a file. You'll need to allow the keychain write or use a secret key.

Test the connection

To check that everything is working, ask Codex to run catena whoami. It will report the agent's name.

Limitations

There are a few things to keep in mind when you use Codex:

• If Codex writes under ~/.config/catena from inside its sandbox, that path must be writable. Allow it, or set CATENA_HOME to a writable directory that persists between runs.
• Payments at or above your approval threshold will wait for an admin.