●VERSION — v2.1.227 landed on August 10 with no new features, just fixes around plan detection and CI behavior●AUTO — Two days remain until August 14, when auto mode becomes the default in Claude Code for Pro, Max, and Team●CI — Bash commands no longer fail across the board under claude-code-action with allowed_non_write_users on GitHub-hosted runners●BILLING — Sessions started with an expired token could misread your plan and nudge Max users toward usage credits; that is now fixed●SUNSET — The legacy Workbench and the experimental prompt tool APIs retire on August 17, five days out●PRICE — Sonnet 5 promo pricing at $2/$10 per Mtok runs through August 31, moving to $3/$15 on September 1●VERSION — v2.1.227 landed on August 10 with no new features, just fixes around plan detection and CI behavior●AUTO — Two days remain until August 14, when auto mode becomes the default in Claude Code for Pro, Max, and Team●CI — Bash commands no longer fail across the board under claude-code-action with allowed_non_write_users on GitHub-hosted runners●BILLING — Sessions started with an expired token could misread your plan and nudge Max users toward usage credits; that is now fixed●SUNSET — The legacy Workbench and the experimental prompt tool APIs retire on August 17, five days out●PRICE — Sonnet 5 promo pricing at $2/$10 per Mtok runs through August 31, moving to $3/$15 on September 1

TAG

cache-invalidation

1 articles

← Back to all tags

claude-api¹ caching¹ redis¹ semantic-cache¹ production¹ observability¹

⬡ API & SDK/2026-06-18Advanced

When Your Claude API Response Cache Returns Stale Answers and Near-Miss Wrong Ones — Field Notes on Freshness and False-Hit Suppression

A Claude API response cache improves latency and cost immediately, but the problems that hurt in production are not average hit rate — they are stale hits and semantic false hits. Here is the key design, freshness management, false-hit suppression, and observability that keep a cache honest.