Codex-with-ChatGPT: Using ChatGPT as Planning Brain for Codex
A GitHub project that lets developers use the ChatGPT web interface for planning and review while Codex handles execution, without requiring API keys or reverse proxies. 6,977 GitHub stars in 35 days since xiaoduoya/codex-with-chatgpt was created (197.8/day). 1 source across 1 channel. Automatically detected; not yet
49Fact cited ·Analysis our interpretation ·Estimate forward-looking · [n] links to the source
5 claims drafted by openai/gpt-oss-20b were kept because each quote was found verbatim in its source; 1 unverifiable claim was discarded. Statements marked AI await human review.
What happened
- Fact The project uses the ChatGPT web app as the planning and review brain for Codex coding sessions.[1]AI
Use the ChatGPT web app as the planning and review brain for your Codex coding sessions, while Codex keeps full ownership of execution.
- Fact Codex execution does not require API keys or reverse proxies.[1]AI
No API keys, no reverse proxy — official web UI plus a read-only MCP bridge.
- Fact Installation is simplified to copying a skill folder and running a setup command, with no need for git, Node, or terminal knowledge.[1]AI
Copy the paragraph below, paste it to your coding agent (Codex), and go grab a coffee:
- Fact The skill automatically checks GitHub daily for updates and can be updated on demand by saying "更新 Codex with ChatGPT".[1]AI
The Skill checks GitHub once a day and updates itself when a new version is released; no action needed. You can also say "更新 Codex with ChatGPT" anytime.
- Fact The GitHub repository xiaoduoya/codex-with-chatgpt was created on 28 Aug 2026 and had 6,977 stars on 2 Oct 2026.[1]
- Fact Its description reads: “ChatGPT thinks. Codex works. Use ChatGPT as the planning brain while keeping the Codex harness.”[1]
- Fact That is 6,977 stars in 35 days, an average of 197.8 per day.[1]
Why it matters
- Analysis Install the skill, set up the ChatGPT connector, and use Codex normally with ChatGPT for planning.AI
- Analysis Automatically detected from public activity data. Not yet reviewed by an analyst.
Should I care?
What changed?
- Fact The project uses the ChatGPT web app as the planning and review brain for Codex coding sessions.[1]AI
Use the ChatGPT web app as the planning and review brain for your Codex coding sessions, while Codex keeps full ownership of execution.
- Fact Codex execution does not require API keys or reverse proxies.[1]AI
No API keys, no reverse proxy — official web UI plus a read-only MCP bridge.
Who is affected?
- Analysis Developers using Codex who want to offload planning and review to ChatGPT without managing API keys.AI
What can developers do with it?
- Analysis Install the skill, set up the ChatGPT connector, and use Codex normally with ChatGPT for planning.AI
Is it production-ready?
Insufficient evidence
Analysis Not assessed.
What would make it important?
Not yet assessed.
What could prevent adoption?
Not yet assessed.
Technical change
- Fact The project uses the ChatGPT web app as the planning and review brain for Codex coding sessions.[1]AI
Use the ChatGPT web app as the planning and review brain for your Codex coding sessions, while Codex keeps full ownership of execution.
- Fact Codex execution does not require API keys or reverse proxies.[1]AI
No API keys, no reverse proxy — official web UI plus a read-only MCP bridge.
- Fact Installation is simplified to copying a skill folder and running a setup command, with no need for git, Node, or terminal knowledge.[1]AI
Copy the paragraph below, paste it to your coding agent (Codex), and go grab a coffee:
- Fact The skill automatically checks GitHub daily for updates and can be updated on demand by saying "更新 Codex with ChatGPT".[1]AI
The Skill checks GitHub once a day and updates itself when a new version is released; no action needed. You can also say "更新 Codex with ChatGPT" anytime.
Architecture
No architecture has been documented for this signal.
Developer impact
Developer implications have not been assessed yet.
Difficulty has not been estimated yet.
Adoption & momentum
No adoption indicators recorded.
Timeline
First seen by the Astrava pipeline[1]
Limitations & risks
- Fact The project relies on the ChatGPT web interface and requires a ChatGPT Plus/Pro subscription for quota usage.[1]AI
ChatGPT Plus/Pro web quota sits idle while your coding agent burns scarce API/Codex tokens on planning and review.
- Analysis Generated from activity metrics only; verify the linked sources before acting on it.
Competing approaches
No competing approaches documented yet.
Who is building on it
No independent projects or organisations are documented as building on this yet.
Evidence & sources
Primary source (1)
Published by the people who built it: release notes, repositories, papers, official docs.
- [1]XiaoDuoYa/codex-with-chatgpt repository(opens in a new tab)
ChatGPT thinks. Codex works. Use ChatGPT as the planning brain while keeping the Codex harness.
Secondary source (0)
Independent reporting, third-party benchmarks, integrations by other projects.
None recorded.
Community signal (0)
Discussion threads and social posts. Evidence of attention, not of correctness.
None recorded.
How the score of 49 was calculated
| Factor | Share of maximum | Points |
|---|---|---|
| NoveltyRubric level 2/4 (Moderate). Heuristic (automated): first published 35 days ago. | 7.5/15 | |
| Technical significanceRubric level 3/4 (High). AI-assisted (openai/gpt-oss-20b), pending human review: Integrates two large language models via a secure read‑only bridge, enabling efficient token usage and separation of planning and execution. Evidence: “No API keys, no reverse proxy — official web UI plus a read-only MCP bridge.” | 11.3/15 | |
| Developer relevanceRubric level 3/4 (High). AI-assisted (openai/gpt-oss-20b), pending human review: Provides a practical workflow for developers to use ChatGPT for planning while keeping Codex for execution, simplifying setup and reducing token costs. Evidence: “Use the ChatGPT web app as the planning and review brain for your Codex coding sessions, while Codex keeps full ownership of execution.” | 11.3/15 | |
| Adoption velocityIndependent integrations: unknown (0 pts). GitHub stars: 197.8 per day since creation; full marks at 1000/day, log-scaled (3.8/5). | 3.8/10 | |
| Community momentumFewer than three periods of activity data, or no baseline activity to compare against. | 0/10 | |
| Source credibilityPrimary source present; mean source-tier weight 1.00 (primary 1.0, secondary 0.7, community 0.35). | 10/10 | |
| Cross-source confirmationNo independent publisher has confirmed this yet. | 0/10 | |
| Evidence strengthMet 2/4: primary source ✓, runnable artifact (code, weights or package) ✓, reproducible or independent benchmark ?, technical documentation or paper ✗. 1 unknown (scored 0). | 5/10 | |
| Time to impactNo time-to-impact estimate yet. | 0/5 | |
| Hype penaltyNo hype indicators detected. | 0 | |
| Breakout Score | 49 |
Low confidence (0.48) — 60% of measured factors have data. 0 independent non-community publishers. At least one primary source. Evidence strength 5/10. Capped at Low: no independent, non-community source yet.
An analytical ranking derived from observable signals using model breakout-v1.2. It is not a prediction and not a measure of quality. How it works