1
00:00:00,000 --> 00:00:05,040
Ever had Claude deep in a twenty-step
refactor only for your Wi-Fi to drop,

2
00:00:05,086 --> 00:00:06,800
taking the entire session with it?

3
00:00:07,240 --> 00:00:12,080
[exhales sharply] Lachlan here, along with
James, and this update is brought to you

4
00:00:12,133 --> 00:00:13,600
by Jellypod AI.

5
00:00:14,000 --> 00:00:17,280
That twenty-step refactor pain is so real.

6
00:00:17,550 --> 00:00:21,840
There is nothing worse than watching your
terminal hang indefinitely on a stale

7
00:00:21,891 --> 00:00:22,960
connection.

8
00:00:22,980 --> 00:00:28,560
But with Claude Code v2.1.179, Anthropic
is finally resolving this by preserving

9
00:00:28,610 --> 00:00:33,520
partial tool responses when socket
connections drop, instead of raising a raw,

10
00:00:33,560 --> 00:00:35,120
session-killing terminal error.

11
00:00:36,000 --> 00:00:38,480
Yeah, it's a massive win for CLI
stability.

12
00:00:38,582 --> 00:00:43,360
Previously, if your connection blinked
while Claude was halfway through executing a

13
00:00:43,420 --> 00:00:49,040
command, the agent state would completely
desync, leaving you with a frozen "running

14
00:00:49,104 --> 00:00:49,920
tool" spinner.

15
00:00:50,160 --> 00:00:55,600
Now, the CLI handles the TCP timeout
gracefully, keeps the output received up to the

16
00:00:55,636 --> 00:00:59,680
disconnect point, and unlocks the prompt
so you can resume without losing your

17
00:00:59,749 --> 00:01:01,520
entire agent execution history.

18
00:01:02,000 --> 00:01:06,400
And keeping those partial tool responses
is crucial because it saves you from

19
00:01:06,480 --> 00:01:09,440
re-running heavy build or test commands
from scratch.

20
00:01:09,600 --> 00:01:13,600
But honestly, the change that's going to
save the most compute is how they've

21
00:01:13,656 --> 00:01:16,240
optimized the Linux sandbox permission
globs.

22
00:01:16,326 --> 00:01:21,360
Specifically, the way broad allowRead and
denyRead policies are handled.

23
00:01:22,000 --> 00:01:25,560
Oh, those glob patterns were absolute
context hogs!

24
00:01:26,400 --> 00:01:30,800
If you specified a broad allowRead pattern
across a massive project tree to secure

25
00:01:30,832 --> 00:01:35,600
your sandbox, the runtime would serialize
those expanded paths directly into the

26
00:01:35,648 --> 00:01:36,880
Bash tool system prompt.

27
00:01:37,060 --> 00:01:41,280
You'd end up blowing your context window
on thousands of lines of raw system

28
00:01:41,342 --> 00:01:44,640
metadata before the model even started
writing code.

29
00:01:45,000 --> 00:01:49,640
Right, you were essentially paying in
tokens to tell the model what it *couldn't*

30
00:01:49,700 --> 00:01:49,960
see.

31
00:01:50,657 --> 00:01:56,044
In v2.1.179, they've refactored how the
sandbox limits are passed to the agent.

32
00:01:56,154 --> 00:02:00,364
Instead of serializing the flat, expanded
directory list into the Bash tool

33
00:02:00,408 --> 00:02:04,764
definition, the CLI now evaluates those
glob rules dynamically,

34
00:02:04,804 --> 00:02:09,164
keeping the system prompt lean and
preventing session bloat on massive repositories.

35
00:02:10,000 --> 00:02:14,800
Which makes a huge difference in response
latency, especially when you're working in

36
00:02:14,860 --> 00:02:16,240
monster monorepos.

37
00:02:16,420 --> 00:02:20,640
And speaking of development environments,
they also snuck in some crucial

38
00:02:20,690 --> 00:02:24,960
quality-of-life fixes for WSL2 and remote
setups.

39
00:02:25,200 --> 00:02:30,160
If you were running WSL2 inside VS Code or
Windows Terminal,

40
00:02:30,180 --> 00:02:34,960
the mouse-wheel scroll behavior was
completely broken in the terminal emulator,

41
00:02:34,987 --> 00:02:36,800
which is now fully fixed.

42
00:02:37,000 --> 00:02:42,040
That WSL2 scrolling issue was a massive
headache when trying to read long stack

43
00:02:42,109 --> 00:02:42,680
traces.

44
00:02:43,597 --> 00:02:47,160
They also parallelized the initialization
phase for remote plugins,

45
00:02:47,200 --> 00:02:51,400
which previously blocked the CLI startup
sequence on sequential network roundtrips

46
00:02:51,512 --> 00:02:53,880
over high-latency SSH connections.