codex - 💡(How to fix) Fix Support for Extended Prompt Cache Retention Policy [1 comments, 2 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openai/codex#18130Fetched 2026-04-17 08:32:21
View on GitHub
Comments
1
Participants
2
Timeline
7
Reactions
2
Timeline (top)
labeled ×4unlabeled ×2commented ×1
RAW_BUFFERClick to expand / collapse

What variant of Codex are you using?

CLI, App-Server

What feature would you like to see?

/v1/responses API supports Extended Prompt Cache Retention Policy, which allows the prompt cache of a thread to be retained up to 24 hours in storage via the API, as opposed for 10-15 mins in memory. This is available for API users, but it would be nice if subscription backend supports it to have this option in codex.

Additional information

No response

extent analysis

TL;DR

Implementing Extended Prompt Cache Retention Policy support in the subscription backend for Codex may require updates to the backend API to match the existing /v1/responses API functionality.

Guidance

  • Review the documentation for the Extended Prompt Cache Retention Policy to understand its requirements and limitations.
  • Investigate the current implementation of the subscription backend to determine what changes would be needed to support this policy.
  • Consider reaching out to the API development team to discuss potential integration points and requirements.
  • Evaluate the potential benefits and trade-offs of implementing this feature, including any potential performance or storage impacts.

Notes

The issue lacks specific technical details about the current implementation and requirements, so a more detailed solution cannot be provided.

Recommendation

Apply workaround: Implement a custom solution to cache prompts in storage for a longer duration, as the existing API already supports this feature, but it may require additional development and testing to integrate with the subscription backend.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

codex - 💡(How to fix) Fix Support for Extended Prompt Cache Retention Policy [1 comments, 2 participants]