Let ChatGPT web plan so Codex stops burning API tokens on review

What it does

It turns your ChatGPT web session into the strategist for Codex coding sessions. ChatGPT handles planning and reviewing through the official web UI, while Codex keeps sole control over actually editing files and running commands. The two talk through a local bridge: an OAuth-secured, read-only MCP server that lets ChatGPT pull exactly the code lines it needs without ever uploading your entire repository.

The interesting bit

The security model is deliberately paranoid in a useful way: the MCP server is read-only by construction—write tools literally do not exist—so prompt injection cannot escalate to code changes. ChatGPT verifies Codex’s work by inspecting git diffs and test records itself rather than trusting summary claims. The project also ships a Codex Skill that tries to install and configure itself automatically, including dependency checks.

Key highlights

• ChatGPT web plans and reviews; Codex keeps exclusive execution rights
• Read-only MCP bridge with 8 tools (read_file, git_diff, etc.)—no upload of your full repo
• OAuth 2.1 + one-time pairing codes; no API keys or reverse proxies needed
• Path containment blocks symlink/../ escapes; sensitive files like .env denied by default
• Includes a Codex Skill for zero-touch installation and auto-updates

Caveats

• Unofficial community project with no OpenAI affiliation
• Requires Node.js >= 20 and cloudflared for the public tunnel connection

Verdict

Worth a look if you pay for ChatGPT Plus/Pro and want to stop burning Codex API credits on planning and review loops. Skip it if you need ChatGPT to actually write code—this keeps execution locked to Codex by design.