Interactive sessions get 5m cache TTL

“Interactive sessions get only 5m prompt-cache TTL while claude -p on same login gets 1h”

Is this your bug? What gets counted gets fixed. Pile on.

Paste this into your agent. It files your report, with your error and version.

I hit this bug: rapsheet.dev/sheets/claude-code/issues/12130/file
Follow it to file my report. Show me the text before you send.

No install. No account. Public and anonymous. The link asks your agent for one report, nothing else. What it sends

Quiet. No reports and thumbs-up in the last two weeks, down from 10 a week at the mid-October peak. Not fixed, but a workaround is known.

Interactive sessions use 5m prompt cache TTL instead of 1h. Interactive CLI sessions write only 5-minute cache entries while headless claude -p on the same account still writes 1-hour.

Is this your bug?

File my report

Where: interactive CLI
Versions: 2.1.296 to 2.1.304
Platforms: macOS, Windows
How bad: Breaks a normal workflow. Some reports say it used to work.

Part of: Prompt cache misses and re-writes11 bugs

Sleep re-sends full agent context4 people
Warm prompt cache fully missed2 people
Resume re-writes prompt cache3 people
CLAUDE.md cache not shared3 people
Cross-session prompt cache misses2 people
Prompt cache misses after system message3 people
Subagent prompt cache expires2 people
Background agent summary requests12 people
Context after prompt breaks cache4 people
Subagent resume cache miss4 people

Original reports4, newest first

Oct 20, 2026Interactive sessions request 5-minute prompt cache on enterprise org, headless uses 1-hour TTL#103753
Oct 20, 2026Interactive CLI uses 5m prompt cache TTL instead of 1h since v2.1.301#103673
Oct 19, 2026Interactive sessions default to 5m prompt-cache TTL while claude -p gets 1h#103392
Oct 13, 2026Interactive sessions write the 5-minute prompt cache from session start, while claude -p on the same account writes 1-hour (2.1.296, Team seat, survives /login)#101685