OpenAI Codex in 2026: features, plans, and practical trade-offs
MarkdownA product overview of Codex execution surfaces, dated plan and model details, permissions, usage limits, and a practical first pilot.
Read full article
This product overview explains where Codex runs, what its plans include, and which limits and permission settings to check in your own project. It uses the official product pages cited below, with prices and model details recorded as of October 4, 2026. It is not a dated collection of user reviews or a measured survey of satisfaction.
First, let me clarify what we’re talking about, because this is a common source of confusion. Codex is an AI coding agent from the same OpenAI that makes ChatGPT. It digs through your files, edits them, and runs commands, while you watch and say “yes” or “try again.” If you first want to understand how an agent itself works, there’s a separate explainer, what an AI agent is, in plain language, and how to install Codex from scratch is shown in what it is and how to launch it. This article focuses on practical product choices rather than installation or a review survey.
Ailoot documentation: API, keys, and setup.
What is Codex, and why does the version matter?
Key points
Codex is a coding agent from OpenAI. It runs in the terminal, in an editor extension, in the cloud, and in a desktop app. The product has changed repeatedly: models, command approval behavior, and pricing have changed. Check the version and date behind any comparison before applying it to your installation.
OpenAI has reused the name Codex before, and that’s the first source of confusion: the old Codex from 2021 was a code-completion model, and support for it ended in March 2023. The current Codex is a separate product, an agent: it edits project files and runs commands on its own.
The Codex CLI open-source code is on GitHub under the Apache-2.0 license: as of October 4, 2026, the repository has 127,810 stars and 20,010 forks (GitHub API data, checked for this article). The project changes actively, which explains the second source of variation in reviews: over the past year, Codex has gone through several model changes—from GPT-5-Codex to the GPT-5.6 family, and in fall 2026 to GPT-6. A comparison of one version may not describe another. The product snapshots below are dated where relevant; there are no attributed user quotations or issue case studies in this overview.
Which Codex features are useful to evaluate?
Key points
Three product features are worth checking on your tasks. First, Codex is included in a ChatGPT subscription, so there’s no need to pay separately. Second, it works in several places: the terminal, editor, cloud, and phone, so you can start a task on your computer and check the result on your phone. Third, it offers GitHub pull-request review, whose findings you should verify with a reproducing test.
The inclusion in ChatGPT plans lowers the barrier to trying the product. Codex isn’t sold as a separate subscription: it’s included in every ChatGPT plan, from the free Free plan to Pro.
Another practical feature is the range of places where it can run.
Which limits and permission settings should you check?
Key points
Check three things in a representative pilot: whether approval prompts fit your workflow, whether the plan’s usage limits cover the session, and whether a complex task reaches a verifiable result. This overview does not provide a measured complaint ranking or specific issue reports.
Inspect the approval and sandbox settings before the pilot. Record the exact command and permission prompt if behavior differs from what you expected, rather than assuming a generic issue applies to your setup.
Check remaining usage and reset windows before a long task; a low entry price does not make usage unlimited.
On complex tasks, define a small working result and run its tests before expanding scope.
Figuring out what goes into the agent’s context so it stays on task and doesn’t lose the thread is exactly what’s called context engineering. The tool, whether Codex or Claude, is secondary: what makes the biggest difference to the result is what the agent is given as context.
Codex prices and plans for October 2026
Key points
There’s no separate Codex subscription; it’s included in ChatGPT plans. As of October 4, 2026: Free—0 dollars, Go—8 dollars, Plus—20 dollars per month, Pro—from 100 dollars (there are $100, $200, and $500 tiers). The business plan with Codex starts at 20 dollars per user per month with annual billing. Model codes and credit rates were checked on OpenAI’s official pricing page.
Here is the dated plan snapshot from OpenAI’s official pricing page (developers.openai.com/codex/pricing, checked 04.10.2026):
| Plan | Monthly price | What’s included |
|---|---|---|
| Free | 0 dollars | limited access, try it on short tasks |
| Go | 8 dollars | light use, a few tasks per day |
| Plus | 20 dollars | Codex on the web, CLI, IDE extension, and iOS, plus cloud background tasks |
| Pro | from 100 dollars | $100 / $200 / $500 plans, access to Astra Ultrafast on $500 |
| Business | 20-25 dollars per user per month | from 2 users; annual billing is 20 $, monthly billing is 25 $ |
| Enterprise / Edu | by contract | credit-based pricing, custom terms |
The billing model changed on April 2, 2026: OpenAI dropped the old “message” limits and switched to credits tied to tokens, as in the API. Current rates from the official pricing page: GPT-6 Astra—250 credits per 1M input tokens and 1,250 per output tokens; GPT-6.1 Sol—50 and 250; GPT-6 Luna—2.5 and 12.5. These are Standard rates; purchased credits and Fast mode cost more (Fast—2x, Astra Ultrafast—6x the standard rate).
Practical takeaway: if you already pay for ChatGPT Plus for chat, Codex comes at no extra charge. You can also start with Free to try it out. Consider switching to Pro when Plus limits start getting in the way of your daily work.
Models currently available in Codex
Key points
After the GPT-6 family launched, the recommended model for complex tasks is GPT-6.1 Sol, GPT-6 Luna is for fast, repeatable tasks, and GPT-6 Astra remains available for the most demanding scenarios. GPT-5.6 Sol, Terra, and Luna are still available in parallel during the transition. The CLI uses gpt-6.1-sol with medium reasoning by default. Switch models with the /model command.
This is the most noticeable change since summer 2026: Codex moved from the GPT-5.6 family to GPT-6. According to the official Codex model documentation (developers.openai.com/codex/models, checked 04.10.2026), three models are recommended now:
- GPT-6 Astra—the most capable model for complex work: coding, applications, research, and extended reasoning.
- GPT-6.1 Sol—a model close to Astra in quality for repeatable, long-running work, at a lower credit cost. It’s the default in fresh CLI installations (
model: gpt-6.1-sol medium, according to the official terminal screentest on the same page). - GPT-6 Luna—the most economical model for clearly defined, high-volume tasks: data extraction, classification, and structured summaries.
The model page also says that GPT-5.6 Sol, Terra, and Luna “remain available during the rollout”—the old generation was given time to transition instead of being shut off abruptly. Older models, however, are being retired on a schedule: GPT-5.4 and GPT-5.4-mini were turned off in Codex on August 31, 2026; GPT-5.3-Codex-Spark on September 14, 2026; and GPT-5.5 is scheduled to go on October 14, 2026, according to the same documentation. If one of these models is still in a saved configuration, it should be replaced with an available one; otherwise, tasks will start failing with an error after the shutdown date.
You can switch the model and reasoning depth on the fly with the /model command in the terminal. The advice still holds: don’t keep the maximum reasoning level on for simple edits—it uses credits without improving quality. Heavy mode makes sense for a heavy task.
Codex CLI, editor extension, or cloud—where should you run it?
Key points
There are several ways in. Codex CLI runs in the terminal, is installed with the npm install -g @openai/codex command, and suits people who are comfortable with the command line. The editor extension puts Codex in the familiar VS Code window. The cloud version runs in a browser inside ChatGPT and suits long background tasks. There’s also a desktop app for macOS and Windows.
Codex has several ways into the same product, so there’s plenty to choose from.
Codex CLI runs in the terminal. It’s installed with one command, which is current as of October 2026 according to the official CLI page (developers.openai.com/codex/cli):
npm install -g @openai/codex
Next, run codex in the project folder. It’s a good idea to start with /init: Codex creates an AGENTS.md file with instructions about the project, then uses it so it doesn’t have to guess from scratch each time.
The editor extension puts Codex in the VS Code window. For most people, this is the easiest way in: the code is in front of you, the agent is alongside it, and everything is in one place.
The cloud version runs in a browser inside ChatGPT. It’s useful for long tasks: you hand off the task, close the tab, and Codex works on its own on OpenAI’s servers; you pick up the result later. There’s a desktop app for macOS and Windows, and a phone app for checking a task’s status from the couch.
Who should try Codex, and what should a pilot check?
Key points
Codex is worth trying if you already have ChatGPT access and want terminal, editor, or cloud workflows. Verify the permission settings and remaining usage in a short pilot before relying on it for daily work. Those are practical selection criteria, not a conclusion drawn from a review sample.
If you already pay for ChatGPT, start with a small task using the included access. Choose one observable result: a script that handles a real input, a bug reproduced and fixed by a test, or a pull-request finding you can verify.
Check the command approval behavior and usage consumed during that pilot. For an agent comparison, use the same starting commit and acceptance criteria; see Codex vs Claude Code and migrating from Claude Code to Codex.
Frequently asked questions
Do you have to pay separately for Codex apart from ChatGPT?
No. Codex is included in every ChatGPT subscription, including the free one. There’s no separate Codex bill. As of October 2026, the plans are: Free—0 dollars, Go—8 dollars, Plus—20 dollars, Pro—from 100 dollars (developers.openai.com/codex/pricing).
Is Codex better than Claude Code?
This overview does not establish a winner. Compare both tools on the same repository task, starting commit, and acceptance criteria, and include time spent checking the output and steering the agent. For a detailed comparison, see the separate article “Codex vs Claude Code.”
Which model is the Codex default now?
After the move to the GPT-6 family, the CLI uses GPT-6.1 Sol with medium reasoning by default. GPT-6 Astra is available for demanding tasks, and GPT-6 Luna for high-volume and simple ones. Switch models with the /model command (developers.openai.com/codex/models, checked 04.10.2026).
How do I install Codex CLI?
Codex CLI is installed with one command in the terminal: npm install -g @openai/codex. After installation, run codex in the project folder. First, it’s a good idea to run /init so Codex creates an AGENTS.md file describing the project.
What should I inspect before a long Codex task?
Check the approval settings, remaining usage, and the task’s acceptance criteria. Run a short pilot first and save the result and usage record; this article does not rank complaints from a user-review sample.
Sources
If you need access to AI models through Ailoot, explore Ailoot.
More details
Questions about OpenAI Codex features and practical use
Does this overview establish what most Codex users think?
No. It explains the product and dated plan details, without a defined review sample or attributed user quotations. Use it to select a pilot, and inspect specific dated reviews or issues separately before drawing conclusions about prevalence.
What should I verify in a first Codex task?
Choose one small result, inspect its diff, and run a reproducing test or real-input check. Record the approval prompts and usage consumed so you can judge whether the workflow fits your project and plan.