1
00:00:00,000 --> 00:00:00,797
G'day everyone!

2
00:00:01,390 --> 00:00:05,281
Lachlan Reed here, and a massive thanks to
Jellypod for helping make this daily show

3
00:00:05,321 --> 00:00:06,721
a reality.

4
00:00:06,741 --> 00:00:12,648
Let's skip the fluff and jump straight
into the v2.1.162 update because we've got

5
00:00:12,696 --> 00:00:16,485
some massive security and workflow
overrides to talk about.

6
00:00:16,645 --> 00:00:21,843
James, starting with WebFetch -- they've
completely flipped the hierarchy on how

7
00:00:21,887 --> 00:00:23,607
permission rules are evaluated.

8
00:00:24,000 --> 00:00:26,639
Yeah, and this is a major security fix.

9
00:00:26,685 --> 00:00:31,361
Historically, WebFetch had a built-in list
of preapproved domains to keep things

10
00:00:31,430 --> 00:00:38,329
smooth, but in v2.1.162, explicit user
blocklists and allowlists now take

11
00:00:38,400 --> 00:00:39,769
absolute precedence.

12
00:00:39,876 --> 00:00:44,652
If you block a domain, it is blocked,
period -- even if the system previously marked

13
00:00:44,679 --> 00:00:45,332
it as safe.

14
00:00:46,000 --> 00:00:49,597
Which is a massive relief for anyone
worried about data-leak vectors [chuckles].

15
00:00:49,637 --> 00:00:54,233
I mean, if I explicitly write a rule to
keep my local development environment or

16
00:00:54,289 --> 00:00:59,913
sensitive API endpoints off the grid, I
don't want some hardcoded "preapproved" list

17
00:00:59,993 --> 00:01:01,357
bypassing my config.

18
00:01:01,570 --> 00:01:04,080
It's all about deterministic control.

19
00:01:05,000 --> 00:01:05,801
Exactly.

20
00:01:05,881 --> 00:01:09,790
Speaking of control, have you seen the UX
overhaul for slash commands?

21
00:01:10,462 --> 00:01:12,586
They finally fixed the autocomplete
behavior.

22
00:01:13,000 --> 00:01:15,565
Oh, the autocomplete change is brilliant!

23
00:01:16,134 --> 00:01:20,595
Before this, if you hit tab or clicked on
a slash command autocomplete suggestion,

24
00:01:20,808 --> 00:01:22,834
it would run the bloody thing immediately.

25
00:01:23,114 --> 00:01:27,795
I can't tell you how many times I
accidentally triggered a dry-run error or fired

26
00:01:27,835 --> 00:01:30,675
off an incomplete command because my
finger slipped.

27
00:01:30,835 --> 00:01:34,836
Now, selecting a suggestion just populates
the input box.

28
00:01:35,000 --> 00:01:37,401
It's a huge quality-of-life win.

29
00:01:37,441 --> 00:01:41,718
You get to actually review the populated
command, edit the arguments,

30
00:01:41,758 --> 00:01:43,879
and hit Enter only when you're ready.

31
00:01:44,039 --> 00:01:46,283
No more accidental executions.

32
00:01:46,363 --> 00:01:50,844
And speaking of QOL, they also tackled a
major headache for containerized

33
00:01:50,899 --> 00:01:54,042
environments: read-only config
directories.

34
00:01:55,000 --> 00:01:59,082
Yeah, this is a lifesaver for anyone
running locked-down Docker containers or

35
00:01:59,126 --> 00:02:00,721
restricted environments.

36
00:02:00,868 --> 00:02:04,926
If the CLI detects that your configuration
folder is read-only,

37
00:02:04,966 --> 00:02:07,888
instead of just crashing out with an ugly
permission error,

38
00:02:07,915 --> 00:02:10,613
it automatically provisions an in-memory
fallback.

39
00:02:10,853 --> 00:02:15,335
It keeps things running smoothly in a
temporary space without throwing a tantrum.

40
00:02:16,000 --> 00:02:18,316
Which is perfect for stateless
deployments.

41
00:02:18,436 --> 00:02:23,431
Along with that, they added a new JSON key
to the `claude agents --json` output.

42
00:02:23,538 --> 00:02:24,950
It's called `waitingFor`.

43
00:02:25,000 --> 00:02:26,844
Ah, the `waitingFor` key!

44
00:02:27,516 --> 00:02:30,047
That's a game-changer for background agent
scripting.

45
00:02:30,180 --> 00:02:35,251
It explicitly outputs exactly what state
or resource the background agent is blocked

46
00:02:35,331 --> 00:02:35,571
on.

47
00:02:35,758 --> 00:02:39,723
So, instead of your orchestrator script
guessing why an agent is hanging,

48
00:02:39,763 --> 00:02:44,122
you can parse that key directly and handle
the bottleneck programmatically.

49
00:02:45,000 --> 00:02:48,038
It makes automated pipelines so much more
robust.

50
00:02:48,182 --> 00:02:54,198
That's a wrap on the key highlights for
v2.1.162 -- grab the update and secure those

51
00:02:54,278 --> 00:02:55,320
WebFetch paths.

52
00:02:56,000 --> 00:02:57,319
Spot on, James.

53
00:02:57,379 --> 00:02:58,718
Catch you all in the next one!