1
00:00:00,373 --> 00:00:04,720
So, I was working in my shed last night,
trying to tune up my old postie bike,

2
00:00:04,760 --> 00:00:05,040
right?

3
00:00:05,240 --> 00:00:09,280
And I- I- I kept thinking, man, if only I
could just, like,

4
00:00:09,360 --> 00:00:14,960
hit Ctrl-Z on my life and get that
original bolt back in place after I've already

5
00:00:15,000 --> 00:00:16,560
cleaned the whole workbench.

6
00:00:16,860 --> 00:00:23,440
And, well, this new Claude Code update,
the v2.1.191

7
00:00:23,500 --> 00:00:28,720
release-brought to you by Jellypod AI-it
pretty much does exactly that for your

8
00:00:28,773 --> 00:00:29,920
terminal sessions.

9
00:00:30,347 --> 00:00:31,195
Wait, really?

10
00:00:31,255 --> 00:00:33,275
You're talking about the new /rewind
capability?

11
00:00:33,355 --> 00:00:37,595
Because, Lachlan, I was playing with that
this morning, and it is a complete

12
00:00:37,659 --> 00:00:39,275
game-changer for token management.

13
00:00:39,395 --> 00:00:43,675
Usually, you run /clear to wipe the
session, save your context,

14
00:00:43,715 --> 00:00:46,635
and keep your API costs down, but then
you're stuck.

15
00:00:46,695 --> 00:00:48,475
You've lost your history.

16
00:00:48,575 --> 00:00:49,035
Now?

17
00:00:49,525 --> 00:00:50,305
Exactly!

18
00:00:50,485 --> 00:00:54,545
Now, even after you've run /clear to sweep
the slate clean,

19
00:00:54,565 --> 00:00:57,345
you can actually /rewind right back to
where you were.

20
00:00:57,532 --> 00:00:59,985
It's like a- a- a temporal safety net.

21
00:01:00,105 --> 00:01:03,345
Under the hood, it's managing these
checkpoints.

22
00:01:03,465 --> 00:01:05,745
And the cool thing is how granular it is.

23
00:01:05,885 --> 00:01:10,225
You can restore just the code, just the
conversation, or both.

24
00:01:10,635 --> 00:01:12,907
Wait, how does it handle the state,
though?

25
00:01:12,939 --> 00:01:17,147
Like, if I've been running a bunch of
terminal commands, does it undo those too?

26
00:01:17,960 --> 00:01:21,053
Ah, well, that is the massive caveat,
mate.

27
00:01:22,720 --> 00:01:25,053
It does not track raw bash commands.

28
00:01:25,240 --> 00:01:31,053
So, if you ran rm -rf on a folder, or
initiated some database migration in the

29
00:01:31,104 --> 00:01:36,253
background, /rewind isn't going to
magically restore those files or roll back your

30
00:01:36,324 --> 00:01:37,053
database.

31
00:01:37,293 --> 00:01:42,253
It's strictly snapshots of your files and
the LLM conversation context.

32
00:01:42,493 --> 00:01:47,053
It's a code and convo time machine, not a
full system backup.

33
00:01:47,627 --> 00:01:48,638
Okay, that makes sense.

34
00:01:48,931 --> 00:01:53,039
So, it's taking snapshots of the files in
your workspace and the chat history.

35
00:01:53,251 --> 00:01:56,318
If you screw up your code, you can roll
back the files.

36
00:01:56,425 --> 00:01:59,358
If you just want to change what you said,
you roll back the convo.

37
00:01:59,498 --> 00:02:02,718
But don't expect it to undo a git commit
or a curl request.

38
00:02:03,625 --> 00:02:04,537
Spot on!

39
00:02:04,597 --> 00:02:05,417
You've got it.

40
00:02:05,630 --> 00:02:10,617
It's about preserving that precious
context window without losing your mind when you

41
00:02:10,667 --> 00:02:14,137
realize you actually needed that bit of
code from three prompts ago.

42
00:02:14,417 --> 00:02:20,537
Now, they also snuck in some massive
quality-of-life fixes in this 191 release.

43
00:02:20,697 --> 00:02:23,897
My laptop fan is certainly breathing a
sigh of relief.

44
00:02:24,389 --> 00:02:26,362
Oh, you mean the CPU usage?

45
00:02:26,490 --> 00:02:27,082
Yeah!

46
00:02:27,162 --> 00:02:31,162
They cut terminal streaming CPU usage by
thirty-seven percent!

47
00:02:31,242 --> 00:02:33,482
That is huge for a CLI tool.

48
00:02:34,072 --> 00:02:35,078
Thirty-seven percent!

49
00:02:35,218 --> 00:02:36,598
And you know how they did it?

50
00:02:36,726 --> 00:02:41,878
They're coalescing the text output to
one-hundred millisecond intervals instead of

51
00:02:41,926 --> 00:02:44,198
streaming every single character raw.

52
00:02:44,411 --> 00:02:48,118
It stops the terminal from choking on the
text waterfall.

53
00:02:48,198 --> 00:02:52,518
Plus, they fixed that annoying
scroll-jumping bug where the terminal would just

54
00:02:52,582 --> 00:02:57,158
violently yank your cursor around while it
was thinking, and they added permanent

55
00:02:57,216 --> 00:02:58,918
background agent stops.

56
00:02:59,548 --> 00:03:00,118
Finally!

57
00:03:00,278 --> 00:03:02,198
No more dizzying scroll jumps.

58
00:03:02,296 --> 00:03:06,038
Honestly, this makes the whole CLI feel
incredibly polished.

59
00:03:06,166 --> 00:03:09,478
Well, I'm going to go update my global npm
packages right now.

60
00:03:09,927 --> 00:03:10,743
Good on ya, mate.

61
00:03:10,816 --> 00:03:13,183
Definitely worth the install.

62
00:03:13,283 --> 00:03:14,583
Catch you next time!