Codex 28 · Theme · #97
Cached input persists across breaks
3people describe this
3 on X
X replies to the promise post are counted apart from Rantr votes. “This happened to me too” adds your browser to this theme on Rantr, once.
Where OpenAI stands
Not addressed yetNo recorded announcement has answered this yet.
In their words
What people said
- Problem
seems that after long pauses the cache still expires?
@baggiiiie on X ↗ · 23 Oct 2026
- Problem
Hey @thsottiaux, I'm logged into Codex but still see 0% cached input after breaks in chats created after your announcement - same model, no visible instruction changes. Is “cache forever” live? OpenAI's support bot says caching isn't permanent.
@MMadrzak on X ↗ · 22 Oct 2026
- Problem
@thsottiaux “Guaranteed to hit the cache” isn’t what my logs show. Codex Desktop 0.163.0-alpha.10.2, logged in, today: • 37 min idle → 89% cached • 56 min idle → 0 of 258k cached • <1 min gap → 0 of 315k cached The last can’t be TTL. Fully rolled out yet? Logs available
@Shermanaetor on X ↗ · 21 Oct 2026
Your experience
Had this too? Say what happened.
JEV reads your words as you type and shows which theme they belong to. It may place them in another theme if that fits better.
Status
Where OpenAI stands
“Shipped” means an announcement was linked to the theme by AI, not that the problem is fixed for everyone. “Not addressed yet” means no recorded announcement was linked; it is not proof that nothing changed.
No recorded announcement has been linked to this theme yet.
Share
Share this theme
Follow
Follow this theme by email
We send a confirmation link first; nothing else is sent until you confirm. Then at most one email a day, only when the theme changes.
X thread: 2769 replies to the promise post collected (4 Oct 2026 – 26 Oct 2026): 2555 placed in a theme and 214 set aside as off-topic or unsafe. X replies are found by search and each one is checked against its public post on X. Last read: 26 Oct 2026, 23:46 UTC. Not every reply is read.
← Every theme