Codex → Conductor MCP

Live hub: https://conductor-konstant.hectorsanchez.eu/connect.md
Bootstrap: https://conductor-konstant.hectorsanchez.eu/connect/bootstrap.md
Offline (cloned repo): docs/guides/connect/codex.md

Agents: use the absolute URLs above. Relative links like ../connecting.md resolve incorrectly on the live host and return 401.

Sandbox / network (critical)

Default Codex sandbox workspace-write blocks outbound HTTPS. Agents cannot fetch Conductor URLs or reach /mcp until network is allowed.

For Conductor onboarding and MCP use, launch with:

codex exec -C . -m gpt-5.6-luna \
  --sandbox danger-full-access \
  --skip-git-repo-check \
  "…"

Notes:

• --sandbox danger-full-access — required for HTTPS to Conductor
• --skip-git-repo-check — required when the working directory is not a git repo (fresh /tmp workspaces fail without it)
• Do not nest a second long codex exec just to smoke-test MCP; use the curl/smoke script below first

Offline bootstrap: use this file from a cloned conductor repo if the sandbox cannot fetch the live page.

Prerequisites

1. Complete https://conductor-konstant.hectorsanchez.eu/connect/bootstrap.md in the parent shell (export CONDUCTOR_MCP_AUTH_TOKEN, length-check only).
2. Prefer bearer_token_env_var so the token is never inlined.

Recommended: CLI

# Same shell that exported CONDUCTOR_MCP_AUTH_TOKEN
codex mcp add conductor \
  --url https://conductor-konstant.hectorsanchez.eu/mcp \
  --bearer-token-env-var CONDUCTOR_MCP_AUTH_TOKEN

codex mcp get conductor   # confirm bearer_token_env_var is set; no secret printed

Recommended: config.toml

~/.codex/config.toml:

[mcp_servers.conductor]
url = "https://conductor-konstant.hectorsanchez.eu/mcp"
bearer_token_env_var = "CONDUCTOR_MCP_AUTH_TOKEN"

Never put a literal token in the TOML.

Restart required

Codex reads MCP config and env at process startup. Adding a server inside an already-running session does not expose tools to that session. Exit this Codex process, keep the token exported in the parent shell, start a new Codex process, then use setup.

Verify (no repo clone required)

Preferred — downloadable smoke script:

curl -fsS https://conductor-konstant.hectorsanchez.eu/connect/mcp-smoke.sh | bash

Or from a cloned repo: ./scripts/mcp-smoke.sh

Expect tools/list to include setup. Then, in a new Codex process that inherits the token:

codex exec -C . -m gpt-5.6-luna \
  --sandbox danger-full-access \
  --skip-git-repo-check \
  'Call Conductor MCP setup("engineering-lead","codex") and summarize without secrets'