# AI use cases for Codex with ChatGPT (XiaoDuoYa/codex-with-chatgpt)

Repo: [XiaoDuoYa/codex-with-chatgpt](https://github.com/XiaoDuoYa/codex-with-chatgpt) | Use cases: 3 | Page: https://dedupedai.com/use-cases/xiaoduoya-codex-with-chatgpt/

A bridge that lets Codex use the ChatGPT web app as its planning and review brain, while Codex keeps doing the code execution.

This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL.

- Plan a coding task in ChatGPT before Codex edits: https://dedupedai.com/use-cases/xiaoduoya-codex-with-chatgpt/plan-with-chatgpt-before-codex-edits/
- Have ChatGPT review Codex changes without uploading the repo: https://dedupedai.com/use-cases/xiaoduoya-codex-with-chatgpt/review-codex-changes-with-chatgpt/
- Keep .env and key files out of ChatGPT reviews: https://dedupedai.com/use-cases/xiaoduoya-codex-with-chatgpt/keep-secrets-out-of-chatgpt-reviews/

## How to plan a coding task in ChatGPT before Codex edits with Codex with ChatGPT

Repo: [XiaoDuoYa/codex-with-chatgpt](https://github.com/XiaoDuoYa/codex-with-chatgpt) | Difficulty: Beginner | Time: 30 minutes | Basis: From the README

Use your ChatGPT web plan for reasoning while Codex keeps all the editing.

**Who it is for:** A developer on a ChatGPT Plus or Pro plan whose Codex token budget runs low because planning and review use up so much of it.

**The problem:** Planning and review consume scarce Codex tokens, while the ChatGPT web quota you already pay for sits idle.

**The outcome:** ChatGPT plans the change using read-only access to your current workspace, and Codex carries out the edits.

### Steps

1. Install Node.js 20 or newer, git, and cloudflared.
2. `git clone https://github.com/XiaoDuoYa/codex-with-chatgpt ~/codex-with-chatgpt` (inferred, check the README)
3. In the checkout folder, run `corepack pnpm install` and then `corepack pnpm build`.
4. Copy skill/SKILL.md into the skills folder under your Codex home, in a Codex with ChatGPT subfolder, and set the checkout path inside the file.
5. Run `c2c setup`, log in to ChatGPT in the built-in browser, and enter the pairing code.
6. In Codex, ask: "Use Codex with ChatGPT to implement <task>."

### Prompt to paste into your agent

```text
Install the repo XiaoDuoYa/codex-with-chatgpt, run corepack pnpm install and corepack pnpm build, then run c2c setup and pair it with ChatGPT. Use the Codex Skill to have ChatGPT plan <task>, and report the final checklist to confirm the file read test passed.
```

### Caveat

The README calls this an unofficial community project that is not affiliated with or endorsed by OpenAI, and it describes itself as V1.

Risk, credentials: You log in to ChatGPT yourself, and the pairing code is the only secret that touches a browser, so keep it private.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/xiaoduoya-codex-with-chatgpt/plan-with-chatgpt-before-codex-edits/

## How to have ChatGPT review Codex changes without uploading the repo with Codex with ChatGPT

Repo: [XiaoDuoYa/codex-with-chatgpt](https://github.com/XiaoDuoYa/codex-with-chatgpt) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Send ChatGPT only the workspace lines it needs to review what Codex wrote.

**Who it is for:** A developer who wants a second, independent review of Codex's changes but does not want to upload the whole repository.

**The problem:** Reviews done by the coding agent itself use up the same scarce token budget, and uploading a full repo is not wanted.

**The outcome:** ChatGPT reads only the specific lines it needs through the read-only bridge and returns a review that Codex can act on.

### Steps

1. Complete the setup in the first use case so the bridge and ChatGPT connector are running.
2. Make or keep the Codex changes you want reviewed in the workspace.
3. Ask Codex: "Use Codex with ChatGPT to review <change>."
4. Check the review in ChatGPT, then ask Codex to apply only the fixes you accept.

### Prompt to paste into your agent

```text
In the workspace at <workspace path>, with the codex-with-chatgpt bridge running, ask Codex to use ChatGPT to review the changes for <change>. Report the review findings and confirm that Codex made no edits without approval.
```

### Caveat

The README says ChatGPT reads selected lines through the bridge rather than the whole repo, but it does not give a full list of what leaves your machine, so check your own sensitivity needs.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/xiaoduoya-codex-with-chatgpt/review-codex-changes-with-chatgpt/

## How to keep .env and key files out of ChatGPT reviews with Codex with ChatGPT

Repo: [XiaoDuoYa/codex-with-chatgpt](https://github.com/XiaoDuoYa/codex-with-chatgpt) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Use the default sensitive-file rules plus your own .c2cignore patterns to protect secrets.

**Who it is for:** A developer working in a repo with .env files, keys, or credentials who wants ChatGPT reviews without exposing those files.

**The problem:** Reviews could expose secrets if the bridge can read them, and the default rules may not cover every file type your project uses.

**The outcome:** Sensitive files stay out of ChatGPT's reach, and your own project-specific patterns are added to the rules.

### Steps

1. Confirm the default rules: `.env*`, keys, SSH, and credentials are denied, and `.env.example` is allowed.
2. Add your own patterns for other sensitive files to `.c2cignore` in the workspace root.
3. Run `c2c status` to confirm the bridge is running for this workspace.
4. Run `c2c doctor` to check the setup. (inferred, check the README)
5. Ask Codex to use Codex with ChatGPT to review a file, and confirm that no ignored file is read.

### Prompt to paste into your agent

```text
In the workspace at <workspace path>, add the pattern <pattern> to .c2cignore, then run c2c status and c2c doctor and report their output. Confirm that the sensitive-file rules still deny .env files.
```

### Caveat

The README lists the default denied file types but does not describe the exact .c2cignore syntax, so check the docs before you rely on a complex pattern.

Risk, credentials: Your own .c2cignore patterns are only as complete as the ones you write, so review them before sharing any repo with ChatGPT.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/xiaoduoya-codex-with-chatgpt/keep-secrets-out-of-chatgpt-reviews/