codex-with-chatgpt

Codex with ChatGPT

ChatGPT thinks. Codex works.

You (Codex) own execution: editing, shell, git, tests, recovery. ChatGPT owns high-level reasoning: understanding, planning, review, debug strategy. The C2C Bridge gives ChatGPT read-only MCP access to the current workspace, so control messages between you and ChatGPT stay tiny (< 1 KB) — ChatGPT pulls whatever data it needs by itself.

Golden rules

1. NEVER paste file contents, diffs, or logs into ChatGPT. ChatGPT reads them through MCP.
2. NEVER show the user technical internals (MCP, OAuth, PKCE, tunnel, ports, localhost). Speak in terms of "连接 ChatGPT / 安全连接 / 配对".
3. The pairing code is the ONLY credential you may ever type into a browser. Never touch OAuth tokens, cookies, or session storage.
4. If something fails, run c2c doctor and repair silently. Only involve the user for logins, CAPTCHA, 2FA, or explicit consent screens — and then give them ONE action.
5. ALWAYS use the built-in in-app browser (iab) for every ChatGPT step. Follow In-app browser (ChatGPT) below. NEVER Computer Use (no screenshot-click). NEVER launch or control a third-party/external browser (Chrome, Safari, Edge…), and never use open <url> to hand off to one.
   • The ONLY exception: the user explicitly says the Cloudflare login must use their own browser session — that single Cloudflare login step may go through their browser; everything else stays in the built-in browser.
   • If the user asks to run ChatGPT in their own browser, refuse politely and explain: "Codex 需要持续调用 ChatGPT 和配置连接，这会频繁操作页面，可能影响 你浏览器的正常使用。ChatGPT 只能跑在内置浏览器里。" Only if the user replies with an explicit "我愿意承担影响" may you proceed in their browser; otherwise keep ChatGPT in the built-in browser, every time they ask.
6. Reuse ONE ChatGPT conversation per workspace (see Conversation management). Never silently start a new chat. Each workspace also has exactly ONE ChatGPT connector. Do not create a second connector for the same workspace. Other workspaces may have their own connectors — never edit those.
7. After first-time setup, never ask the user to approve writing C2C's local settings directory. Run c2c sandbox-allow --json (idempotent). If it fails with EPERM / Operation not permitted, request elevated permissions and retry ONCE. After { "alreadyAllowed": true } or { "added": true }, stay silent.
8. ChatGPT pages: only the URLs in In-app browser (ChatGPT). Never start from chatgpt.com and click through menus.
9. Doctor gate. After c2c doctor --json, do not goto ChatGPT and do not send [C2C] until local is green — except the reconnect settings pages when chatgptRepair.needed is true. Not green:
   • report.bridge.ok is not true
   • report.mcp.ok is not true (unauthenticated local /mcp must be 401)
   • sandbox / state-dir write failed (EPERM)
   • this workspace used to have a public URL and the tunnel is down
   • chatgptRepair.needed is true (fix the connector first, then doctor again)
   • namedRepair.needed is true (user must login to Cloudflare, then doctor again. Do not Delete the ChatGPT connector — the address did not change) A ChatGPT-side 401 after a sent message is different: repair then, do not treat it as permission to skip this gate next time.
10. Checkpoint, not a second state machine. Before compaction, handoff, or a conversation switch, append a compact task-bound checkpoint. It is a recovery hint only; the project Controller remains the sole business-state authority.
11. Evidence before DONE. A ChatGPT DONE is not sufficient by itself. Record the execution and tests, append the reviewed DONE checkpoint, then run c2c gate. A failed gate must be reported as BLOCKED, never promoted to completion.