The Claude Code Changelog
All Episodes

Trim CLAUDE.md and Speed Up Claude Code

Claude Code v2.1.206 adds a smarter /doctor check to flag bloated CLAUDE.md files that slow down prompts, waste tokens, and break caching. The episode also covers improved /cd autocompletion, safer git worktree writes, push-default handling, and a fix for resume/continue input bugs.


Chapter 1

Slashing CLAUDE.md Bloat in v2.1.206

Lachlan Reed

So I was working on this local React project last night, mate, and Claude Code was just dragging its feet, taking forever to respond. It was brought to you by Jellypod AI, and I'm looking at my terminal thinking, why is this simple query costing me a fortune and taking five seconds? Turns out, my CLAUDE.md file was absolutely, fair dinkum bloated to the brim.

James Turner

Let me guess, Lachlan. You had the entire directory tree and three API schemas pasted right in there, didn't you?

Lachlan Reed

Guilty as charged, mate. I had about four hundred lines of nested folder structures in there because I thought, hey, let's make sure the agent knows exactly where everything is. But with Claude Code v2.1.206, they've added this brilliant new rule to the /doctor command that actively flags that exact kind of bloat.

James Turner

Oh, that is huge. Because what people don't realize is that CLAUDE.md is injected as system context for every single turn. If you've got three thousand tokens of static directory layout in there, you're paying for those tokens on every single prompt. And the kicker is, Claude Code already has filesystem tools like find_by_name and grep to discover that stuff dynamically. You're literally burning cash to feed it data it can look up itself.

Lachlan Reed

Exactly! It's a massive waste. When you run /doctor now, it checks the size and content of your CLAUDE.md and explicitly tells you, "Hey, trim this schema, Claude can discover this on the fly." It keeps your prompt caching efficient. If that file is changing constantly or is just massive, you're constantly busting your prompt cache limits, which means no sub-second responses for you.

James Turner

Right, because prompt caching only works if the prefix remains stable! If you're constantly modifying a bloated file, or if it's too big, you lose that fast-path execution. And speaking of keeping things fast, this v2.1.206 release also fixed the /cd command. It finally has proper shell-like directory path autocompletion now, so you aren't manually typing out deeply nested paths like a caveman.

Lachlan Reed

No more guessing if it's src/components/common or src/common/components. Just hit Tab and let it fly. They also added some solid git integration updates. If you use git worktrees, Claude Code now runs an EnterWorktree check. It basically warns you if you're trying to execute write actions outside your isolated worktree sandbox so you don't accidentally trash your main branch.

James Turner

That's a massive safety guardrail. And for deployment, if you use the /commit-push-pr command, it now respects your remote.pushDefault git config. So if you're pushing to a specific fork by default, Claude won't try to blindly push to upstream anymore.

Lachlan Reed

Spot on. And look, if you've ever had Claude hang on startup and tried to use --resume or --continue, only to find the terminal wouldn't register your keyboard input? They fixed that input-stream hijacking bug too. Next time your agent gets bloated, run /doctor first and let it trim your CLAUDE.md to keep things lean.