1
00:00:00,079 --> 00:00:03,659
You are running an automated task in your
terminal, everything is humming along

2
00:00:03,759 --> 00:00:04,719
nicely, and then...

3
00:00:05,879 --> 00:00:06,239
nothing.

4
00:00:06,639 --> 00:00:07,559
Total freeze.

5
00:00:08,359 --> 00:00:12,979
You check the logs, and it turns out an
external HTTP endpoint just kept a response

6
00:00:13,039 --> 00:00:16,639
stream open without ever finishing,
leaving your agent completely hanging.

7
00:00:17,399 --> 00:00:20,000
This lightning talk is brought to you by
Jellypod AI.

8
00:00:20,639 --> 00:00:25,000
James, mate, Anthropic actually addressed
this exact headache in Claude Code version

9
00:00:25,139 --> 00:00:26,919
2.1.268, didn't they?

10
00:00:27,244 --> 00:00:28,524
Yeah, they totally did!

11
00:00:29,024 --> 00:00:34,824
In the 2.1.268 release notes, Anthropic
specifically documented a fix for WebFetch

12
00:00:35,164 --> 00:00:39,404
hanging indefinitely on a server that
keeps the response open without finishing.

13
00:00:39,984 --> 00:00:44,584
So now, by default, a fetch automatically
fails after a 300 second,

14
00:00:44,725 --> 00:00:46,844
or five minute, hard deadline.

15
00:00:46,864 --> 00:00:50,064
And on top of that, they gave us a brand
new environment variable,

16
00:00:50,504 --> 00:00:56,045
CLAUDE CODE WEBFETCH DEADLINE MS, so you
can customize that timeout to whatever fits

17
00:00:56,084 --> 00:00:56,444
your setup.

18
00:00:56,739 --> 00:00:59,359
Right, right, which is massive for CI
pipelines.

19
00:00:59,439 --> 00:01:02,139
Like, five minutes is fine when you are
sitting at your desk,

20
00:01:02,719 --> 00:01:06,859
but if you are running automated test
suites, five minutes of idle waiting is an

21
00:01:06,960 --> 00:01:08,899
absolute eternity, mate.

22
00:01:08,960 --> 00:01:14,039
So in your pipeline, you can just do
export CLAUDE CODE WEBFETCH DEADLINE MS equals

23
00:01:14,139 --> 00:01:15,260
15000, right?

24
00:01:15,920 --> 00:01:20,879
That sets a tight 15 second limit so your
builds fail fast instead of clogging up

25
00:01:20,979 --> 00:01:21,680
runner capacity.

26
00:01:21,947 --> 00:01:22,507
Exactly.

27
00:01:23,047 --> 00:01:25,567
But you do have to be a little careful
with tight timeouts.

28
00:01:26,128 --> 00:01:30,928
If you set it to something like 10 or 15
seconds, a slow documentation site or a

29
00:01:30,968 --> 00:01:36,147
heavy API endpoint might get cut off mid
response, throwing a false failure.

30
00:01:36,208 --> 00:01:40,867
And on the flip side, setting the variable
to 0 disables the deadline entirely.

31
00:01:41,507 --> 00:01:45,447
That can be super useful if you are
intentionally monitoring a live local API

32
00:01:45,587 --> 00:01:49,267
stream, but if you leave 0 in a headless
CI environment, well,

33
00:01:49,888 --> 00:01:54,228
you bring back the exact unhandled HTTP
hangs that this update was built to fix.

34
00:01:55,292 --> 00:01:58,531
Yeah, back to square one, trailing off
into the abyss!

35
00:01:59,591 --> 00:02:05,011
Now, version 2.1.268 had a few other
subtle quality of life tweaks that caught my

36
00:02:05,071 --> 00:02:05,591
eye too.

37
00:02:06,391 --> 00:02:09,411
For starters, if you are running self
hosted infrastructure,

38
00:02:09,831 --> 00:02:14,451
there is a new flag, double dash remove
session state, for the self hosted runner

39
00:02:14,511 --> 00:02:14,951
command.

40
00:02:15,712 --> 00:02:19,951
It automatically purges finished session
directories under your sessions folder so

41
00:02:20,011 --> 00:02:22,212
your disk space doesn't get clogged up
over time.

42
00:02:22,494 --> 00:02:24,615
Oh, that is super clean for maintenance.

43
00:02:25,414 --> 00:02:26,674
What else was tucked into that build?

44
00:02:26,708 --> 00:02:31,348
They added the double dash json flag to
all the claude plugin CLI commands like

45
00:02:31,428 --> 00:02:37,188
install, uninstall, enable, and disable,
making it much easier to parse plugin

46
00:02:37,259 --> 00:02:38,948
statuses programmatically.

47
00:02:39,124 --> 00:02:43,028
Plus, they tightened security in local
Cowork sessions.

48
00:02:43,128 --> 00:02:47,668
The Artifact tool now explicitly refuses
to touch local files outside your approved

49
00:02:47,708 --> 00:02:51,748
session folders or behind symlinked paths
without asking first,

50
00:02:51,788 --> 00:02:54,228
keeping local execution super contained.

51
00:02:54,308 --> 00:02:59,028
Small tweaks, but man, they make a huge
difference in daily reliability.