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

OpenAI adds 12-hour prompt cache for GPT-5.6+ API

Send on LINE
OpenAI adds 12-hour prompt cache for GPT-5.6+ API

3 Key Points

  1. What happened

    OpenAI's Day 16 release lets Responses API users set prompt_cache_options.ttl: "12h" on GPT-5.6-and-later models, while logged-in Codex and ChatGPT Work users get guaranteed cache hits when resuming past conversations, per Tibo Sottiaux.

  2. Why it matters

    The change targets work that is paused and picked up hours later, letting developers and Codex users avoid reprocessing the same long context; API cache hits are not guaranteed per request, and the 12-hour window is a minimum retention period, not a deletion deadline.

WHO IT HITSDevelopers building on the Responses API and teams using Codex or ChatGPT Work for long-running coding tasks stand to benefit most, as resuming a session hours later may no longer mean paying to reprocess the same context from scratch.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, every morning.

Context & Analysis

Day 16 sits inside OpenAI's 28-day shipping cadence and follows a run of changes aimed at long-context work. Day 7 raised GPT-6.1 Sol's standard context from 272K to 500K tokens, and Day 12 improved context reuse and routing between sub-agents. Day 16 shifts the focus from capacity to persistence: keeping a reusable cache alive across hours-long gaps, both through an explicit API setting and through a product-level guarantee for logged-in Codex and Work users.

The two halves of the announcement are governed by different rules. The API option is a TTL choice that offers reuse opportunities but does not promise a hit on any individual request, while the Codex / Work guarantee describes the experience of returning to an old thread. Existing users should also note that the new prompt_cache_options.ttl parameter is not the same as the older prompt_cache_retention used by earlier models, so a "12h" value cannot simply be passed to the old field.

The practical effect depends on usage patterns. A long shared prefix reused at wide intervals can make the higher write cost worthwhile, but frequent use within 30 minutes may favor the default. Cost measurement still hinges on the usage breakdown, since cached tokens continue to count toward the TPM rate limit.

FAQ
Is the 12-hour cache option available on all OpenAI models?
No. The ttl setting applies to the Responses API on GPT-5.6-and-later models; it cannot be applied as-is to all older models or the Chat Completions API.
Does the 12-hour setting mean my cached data is deleted after 12 hours?
No. TTL: "12h" is a minimum retention period, and OpenAI may retain the cache longer; it is not a deletion deadline or a change to data-retention policy.
How many reuses make the 12-hour cache cheaper than the default 30-minute cache?
Under a simplified assumption where the 30-minute cache expires every 30 minutes, the 12-hour option becomes cheaper from three uses onward.
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'