← Home

OpenAI Reduces Codex Model Context Size from 372k to 272k Tokens, Frustrating Developers

The Facts

OpenAI quietly reduced the Codex model's context window from 372,000 to 272,000 tokens — a roughly 27% cut. The change was first noticed by developers who observed an abrupt drop in the model's ability to process large codebases in a single session. As of this writing, OpenAI has provided no official explanation for the reduction.

Codex is the engine that powers several GitHub Copilot features, including the ability to analyze entire repositories for more contextually accurate suggestions. The larger context window — which allowed the model to effectively "read" roughly 372,000 tokens of code at once — was a key selling point for development teams working with complex, interconnected codebases.

Context

A language model's context window determines how much information it can process at one time. For developers using Codex to analyze full source code, a larger window meant the ability to understand an entire project's architecture before suggesting changes or generating new code.

The 100,000-token reduction represents a significant loss — equivalent to tens of thousands of lines of code that must now be broken across multiple calls. The impact is especially acute for monolithic projects or refactoring tasks that require a holistic view of the codebase.

Analysis

Reducing the context window without prior communication or explanation erodes developer trust. In an ecosystem where OpenAI already faces growing skepticism about its governance practices — especially after unilateral changes to service terms and moderation policies — this silent downgrade is particularly poorly received.

The reduction suggests OpenAI is prioritizing cost and latency over capability. Maintaining larger context windows requires more GPU memory and compute per request, which pressures operating margins. For a company seeking a path to profitability, cutting context is a lever — but for developers, it's a genuine regression that breaks established workflows.

What to Watch

The developer community's reaction will be the key barometer. Migrations to alternatives like Claude Code (Anthropic), Gemini (Google), or local models like Llama 4 and Qwen 3.8 may accelerate. OpenAI may be forced to reverse the decision or offer a paid tier with a larger context window. The episode also reignites the debate about the risks of depending on proprietary APIs for essential development tooling.

Source: Hacker News