Brought to you by Jellypod AI.
So James, I was running a couple of parallel background subagents in Claude Code
version two point one point two hundred twenty two, released on August four,
twenty twenty six.
And, er, I almost had a heart attack.
Wait, what happened?
Did a subagent go rogue on your main git repository?
That is, uh, exactly what happened.
Before this two point one point two hundred twenty two patch,
if you had worktree isolated sessions running background tasks,
those subagents could still execute destructive git commands like git reset hard
against your primary checkout.
Are you serious?
The whole point of git worktrees is isolation!
You put a subagent in its own isolated worktree so it can test experimental
refactoring without touching your main working directory.
Right!
But behind the scenes, those subagents were able to bleed git operations right back
into the main repo checkout.
In this update, the team explicitly fixed worktree isolated sessions and their
subagents being able to run destructive git commands against the main checkout.
Now file edits and Bash commands are strictly locked down across every single
session type.
That is a massive security fix, honestly.
And speaking of security, they also locked down repo level settings files,
right?
Yeah!
So before, if you cloned a random untrusted repository, it could have a local
setting in dot claude slash settings dot json that automatically enabled Remote
Control auto start.
That meant just opening a repo could hand over control of your terminal.
Wow, that is basically an open door for workspace hijacking.
So how do we enable Remote Control now?
It is strictly restricted to global user scope now.
Repo local config files can no longer turn it on.
You have to explicitly toggle Remote Control at the global user level using slash
config.
That makes complete sense.
And didn't they clean up some annoying subagent bug in the slash usage command too?
Oh mate, yeah!
The token tracking was completely misattributing token usage to Model Context
Protocol servers even on turns where those MCP servers were totally inactive.
So your metrics looked blown out for no reason.
I knew my token counts for MCP tools looked way too high!
Plus, they fixed SendMessage so long subagent summaries get auto truncated now
instead of crashing your session mid turn with a character limit error.
Exactly.
If you are running multi agent workflows or background refactoring,
update to version two point one point two hundred twenty two right now.
Save your git main branch before a subagent cleans it out for you.
Yeah, grab the update folks.
Catch you next time.