What it does
ChatGPT thinks. Codex works. Use ChatGPT as the planning brain while keeping the Codex harness.
- Connects Instruction files the AI reads; connects to nothing
- Account or key No key needed
- Category Automation and agents
For makers: add a badge to your README
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/skills/xiaoduoya-codex-with-chatgpt)Similar Skills
Same kind of work, ordered like the Skills list
1 skills (instruction sets) by XiaoDuoYa that an AI reads and follows · not an MCP server
How a Skill differs from MCP
MCP = the hands
Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.
Skill = the manual
A text file that teaches the AI how to do a task. It connects to nothing.
Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.
Works with
Codex
From the maker’s README and the folders in the repo
Install
Is it safe?
- Who made it
GitHub account XiaoDuoYa (person), 4 years old
- Use and upkeep
★ 7,718 stars · code last changed Oct 1, 2026
- Any scripts?
No, plain text files the AI reads and follows
- Uses the internet?
No scripts, so it does not go online by itself
- Changes machine-wide settings?
No hooks or writes to machine settings found
Checked automatically from the repo files at commit 535a07d (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
First: which AI do you use?
Pick your app and this page shows only how to install it there
Option 1Upload to claude.ai (web and app)
Uploading to claude.ai would fail: the description is over 200 characters (343). Use "Let the AI install it" instead
Option 1Let Claude Code install it
Copy this sentence and paste it into a Claude Code chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Restart Claude Code, then type /skill or ask for a matching task and Claude picks it up
Checked against official docs Nov 12, 2026 · Source: code.claude.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.claude/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/xiaoduoya/codex-with-chatgpt.git /tmp/popnx-skill-xiaoduoya-codex-with-chatgpt-535a07d && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-xiaoduoya-codex-with-chatgpt-535a07d/skill' ~/.claude/skills/skillRestart Claude Code, then type /skill or ask for a matching task and Claude picks it up
ChatGPT desktop app
The ChatGPT desktop app has Codex built in, and Codex reads skills from ~/.agents/skills
Option 1Let ChatGPT install it
Open Codex in the ChatGPT desktop app and paste this sentence into the chat
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Option 2Put the folder there yourself
Put the codex-with-chatgpt folder at ~/.agents/skills/codex-with-chatgpt
~ is your home folder ($HOME)
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.agents/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/xiaoduoya/codex-with-chatgpt.git /tmp/popnx-skill-xiaoduoya-codex-with-chatgpt-535a07d && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-xiaoduoya-codex-with-chatgpt-535a07d/skill' ~/.agents/skills/skill
After installing
- ChatGPT desktop app: open Skills in the sidebar to see that the skill is there
- To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
- Codex picks up newly installed skills by itself; if one does not show up, restart Codex
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
ChatGPT on the web and mobile
Skills you install yourself do not work here; only skills that come with a plugin from the directory
To use this skill with ChatGPT, use the ChatGPT desktop app as above
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
Option 1Let Codex install it
Copy this sentence and paste it into a Codex chat · Works in Codex inside the ChatGPT desktop app, Codex CLI and the IDE extension
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex picks up newly installed skills by itself; if one does not show up, restart Codex · To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.agents/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/xiaoduoya/codex-with-chatgpt.git /tmp/popnx-skill-xiaoduoya-codex-with-chatgpt-535a07d && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-xiaoduoya-codex-with-chatgpt-535a07d/skill' ~/.agents/skills/skillRestart Codex, then ask for a matching task; Codex lists the skill
Option 1Let Cursor install it
Copy this sentence and paste it into a Cursor chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
In Cursor’s Agent chat, type / and pick skill
Checked against official docs Nov 12, 2026 · Source: cursor.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.cursor/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
git clone --depth 1 https://github.com/xiaoduoya/codex-with-chatgpt.git /tmp/popnx-skill-xiaoduoya-codex-with-chatgpt-535a07d && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-xiaoduoya-codex-with-chatgpt-535a07d/skill' ~/.cursor/skills/skillIn Cursor’s Agent chat, type / and pick skill
Option 1Let the AI install it
For other apps that read skills. The sentence gives the paths for Claude Code, Codex and Cursor so the AI picks the one for your app · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs Nov 12, 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com
For Terminal users
Other apps that support Agent Skills (such as Gemini CLI or GitHub Copilot) use different folders. Check that app’s guide, then copy the folder with the SKILL.md there.
Skill folders checked against the official Claude Code, Codex and Cursor guides on Nov 11, 2026
✓ Commands checked Nov 16, 2026
View the original SKILL.md
The text below comes from the maker’s repo, not from PopNx MCP
Showing the first 8,000 characters · Open the full file on GitHub
---
name: codex-with-chatgpt
description: >
Use ChatGPT (web) as the planning and review brain for Codex coding sessions,
while Codex keeps full execution ownership. Use when the user says
"使用 Codex with ChatGPT ..." / "Set up Codex with ChatGPT" / "用 ChatGPT 规划",
when they ask to connect ChatGPT to the current workspace, disconnect it,
or run a task through the ChatGPT planning loop.
---
# 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 / 安全连接 / 配对". The only exception is the
**guided manual ChatGPT setup** below: expose only the exact settings
field labels/values the user must enter, without explaining internals.
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, explicit consent screens, or **guided manual
ChatGPT setup** below — and then give them ONE action.
Before the first ChatGPT connection on this machine, `c2c prefs --json`:
- `setupMode` missing: tell the user exactly `setupChoicePrompt`, wait for
「1」or「2」, then `c2c prefs set --setup-mode auto|manual --json`.
Do not start ChatGPT configuration until they answer. Do not guess.
- `setupMode` is `manual`: skip automatic ChatGPT settings. Use guided
manual from the start (chosen, not a failure).
- `setupMode` is `auto`: automatic browser setup. Two explicit failures of
the same configuration step after repair then enter guided manual.
A browser/js timeout, a page still loading/generating, or waiting for
user login/2FA does NOT count as a failure. Do not change the saved
`setupMode` when falling back.
`developerModeEnabled: true` means skip `#settings/Security` until a
connector create fails because developer mode is required. Then open
that page, enable it, and `c2c prefs set --developer-mode --json`.
These prefs are for this machine, not per workspace. Do not ask again
on reconnect or a second repo. A new computer (empty prefs) asks/checks
once.
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. Conversation reuse depends on `c2c session --json` → `conversation.mode`
(see Conversation management). Do not invent a second mode.
- **long-chat** (legacy session file, or the user opted out): ONE ChatGPT
conversation per workspace. Never silently start a new chat.
- **project** (new workspaces, or an existing workspace that opted in):
ONE ChatGPT Project (collection) per workspace. Same Codex conversation
reuses the ChatGPT chat URL saved in THIS thread. A new Codex
conversation opens a new chat from the Project collection page — never
`goto` `https://chatgpt.com/` to create it, and never reuse another
Codex conversation's chat URL just because `session.url` exists.
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 log in to Cloudflare, then doctor again.
Do not Delete the ChatGPT connector — the address did not change)
- `report.bridge` says 状态无法确认: the local bridge may still be running.
Do not `c2c start`, do not Delete the connector, do not treat it as
`chatgptRepair`. Wait and run doctor again.
If doctor is already green and `chatgptRepair.needed` is false, do not
`c2c restart`, do not start a second tunnel, and do not Delete the
connector. ChatGPT/IAB-only errors are not permission to churn the
public address.
A ChatGPT-side 401 after a sent message is different: repair then, do not
treat it as permission to skip this gate next time.
## In-app browser (ChatGPT)
Official skill: `control-in-app-browser`. These C2C rules override defaults
that close the tab, hide the window, or stall on the settings page.
1. **Surface.** Once per Codex session: `setupBrowserRuntime()`, then
`const iab = await agent.browsers.get("iab")`. Reuse `iab`. Do not re-read
`documentation()` if it is already bound. Never `getDefault()`, `getForUrl()`,
or Computer Use.
2. **One tab.** Create the ChatGPT tab once (`tabs.new()`). After that, only
`tab.goto(...)` to switch URLs. If the tab still exists, claim it — never
open a second ChatGPT tab. Do not `goto` the URL you are already on.
3. **Foreground + keep (standby).** Right after opening or claiming the tab:
- `await (await iab.capabilities.get("visibility")).set(true)` — first-time
setup and ChatGPT chatting stay in front of the user so they can watch.
- `await tab.markHandoff()` immediately, then again at the start and end of
every turn. After setup succeeds or the C2C chat is open, also
`await tab.markDeliverable()`.
Never close this tab. Finished, waiting for the user, or timed out: leave it
marked (standby). Do not let default turn cleanup close it.
4. **URLs only** (same tab, `goto` — never hunt menus):
- 开发人员模式: `https://chatgpt.com/#settings/Security`
(skip when `c2c prefs --json` has `developerModeEnabled: true`)
- 插件总管: `https://chatgpt.com/plugins`
- 加插件: `https://chatgpt.com/plugins#settings/Connectors?create-connector=true&redirectAfter=%2Fplugins`
- 新对话 (long-chat only, and only if no saved chat): `https://chatgpt.com/`
- Saved C2C chat: `conversation.chatUrl` / `session.url` (long-chat, or
the chat already bound in THIS Codex conversation)
- Saved Project collection: `conversation.projectUrl`
(`https://chatgpt.com/g/g-p-…/project`)
Never click ReconnectDiscussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
From GitHub
- GitHub stars
- 7,718
- Maker
- XiaoDuoYa
- License
- MIT
- Last code change
- Oct 1, 2026
- SKILL.md files in the repo (including translated copies and templates)
- 1
- Topics
- ai-agents, chatgpt, codex, mcp, model-context-protocol, oauth