1
00:00:00,079 --> 00:00:01,459
I- I- I'm still...

2
00:00:01,659 --> 00:00:07,039
uh, literally sweating from that
fifty-dollar runaway API bill I got last month.

3
00:00:07,799 --> 00:00:11,079
You know, when my local Claude agent went
on that absolute,

4
00:00:11,159 --> 00:00:15,899
like, tear, just spawning subagents like
rabbits in my backyard shed.

5
00:00:16,719 --> 00:00:22,020
I- I thought v2.1.217 capping it at depth
two saved my bacon,

6
00:00:22,119 --> 00:00:22,859
but...

7
00:00:22,899 --> 00:00:24,639
well, we're back in the fire now.

8
00:00:25,751 --> 00:00:30,451
Yeah, well, that fifty-dollar bill was
the- the ultimate cautionary tale,

9
00:00:30,511 --> 00:00:30,911
Lachlan.

10
00:00:31,591 --> 00:00:34,831
But the reality is, when Anthropic clamped
it down to depth two,

11
00:00:35,331 --> 00:00:38,091
developers started complaining that Claude
Code lost its...

12
00:00:38,771 --> 00:00:39,451
its mojo.

13
00:00:39,991 --> 00:00:43,632
It just couldn't solve complex, deeply
nested debugging tasks.

14
00:00:44,171 --> 00:00:49,731
So in v2.1.219-which, by the way, is
brought to you by our friends at Jellypod AI,

15
00:00:50,132 --> 00:00:53,971
the team making it dead simple to turn
your daily newsletters into clean

16
00:00:54,031 --> 00:00:57,251
podcasts-Anthropic is re-opening the
throttle.

17
00:00:57,911 --> 00:01:01,251
We are officially back to a default
nesting depth of three.

18
00:01:01,972 --> 00:01:02,691
Depth three?

19
00:01:03,051 --> 00:01:03,591
Crikey.

20
00:01:03,711 --> 00:01:04,391
So that's...

21
00:01:04,571 --> 00:01:05,331
let me do the math.

22
00:01:06,131 --> 00:01:12,252
Coordinator, then Subagent One, Subagent
Two, and then Subagent Three?

23
00:01:13,212 --> 00:01:15,451
That is a- a proper hierarchy.

24
00:01:16,391 --> 00:01:19,951
But James, if Subagent Two decides to spin
up three more subagents,

25
00:01:20,351 --> 00:01:22,591
that tree is going to expand
exponentially.

26
00:01:23,031 --> 00:01:25,331
I'll be bankrupt before I can even boil
the kettle!

27
00:01:26,097 --> 00:01:26,437
Right!

28
00:01:26,897 --> 00:01:29,597
It- it- it can get out of hand incredibly
fast.

29
00:01:30,097 --> 00:01:34,238
So to prevent your wallet from imploding
again, they've introduced this new,

30
00:01:34,537 --> 00:01:36,418
clever soft brake.

31
00:01:36,477 --> 00:01:41,338
It's a configuration key called
workflowSizeGuideline and by default,

32
00:01:41,397 --> 00:01:42,337
it's set to "medium".

33
00:01:42,417 --> 00:01:42,897
Medium?

34
00:01:42,977 --> 00:01:44,177
What does...

35
00:01:44,204 --> 00:01:48,257
uh, what does "medium" actually translate
to in terms of real API requests?

36
00:01:48,444 --> 00:01:49,857
Is it a hard ceiling?

37
00:01:49,875 --> 00:01:53,475
It's actually an advisory limit of fifteen
total agents.

38
00:01:53,635 --> 00:01:57,875
But here's the cool part: instead of just,
you know, pulling the plug and crashing

39
00:01:57,891 --> 00:02:02,915
your build mid-flight when you hit
fifteen, the "medium" guideline acts as a...

40
00:02:02,955 --> 00:02:04,195
a soft advisory.

41
00:02:04,302 --> 00:02:07,475
It tells the parent agent, "Hey, you're
approaching the boundary,

42
00:02:07,528 --> 00:02:11,155
so wrap up your active branches and don't
start any new subtasks."

43
00:02:11,288 --> 00:02:14,035
It's a graceful landing rather than a hard
crash.

44
00:02:14,161 --> 00:02:16,282
Oh, I- I actually like that.

45
00:02:17,401 --> 00:02:21,301
It's like a warning light on the dash of
my trail bike rather than the engine just

46
00:02:21,421 --> 00:02:22,601
seizing up flat out.

47
00:02:23,741 --> 00:02:24,841
But look, what if I'm...

48
00:02:25,521 --> 00:02:30,861
um, what if I'm working in a strict local
environment and I absolutely do not want

49
00:02:30,901 --> 00:02:33,681
it to touch depth three under any
circumstances?

50
00:02:34,281 --> 00:02:36,462
Can I- can I chain this beast up?

51
00:02:36,682 --> 00:02:37,361
Absolutely.

52
00:02:37,881 --> 00:02:44,602
You can drop
CLAUDE_CODE_MAX_SUBAGENT_SPAWN_DEPTH=1

53
00:02:44,701 --> 00:02:46,302
straight into your shell profile, and
that'll clamp it right back to blocking any

54
00:02:46,422 --> 00:02:47,422
nested nesting at all.

55
00:02:48,181 --> 00:02:51,462
Or, if you're on the other end of the
spectrum and want to do a massive,

56
00:02:51,601 --> 00:02:56,561
hands-free refactoring of a legacy
codebase, you can run /config in the interactive

57
00:02:56,621 --> 00:03:00,361
terminal and set that
workflowSizeGuideline to "unrestricted".

58
00:03:00,494 --> 00:03:05,434
"Unrestricted" sounds like a- a very fast
way to buy Anthropic a new office block,

59
00:03:05,554 --> 00:03:06,434
but fair enough!

60
00:03:08,114 --> 00:03:11,394
Hey, speaking of the terminal, they
shipped some real, like,

61
00:03:11,574 --> 00:03:17,034
quality of life fixes in 2.1.219 that are
going to save me from pulling my hair out.

62
00:03:17,614 --> 00:03:20,234
Specifically, the network sandbox stuff.

63
00:03:20,834 --> 00:03:23,534
Have you seen
sandbox.network.strictAllowlist?

64
00:03:23,842 --> 00:03:24,342
Yes!

65
00:03:24,762 --> 00:03:27,983
Oh my god, the strict allowlist is huge.

66
00:03:28,543 --> 00:03:32,903
Previously, if a sandboxed tool tried to
hit an unauthorized external API,

67
00:03:33,402 --> 00:03:38,562
the CLI would just hang there, waiting for
you to type "yes" or "no" on a prompt

68
00:03:38,602 --> 00:03:41,623
that you sometimes couldn't even see if
you were running a background script.

69
00:03:41,667 --> 00:03:41,987
Yeah!

70
00:03:42,067 --> 00:03:43,187
It- it- it just stalled.

71
00:03:43,467 --> 00:03:48,387
Now with strictAllowlist enabled, if it's
not on the list, it's an immediate,

72
00:03:48,454 --> 00:03:49,507
clean block.

73
00:03:49,694 --> 00:03:51,267
No hanging, no prompt.

74
00:03:51,427 --> 00:03:52,787
It just keeps moving.

75
00:03:52,927 --> 00:03:55,667
And- and they also added a new event hook,
didn't they?

76
00:03:55,787 --> 00:03:58,467
For when you register a new directory
mid-session?

77
00:03:58,458 --> 00:04:00,058
Yeah, the DirectoryAdded hook.

78
00:04:00,198 --> 00:04:05,738
The moment you run /add-dir to bring a new
workspace folder into the context,

79
00:04:05,791 --> 00:04:10,378
it immediately fires off any custom setup
or indexing scripts you've defined.

80
00:04:10,511 --> 00:04:12,778
It's a game-changer for mono-repos.

81
00:04:13,751 --> 00:04:14,731
Oh, thank goodness.

82
00:04:16,272 --> 00:04:19,491
Honestly though, my favorite fix is the
most boring one.

83
00:04:20,091 --> 00:04:24,771
I use GNU screen a lot, and whenever I'd
copy text out of the Claude terminal,

84
00:04:25,191 --> 00:04:27,691
it would corrupt the buffer and output
this...

85
00:04:28,311 --> 00:04:32,831
this horrible, raw base64 garbage instead
of my code.

86
00:04:33,531 --> 00:04:36,691
That's finally gone in 2.1.219.

87
00:04:37,171 --> 00:04:42,171
And- and if you use Vim mode, hitting the
left arrow on an empty prompt now actually

88
00:04:42,271 --> 00:04:46,911
exits back to the agent view properly
instead of trapping you in terminal purgatory.

89
00:04:47,921 --> 00:04:50,042
The Vim trap is finally broken.

90
00:04:50,762 --> 00:04:53,481
Alright, I'm going to go update my shell
profile before my next run.

91
00:04:53,542 --> 00:04:55,382
Yeah, go set that depth to one, mate.

92
00:04:55,529 --> 00:04:56,982
Catch you later.