Connecting Codex CLI

Veri connects Codex CLI (codex) through its user-global ~/.codex/config.toml — the one supported agent whose MCP config is not a file in your project. This page documents exactly what gets written, where, and how to verify it works. Using a different agent? See Claude Code, Cursor, or Gemini CLI.

What Veri writes

Open a work order in Veri and click Start agent session. The roster lists every agent detected on your machine; if Codex CLI's row says mcp config: veri entry missing, click Set up & launch. Veri appends one TOML block to ~/.codex/config.toml (creating the file if needed):

[mcp_servers.veri]
command = "node"
args = ["/Applications/Veri.app/Contents/Resources/app/node_modules/@veri/mcp/dist/server.js", "/Users/you/code/your-project"]

command = "node" — Codex launches the server with your own Node (version 20 or newer).
First argument — the MCP server script that ships inside the Veri app. The path contains no version segment, so it stays valid across app self-updates.
Second argument — the project root the server serves: the folder containing veri/.

This file is user-global, not per-project. Unlike the other agents' project-scoped configs, ~/.codex/config.toml is shared by every Codex session on your machine, and its veri block points at the one project it was set up from. Working on a different Veri project with Codex? Edit the second args string to that project's root — or delete the block and run Set up & launch from the other project.

Veri only recognizes the exact block it writes — command = "node" and a two-string args array. Any other [mcp_servers.veri] body is surfaced as a conflict and never modified, and every other section of your config.toml is preserved untouched.

Restart your agent

Agents read MCP config on launch. Set up & launch starts a fresh codex session in Terminal after writing the file, so the config is picked up. For sessions you start yourself, launch codex after the block exists — an already-running session won't see a config written mid-flight.

Verify it works

Two sides to prove. The server side: Veri's connection screen (Settings → Agent connection) has LIVE CHECK → Verify connection, which launches the server with a real MCP handshake and a search call proving it serves this project — the same script and project root your Codex config points at. The agent side: in a Codex session, ask it to search the veri knowledge base — a working connection answers with your project's documents through the veri tools rather than by grepping files.

What the agent gets

The same ten tools every connected agent gets — get_context, get_import_instructions, search, get_document, get_neighbors, file_decision, file_work_order, file_requirement, file_source, file_receipt — detailed in the tool table on the Claude Code page.

Where next: the quickstart to watch the agent pull its first context package, or troubleshooting if verification didn't come back green. Other agents: Claude Code · Cursor · Gemini CLI.