March 13, 2026
Size matters? The thread says otherwise
"Added 1M context window for Opus 4.6 by default for Max, Team, and Enterprise"
Huge memory, same mood: devs split between wow and “still forgets”
TLDR: Claude made a 1‑million token memory window standard for premium users. Commenters argue it won’t fix “context rot,” praise auto‑compaction and bug fixes, and flag occasional tool instability—raising the bigger question: does a giant memory actually improve recall, or is it just a flashy flex?
Claude just cranked its memory to a jaw-dropping 1 million tokens for top-tier users (now default for Max, Team, Enterprise—previously a paid extra), but if you thought the internet would throw confetti—think again. The thread lit up with skepticism as one dev, tyleo, sighed that “context still rots at the same rate,” claiming 90k tokens misbehave whether the window is 100k or 1M, and adding their 6M+ codebase worked fine before. Others countered that Claude Code’s auto-compaction and “continue where it left off” already keep long chats manageable, asking if the supersized window is just a way to dodge tool calls. Another commenter noted compaction now even tells you which file to open for past context, while warning that MCPs (tool connectors) can wobble after compaction—though it’s improving.
Meanwhile, a quieter chorus cheered the quality-of-life fixes: color-coded sessions, clearer permission prompts, voice mode finally behaving, a bash “!” bug squashed, and smarter token counting so your chat doesn’t shrink itself too early. Someone dropped a throwback link to a previous debate, fanning the flames. The meme energy? Think “elephants never forget”—except this elephant misplaces your thread. The vibe: big numbers wow the crowd, but veterans mutter, “It’s not the size of the window—it’s the recall.”
Key Points
- •Version 2.1.75 sets a 1M-token context window as the default for Opus 4.6 on Max, Team, and Enterprise plans.
- •New features include /color, session name display after /rename, memory file last-modified timestamps, and hook source display in permission prompts.
- •Multiple fixes address voice mode activation, model name header updates, session crash on undefined attachment computations, Bash '!' handling, and token estimation over-counting.
- •Platform and tooling improvements include macOS startup performance, Windows RTL rendering, Windows LSP URI handling, marketplace config path handling, and suppressed async hook messages by default.
- •A breaking change removes the deprecated Windows managed settings fallback path; users must use C:\Program Files\ClaudeCode\managed-settings.json.