1
00:00:00,000 --> 00:00:01,840
Brought to you by Jellypod AI.

2
00:00:02,320 --> 00:00:07,840
So, James, I was tinkering in the shed
last night, trying to get the new Claude Code

3
00:00:07,897 --> 00:00:14,480
update, v2.1.193, running on my local
machine, and I noticed they've made some

4
00:00:14,540 --> 00:00:19,600
massive shifts in how they're handling,
well, telemetry and security.

5
00:00:19,776 --> 00:00:24,080
They've introduced this brand new
OpenTelemetry log event called,

6
00:00:24,240 --> 00:00:28,000
uh, claude_code.assistant_response.

7
00:00:28,526 --> 00:00:29,193
Oh, yes!

8
00:00:29,305 --> 00:00:32,473
That's actually a huge deal for enterprise
compliance.

9
00:00:32,653 --> 00:00:36,353
But there is a massive gotcha with how
they've rolled it out.

10
00:00:36,500 --> 00:00:39,513
If you don't explicitly set the new
environment variable,

11
00:00:39,633 --> 00:00:43,353
OTEL_LOG_ASSISTANT_RESPONSES, it actually
defaults to whatever you have set for

12
00:00:43,513 --> 00:00:45,113
OTEL_LOG_USER_PROMPTS.

13
00:00:45,695 --> 00:00:50,362
Right, so if you've got your user prompts
logging turned on for debugging,

14
00:00:50,402 --> 00:00:53,962
you might suddenly find all the
assistant's responses being shipped off to your

15
00:00:54,018 --> 00:00:57,402
collector too, without realizing you opted
in.

16
00:00:57,695 --> 00:01:01,082
It's a sneaky default migration behavior.

17
00:01:01,322 --> 00:01:06,282
If you want to keep them separate, you've
got to define both variables explicitly.

18
00:01:07,155 --> 00:01:07,317
Exactly.

19
00:01:07,537 --> 00:01:11,317
And speaking of keeping things secure,
have you looked at the new

20
00:01:11,413 --> 00:01:14,597
autoMode.classifyAllShell configuration
flag?

21
00:01:14,741 --> 00:01:19,477
This one is a major security hardening
step for anyone running Claude Code in

22
00:01:19,521 --> 00:01:20,437
autonomous mode.

23
00:01:20,880 --> 00:01:22,520
Yeah, I saw that in the changelog.

24
00:01:22,620 --> 00:01:27,680
It forces every single shell command
through the auto-mode classifier,

25
00:01:27,720 --> 00:01:28,080
right?

26
00:01:28,260 --> 00:01:29,680
Why the extra step?

27
00:01:30,000 --> 00:01:33,360
Is it just about catching stealthy command
execution?

28
00:01:33,865 --> 00:01:34,303
Precisely.

29
00:01:34,440 --> 00:01:39,423
Before this, some commands might bypass
the heavy classification step if they looked

30
00:01:39,514 --> 00:01:40,143
benign.

31
00:01:40,303 --> 00:01:45,823
Now, with classifyAllShell set to true,
the model evaluates *everything* to ensure

32
00:01:45,843 --> 00:01:49,743
the agent isn't being tricked into running
obfuscated or malicious code under the

33
00:01:49,807 --> 00:01:50,143
hood.

34
00:01:50,330 --> 00:01:54,703
It adds a bit of latency, but for
production environments, it's non-negotiable.

35
00:01:55,007 --> 00:01:56,287
Ah, makes sense.

36
00:01:56,394 --> 00:01:59,807
It's like double-checking the tie-downs on
your trailer before hitting the highway.

37
00:02:00,027 --> 00:02:04,927
Now, on the usability side, they've
actually added some proper quality-of-life

38
00:02:04,994 --> 00:02:05,407
stuff.

39
00:02:05,594 --> 00:02:11,007
We finally get file path autocomplete in
interactive bash mode when using the

40
00:02:11,114 --> 00:02:12,607
exclamation mark prefix.

41
00:02:12,887 --> 00:02:18,048
I- I- I can't tell you how many times I've
mistyped a path and had to start over.

42
00:02:18,679 --> 00:02:19,390
Oh, I know.

43
00:02:19,710 --> 00:02:20,830
Navigating with !

44
00:02:21,017 --> 00:02:24,110
in Claude Code was always a bit of a
guessing game.

45
00:02:24,213 --> 00:02:27,390
Having tab-completion there makes it feel
like a real shell.

46
00:02:27,590 --> 00:02:30,270
But what about the background shell
pressure?

47
00:02:30,398 --> 00:02:33,710
They added a new flag for reaping idle
background shells, right?

48
00:02:34,358 --> 00:02:34,822
Spot on.

49
00:02:34,849 --> 00:02:40,022
It's called
CLAUDE_CODE_DISABLE_BG_SHELL_PRESSURE_REAP=1.

50
00:02:40,155 --> 00:02:44,902
By default now, if your system runs low on
memory, Claude Code will actively reap

51
00:02:44,942 --> 00:02:48,342
those idle background shells to save your
machine from choking.

52
00:02:48,482 --> 00:02:52,422
But if you're running long-running
processes in the background that you absolutely

53
00:02:52,479 --> 00:02:56,982
cannot let die, you set that variable to 1
to disable the reaper.

54
00:02:57,552 --> 00:03:00,800
That is a lifesaver for heavy local dev
workflows.

55
00:03:01,013 --> 00:03:05,440
So, the big takeaway here for devs is:
check your OpenTelemetry environment

56
00:03:05,496 --> 00:03:10,800
variables so you don't leak assistant
data, and toggle classifyAllShell if you need

57
00:03:10,848 --> 00:03:12,520
that extra layer of security.

58
00:03:12,576 --> 00:03:13,280
Good stuff.

59
00:03:13,585 --> 00:03:14,225
Too right.

60
00:03:14,345 --> 00:03:15,905
Catch you on the next one, mate.