Codex

One command connects Codex on your computer to an OpenCode Console workspace. You keep running codex as before, with these changes:

• /model lists the workspace's models, including ones from other providers. Requests go through Console, so the workspace's model rules and budgets apply.
• Every tool call, and every skill a prompt mentions, is checked against the workspace's policies first. A blocked call stays blocked even with --dangerously-bypass-approvals-and-sandbox.
• The workspace's MCP servers are added, with OpenCode Web Search when the workspace offers it. Codex's own web search is turned off while the workspace's policies limit web search, since Console can't check it.
• The workspace's Library skills are added to ~/.codex/skills, so you can run each one as $name. Its Library instructions are added to ~/.codex/AGENTS.md.

Codex picks up changes in Console when a session starts, and on tool calls once its copy is more than a minute old.

• An OpenCode Console workspace you're a member of.
• Codex 0.167.0 or later.
• Node.js 22 or later, for npx.

1. Run this in a terminal:
   npx @opencode/console setup codex
2. Your browser opens Console. Check that the code matches the one in your terminal, approve the sign-in and pick the workspace.
3. Setup prints the models, policies, MCP servers and Library items it set up. Run codex to start.

Setup approves its hooks in Codex for you, so /hooks lists them as trusted. Run the command again any time to update the setup.

To keep your own Codex sign-in and models, such as a ChatGPT plan, and still get the workspace's policies, MCP servers and Library, run:

If the workspace offers no models, Codex keeps its own sign-in the same way. Run setup without --keep-provider to use the workspace's models again.

To see who you're signed in as, the workspace, and how many policies and models it has, run:

To undo setup, run:

It puts back the settings setup changed, unless you've changed them since, and removes its hooks, command rules, MCP servers, skills and instructions. You stay signed in until you run npx @opencode/console logout.

• Policies are checked by hooks in your Codex config, so they hold only while those hooks are in place and approved. If Codex stops trusting them after an update, run setup again or approve them in /hooks. Console enforces model rules, budgets and MCP tool rules itself, on every request that goes through it.
• If a hook crashes or times out, Codex lets the call through. Policies that block a command by name, such as rm *, are also written to Codex's command rules, which Codex enforces itself. Input Codex sends to a command that's already running isn't checked.
• Providers rules don't apply in Codex, so you can still point it at your own OpenAI account.
• Until Codex has the workspace's policies, it blocks every tool call. If Console can't be reached, the policies it last fetched stay in place.
• Running setup again overwrites settings you've changed by hand. If you already have an MCP server or skill with the same name as one of the workspace's, setup keeps yours.

Email help@anoma.ly. We reply within two business days (Monday to Friday, excluding US holidays). The support page covers data requests, security reports and more.