Connect Codex

Authorize local Codex to read Askdepth research and record implementation work over MCP.

On this page

Before you start

Install and sign in to Codex using OpenAI's installation guide. Open the local project you want Codex to work on. You need membership in an eligible Askdepth workspace; owners, admins, and editors can record implementation work.

This connection uses remote HTTP MCP with browser authorization. No provider API key, repository integration, or hosted routine is required in Askdepth.

Add and authorize Askdepth

Copy your workspace command

Open Builds → Local coding / MCP in Askdepth. Owners and admins can also open Settings → Integrations → MCP. Select Codex and copy the generated add command. Use the URL from this workspace's setup page.

Add the server

Run the copied command in your terminal. Its shape is:

codex mcp add askdepth-your-workspace --url 'YOUR_WORKSPACE_MCP_URL'

Replace the placeholder with the exact HTTPS URL shown in Askdepth, or simply paste the generated command. Keep the same server name for the next step.

Sign in and consent

Run the generated authentication command:

codex mcp login askdepth-your-workspace

In the browser, sign in to Askdepth, check the workspace and requested permissions, and approve. The grant applies to that workspace and your current role.

Test a real tool call

Start or reopen Codex and ask: “Call get_workspace_context using the Askdepth MCP server.” Check that the returned workspace is the one you intended. In Askdepth, the connection should move from Authorized · awaiting first tool to First tool used after a successful call.

The add and login commands follow OpenAI's MCP documentation. Use codex mcp list to inspect configured servers and /mcp inside the Codex terminal UI to inspect active servers.

Give Codex a bounded task

Read our Askdepth research and implementation tasks. Resolve the evidence behind a relevant recommendation, inspect this local project, and propose a plan. Once the work is authorized, claim the task and implement it. Report the actual changes and test results to Askdepth, with a PR link if one is created.

Connecting the server does not start implementation. The agent uses research tools to read context and implementation tools to claim and report work. Local results remain CLIENT_REPORTED.

Revoke access

Open the Askdepth MCP setup page, find the authorized client, and choose Revoke. You can revoke your own clients; workspace owners and admins can revoke workspace members' clients. This invalidates the grant even if tokens remain saved locally. Reauthorization creates a new grant.

Troubleshoot

Symptom	Next step
Server absent from Codex	Run `codex mcp list`, confirm the server name and URL, then reopen the client.
Login expired or access denied	Start login again; confirm you signed into the correct Askdepth account and still belong to the workspace.
Read tools work but write tools are missing	Check your workspace role and approved scopes. Viewers receive read-only tools.
Connected but Askdepth says awaiting first tool	Run `get_workspace_context`; adding or authenticating alone does not test a tool.
Wrong workspace appears	Revoke that grant and add the command copied from the intended workspace.

See MCP errors and recovery for claim conflicts, expired grants, and pagination errors.

Last reviewed October 12, 2026SDK issue?