1
00:00:00,000 --> 00:00:04,800
So, I- I was working on this really heavy
local build in the shed last night,

2
00:00:04,840 --> 00:00:09,600
right, and just as the background agent
was about to finish...

3
00:00:09,653 --> 00:00:10,160
poof.

4
00:00:10,528 --> 00:00:13,440
Just, uh, completely vanished.

5
00:00:13,680 --> 00:00:18,400
No warning, just a nasty socket error and
my terminal went dead silent.

6
00:00:19,324 --> 00:00:20,773
Oh, the socket error.

7
00:00:21,053 --> 00:00:22,653
I know that exact pain.

8
00:00:22,723 --> 00:00:26,533
You leave a Claude Code run going, and it
silently eats up your local RAM until the

9
00:00:26,640 --> 00:00:29,893
OS kernel just, you know, aggressively
terminates the process.

10
00:00:30,192 --> 00:00:30,752
Spot on.

11
00:00:30,939 --> 00:00:34,832
It's like a kangaroo loose in the paddock,
just chewing through everything until the

12
00:00:34,889 --> 00:00:35,952
system crashes.

13
00:00:36,112 --> 00:00:43,072
But, the, the new releases, v2.1.195 and
v2.1.193, they're

14
00:00:43,108 --> 00:00:46,512
actually targeting this exact background
daemon fragility.

15
00:00:46,958 --> 00:00:51,310
Wait, v2.1.195?

16
00:00:51,390 --> 00:00:53,950
What are they doing differently with the
daemons under the hood now?

17
00:00:54,240 --> 00:00:57,680
Well, they've built in this automatic
memory-pressure reaping.

18
00:00:57,973 --> 00:01:02,880
So, if you have these idle background
shells just sitting there doing nothing,

19
00:01:02,920 --> 00:01:07,120
instead of letting them hoard your RAM,
the system automatically reaps them.

20
00:01:07,200 --> 00:01:10,960
And they added self-healing control
sockets for the agent daemon itself.

21
00:01:11,484 --> 00:01:14,220
Self-healing control sockets...

22
00:01:14,284 --> 00:01:18,940
okay, so if the socket connection actually
drops or gets interrupted,

23
00:01:18,993 --> 00:01:21,900
it doesn't just bail and crash the whole
agent task anymore?

24
00:01:22,060 --> 00:01:23,100
It recovers?

25
00:01:23,402 --> 00:01:24,282
Exactly.

26
00:01:24,362 --> 00:01:27,802
It heals itself and keeps the task ticking
over in the background.

27
00:01:28,102 --> 00:01:33,962
But, say you're like me and you're
running, I don't know, a local database or a

28
00:01:34,013 --> 00:01:37,642
persistent test runner in one of those
background shells...

29
00:01:37,682 --> 00:01:41,882
you might not want the system to
aggressively reap it when your RAM gets tight.

30
00:01:42,168 --> 00:01:43,208
Yeah, definitely.

31
00:01:43,341 --> 00:01:47,448
If I'm running a local hot-reloading
server, the last thing I want is the agent

32
00:01:47,494 --> 00:01:50,808
memory controller quietly killing my dev
server process.

33
00:01:50,968 --> 00:01:52,968
Is there a way to, like, opt out of that?

34
00:01:53,277 --> 00:01:53,517
Yep.

35
00:01:53,565 --> 00:01:55,357
They gave us a new environment variable.

36
00:01:55,497 --> 00:02:01,917
You just set
CLAUDE_CODE_DISABLE_BG_SHELL_PRESSURE_REAP=1 and it flags those shells

37
00:02:01,944 --> 00:02:05,917
to stay alive, no matter how much memory
pressure the OS is screaming about.

38
00:02:06,213 --> 00:02:13,813
CLAUDE_CODE_DISABLE_BG_SHELL_PRESSURE_REAP=1.

39
00:02:13,957 --> 00:02:17,093
That is a massive relief for persistent
local services.

40
00:02:17,280 --> 00:02:21,813
It actually lets us run long-lived agent
loops without babying the terminal.

41
00:02:22,108 --> 00:02:22,748
Too right.

42
00:02:22,928 --> 00:02:27,388
And, oh, they snuck in this other tiny
feature that I'm already using constantly.

43
00:02:27,628 --> 00:02:33,628
In bash mode, if you type an exclamation
mark-just a single !-it instantly triggers

44
00:02:33,692 --> 00:02:35,308
file path autocompletion.

45
00:02:35,826 --> 00:02:37,858
No way, just the exclamation mark?

46
00:02:37,970 --> 00:02:43,138
That is so much faster than constantly
hitting tab or typing out deeply nested

47
00:02:43,185 --> 00:02:45,138
directories while you're trying to guide
the agent.

48
00:02:45,453 --> 00:02:46,653
Mate, it's brilliant.

49
00:02:46,760 --> 00:02:50,333
Makes navigating the project structure
feel incredibly snappy.

50
00:02:50,445 --> 00:02:55,373
Good to see them hardening the plumbing
while making the actual developer UX a bit

51
00:02:55,417 --> 00:02:55,933
smoother.

52
00:02:56,227 --> 00:03:01,347
Yeah, keeping those background processes
stable makes a huge difference.

53
00:03:01,411 --> 00:03:02,547
Glad they've sorted this out.