A 272K context window means Codex can work with approximately 272,000 tokens of information in one task. This can include your instructions, conversation, files and code. The larger the context window, the more background Codex can consider before older material may need to be compacted. In the Codex CLI, type /status to see the active model and remaining context for the session you are in.
Direct answer: The change matters most for large repositories, long-running agents and multi-stage work. Short, focused tasks are less likely to notice it. Keep important decisions in durable project files, break work into verifiable stages and do not treat one chat thread as the only record of the project.
What changed in the Codex context window?
On 18 July 2026, an OpenAI Codex pull request for the stable0.144 release line said the bundled metadata would keep a 272,000-token context and maximum context window for GPT-5.6 Sol, Terra and Luna. The pull request described these as corrected context-window values.
InfoWorld reported that the configured GPT-5.6 input context in Codex moved from 372,000 to 272,000 tokens. The publication connected the change to concerns about more frequent compaction in large codebases and long-running sessions.
The difference is 100,000 tokens, or approximately 26.9%. That figure describes the change in configured working context reported for Codex. It is not a benchmark score, a model-intelligence score or a universal limit across every OpenAI product.
Why 272K and 1.05 million can both be correct
Context limits are product- and configuration-specific. OpenAI’s current documentation lists different figures for GPT-5.6 Sol depending on where it is used.| Product or surface | Documented context figure | What it means |
|---|---|---|
| Codex stable bundled metadata | 272,000 tokens | Configured context and maximum context values in the referenced Codex update |
| ChatGPT Business, GPT-5.6 Sol | 272K tokens | The current context window listed for this ChatGPT plan and model |
| OpenAI API, GPT-5.6 Sol | 1,050,000 tokens | The model context window listed on the API model page |
What a context window is, and what it is not
A context window is the active working space a model can use for the current request or session. It may contain instructions, conversation history, code, documents, tool results and reasoning material needed to continue the task. When that working space fills, an agent may need to compact, summarise, reload or drop older material to make room for new information. Good compaction can preserve the important thread of a project. It is still not identical to retaining every earlier detail verbatim. A context window is not:- the model’s general intelligence;
- its training knowledge;
- a guarantee that every token will receive equal attention;
- the same as long-term memory or project files;
- a substitute for version control, documentation or review.
How to check the Codex context window
In the Codex CLI, type/status in the current chat. OpenAI’s command reference says this shows the session configuration and token usage: the active model, the approval policy, the writable roots, and the remaining context capacity.
That figure is for the session you are in. It is not your account-wide token history. For account token activity, type /usage.
To keep the context figure on screen, type /statusline, turn on the context items, and confirm. OpenAI says the footer updates immediately and the choice is saved in config.toml under tui.status_line.
/status does not mean every OpenAI product uses 272,000 tokens. The Codex configuration and the API model page can list different limits. Check the product and plan you are actually using.
Why does the Codex 272K limit show up as about 258,400 tokens?
Short answer: 272K is the most Codex takes in by default, and it keeps about 5% of that free as headroom, so the usable space comes out near 258,400 tokens. It is a deliberate default, not a fault, and it is not a second, smaller limit.
A token is a small chunk of text the AI reads, often a short word or part of a longer one. The context window is how many tokens Codex can hold in view while it works on your task. Unblocked, which makes a developer context tool, works the figure out as 272,000 x 0.95, about 258,400, and traces it to a public Codex GitHub issue (#32806) in its Codex context window guide.
Two things are worth knowing if your number looks different:
- Trust your own /status. Type /status in the Codex CLI to see what your session reports today. OpenAI can change the default, so the live figure beats any article, including this one.
- The window can be raised, but you may not need to. Unblocked’s guide shows how to set a 1 million-token window for GPT-5.6 Sol with two settings in the Codex config file. A bigger window is more room, not more intelligence, and the API charges more once a request passes 272K input tokens.
Working on Linux? Codex also comes in OpenAI’s desktop app there now, and our ChatGPT for Linux guide shows how to install it.
Before you chase more room, try the six ways below. A tidier task usually beats a bigger window.
When the 272K Codex context window is most likely to matter
The reduction is most relevant when a task accumulates a large amount of active material, for example:- repository-wide refactoring across many packages;
- migrations that span several services and deployment steps;
- long debugging sessions with repeated logs, screenshots and experiments;
- extended research that combines many documents and web sources;
- multi-day tasks where requirements and decisions evolve;
- agent workflows that call many tools and return large outputs.
Six ways to work within the Codex context window
1. Scope each task around one verifiable outcome
Give the agent a concrete objective, the relevant folder or repository, and a clear definition of done. A focused task reduces irrelevant context and makes review easier. For a large programme, create a sequence of bounded tasks instead of one conversation that tries to hold the entire programme at once.2. Store important decisions in durable project files
Write architecture decisions, product constraints, release gates and naming rules into the repository or project workspace. Use anAGENTS.md, project brief, decision log, runbook or handoff file where appropriate.
Conversation context is helpful. Durable files are inspectable, searchable and available to the next task even when the active window changes.
3. Use checkpoints before the work becomes difficult to reconstruct
Pause after meaningful stages to record what changed, what was verified, what remains open and which evidence supports the next step. A checkpoint should make it possible to continue without rereading an entire conversation. OpenAI’s guidance for long-running Codex work similarly emphasises breaking ambitious goals into verifiable steps and preserving continuity across workstreams.4. Keep tool output selective
Avoid pasting entire logs, repositories or exports when a bounded excerpt, file path or search result will do. Let Codex retrieve the relevant material from the real source when possible. Selective context is not about hiding evidence. It is about keeping the evidence needed for the current decision visible and reducing duplication.5. Commit and test at meaningful boundaries
Version control is external memory with accountability. Small, meaningful commits preserve known-good states, make diffs reviewable and reduce the cost of restarting a task. Do not claim a commit, push or deployment happened unless it was verified. Context management works only when the durable record is real.6. Start a fresh task when the objective changes
If a debugging task becomes a redesign, or a content draft becomes a publishing operation, create a clean handoff and start the new objective with the relevant facts. Carry forward the decisions and evidence, not every line of the old conversation.What business teams should monitor next
The 272K configuration may change again. Model availability, product limits, pricing and agent behaviour can evolve independently. Teams using Codex for important work should monitor:- the Codex version and model selected;
- documented context limits for the actual product and plan;
- how often compaction occurs in long tasks;
- whether important instructions survive checkpoints;
- repeated searches or work that may signal lost context;
- the quality of project files, handoffs and version history.
Frequently asked questions about the Codex context window
What does Codex 272K mean?
It means Codex can hold about 272,000 tokens of your instructions, conversation, files and tool output in view at once by default. A token is a small chunk of text, so this is a working-space limit, not a measure of how clever Codex is.
Why does Codex show 258,400 when the limit is 272K?
Codex keeps about 5% of the 272,000 default as headroom, which leaves roughly 258,400 usable tokens, according to Unblocked’s guide to the Codex context window. Type /status to see the figure your own session uses.
How do I check the context window in Codex?
In the Codex CLI, type /status. It shows the active model and the context left in that session. Type /statusline to keep the context figure in the footer, and /usage for account-wide token activity, which is a different number.
Can I make the Codex context window bigger?
Yes, in some setups. Unblocked’s guide to the Codex context window shows how to set a 1 million-token window for GPT-5.6 Sol in the config file. A bigger window is not smarter, and the API charges more above 272K input tokens, so first try smaller tasks and saved project notes.
Did GPT-5.6 become less intelligent?
There is no evidence in the cited update that GPT-5.6’s reasoning capability was reduced. The documented change concerns configured context metadata. A smaller active context can affect continuity in long sessions without being the same as lower intelligence.
Is the GPT-5.6 context window always 272K?
No. OpenAI currently lists 272K for GPT-5.6 Sol in ChatGPT Business and in the referenced Codex metadata, while the GPT-5.6 Sol API page lists a 1.05-million-token context window. Check the product, plan and current documentation.
The practical takeaway
The Codex context window change is a workflow signal, not a crisis, and not a reason to abandon long-running AI work. You don’t need to memorise token counts to act on it. Treat the active conversation as working space, not the only source of truth. Keep the objective focused, store decisions durably, verify in stages and preserve real project history. Ankor Business Solutions builds practical, human-guided AI business systems for clearer operations. If your team needs a more durable way to organise decisions, responsibilities and AI-assisted workflows, start with the AI business tools overview, compare Ankor Nexa, or browse the current shop. Curious whether ChatGPT can describe your own business correctly? Ask for a free AI visibility check.Ankor tips
Stay in the loop
Practical AI tips for small businesses and the odd product update. No spam, unsubscribe any time.