1
00:00:00,360 --> 00:00:05,720
This one's brought to you by Jellypod AI,
and it's the other half of the unattended

2
00:00:05,800 --> 00:00:07,420
stability story from last time.

3
00:00:08,340 --> 00:00:14,500
We covered denyInsteadOfPrompting in
2.1.319, which stops agents stalling on

4
00:00:14,540 --> 00:00:15,360
permission prompts.

5
00:00:16,460 --> 00:00:22,020
Same release, there's a change to auto
mode that can quietly turn your CI red.

6
00:00:22,703 --> 00:00:24,063
Right, so here's what changed.

7
00:00:24,503 --> 00:00:29,543
Before 2.1.319, if auto mode couldn't
reach the server side safety check,

8
00:00:29,903 --> 00:00:33,323
Claude Code fell back to a built in client
side classifier.

9
00:00:33,843 --> 00:00:38,083
That happened with telemetry or feature
flags off, and behind LLM gateways.

10
00:00:38,983 --> 00:00:39,943
Now there's no fallback.

11
00:00:40,423 --> 00:00:42,983
Calls the server can't check are asked
about or denied.

12
00:00:43,683 --> 00:00:46,943
Bedrock, Vertex and Foundry are unchanged,
per the release notes.

13
00:00:47,743 --> 00:00:50,403
And the headless part is the sharp edge.

14
00:00:51,103 --> 00:00:56,983
Previously, claude dash p in auto mode
could exit zero even when its actions were

15
00:00:57,043 --> 00:00:59,823
refused because no safety check was
available.

16
00:01:01,083 --> 00:01:03,343
A green tick, and nothing actually
happened.

17
00:01:04,003 --> 00:01:07,523
Now, text and JSON output both exit one.

18
00:01:08,317 --> 00:01:10,117
So that's good, it fails closed.

19
00:01:10,557 --> 00:01:15,037
But if you upgrade a pipeline running
behind a gateway, it can go red the moment you

20
00:01:15,077 --> 00:01:16,737
pull 2.1.319.

21
00:01:17,957 --> 00:01:23,017
Same for a resumed run: claude p with
resume and a prompt now exits one if a

22
00:01:23,057 --> 00:01:26,437
deferred tool call's MCP server is
missing, keeps the call,

23
00:01:26,777 --> 00:01:27,977
and refuses later input.

24
00:01:28,712 --> 00:01:30,672
Okay, so how do you deal with it.

25
00:01:31,792 --> 00:01:34,372
First, check what your session actually
has.

26
00:01:34,932 --> 00:01:38,692
Run slash status and look at the Auto mode
server row.

27
00:01:39,772 --> 00:01:44,052
That row used to say Enabled even when a
gateway was dropping the server side

28
00:01:44,092 --> 00:01:44,472
review.

29
00:01:45,192 --> 00:01:47,132
It's fixed now, so it tells you the truth.

30
00:01:48,095 --> 00:01:49,975
Then you've got two env vars.

31
00:01:50,535 --> 00:01:53,775
If you want the old behavior, the client
side classifier, set

32
00:01:53,995 --> 00:01:58,195
CLAUDE_CODE_AUTO_MODE_SERVER equals zero.

33
00:01:58,755 --> 00:02:03,835
So: export CLAUDE_CODE_AUTO_MODE_SERVER=0
in your shell or CI environment.

34
00:02:04,415 --> 00:02:06,655
That's the explicit opt in to the
fallback.

35
00:02:07,555 --> 00:02:08,614
Other direction is one.

36
00:02:09,195 --> 00:02:14,215
Behind a gateway,
CLAUDE_CODE_AUTO_MODE_SERVER equals one turns the server side

37
00:02:14,275 --> 00:02:18,455
check on, even with
CLAUDE_CODE_DISABLE_EXPERIMENTAL_BETAS set.

38
00:02:19,075 --> 00:02:23,775
And if your managed settings set that
betas variable, they have to set the one too,

39
00:02:24,035 --> 00:02:25,175
or the check won't come on.

40
00:02:26,483 --> 00:02:30,163
For CI, practical step: stop treating zero
as a given.

41
00:02:30,763 --> 00:02:34,983
Run your claude p job with auto mode in a
test branch, and confirm your script

42
00:02:35,023 --> 00:02:36,443
handles a non zero exit.

43
00:02:37,103 --> 00:02:41,843
If it fails, check status output first,
because the likely cause is a gateway not

44
00:02:41,903 --> 00:02:43,303
passing the server review through.

45
00:02:43,963 --> 00:02:46,303
Fix the gateway, or choose zero on
purpose.

46
00:02:46,983 --> 00:02:47,723
One more caveat.

47
00:02:48,483 --> 00:02:52,543
If your permission rules or autoMode
settings are very large,

48
00:02:53,143 --> 00:02:55,883
auto mode used to refuse without saying
why.

49
00:02:57,123 --> 00:03:01,343
Now it explains, and unless you've set
autoMode deny rules,

50
00:03:01,743 --> 00:03:02,843
it asks you in the terminal.

51
00:03:04,538 --> 00:03:06,078
A few smaller things worth a mention.

52
00:03:06,578 --> 00:03:12,598
There's a new
CLAUDE_CODE_DISABLE_FEATURE_FLAGS variable that stops feature flag

53
00:03:12,718 --> 00:03:16,798
fetching without turning off telemetry, so
every flag uses its built in default.

54
00:03:17,938 --> 00:03:21,678
Slash usage now shows spend for today,
this week and this month,

55
00:03:21,738 --> 00:03:24,938
for developers behind a Claude apps
gateway with no spend limit.

56
00:03:25,630 --> 00:03:31,730
And slash tasks has a new Earlier in this
session row listing finished subagents,

57
00:03:32,170 --> 00:03:35,210
so you can reopen one and message it, even
after a restart.

58
00:03:36,450 --> 00:03:43,270
Also slash claude-api latency-optimize,
which finds where your API code makes

59
00:03:43,310 --> 00:03:46,530
people wait and tries faster settings
against your eval.

60
00:03:47,710 --> 00:03:52,910
Bottom line: check status, pick one or
zero deliberately, and test your exit codes

61
00:03:52,950 --> 00:03:53,650
before Monday.

