Fallback · Codex

Codex — manual setup

Most users never see this page. The default path is one command: say launch this in your IDE chat and let your agent run launch-here for you (Codex is auto-detected). This page exists only as a fallback when auto-attach can't run.

Default path: /install · Manual config below.

1. Get a key

chieflab.io/get-key → copy the clp_dev_ or clp_live_ key.

2a. Hosted (preferred)

Edit Codex MCP config — typically ~/.codex/mcp.json:

{
  "mcpServers": {
    "chieflab": {
      "url": "https://api.chieflab.io/api/mcp",
      "headers": {
        "Authorization": "Bearer clp_dev_<paste-your-key>"
      }
    }
  }
}

2b. Stdio bridge (if hosted MCP unsupported)

npm install -g @chieflab/mcp-server

# Then in Codex MCP config:
{
  "mcpServers": {
    "chieflab": {
      "command": "chieflab-mcp",
      "env": { "CHIEFLAB_API_KEY": "clp_dev_<paste-your-key>" }
    }
  }
}

3. Restart Codex

Quit + reopen the Codex session (or restart the daemon). Ask: launch this. Codex picks chieflab_launch_product, drafts render inline, you approve in chat.

Troubleshooting

  • Tools don't appear: restart the Codex daemon (some builds cache MCP tool lists across sessions).
  • 401 Unauthorized: Bearer key wrong. Re-mint at /get-key.
  • Codex doesn't call ChiefLab: trigger noun match matters. Say launch this / get users / market this rather than vague "help me grow."
  • Tool call hangs: image generation can take 10-30s. Raise the Codex MCP timeout if available.

More