AIToday
Large Language ModelsAI Coding AssistantsZenn AI/MLPublished: Oct 28, 2026, 13:00 JST

Day 12: Tibo Sottiaux adds cache reuse to Codex

Send on LINE
Day 12: Tibo Sottiaux adds cache reuse to Codex

3 Key Points

  1. What happened

    Tibo Sottiaux announced Day 12 changes for Codex and ChatGPT Work: context reuse across subagents, longer cache retention, and routing that raises cache hit rates for more work per plan.

  2. Why it matters

    The changes cut redundant re-processing of shared context, so the same plan allowance may stretch to more tasks. The exact savings and multiplier were not disclosed.

WHO IT HITSDevelopers and teams running multi-agent Codex or ChatGPT Work tasks with long shared context, such as repository-wide reviews, may see more tasks completed within the same plan limits.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, every morning.

Context & Analysis

The Day 12 update sits inside OpenAI's "28 days, daily improvement or full reset" program. Previous days addressed different bottlenecks: Day 7 expanded the standard context window from 272K to 500K, and Day 11 reduced capacity-shortage errors and added automatic continuation. Day 12 targets a third problem — the repeated processing of identical context — by reusing context across subagents, holding caches longer, and routing requests to machines that already hold the relevant cache.

The practical effect depends on workload shape. Tasks that share long specifications or repository rules across several subagents stand to gain the most; tasks where each subagent works on entirely separate context may see little change. Because OpenAI did not publish hit-rate or savings figures, users comparing before and after should control for model, context size, subagent count, and task difficulty rather than relying on a remaining-usage percentage alone.

Separately, the GPT-6 Astra Pro update for the Chat tab on Pro plans adds parallel agents with progress tracking and artifact review. That is a different surface from the Codex and Work cache improvements, and the two should not be read as one combined quota change.

FAQ
Does Day 12 double the weekly usage limit?
No. OpenAI did not announce a 2× increase. It said the changes increase the effective usage you get, without specifying a multiplier.
Is the GPT-6 Astra Pro parallel-agent update the same as the Codex cache changes?
No. The cache changes target Codex and ChatGPT Work efficiency, while the GPT-6 Astra Pro update is for the Chat tab on individual Pro plans.
Do I need to change API settings to benefit?
No special API parameter was announced for Day 12. For GPT-5.6 and later, cache routing is handled automatically and prompt_cache_key is not required.
Send on LINE

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleAnthropic: best of a flawed field, yet 'insufficient'