Claude Code bug: interactive sessions write 5-min prompt cache while claude -p gets 1-hour
chrs-myrs · ghdev · 2026-10-13
- The bug: developer chrs-myrs filed anthropics/claude-code issue #101685 reporting that since 2026-10-12 18:18 UTC, every newly started interactive Claude Code session writes its main-conversation prompt cache with a 5-minute TTL, while claude -p runs on the same account, version and model still write 1-hour.
- Evidence: local transcripts (message.usage.cachecreation) show all 5 interactive sessions started after the onset write 5m from the first turn; 4 headless runs still get 1h; re-auth via /login doesn't help. Across 14 sessions the TTL never changed mid-session, suggesting it's fixed at startup.
- Environment: Claude Code 2.1.296 on Linux/WSL2, Team subscription seat — per official docs interactive, -p and SDK turns should share the same 1-hour bucket.
More from coding & agent
- Claude Code Pushes Urgent Security Update Across All Installations — umeshonai · 2026-10-23
- Claude cut a 2.6-hour video export to 20 minutes — but only after being told to rebuild the server — byhewar · 2026-10-23
- 3 flight-booking rules my AI agent checks that I'd never do by hand — Efistoffeles · 2026-10-23
- OpenJet claims Qwen3.8-27B coding runs 1.9x faster than llama.cpp on one RTX 3090 — JeremyCMorgan · 2026-10-23
- Building an autonomous SEO agent in Hermes with three skills: programmatic pages, Keywords Everywhere, DataForSEO — EXM7777 · 2026-10-23
- Building a sports betting AI agent with onchain execution and human approval by default: architecture and lessons — Dry-Comfortable-2678 · 2026-10-23