OpenAI Quietly Cut Codex Context Window by 27 Percent: Why Provider-Specific Limits Are Not a Contract

In mid-2026, OpenAI reportedly imposed an unannounced server-side 272K-token context cap on its Codex CLI, reducing the previously documented roughly 372K-token capacity by about 27% despite the underlying GPT-5.6 Sol model supporting larger contexts. Developers identified the change through failed or truncated long-context operations, community reports, and configuration values, highlighting that provider specifications such as context limits, pricing, and rate limits may change without version updates or public notice. The account argues that organizations should avoid hardcoding these limits, instead validating available capacity at runtime, designing prompts and workflows to degrade gracefully when content must be truncated, monitoring token use and error rates for changes, and using provider-agnostic gateway layers to enable fallback across AI services. It also calls on providers to publish configuration changelogs, offer transition periods for reduced limits, and provide APIs that expose current runtime constraints.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.