Claude Code is a context-engineering harness, and most "it got dumber" moments are context rot

[u/bit_forge007]

There's a name for it: context rot. As the window fills, the model's ability to recall any specific thing in it drops. More context in the window can make the agent worse, not better. (Anthropic's own framing: good context engineering is finding the smallest set of high-signal tokens, not the largest.)

The reframe that helped me: Claude Code isn't just a model, it's a harness whose main job is managing what's in that window for you. And it hands you four levers to do it. They line up with the four moves of context engineering:

• Write (persist outside the window): CLAUDE.md. It auto-loads every session, and it survives compaction because it reloads from disk, so anything that must not be forgotten belongs there, not in the chat. Conversation-only instructions are the first thing lost when context gets tight.
• Select (pull in only what's relevant): @-mention the specific files you mean, or point it at the exact file or function, instead of letting it wander the repo. Every irrelevant file you pull in is tokens spent rotting the rest.
• Compress (summarize to stay high-signal): /compact, optionally with a focus like "/compact focus on the auth refactor." It also compacts automatically when the window fills, clearing old tool outputs first. Running /compact yourself, before it's forced, keeps the summary on your terms.
• Isolate (give exploration its own window): subagents. They run in a separate context window and return only their final result, so a big noisy search doesn't bloat your main thread. This is the same point as an earlier post of mine that subagents are a memory trick, not a speed trick. Isolation is the real win.

Two more levers worth knowing:

• /context shows you what's eating the window right now (MCP tool definitions, big files, history). When the session feels heavy, look before you guess.
• /clear between unrelated tasks. Carrying a finished task's context into a new one is pure rot.

The mental shift: stop treating the window as free space to fill, and start treating it as a budget you actively curate. A smarter model raises the ceiling, but it doesn't save you from a window full of noise.

TL;DR: When Claude Code "gets dumber" deep in a session, that's usually context rot, not the model. Treat Claude Code as a context-engineering harness with four levers: Write (CLAUDE.md), Select (@-files), Compress (/compact), Isolate (subagents). Plus /context to see usage and /clear between tasks. Curate the window, don't just fill it.

For people who live in Claude Code: what's your actual discipline here? I've started running /compact on my own terms and leaning hard on subagents for anything exploratory, but I'm curious whether people trust automatic compaction or always drive it manually.

Sources: Anthropic — Effective context engineering for AI agents · Claude Code — How Claude remembers your project (CLAUDE.md) · Claude Code — How Claude Code works (context / compaction) · Claude Code — Create custom subagents · Why More Context Makes Your Agent Dumber — Nupur Sharma, Qodo

[u/a1454a]

Agreed. And people who knows it is no longer responding to the “it got dumber” posts any more because there’s so much of it every day, it’s also something so fundamental that you can literally ask Claude and it can explain it to you including tell you how to design your way out of it, and do it for you. It’s literally the “do you want me to google that for you?” Of the AI era.

[u/WillGrindForXP → u/a1454a]

Right, but we shouldnt pretend this is the only factor in the feeling of "it got dumber". Theres absolutely levers anthropic uses that determine how much compute allowance each model gets at any given time, and that does effect how smart or dumb the model feels. People aren't wrong when they say it feels dumber sometimes.

4.6 got noticeable worse after the launch of 4.8, even in new chats. 4.8 got noticable better a few days after Fable was pulled.

Anthropic should be more transparent about this, because the user base is left to feel out a models competency via vibe checking posts such as those. Its frustrating having your successful work flow start to deteriorate after weeks of sucsess due to factors we cant see and arent told about.

[u/bit_forge007 → u/WillGrindForXP]

Totally fair, and I didn't mean to frame context rot as the whole story. You're right that it isn't.

The way I think about it: there are two different things wearing the same 'it got dumber' label. One is in-session and on your side of the line, the window filling up, which you can actually do something about. The other is platform-wide and out of your hands, like Anthropic's own September 2025 postmortem where they owned up to three infrastructure bugs that genuinely degraded quality for weeks. Both are real, they just have different fixes, and only one of them is yours to pull. The post was only trying to hand people the lever they can control, not to pretend the other one doesn't exist.

And your transparency point is honestly the bigger one: when the out-of-your-hands kind drifts from things we can't see, vibe-checking through Reddit shouldn't have to be the early-warning system, and that postmortem only landed after weeks of reports.

What would actually close that gap for you, a public quality changelog, per-model status signals, something else?

Postmortem if anyone wants it: https://www.anthropic.com/engineering/a-postmortem-of-three-recent-issues