Skip to content

Codex access guide

Codex Blocked, Suspended or Out of Usage? Read the Notice First

Sources checked November 18, 2026. An independent guide by Cue. OpenAI handles account, seat, usage and billing decisions.

Codex is OpenAI's coding agent. You can use it in the terminal (CLI), the IDE extension, the ChatGPT desktop app, or cloud tasks. Access can stop for different reasons, and each reason has a different owner and fix. Read the notice first, then match it to the table below.

Published · Cue editorial team

Read the notice first

Save the exact message, the time you saw it with your time zone, the surface you were using (CLI, IDE extension, desktop app, or cloud), and whether you signed in with a personal or a workspace account. A sign-in error alone does not tell you why access changed. OpenAI separates warnings from restrictions: "A warning does not, by itself, mean your account has been suspended or closed." Source: OpenAI account warnings, safety suspensions, and closures.

Match the notice to the right next step

What you seeWhere to start
Temporary safety suspensionFollow the suspension notice. To request review, use the appeal link in the suspension email. If you received two notices, use the link for the decision you want reviewed.
Permanent account closureUse the appeal link in the closure email. If you cannot access it, use the OpenAI appeal form. A review request does not guarantee restoration.
Warning, and you can still use CodexRead the cited policy and any deadline, and stop the activity at issue. Per OpenAI, continued violations after a warning may lead to further restrictions or closure.
Workspace seat removed, or Codex missing in a workspaceUNKNOWN: we did not find an official page describing the seat-removal notice. Ask your workspace administrator to check your role and Codex access. OpenAI notes that for Enterprise, cloud access is off by default unless enabled, and that workspace admins manage member controls.
Usage limit reachedCheck which allowance is used up and any reset time shown. In an active Codex CLI session, enter /status. OpenAI says you can wait for the reset, upgrade your plan, or buy credits where eligible.
Sign-in fails, or Codex Cloud is not availableSign in with your ChatGPT account in the client you use. OpenAI states that Codex Cloud is not included with Free or Go. If the desktop app asks you to add or verify a phone number, follow the plan guide.
"Deleted or deactivated" messageCheck OpenAI's deleted or deactivated account guidance. Per that page, a deleted account cannot be reactivated, and a deactivated account may need identity verification.
Unfamiliar activity or chargesChange your password, rotate any exposed API keys, and follow OpenAI's unrecognized activity guidance. Contact [email protected] if you cannot reach your account.

What OpenAI's pages say about Codex access and usage

We read these pages on November 18, 2026. Quotes are from the pages; check them again before relying on them.

  • Codex is included across ChatGPT plans, including Free and Go. Codex Cloud is available to eligible Plus, all Pro tiers, Business, Enterprise, Healthcare, and Education accounts, subject to rollout and workspace settings, and is not included with Free or Go. Usage limits vary by plan. Source: Using Codex with your ChatGPT plan.
  • Auto-review safety checks are free when signed in with a ChatGPT account and do not count toward plan usage limits. They do not remove your workspace's restrictions. Source: the same plan article.
  • The usage-limits page states that starting in December, "Plus, Pro, and Business plans' usage allowance will be shared across ChatGPT and Codex," and that combined remaining usage appears in Settings → Usage. Source: Understanding ChatGPT and Codex usage limits.
  • Specific limits, rates, and credit amounts: UNKNOWN from these pages. Do not rely on third-party figures. Check your own Settings → Usage and the plan pages.

Copy this appeal template

Fill in facts you can verify, and delete lines that do not apply. Share identifiers only through official support. Redact unrelated personal and client details from screenshots. Never include a password, verification code, API key, or full card number.

Subject: Request to review my Codex [suspension / closure / warning]

Account email: [official private support only]
Notice or reference: [relevant excerpt, or "no notice received"]
First observed: [date, time and time zone]
Affected surface: [Codex CLI / IDE extension / ChatGPT desktop app / cloud]
Account type: [personal / workspace]
User or organization ID: [if available]
Facts to review: [what happened and why you are requesting review]
Possible unauthorized activity: [date range, or "unknown"]
Steps taken: [only actions already completed]

Please review this decision and tell me which official process to use
if you need more information. Thank you.

Save the case number and confirmation. Add new facts to the same case when possible. An appeal is a request for review; OpenAI states that requesting a review does not guarantee restoration, and no response time is guaranteed.

Separate account access, data and billing

  • Data: Export steps for Codex data were UNKNOWN in the pages we checked. For workspace data, ask the workspace owner or administrator.
  • Billing: Check the receipt to see who billed you. Manage App Store or Google Play subscriptions in that store. For refund or cancellation questions during a temporary suspension, OpenAI directs you to [email protected]. Cancellation, refunds, and review are separate steps.

Keep your work portable: handoff file

Before you stop, save a Git checkpoint. OpenAI's IDE guide recommends creating Git checkpoints before and after a task so you can revert changes. Then write a short handoff file so you can continue in another approved tool:

Goal: [the Codex task to finish]
Surface and account type: [CLI / IDE / desktop / cloud; personal / workspace]
Repository and branch: [name; last commit ID]
Done so far: [verified changes, with file paths]
Decisions made: [approved decisions only]
Open questions: [unknowns]
Commands to re-run: [exact commands and expected results]
Do not include: passwords, API keys, tokens, or client data you may not share
Next action: [one concrete step]

Share only excerpts you are allowed to share, and do not invent owners, dates, or results.

Reduce preventable problems

Use your own approved seat, and do not share accounts or API keys. OpenAI notes that sharing accounts or API keys in ways that violate its terms may lead to closure. Check /status or Settings → Usage before long tasks. Respond to verification deadlines promptly. Keep a project file with the goal, decisions, open questions, and next steps so the work can move if access changes.

One desktop AI agent for different everyday workflows. Use Cue to work with authorized documents, notes, and tasks, with Claude and GPT model options. Check Cue's plan details and your account for available models and allowances. Cue's terms and applicable model-service rules still apply. Codex appeals, workspace decisions, billing, and history for your OpenAI account stay with OpenAI.