1
00:00:00,119 --> 00:00:02,079
So, I'm- I'm out in the shed last week,
right?

2
00:00:02,539 --> 00:00:05,519
Hands covered in grease from restoring
this old postie bike,

3
00:00:06,019 --> 00:00:09,019
and I leave Claude Code running a
background refactoring job.

4
00:00:09,639 --> 00:00:12,219
I wash up, walk back inside, and- and
boom.

5
00:00:12,920 --> 00:00:13,659
Fifty dollars.

6
00:00:13,960 --> 00:00:14,799
Just gone.

7
00:00:15,939 --> 00:00:16,639
Vaporized.

8
00:00:17,638 --> 00:00:19,198
Wait, fifty dollars?

9
00:00:19,698 --> 00:00:20,917
On a background refactor?

10
00:00:21,597 --> 00:00:24,037
How- how is that even possible for a local
tool?

11
00:00:24,242 --> 00:00:26,062
It spawned subagents, mate.

12
00:00:26,962 --> 00:00:31,762
But- but then those subagents spawned
their own subagents, and it just became this

13
00:00:31,922 --> 00:00:35,742
nested, infinite loop of digital workers
hiring more workers.

14
00:00:36,182 --> 00:00:37,902
A complete runaway swarm.

15
00:00:38,762 --> 00:00:45,322
Thankfully, Anthropic just dropped
v2.1.217 on July 21st, 2026,

16
00:00:45,782 --> 00:00:49,802
and it's basically a direct response to
this whole infinite fan-out nightmare,

17
00:00:50,242 --> 00:00:51,962
brought to us by Jellypod AI.

18
00:00:52,302 --> 00:00:54,982
Yeah, they completely clamped down on it.

19
00:00:55,043 --> 00:00:57,962
The default nesting limit used to be five
levels deep.

20
00:00:58,382 --> 00:00:58,882
Five!

21
00:00:59,442 --> 00:01:00,162
Now?

22
00:01:00,202 --> 00:01:00,843
It's zero.

23
00:01:01,343 --> 00:01:02,742
Absolute zero.

24
00:01:03,342 --> 00:01:08,062
By default, a subagent is strictly
forbidden from spawning its own nested subagents.

25
00:01:08,103 --> 00:01:09,642
It- it just blocks it outright.

26
00:01:10,426 --> 00:01:14,107
Zero is a pretty heavy hammer, but I
reckon it'll save a lot of wallets.

27
00:01:14,726 --> 00:01:16,726
What if you actually need that depth,
though?

28
00:01:16,966 --> 00:01:20,706
Like, if you're working on a massive
legacy system and you need the agents to

29
00:01:20,746 --> 00:01:21,146
delegate?

30
00:01:21,246 --> 00:01:25,006
You have to explicitly override it now
using the environment variable

31
00:01:25,266 --> 00:01:28,147
CLAUDE_CODE_MAX_SUBAGENT_SPAWN_DEPTH.

32
00:01:28,746 --> 00:01:30,967
But if you do that, you've got to watch
your concurrency.

33
00:01:31,566 --> 00:01:36,547
There's a second variable now,
CLAUDE_CODE_MAX_CONCURRENT_SUBAGENTS,

34
00:01:37,006 --> 00:01:38,667
which limits how many can run in parallel.

35
00:01:39,286 --> 00:01:42,087
That one defaults to twenty, which is
still a lot of horsepower.

36
00:01:42,604 --> 00:01:45,524
Right, because the budget check was only
happening at the coordinator level,

37
00:01:45,704 --> 00:01:46,784
not the active workers.

38
00:01:47,625 --> 00:01:50,545
But in v2.1.217, they fixed that.

39
00:01:50,965 --> 00:01:57,045
If you run, say, claude -p "Refactor API
routing" --max-budget-usd 5,

40
00:01:57,545 --> 00:01:59,844
the engine now tracks the spend in real
time.

41
00:02:00,424 --> 00:02:05,584
The microsecond that five-dollar limit is
breached, it forcefully kills every active

42
00:02:05,625 --> 00:02:07,224
background subagent.

43
00:02:07,284 --> 00:02:07,924
No exceptions.

44
00:02:07,958 --> 00:02:08,918
Instant death.

45
00:02:09,131 --> 00:02:13,398
No zombie processes, no delayed API calls
draining your account.

46
00:02:13,526 --> 00:02:15,318
That's exactly what we needed.

47
00:02:15,558 --> 00:02:18,278
Oh, they also snuck in a few smaller
things.

48
00:02:18,411 --> 00:02:22,918
If you type :hea now, it triggers an emoji
autocomplete in the terminal.

49
00:02:22,998 --> 00:02:24,198
Very modern.

50
00:02:25,167 --> 00:02:26,887
Please tell me there's a way to turn that
off.

51
00:02:27,387 --> 00:02:29,267
I don't need emojis in my git logs.

52
00:02:29,333 --> 00:02:29,893
You can!

53
00:02:30,053 --> 00:02:33,813
You just set emojiCompletionEnabled to
false in your config.

54
00:02:33,993 --> 00:02:39,493
But hey, they also made the footer pull
request links clickable for raw SSH and tmux

55
00:02:39,560 --> 00:02:43,813
users, and they added disk space warnings
so your terminal transcripts don't

56
00:02:43,875 --> 00:02:46,133
silently corrupt when your drive fills up.

57
00:02:46,125 --> 00:02:49,565
Clickable SSH links are actually huge for
my terminal workflow.

58
00:02:49,685 --> 00:02:52,445
Alright, well, glad your wallet is safe
now.

59
00:02:52,458 --> 00:02:53,818
Yeah, thank goodness.

60
00:02:54,258 --> 00:02:57,898
I'm going back to my bike before any more
robots try to charge me.

61
00:02:57,965 --> 00:02:58,858
Catch you later.