Claude Code Rate Limits May Be Due to 1M Context Window Overload

Context Window Expansion Causing System Strain

Anthropic recently released Opus 4.6 with a 1 million token context window to all users. Following this release, users have reported two significant issues: degraded long-task performance and increased capacity problems. There was initially no option to opt out of the 1M context model.

The Theory: Inefficient Context Compression

The Reddit user's analysis suggests that Claude Code's context compression system—which summarizes old conversation history to save tokens—isn't aggressive enough for the expanded 1M context window. This means each Claude Code session is likely sending more raw token data per request than necessary. When multiplied across the entire userbase, this creates server overload as users unintentionally send bloated contexts containing unnecessary information.

Impact on Usage Limits

The theory posits that Anthropic's short-term solution has been to lower usage limits to compensate for the increased server load. This explains why limits appear to have shrunk—users are burning through tokens faster per task, not because of intentional limit reductions by Anthropic.

Workaround Identified

Yesterday, Anthropic quietly reintroduced the older, non-1M context model as an option. Users who switched to this model reported noticeably improved stability and slower consumption of their usage limits, supporting the theory about context window inefficiencies.

Recommended Action

For immediate relief from rate limits and stability issues, try switching off the 1M context model. The long-term solution likely requires improved context compression algorithms. Once implemented, this could allow Anthropic to restore previous usage limits.