How to get more usage on Codex: make every window count

Why your Codex usage disappears

OpenAI's Codex help article lists what drives usage: the model, where the task runs, task complexity, context, reasoning, speed and tools. In practice, the expensive moments are easy to spot. A feature that touches several files, followed by a few rounds of failing tests, uses far more than an afternoon of questions and small edits. That's where the quota goes, and that's where to act.

1. Hand the heavy builds to XCR

This is the biggest lever: XCR takes on the heavy build work, so your Codex quota goes to planning and review.

XCR is a plugin that connects to Codex and takes over the expensive part of the job:

1. Codex hands the task over. Any request bigger than a small edit (roughly more than 30 lines, or more than one file) goes to XCR.
2. XCR builds it. It writes the change on a copy of your project, runs your project's own checks and repairs failures.
3. Codex reviews. It gets a short report with the requirements done, files changed and check results, and checks the change against your request.

XCR routes each task to models from OpenAI, Anthropic and Google, so one account covers all of them. Checks run on your machine. Code is sent to the model only for the task, and XCR doesn't store it. Quick questions and one-line fixes stay in Codex, exactly as before.

Codex still does what it's best at: understanding the request, choosing the approach and reviewing the diff.

2. One task per thread

Every turn carries the thread's history. Start a new thread when you switch to an unrelated task, and old context stops riding along.

3. Write the whole requirement up front

Drip-fed requirements mean rework. Put the goal, the constraints and how to test it in the first message, and the job is done in one pass.

4. Point Codex at the right files

Name the files, functions and tests that matter instead of asking Codex to search the whole repository.

5. Keep AGENTS.md lean

Codex reads it on every task. Keep it to the rules that change how code gets written.

6. Match the model and effort to the task

Use lighter settings for routine edits and save the strongest model and highest reasoning effort for design questions and hard bugs.

7. Keep an eye on your windows

Open Settings or your usage dashboard, or enter /status in the Codex CLI, to see what's left and when it resets. Plan the big sessions around it.

Official ways to get more Codex usage

When a limit is reached, the limit notice shows what your account can do: add credits, use an available reset, upgrade your plan, or wait for the reset. Eligible Plus and Pro users can buy credits without changing plans. Current limits and options are on ChatGPT pricing. For a full walkthrough of the limits themselves, read Codex usage limit: make your Codex quota last longer.

How to set up XCR in Codex: install and first task

What you need

• Codex installed and signed in on a computer running macOS or Linux.
• Node.js 20 or later. If it's missing, Codex installs it for you and asks before it does.
• A project in a folder on that computer. A git repository works best.

Step 1: Create your XCR account

Open the install page, enter your email and choose Email me a sign-in link. The link arrives in seconds and works for 15 minutes. There is no password, and the same link creates your account the first time.

Step 2: Connect XCR to Codex

1. Open Install on a computer and choose the Codex tab.
2. Read What XCR will change on your computer and tick the box to agree.
3. Click Copy install instruction, paste it into Codex and allow the command when it asks.
4. The command downloads the plugin from xcr.ai and checks its SHA-256 before it runs anything. Your console switches to Connected.
5. Restart Codex.

XCR registers itself as an MCP server in ~/.codex/config.toml and adds one short rule to ~/.codex/AGENTS.md, so Codex hands bigger changes to XCR on its own. Your original files are backed up first, and every change sits between clearly marked XCR lines. The instruction works once, for the next 10 minutes; if it expires, copy it again.

Step 3: Hand off your first task

Once your console shows Connected, ask Codex for something bigger than a small edit, as you normally would:

• "Add CSV export to the orders page, with filters by date and status."
• "Add unit tests for the payment module and make them pass."

Codex hands the job to XCR, and the task appears under Tasks in your console.

Step 4: Review the result

XCR builds the change on a copy of your project and runs your project's own checks (type check, lint, tests). Codex gets back a short report: requirements done, files changed and check results. When the checks pass, the change lands in your working tree without a commit, ready to review in your usual diff. Anything that needs the internet, such as installing packages, comes back for Codex to finish.

Pause XCR anytime with the switch at the top of Overview, or tell Codex "Uninstall XCR from this computer" to remove exactly what XCR added. More detail: XCR quick start and install XCR in Codex.