So, I- I- I was spinning up a git worktree the other day, right?
And normally, with CLI tools like Claude Code-this episode,
by the way, is brought to you by Jellypod AI-the moment you bounce between
directories or open a monorepo, you- you have to completely restart the session just
so the Model Context Protocol, the MCP servers, actually know where they are.
Right, which completely wipes your conversational history.
It's a massive pain when you're deep in a debugging flow.
Exactly!
But in v2.1.203 and .204, they finally fixed this.
Now, when Claude Code registers a new directory, it just appends it to the MCP
roots/list dynamically.
And it triggers notifications/roots/list_changed under the hood without a session
restart.
Oh, that's clever.
So the workspace indexers can just listen for that notifications/roots/list_changed
event and update their indexing path on the fly.
No more tearing down the whole process just because you checked out a new branch or
jumped folders.
Precisely.
It just keeps running.
Though, speaking of things tearing down, that headless session bug in v2.1.204 is a
huge save if you're running this in CI/CD pipelines.
Apparently, if you had a SessionStart hook running in a remote environment,
it was dead silent.
Oh, let me guess.
The silent stdout meant the remote orchestrator assumed the container was dead or
stuck, and just reaped it?
Spot on.
It- it- it would get idle-reaped because of a silent startup hook.
v2.1.204 now forces streaming of stdout during those SessionStart hooks.
So the orchestrator sees the traffic, knows the container is actually doing work,
and doesn't murder your build agent mid-run.
That is going to save so many pipeline minutes.
But tell me they did something about the macOS memory leaks.
I've been getting these weird, random freezes since v2.1.196.
Ah, the- the dreaded twenty-second stall!
Yeah, that was a false-positive on a low-memory warning.
The tool thought it was saving you from an out-of-memory crash when the RAM was
actually fine.
v2.1.203 completely bins that false threshold check, so no more random pauses on
macOS.
Thank goodness.
I thought my machine was giving up on me.
And what about Windows?
I saw some devs complaining about auth errors on background agents.
Yeah, they squashed a bug where background agents would throw a 401 unauthorized
because they weren't inheriting the ANTHROPIC_BASE_URL environment variable properly
on Windows.
So if you were using a custom gateway or a proxy, it just fell over.
Ah, that makes sense why my local proxy kept dropping connections!
But the biggest CPU saver has to be the fix to the context-usage indicator.
Before this, Claude Code was literally re-analyzing the entire conversation
transcript...
...on every single token!
Like, talk about burning cycles.
No wonder my laptop fan sounded like a jet taking off during long chats.
Exactly!
Now it lazily evaluates that transcript state, so your terminal doesn't melt while
it's actively streaming a response.
If you're writing custom MCP servers for your monorepos, make sure they actually
handle that notifications/roots/list_changed payload.
If they do, your tools can dynamically index your code without you ever having to
restart your session.