Your Claude Code Limits Didn't Shrink — I Think the 1M Context Window Is Eating Them Alive
TL;DR Highlight
An analysis post arguing that the perceived sudden reduction in Claude Code limits is not an actual limit decrease, but rather a spike in token consumption driven by the 1M context window.
Who Should Read
Developers who use Claude Code daily and find themselves hitting usage limits more frequently, or feel like their limits are being exhausted faster than before.
Core Mechanics
- Access to the original post was blocked, so the specific content could not be verified. The following is inferred from the title and URL alone.
- Based on the title, it appears many users have been reporting a phenomenon where Claude Code's usage limits (rate limit or usage cap) seem to have decreased.
- The post author is believed to argue that the cause is not Anthropic lowering the limits, but rather that the number of tokens consumed per request has increased dramatically as Claude leverages its 1M token context window.
- The post appears to point out a structural issue: when handling large codebases or long conversations, a larger context window means more tokens are processed per API call, which reduces the number of tasks that can be handled within the same limit.
Evidence
- Author verified: switching to non-1M model reduced rate limit frequency and sessions felt more stable
- Many comments agree: context burns noticeably faster in long sessions since 1M window — /compact command helps somewhat
- User tracking with claude-lens (github.com/Astro-Han/claude-lens) confirms higher burn rate on 1M model vs same workload
- Counter: Pro plan (no 1M limit) shows same rate limit issue — theory may not fully hold / off-peak usage discounts add another variable
How to Apply
- "If you feel your Claude Code limits are being exhausted faster, check how many files and how much code are currently included in your context before assuming the limit policy has changed. Excluding unnecessarily large files from the context can reduce token consumption. When working with large codebases, consider periodically resetting the context with the /clear command or breaking tasks into smaller units to reduce the context size per session. To read the original post directly, log in with a Reddit account or open the post URL (https://www.reddit.com/r/ClaudeAI/comments/1s3bcit/) directly in your browser to view the full discussion."
Terminology
Related Papers
Claude Code sends 33k tokens before reading the prompt; OpenCode sends 7k
동일한 모델과 작업 환경에서 Claude Code와 OpenCode의 실제 토큰 사용량을 API 레벨에서 측정한 결과, Claude Code가 시스템 프롬프트 오버헤드만으로 OpenCode 대비 4.7배 더 많은 토큰을 소비한다는 것을 확인했다.
Mesh LLM: distributed AI computing on iroh
사무실, 집, 클라우드에 흩어진 GPU들을 하나의 OpenAI 호환 API로 묶어주는 분산 LLM 실행 시스템으로, 비싼 API 비용 없이 큰 모델을 직접 운영할 수 있다.
Show HN: Frugon – Find which LLM calls a cheaper model could handle (local, MIT)
내 LLM API 비용이 어디서 새는지 로컬에서 분석해주는 오픈소스 CLI 도구로, 비싼 모델 대신 저렴한 모델로 전환 가능한 호출을 골라낸다.
Jamesob's guide to running SOTA LLMs locally
2천 달러짜리 RTX 3090 한 장부터 4만 달러짜리 RTX PRO 6000 4장 셋업까지, 로컬에서 최신 LLM을 직접 돌리는 방법을 하드웨어 선택·구성·실행 설정까지 통째로 정리한 실전 가이드다.
Faster embeddings: how we rebuilt the ONNX path in Manticore
Manticore Search가 기존 SentenceTransformers/Candle 백엔드를 ONNX Runtime으로 교체해 텍스트 임베딩 생성 속도를 평균 14배 향상시켰다. 별도 모델 서비스 없이 DB 내부에서 직접 임베딩을 처리하는 구조에서 INSERT 속도가 곧 임베딩 속도이기 때문에 이 개선은 실질적인 ingest 처리량 향상으로 직결된다.
Asymmetric Quantization: Near-Lossless Retrieval with 97% Storage Reduction
멀티벡터 검색 모델의 문서 벡터를 1비트 이진값으로 압축하고 쿼리 벡터만 int8로 유지하는 비대칭 양자화 기법으로, 스토리지를 97% 줄이면서 검색 품질 손실을 0.61점(NDCG@10 기준)에 그치게 만든 실제 프로덕션 적용 사례다.