Claude Reportedly Resets Your Cache to Charge You More

For context, a Claude Code user has highlighted a number of prompt-caching behaviors that can cause long sessions to consume significantly more usage than anticipated.

Key points

• Starting with Claude Code v2.1.251, the command includes a Prompt cache (main) line showing the cache hit rate.
• These controls require Claude Code v2.1.242 or newer, and API-key users can employ them as well.
• From v2.1.260 onward, Claude Code can additionally identify the probable reason for the most recent cache miss.
• It increases the total amount of processing required. /usage Can Show Your Cache Hit Rate.
• That means the gap before Claude has to process the conversation again becomes 12 times shorter, even though the user is still working in the same session.

Reddit user u/virtualunc remarked they identified the details while going through Claude Code's documentation rather than its changelog.

Notably, the biggest matter involves how long Claude Code keeps the main conversation cached. Prompt Cache Drops From One Hour to Five Minutes.

For subscription users who are still within their included plan usage, Claude Code keeps the main conversation's prompt cache alive for one hour.

Nevertheless, once the user exceeds that allowance and starts using further usage credits, the cache time-to-live drops to just five minutes.

Users accessing Claude Code through an API key or cloud provider obtain the five-minute cache by default. Apple, Meta End Fight to Launch Muse AI on Macs.

Your Claude Code prompt cache drops from an hour to five minutes the second you pass your plan limit byu/virtualunc inClaudeAI. Subagents Already Employ a Five-Minute Cache. The longer cache applies only to the main conversation.

Other Claude Code activity, including subagents, workflows, compaction, and session-title generation, uses a five-minute cache regardless of the subscription tier.

Consequently, returning to a subagent after 10 minutes can require its context to be processed again from scratch, even on a Max subscription. Users Can Extend the Cache.

According to the Reddit post, users can change this behavior by setting promptCacheTtl to 1h or using the CLAUDE_CODE_PROMPT_CACHE_TTL environment variable.

Meanwhile, the subagentPromptCacheTtl setting controls the cache duration for other requests, including subagents.

These controls require Claude Code v2.1.242 or newer, and API-key users can employ them as well. Switching Models Rebuilds the Cache. Another significant detail involves switching models during an active session.

Changing models causes Claude Code to read the entire conversation history again with no cache hits. This can become especially noticeable with opusplan.

When Claude Code switches between Opus for planning and another model for execution, each move into or out of plan mode counts as a model switch. Repeatedly moving between planning and building can therefore rebuild the cache each time. X Launches Unified AI Subscription With Grok, Cursor, and X Premium. Agent Teams Can Employ Around 7x More Tokens.

Agent teams can additionally consume substantially more usage than a normal Claude Code session.

In practice, the documentation states that teams can employ roughly seven times as numerous tokens when teammates remain in plan mode.

Each teammate maintains its own context. It increases the total amount of processing required. /usage Can Show Your Cache Hit Rate. Users can check their own cache performance by running /usage.

In practice, the findings support explain why long Claude Code sessions can suddenly start consuming more usage even when the actual workload has not changed. Stay Connected with ProPakistani.

Obtain the latest tech news, telecom insights, and product launches wherever you prefer. Follow on Google Discover. Follow on Google News Join WhatsApp. See more ProPakistani stories in Google Search and Top Stories.

Technology and Automotive Specialist covering the latest cars, smartphones, AI breakthroughs, and.

For now, claude Reportedly Resets Your Cache to Charge You More remains the part of the story worth watching, and further updates are likely as more details are confirmed.