Codex 28 · Theme · #70

Cache preserved across effort changes

5people describe this

5 on X

3 wins · 2 problems · first reported 23 Oct 2026

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 yet

No recorded announcement has answered this yet.

In their words

What people said

Win
Keeping cache hits while reasoning changes makes iterative coding feel much less wasteful

@voidJan on X ↗ · 25 Oct 2026
Problem
the reasoning change not busting cache is the one I'd feel most. Bumping reasoning up halfway through a Codex session when it's stuck on something gnarly felt like paying to reload the whole context, so I mostly just didn't. Gonna try leaving it on medium and only cranking it…

@ArthasProudmore on X ↗ · 24 Oct 2026
Problem
Changing reasoning effort still broke the cache for me (n=1). Codex CLI 0.164.0, GPT-6.1 Sol, exec resume: low to high, 7,168 of 57,950 input tokens cached (12%). High to medium 0%. Back to low 76%. Same effort after 1 min: 99.6%.

@sergey_moloman on X ↗ · 24 Oct 2026
Win
Cache persisting when you change reasoning/work mid-conversation is huge. That invalidation bug broke longer Codex flows — fixing it + faster dots connects makes sustained use actually practical.

@TechAngleHQ on X ↗ · 24 Oct 2026
Win
Cache not dying every time I bump reasoning mid chat. My weekly limit thanks you

@cradrrat on X ↗ · 23 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.

What happened with “Cache preserved across effort changes”?

0 / 1200

Tell us a little more — at least 20 characters.

Your words stay yours.

AI reads your draft as you type. Only what you publish is public. Privacy

Not sure where to start?

Think of the last task you tried. What were you doing, what happened, and what would have helped? You can also say you haven't tried a change yet.

01
What you said

Read as you type: a win, a problem or an idea, and the words that carry it.
Ready when you are
Who else had it

The theme your words join, and how many people on Rantr and X described it.
Where OpenAI stands

Shipped, reset, or not addressed yet, from the recorded announcements.
What to do now

A step the announcements make possible for you, when there is one.

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.

Corrections

Changes to this theme

26 Oct 2026, 04:51 UTC

Renamed from “Cache reuse changes with reasoning effort” to “Cache preserved across effort changes” as more people described it.
25 Oct 2026, 02:35 UTC

“Session cache survives reasoning changes” was merged into this theme: JEV judged them the same problem.

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