1
00:00:00,079 --> 00:00:02,440
Brought to you by Jellypod AI!

2
00:00:03,079 --> 00:00:07,379
You know, Lachlan, if you have ever asked
an AI coding agent to run something like

3
00:00:07,440 --> 00:00:12,199
sed or prettier write in your terminal,
you know there is this annoying blind spot.

4
00:00:12,569 --> 00:00:14,069
Oh, mate, absolutely.

5
00:00:14,490 --> 00:00:16,909
It is like firing a arrow into the dark,
right?

6
00:00:17,389 --> 00:00:21,690
The tool runs, returns exit code zero, and
Claude is sitting there thinking,

7
00:00:22,289 --> 00:00:23,569
well, I guess that worked!

8
00:00:24,189 --> 00:00:28,649
But it has no idea what actually changed
on disk unless it goes and runs a separate

9
00:00:28,809 --> 00:00:30,750
git diff or a Read tool call.

10
00:00:31,052 --> 00:00:32,152
Exactly.

11
00:00:32,212 --> 00:00:35,492
It wastes an entire extra tool turn just
to confirm what it did.

12
00:00:36,172 --> 00:00:42,433
But in Claude Code 2.1.269, and tweaked
again in 2.1.270,

13
00:00:43,072 --> 00:00:46,232
Anthropic added a setting called
bashEditDiffEnabled.

14
00:00:46,531 --> 00:00:50,491
Okay, so what does bashEditDiffEnabled
actually do under the hood?

15
00:00:50,741 --> 00:00:55,121
When you toggle bashEditDiffEnabled in
your configuration, the Bash tool runner

16
00:00:55,181 --> 00:00:57,201
intercepts file modifications on the fly.

17
00:00:57,801 --> 00:01:02,641
So if a shell command alters a file, it
automatically appends an inline unified diff

18
00:01:02,801 --> 00:01:04,441
right into the tool result itself.

19
00:01:04,682 --> 00:01:06,241
Oh, that is clever!

20
00:01:06,921 --> 00:01:11,941
So Claude sees the exact lines that
changed immediately, no extra git diff required.

21
00:01:12,179 --> 00:01:12,879
Right on the spot.

22
00:01:13,399 --> 00:01:17,039
Though, you do have to be a bit careful
with context token usage,

23
00:01:17,099 --> 00:01:17,339
you know?

24
00:01:17,940 --> 00:01:22,819
If you run codegen or format fifty files
at once, suddenly you are dumping huge

25
00:01:22,920 --> 00:01:24,199
diffs into your context window.

26
00:01:24,469 --> 00:01:25,309
Yeah, fair point.

27
00:01:25,629 --> 00:01:28,429
You gotta weigh the convenience against
blowing out your prompt limits.

28
00:01:29,250 --> 00:01:33,130
But speaking of shell commands doing
sneaky things, there was a really important

29
00:01:33,210 --> 00:01:34,809
security fix around this too, yeah?

30
00:01:35,282 --> 00:01:37,222
Yeah, the tee command fix.

31
00:01:37,982 --> 00:01:41,482
Previously, if you set path scoped deny
rules for Edit calls,

32
00:01:41,922 --> 00:01:46,722
a Bash command using tee could sometimes
bypass the check and overwrite files

33
00:01:46,782 --> 00:01:48,402
outside your working directories.

34
00:01:49,022 --> 00:01:53,362
Now, Edit deny rules explicitly cover tee
commands in Bash too.

35
00:01:54,097 --> 00:01:57,756
Man, sandboxing AI agents is such a moving
target.

36
00:01:57,857 --> 00:02:00,296
I love seeing those security holes patched
up.

37
00:02:00,337 --> 00:02:06,596
And speaking of bugs, version 2.1.270
fixed that super annoying git prompt issue,

38
00:02:06,676 --> 00:02:06,877
right?

39
00:02:07,417 --> 00:02:07,997
Oh yeah!

40
00:02:08,497 --> 00:02:12,918
If you were in a long session, read only
git commands like git log or git status

41
00:02:13,337 --> 00:02:16,737
would suddenly start asking for explicit
user permissions out of nowhere.

42
00:02:17,692 --> 00:02:20,872
Like mate, why are you asking me for
permission to read a log?

43
00:02:21,753 --> 00:02:23,712
You have been doing it for three hours!

44
00:02:24,252 --> 00:02:30,692
It was a regression in 2.1.269, but
2.1.270 completely fixed it

45
00:02:31,212 --> 00:02:33,093
so read only git commands stay smooth.

46
00:02:33,633 --> 00:02:38,433
Plus, the goal command now automatically
handles exponential backoff retries if your

47
00:02:38,492 --> 00:02:42,433
API drops or hits rate limits, instead of
silently stalling out.

48
00:02:42,619 --> 00:02:44,919
That is a huge quality of life step.

49
00:02:46,059 --> 00:02:49,960
Little friction fixes like that make
working with terminal agents so much less

50
00:02:50,000 --> 00:02:50,480
frustrating.

51
00:02:50,699 --> 00:02:51,139
Definitely.

52
00:02:51,740 --> 00:02:56,339
Toggle bashEditDiffEnabled, update your
CLI, and your refactoring loops will be way

53
00:02:56,379 --> 00:02:56,719
faster.