1
00:00:00,119 --> 00:00:04,959
You know that absolute pain where, uh,
where you are watching Claude Code refactor

2
00:00:05,079 --> 00:00:10,380
six files at once, and you are frantically
pounding alt tab or opening a second

3
00:00:10,479 --> 00:00:14,039
terminal window just to run git diff to
see what it actually touched?

4
00:00:15,599 --> 00:00:21,059
Today's episode is brought to you by
Jellypod AI, but man, Anthropic just killed

5
00:00:21,100 --> 00:00:25,239
that tab dance completely in Claude Code
version 2 point 1 point 260.

6
00:00:25,458 --> 00:00:29,058
Wait, did they finally put an actual diff
right in the terminal interface?

7
00:00:29,121 --> 00:00:29,602
They did!

8
00:00:30,121 --> 00:00:32,762
It is a live, split screen diff panel.

9
00:00:33,281 --> 00:00:36,821
So if you are running in fullscreen mode,
you just type slash diff,

10
00:00:37,181 --> 00:00:40,981
and boom, a panel snaps open right beside
your active conversation.

11
00:00:41,364 --> 00:00:42,104
Side by side?

12
00:00:42,844 --> 00:00:44,944
Like, in a standard terminal emulator?

13
00:00:44,958 --> 00:00:45,438
Yeah!

14
00:00:45,478 --> 00:00:46,558
Right in the terminal.

15
00:00:46,771 --> 00:00:52,158
As Claude writes or edits code, your
uncommitted changes update in real time in that

16
00:00:52,206 --> 00:00:52,878
side panel.

17
00:00:53,118 --> 00:00:57,438
I was doing a big React component refactor
yesterday, and while the agent was still

18
00:00:57,486 --> 00:01:02,078
streaming its response, I caught it
silently deleting an export prop that I actually

19
00:01:02,124 --> 00:01:02,558
needed.

20
00:01:02,838 --> 00:01:06,398
I saw it hit the diff pane before the turn
even finished, so I could jump in

21
00:01:06,454 --> 00:01:07,038
instantly.

22
00:01:07,042 --> 00:01:08,242
That is huge.

23
00:01:08,302 --> 00:01:13,842
And if your conversation buffer gets
totally cluttered with long tool outputs,

24
00:01:13,902 --> 00:01:16,722
can you clear the screen without losing
that diff view?

25
00:01:16,708 --> 00:01:17,348
Spot on.

26
00:01:17,448 --> 00:01:21,988
You hit control L or command K in
fullscreen, and it clears your transcript

27
00:01:22,034 --> 00:01:26,388
scrollback like a standard terminal clear,
but the live diff panel stays pinned

28
00:01:26,441 --> 00:01:27,588
right where it is.

29
00:01:27,728 --> 00:01:32,388
Now, just a quick operational heads up on
that split view, your terminal geometry

30
00:01:32,424 --> 00:01:35,988
actually needs enough horizontal columns
to render both panes,

31
00:01:36,041 --> 00:01:37,508
or it won't trigger cleanly.

32
00:01:37,599 --> 00:01:38,539
Makes total sense.

33
00:01:38,899 --> 00:01:42,059
You can't squeeze a full split diff into
an eighty column window.

34
00:01:42,099 --> 00:01:47,239
But okay, speaking of under the hood
visibility, the update to slash cost is what

35
00:01:47,260 --> 00:01:50,000
caught my eye in the 2 point 1 point 260
release notes.

36
00:01:50,042 --> 00:01:52,922
Ah, the prompt cache miss diagnostics!

37
00:01:52,917 --> 00:01:53,477
Yes!

38
00:01:53,557 --> 00:02:00,357
We had this pipeline in our CI setup where
prompt cache hit rates were just randomly

39
00:02:00,437 --> 00:02:03,677
plunging, and our API bill was spiking.

40
00:02:03,740 --> 00:02:08,277
Before this patch, the prompt cache field
in slash cost just told you,

41
00:02:08,357 --> 00:02:09,917
hey, you missed the cache.

42
00:02:10,010 --> 00:02:11,397
It never told you why.

43
00:02:11,417 --> 00:02:14,057
Right, it was just a blank number glaring
at you.

44
00:02:14,042 --> 00:02:14,762
Exactly.

45
00:02:14,842 --> 00:02:21,082
But now, both slash cost and the status
line's prompt cache field explicitly break

46
00:02:21,130 --> 00:02:22,762
down the exact root cause.

47
00:02:22,869 --> 00:02:26,522
It will literally tell you, hey, your tool
definitions changed,

48
00:02:26,575 --> 00:02:31,642
or your system prompt was modified, or you
simply idled past the time to live limit.

49
00:02:32,704 --> 00:02:36,784
Turns out it was an MCP tool server
updating its schema on launch,

50
00:02:37,045 --> 00:02:37,204
right?

51
00:02:37,375 --> 00:02:38,335
It, it, it was!

52
00:02:38,375 --> 00:02:42,495
One of our Model Context Protocol servers
was sending slightly dynamic tool

53
00:02:42,538 --> 00:02:47,055
descriptions on reboot, invalidating the
entire cached prefix every single time.

54
00:02:47,181 --> 00:02:53,135
Having that exact reason explicitly stated
in slash cost saved us hours of digging

55
00:02:53,165 --> 00:02:54,815
through API payload logs.

56
00:02:54,833 --> 00:02:56,673
That is so satisfying.

57
00:02:56,893 --> 00:03:01,953
And look, if you are running automated or
headless sessions through the Agent SDK or

58
00:03:01,999 --> 00:03:06,033
Remote Control, they added some big
quality of life tweaks there too.

59
00:03:06,153 --> 00:03:10,993
You can now use a text form slash advisor
command, like slash advisor,

60
00:03:11,064 --> 00:03:16,113
followed by the model name, or slash
advisor off, right inside headless sessions.

61
00:03:16,305 --> 00:03:21,153
Plus slash reload plugins is now
officially available for SDK users.

62
00:03:21,167 --> 00:03:25,167
Oh, that saves restarting the whole
headless process when you tweak a custom plugin!

63
00:03:25,167 --> 00:03:25,887
Precisely.

64
00:03:25,990 --> 00:03:31,247
Though do watch out if you run zsh scripts
in auto mode, they patched a security

65
00:03:31,311 --> 00:03:36,527
edge case where command substitutions
hidden inside assignments like REPORTTIME or

66
00:03:36,607 --> 00:03:39,007
DIRSTACKSIZE were auto approving.

67
00:03:39,167 --> 00:03:41,647
Now those will properly prompt you for
approval.

68
00:03:41,866 --> 00:03:42,886
Good security catch.

69
00:03:43,706 --> 00:03:48,426
So between live split screen diffing with
slash diff and cache debugging in slash

70
00:03:48,566 --> 00:03:53,886
cost, version 2 point 1 point 260 gives us
way better visibility across the board.

71
00:03:54,083 --> 00:03:56,803
No more tab switching just to check your
code edits.

72
00:03:56,936 --> 00:04:00,083
Go update your binary and give slash diff
a spin!