Codex Usage Limits: How to Check Credits and Tasks

Check your current Codex limits in the Codex Usage Dashboard. During an active Codex CLI session, run /status to see remaining limits. ChatGPT Work follows the same usage structure as Codex, so eligible agent work can draw from the same allowance or credit pool.

How to check Codex usage limits

Where you work	What to do	What it tells you
Codex app or ChatGPT	Open the Codex Usage Dashboard	Your current plan limits and available credits
Codex CLI	Run /status during an active session	Your remaining limits for the active window
ChatGPT Work	Check the same usage dashboard	Work follows the same usage structure as Codex

The dashboard is the source of truth for your account. Availability and limits can vary by plan and workspace, so use the current dashboard and Codex pricing page instead of relying on a fixed task count from an old article.

Quick verdict

If you are trying to do this	Start here	Watch this limit
Research, summarize, draft, or turn scattered work into a finished deliverable	ChatGPT Work	Agentic usage allowance
Fix code, review a repo, run tests, or create a pull request	Codex	Check the Usage Dashboard or /status
Clean data, build a small internal tool, automate a workflow, or create a technical report	Codex inside ChatGPT Work	Task size and session length
Run a serious codebase with local files, scripts, tests, and memory	Claude Code	Your Anthropic plan and local execution setup
Build an AI operating system for recurring work	Second Brain AI plus the right agent	The workflow design, not only the plan limit

The mistake is treating limits as a pricing footnote. Limits shape what you delegate, how you split work, and whether the result is worth the spend.

ChatGPT Work and Codex: what shares usage

ChatGPT Work is designed for longer, multi-step tasks that produce a finished deliverable. Codex remains the dedicated technical workspace for code, repositories, terminals, and developer tools. Both sit inside OpenAI's wider agentic workflow, but they fit different kinds of work.

OpenAI says ChatGPT Work follows the same usage structure as Codex. On eligible plans, usage across Codex, Work, spreadsheet work, and Workspace Agents can draw from the same agentic allowance or credit pool. That does not mean every task costs the same. The plan, model, task size, complexity, and execution environment still matter.

That matters because the search intent is changing. People will ask:

• Is Codex part of ChatGPT now?
• Where do I check my Codex usage limit?
• Does ChatGPT Work use my Codex limits?
• How many Codex tasks do I get?
• Should I use ChatGPT Work or Codex for this job?
• When should I stop using OpenAI and move deep repo work to Claude Code?

Those are buying questions, not trivia questions.

The simple model

Think about the work in three layers.

Layer	What it means	Best tool
Business surface	The work involves documents, meetings, files, research, browser context, and team apps	ChatGPT Work
Technical execution	The work needs code, repo access, scripts, tests, or generated tools	Codex
Operating system	The work needs persistent memory, repeatable workflows, local files, and review loops	Claude Code or Second Brain AI

Most founders will use all three. ChatGPT Work becomes the front door. Codex handles technical tasks inside that front door. Claude Code or a structured Second Brain handles deeper systems that need memory and repeatability.

How Codex usage is counted

Codex usage depends on your plan, the model, the size and complexity of the task, and where the task runs. The current pricing documentation also notes that local messages and cloud tasks share a five-hour usage window. Your dashboard is the practical place to see the limit that applies right now.

A small script can use a small part of your allowance. A larger repo task, long session, or complex model run can use more. That is why you should not plan Codex around a fixed number of tasks.

That means you should not plan Codex like a fixed number of messages.

Plan it like this:

1. Define the outcome.
2. Split the work into verifiable tasks.
3. Use cheaper or smaller runs for exploration.
4. Save expensive runs for execution.
5. Stop the agent when the next step needs human judgment.

This is the same way good operators manage contractors. You do not pay someone to wander. You pay them to finish a scoped task.

ChatGPT Work vs Codex: which one uses the budget better?

Use ChatGPT Work when the work is messy and cross-functional.

Good examples:

• Turn meeting notes, docs, and Slack context into a decision memo.
• Create a first draft of a board update.
• Compare vendors from websites, PDFs, and pricing pages.
• Build a weekly operating brief from connected sources.
• Convert scattered research into a clear plan.

Use Codex when the work has a technical object.

Good examples:

• Fix a bug in a repo.
• Create a script.
• Add a small internal tool.
• Clean a dataset.
• Review code.
• Turn a workflow into automation.
• Generate a spreadsheet model or technical report.

The boundary is the artifact. If the output is a memo, deck, doc, or operating plan, start in ChatGPT Work. If the output is code, a tool, data cleanup, or a technical artifact, use Codex.

For a deeper tool comparison, see Codex vs Claude Code and Claude Code CLI vs Desktop. The right choice depends more on the work object and feedback loop than on a headline task allowance.

The founder workflow I would use

Start every agent task with this five-line brief.

Goal:
Inputs:
Output format:
Definition of done:
Stop conditions:

Example:

Goal: Create a weekly customer insight memo from support tickets.
Inputs: CSV export, product changelog, last week's roadmap notes.
Output format: 1-page memo with themes, quotes, risks, and next actions.
Definition of done: I can send it to the team without rewriting the structure.
Stop conditions: Stop if the data is missing columns or if customer names appear in raw quotes.

This saves usage because the agent does less guessing.

Then route the work:

Step	Tool	Why
Frame the outcome	ChatGPT Work	It can reason across the business context
Create or clean technical artifacts	Codex	It can execute code-like work
Store the repeatable workflow	Second Brain AI	The same task should improve over time
Run deep repo changes	Claude Code	Local tests, files, and memory matter

The real gain comes when the task becomes reusable. A one-off Codex run saves time once. A stored workflow saves time every week.

How to avoid wasting Codex credits

Most wasted usage comes from vague prompts and oversized tasks.

Use these rules:

1. Ask for a plan before execution when the task is large.
2. Give the agent the exact files, URLs, or data source.
3. Require a short diff summary before any broad change.
4. Ask for tests or verification steps in the same task.
5. Split exploration from implementation.
6. Stop after a useful checkpoint.

Bad prompt:

Improve our onboarding.

Better prompt:

Read the onboarding checklist and the last 20 support tickets. Find the 5 most common setup blockers. Return a table with blocker, evidence, fix, and owner. Do not edit files yet.

That second prompt is cheaper because it narrows the job.

When to upgrade, buy credits, or change tools

Upgrade only when the limit blocks a recurring workflow that already saves real time.

Use this test:

Signal	What to do
You hit limits while experimenting	Split tasks better first
You hit limits on one-off curiosity	Do nothing
You hit limits on weekly work that saves hours	Upgrade or buy credits
You hit limits on repo work with lots of local context	Move that loop to Claude Code
A team member burns credits with vague tasks	Fix the workflow brief before buying more

Credits are useful when the workflow is already proven. They are a bad fix for unclear delegation.

Where Second Brain fits

ChatGPT Work and Codex can execute. They do not automatically give your company a memory system.

That is where the Second Brain layer matters.

The compounding system is:

1. Capture the work pattern.
2. Turn it into a repeatable workflow.
3. Store prompts, inputs, outputs, decisions, and review notes.
4. Link the workflow to the right agent.
5. Improve the workflow each time it runs.

If your team is only buying more agent credits, you are renting intelligence. If you capture the workflow, you are building operational memory.

For that layer, start with the AI Chief of Staff workflow. If you want the full operating system around your agents, use Second Brain AI.

FAQ

Where do I check my Codex usage limit?

Open the Codex Usage Dashboard for your current limits and available credits. In an active Codex CLI session, run /status to see the remaining limits for the current window.

Is Codex part of ChatGPT?

Codex is OpenAI's dedicated technical workspace, while ChatGPT includes Chat and Work. They can share the same agentic usage structure when the features are available on your plan, but Codex remains the place for code, repositories, terminals, and developer tools.

Does ChatGPT Work use the same limits as Codex?

ChatGPT Work follows the same usage structure as Codex. Where both features are available, agent work can draw from the same allowance or credit pool. The exact limits depend on the plan and workspace, so check the dashboard for the account you are using.

How many Codex tasks do I get?

There is no single task count that fits every plan and task. Usage depends on the model, task size, complexity, session length, and where Codex runs. Check the Usage Dashboard or run /status in the CLI for the current limit.

Is Codex worth it for non-developers?

Yes, when the work has a technical artifact. OpenAI shows knowledge workers using Codex for reports, spreadsheets, presentations, contracts, automation, data analysis, and lightweight tools. If the work is only writing or synthesis, start with ChatGPT Work.

Should founders use ChatGPT Work, Codex, or Claude Code?

Use ChatGPT Work for broad business delegation. Use Codex for OpenAI-native technical execution. Use Claude Code when the repo, terminal, tests, hooks, memory files, and local workflow are central to the job.

What is the safest way to manage usage?

Scope every task before execution. Define the goal, inputs, output format, definition of done, and stop conditions. Then split large work into smaller checkpoints.

Official sources checked

• OpenAI Help: ChatGPT Work and Codex
• OpenAI Help: Using Codex with your ChatGPT plan
• OpenAI: Codex pricing

Bottom line

ChatGPT Work is the broad work surface. Codex is the technical execution layer. Claude Code remains the stronger deep repo system.

The founder move is to stop treating agent limits as an annoyance and start treating them as an operating design constraint.

Use expensive agent work for scoped execution. Use cheaper thinking for planning. Store the workflows that repeat. That is how you turn usage into compounding advantage instead of another SaaS bill.