1
00:00:00,080 --> 00:00:03,180
Welcome to the lightning round, brought to
you by Jellypod AI.

2
00:00:03,760 --> 00:00:09,720
Look, Anthropic just dropped Claude Code
version 2.1.278, and if,

3
00:00:09,880 --> 00:00:13,900
if you run auto mode, your API bill is
about to look a whole lot cleaner.

4
00:00:14,598 --> 00:00:16,498
Mate, it is, uh, about time.

5
00:00:17,118 --> 00:00:20,918
Every single background shell command or
network check used to,

6
00:00:21,318 --> 00:00:26,458
to fire off a separate classifier request,
and you paid full token price for every

7
00:00:26,578 --> 00:00:28,178
single one of those sanity checks.

8
00:00:28,428 --> 00:00:32,848
Right, but now, Anthropic shifted that
safety classification right over to the

9
00:00:32,888 --> 00:00:35,368
server side at zero extra token cost.

10
00:00:35,888 --> 00:00:40,208
So when Claude Code checks an action
before running it, those classifier tokens do

11
00:00:40,268 --> 00:00:41,408
not hit your bill anymore.

12
00:00:41,660 --> 00:00:44,840
Unless, of course, your corporate
enterprise proxy decides to,

13
00:00:45,460 --> 00:00:46,820
to throw a spanner in the works.

14
00:00:50,143 --> 00:00:51,823
Oh man, the proxy trap!

15
00:00:52,503 --> 00:00:57,283
So here is what happens: if your network
uses an LLM gateway that strips

16
00:00:57,363 --> 00:01:01,263
unrecognized payload fields, like
safeguards or safeguard results,

17
00:01:01,743 --> 00:01:03,963
the server checks never reach your
session.

18
00:01:04,200 --> 00:01:04,980
Exactly.

19
00:01:05,740 --> 00:01:08,940
Claude Code realizes it cannot talk to the
server classifier,

20
00:01:09,600 --> 00:01:14,540
so it holds the prompt and hits you with
that exact warning: We're changing auto

21
00:01:14,600 --> 00:01:17,940
mode to no longer charge for classifier
requests in Claude Code.

22
00:01:18,640 --> 00:01:20,880
However, this session isn't eligible.

23
00:01:21,120 --> 00:01:24,580
And then it falls right back to client
side checks, which means,

24
00:01:24,720 --> 00:01:28,520
well, you are back to paying for those
classifier tokens.

25
00:01:29,285 --> 00:01:33,045
I actually got caught in this exact loop
yesterday while running a background

26
00:01:33,105 --> 00:01:33,745
terminal build.

27
00:01:34,365 --> 00:01:37,805
The, the session hit a proxy prompt hang
right in the middle of a script,

28
00:01:38,185 --> 00:01:41,985
holding the whole task hostage until I
noticed the CLI sitting there,

29
00:01:42,485 --> 00:01:44,365
um, waiting for an Enter key press.

30
00:01:45,105 --> 00:01:48,405
Total nightmare when you think your
background worker is flying through code.

31
00:01:48,625 --> 00:01:49,425
That is brutal.

32
00:01:49,545 --> 00:01:53,585
But there are a couple quick ways to, you
know, diagnose and fix it,

33
00:01:53,625 --> 00:01:53,985
right?

34
00:01:54,000 --> 00:01:54,720
Spot on.

35
00:01:54,773 --> 00:01:58,240
First off, run slash status in your
terminal.

36
00:01:58,340 --> 00:02:01,360
You will see a new row called Auto mode
server.

37
00:02:01,547 --> 00:02:05,120
If server side checks are working, it says
Enabled.

38
00:02:05,280 --> 00:02:08,560
If your proxy broke the headers and forced
a fallback, it, uh,

39
00:02:08,653 --> 00:02:10,000
reads Disabled.

40
00:02:10,000 --> 00:02:15,440
And if you are stuck behind a locked down
corporate proxy where you know you cannot

41
00:02:15,520 --> 00:02:21,360
pass custom headers, you do not want that
warning interrupting headless scripts or

42
00:02:21,404 --> 00:02:23,600
terminal loops every single time.

43
00:02:23,625 --> 00:02:28,505
Right, so you just export CLAUDE CODE AUTO
MODE SERVER equals zero in your shell

44
00:02:28,575 --> 00:02:30,505
profile or environment variables.

45
00:02:30,633 --> 00:02:35,785
That opts you out of asking the server,
silences the eligibility warning completely,

46
00:02:35,885 --> 00:02:39,625
and keeps your automated tasks running
smoothly on client checks.

47
00:02:39,625 --> 00:02:43,785
Or if you manage the gateway, just
configure it to pass those request headers and

48
00:02:43,845 --> 00:02:45,785
payload fields through untouched.

49
00:02:45,895 --> 00:02:50,185
Forward the safeguards request field and
do not drop safeguard results in the

50
00:02:50,254 --> 00:02:53,785
stream, and boom, zero cost classifier
checks.

51
00:02:53,792 --> 00:02:54,512
Simple as that.

52
00:02:54,725 --> 00:02:59,072
Oh, and speaking of nice quality of life
updates, did you catch what landed in

53
00:02:59,152 --> 00:03:01,952
2.1.277 right before this?

54
00:03:01,958 --> 00:03:03,878
The, uh, instruction file fallback?

55
00:03:04,157 --> 00:03:04,437
Yes!

56
00:03:04,997 --> 00:03:11,717
One AGENTS.md can now brief Claude Code
too, in any repo that has no CLAUDE.md.

57
00:03:11,875 --> 00:03:14,515
That is huge for multi agent frameworks.

58
00:03:14,702 --> 00:03:20,355
If you already have an AGENTS.md set up
for other tools, Claude Code just reads it

59
00:03:20,401 --> 00:03:24,675
automatically without making you duplicate
rules into a CLAUDE.md file.

60
00:03:25,488 --> 00:03:30,328
Less boilerplate, zero classifier
overhead, and no more surprise proxy hangs.

61
00:03:30,928 --> 00:03:33,508
Fair dinkum, that is how you polish a
developer tool.

62
00:03:33,625 --> 00:03:34,745
That is the update.

63
00:03:34,845 --> 00:03:39,705
Get your proxy headers cleared or export
that env var, and enjoy the free classifier

64
00:03:39,785 --> 00:03:40,385
runs.

65
00:03:40,455 --> 00:03:41,145
See ya!