1
00:00:00,099 --> 00:00:02,000
Brought to you by Jellypod AI.

2
00:00:03,159 --> 00:00:06,940
So James, I was running a couple of
parallel background subagents in Claude Code

3
00:00:07,019 --> 00:00:10,679
version two point one point two hundred
twenty two, released on August four,

4
00:00:10,719 --> 00:00:12,019
twenty twenty six.

5
00:00:12,119 --> 00:00:14,659
And, er, I almost had a heart attack.

6
00:00:15,127 --> 00:00:16,427
Wait, what happened?

7
00:00:16,447 --> 00:00:18,687
Did a subagent go rogue on your main git
repository?

8
00:00:18,708 --> 00:00:20,868
That is, uh, exactly what happened.

9
00:00:21,005 --> 00:00:25,428
Before this two point one point two
hundred twenty two patch,

10
00:00:25,455 --> 00:00:29,428
if you had worktree isolated sessions
running background tasks,

11
00:00:29,468 --> 00:00:34,468
those subagents could still execute
destructive git commands like git reset hard

12
00:00:34,548 --> 00:00:36,308
against your primary checkout.

13
00:00:36,912 --> 00:00:37,851
Are you serious?

14
00:00:38,231 --> 00:00:40,551
The whole point of git worktrees is
isolation!

15
00:00:40,871 --> 00:00:45,031
You put a subagent in its own isolated
worktree so it can test experimental

16
00:00:45,071 --> 00:00:47,611
refactoring without touching your main
working directory.

17
00:00:47,667 --> 00:00:48,147
Right!

18
00:00:48,267 --> 00:00:53,427
But behind the scenes, those subagents
were able to bleed git operations right back

19
00:00:53,491 --> 00:00:55,107
into the main repo checkout.

20
00:00:55,347 --> 00:01:00,867
In this update, the team explicitly fixed
worktree isolated sessions and their

21
00:01:00,967 --> 00:01:04,947
subagents being able to run destructive
git commands against the main checkout.

22
00:01:05,127 --> 00:01:09,907
Now file edits and Bash commands are
strictly locked down across every single

23
00:01:09,957 --> 00:01:10,707
session type.

24
00:01:10,907 --> 00:01:13,948
That is a massive security fix, honestly.

25
00:01:14,587 --> 00:01:18,327
And speaking of security, they also locked
down repo level settings files,

26
00:01:18,407 --> 00:01:18,487
right?

27
00:01:18,542 --> 00:01:18,942
Yeah!

28
00:01:19,102 --> 00:01:23,822
So before, if you cloned a random
untrusted repository, it could have a local

29
00:01:23,882 --> 00:01:28,782
setting in dot claude slash settings dot
json that automatically enabled Remote

30
00:01:28,842 --> 00:01:30,142
Control auto start.

31
00:01:30,302 --> 00:01:34,302
That meant just opening a repo could hand
over control of your terminal.

32
00:01:34,771 --> 00:01:37,951
Wow, that is basically an open door for
workspace hijacking.

33
00:01:38,511 --> 00:01:40,111
So how do we enable Remote Control now?

34
00:01:40,125 --> 00:01:42,765
It is strictly restricted to global user
scope now.

35
00:01:42,941 --> 00:01:46,205
Repo local config files can no longer turn
it on.

36
00:01:46,345 --> 00:01:51,085
You have to explicitly toggle Remote
Control at the global user level using slash

37
00:01:51,165 --> 00:01:51,805
config.

38
00:01:51,792 --> 00:01:53,072
That makes complete sense.

39
00:01:53,132 --> 00:01:57,152
And didn't they clean up some annoying
subagent bug in the slash usage command too?

40
00:01:57,447 --> 00:01:59,086
Oh mate, yeah!

41
00:01:59,126 --> 00:02:03,686
The token tracking was completely
misattributing token usage to Model Context

42
00:02:03,766 --> 00:02:08,426
Protocol servers even on turns where those
MCP servers were totally inactive.

43
00:02:08,906 --> 00:02:11,047
So your metrics looked blown out for no
reason.

44
00:02:12,022 --> 00:02:15,142
I knew my token counts for MCP tools
looked way too high!

45
00:02:15,642 --> 00:02:19,223
Plus, they fixed SendMessage so long
subagent summaries get auto truncated now

46
00:02:19,242 --> 00:02:22,402
instead of crashing your session mid turn
with a character limit error.

47
00:02:22,617 --> 00:02:23,317
Exactly.

48
00:02:24,117 --> 00:02:27,297
If you are running multi agent workflows
or background refactoring,

49
00:02:27,878 --> 00:02:31,338
update to version two point one point two
hundred twenty two right now.

50
00:02:32,117 --> 00:02:35,277
Save your git main branch before a
subagent cleans it out for you.

51
00:02:36,219 --> 00:02:37,399
Yeah, grab the update folks.

52
00:02:37,899 --> 00:02:38,480
Catch you next time.