← Reddit

Did claude bring back the 60 minutes context cache?

Reddit · Background_Fox2241 · May 18, 2026
A user reported observing a 60-minute context cache setting in the Claude Usage Tracker Extension after previously noting Claude's 5-minute context cache was consuming significant tokens. The user expressed uncertainty about whether the longer cache duration represents an actual change or an extension display error and indicated plans to verify the observation through API calls.

Detailed Analysis

A Reddit user in the r/ClaudeAI community has observed what appears to be a potential reversal in Anthropic's context caching policy, reporting that Claude's context cache duration may have returned to 60 minutes after a prior reduction to 5 minutes. The observation was made through the Claude Usage Tracker browser extension, which the user says is displaying a 60-minute cache window during an active Claude web chat session. The post includes a screenshot as evidence and notes that the user planned to investigate further by examining raw API calls to confirm whether the change is genuine or an artifact of the extension's display logic.

The significance of this development, if confirmed, lies in the practical economics of working with Claude at scale. Context caching is a mechanism that allows Claude to retain processed information from prior turns or documents without reprocessing them each time, thereby reducing token consumption and associated costs. The earlier reduction from 60 minutes to 5 minutes was a meaningful change that affected power users and developers who rely on long, uninterrupted working sessions — the shorter cache window forced more frequent re-ingestion of context, burning tokens at a substantially higher rate. The user explicitly notes the 5-minute window had been "burning tokens like crazy," reflecting a common complaint among heavy users of Claude's web interface.

What makes this report particularly notable is the absence of any official announcement or corroborating community discussion at the time of posting. Anthropic has historically adjusted model behavior, pricing, and infrastructure features — including cache durations and rate limits — without always issuing prominent public notices, particularly for web interface changes as opposed to API-level updates. This means meaningful shifts in user experience can go unnoticed for extended periods, surfacing only through community-driven tools like usage tracker extensions. The reliance on third-party browser extensions to detect backend behavioral changes underscores a broader transparency gap between Anthropic's infrastructure decisions and user awareness.

In the wider context of competitive AI development, context window and caching policies have become a significant differentiator among frontier model providers. Longer cache windows reduce operational friction for developers and researchers working on complex, multi-step tasks, and they directly affect the cost-efficiency of using models like Claude for production applications. If Anthropic did quietly restore the 60-minute cache, it would represent a notable concession to user feedback and competitive pressure — particularly as rivals continue to expand context window capabilities and optimize token economics. However, without official confirmation, the observation remains unverified, and the possibility of an extension bug or localized A/B test cannot be ruled out until API-level inspection or broader community confirmation is obtained.

Read original article →