Docs

Connect Codex

Connect Codex to your workspace memory. The server is https://agentics.you/mcp, named agentics in every tool, so an admin can allowlist one name.

One click from the desktop app

In the Agentics desktop app, Connect your agents lists Codex with its state. Nothing changes until you confirm.

Click Connect. Before anything changes, the app shows what it will do: “Add Agentics to Codex for your user. The ChatGPT desktop app reads the same ~/.codex/config.toml.” With it are the command it runs and the file it changes.
Click Confirm. The app saves a backup of the file beside it (<file>.agentics-backup-<timestamp>, readable by you only), runs codex mcp add agentics --url https://agentics.you/mcp, then runs codex mcp list --json to check that agentics is there.
The command goes on to open your browser so you can sign in to Agentics. The app counts the connect as done once the entry is written.

If Codex isn't installed, its row says so and offers nothing to click. Once it has agentics, the row says Connected and offers Disconnect.

The app is for macOS and Windows. Get it from Download, which lists each build once a release is published.

By hand

Run this in a terminal. It is the command the app runs:

Shell

codex mcp add agentics --url https://agentics.you/mcp

The entry it writes to ~/.codex/config.toml includes:

TOML

[mcp_servers.agentics]
url = "https://agentics.you/mcp"

If CODEX_HOME is set, the file is config.toml in the folder it names.

~ is your home folder.

Codex opens your browser to sign in when it adds the server. If it doesn't, run codex mcp login agentics. In the ChatGPT desktop app, open Settings > MCP servers and click Authenticate.

A console API key (ak_…) does not work here. Production answers HTTP 401 {"error":"invalid_token"} to one.

Check it worked

Run codex mcp list --json. It lists agentics at https://agentics.you/mcp.

Then ask your agent to use it:

Paste this into your agent

Call the remember tool with content "The customer prefers email over phone." Then call recall with the query "how does the customer like to be contacted?" and tell me the receipt_hash.

remember answers with saved true and a receipt_hash. recall returns that memory in results. Open the verify_url: the check does not show the memory's text.

Disconnect

In the desktop app, click Disconnect, then Confirm. It backs up the file, runs codex mcp remove agentics, then runs codex mcp list --json to check that agentics is gone.

By hand, run:

Shell

codex mcp remove agentics

If your organization manages Codex

Before it changes anything, the app reads these files. One that blocks agentics stops the connect: the row says “Blocked by your organization's policy” and names the file. One that already provides agentics means there is nothing to add. A file that exists but can't be read stops the connect too.

Codex's requirements. Its [mcp_servers] table lists the servers Codex may turn on, and an empty one turns MCP off. The app looks at /etc/codex/requirements.toml on macOS, %ProgramData%\OpenAI\Codex\requirements.toml on Windows and /etc/codex/requirements.toml on Linux.
The same requirements, delivered by an MDM profile. The app looks at /Library/Managed Preferences/com.openai.codex.plist on macOS.

What the app can't check

Requirements your workspace sets in ChatGPT's Agent Security aren't visible on this computer. codex mcp list shows a server they disable.

If it does not connect

What you see	What it means
Not installed	The app found no Codex on this computer. Install it, then click Check again.
Another agentics server	Codex already has a different server named `agentics`. The app won't replace it: remove that one in Codex first.
Can't read its settings	The app couldn't read Codex's config or a policy file, so it changes nothing. The row names the file and why.
Blocked by policy	A policy file blocks agentics. The row names it; see the policy files.
Provided by your organization	Your organization already gives Codex `agentics`, so there is nothing to add.
HTTP 401 `{"error":"invalid_token"}`	Sign-in did not finish, or a console key (`ak_…`) was sent. Sign in again, or send an agent key (`agk_mcp_…`).
HTTP 405 `{"error":"Use POST for JSON-RPC"}`	Something sent GET, as a browser tab does. Clients send POST to `https://agentics.you/mcp`.
HTTP 403, code `-32000`, `Token lacks the mcp:tools scope`	The sign-in can't use the server. Remove agentics, add it again, and choose Allow.
`Unknown tool: remember`	The tool list is stale. Reconnect agentics so the tools are read again after sign-in.
`This connection cannot use remember.`	The grant is missing `actions:record`. Connect again and choose Allow.
`content is required.` (code `-32602`)	`remember` needs `content` as a string.
`Unknown field: …` (code `-32602`)	That argument is not one `remember` takes.
HTTP 429 `{"error":"Too many requests. Try again in a minute.","retry_after":…}`	120 calls a minute on that sign-in. Wait `Retry-After` seconds.
`This workspace has used its 10,000 actions for this month on Free. New actions are paused until the 1st (UTC).`	Free is at its monthly write cap. `recall` still works.

More errors are on Connect any MCP client.