1
00:00:00,000 --> 00:00:05,760
Lachlan here alongside James, talking
Claude Code-brought to you by Jellypod AI.

2
00:00:05,940 --> 00:00:10,000
Now, if you're like me, spending half your
day inside a terminal shell,

3
00:00:10,120 --> 00:00:12,880
you- you hate taking your hands off the
home row.

4
00:00:12,976 --> 00:00:19,760
Well, Anthropic just dropped v2.1.208 and
v2.1.209,

5
00:00:19,860 --> 00:00:24,560
and they finally added support for
vim-insert-mode-remaps in the settings.

6
00:00:24,640 --> 00:00:30,242
This means you can finally map, uh, jj to
escape when you're editing code inside the

7
00:00:30,299 --> 00:00:32,002
Claude terminal interface.

8
00:00:32,200 --> 00:00:32,640
Yes!

9
00:00:32,780 --> 00:00:37,680
Not having to reach for that physical
escape key is a massive deal for terminal

10
00:00:37,744 --> 00:00:38,080
flow.

11
00:00:38,160 --> 00:00:40,200
And it's- it's dead simple to set up.

12
00:00:40,250 --> 00:00:44,720
You just open your settings dot JSON file
inside your dot-claude folder and drop in

13
00:00:44,760 --> 00:00:45,840
a raw JSON block.

14
00:00:45,973 --> 00:00:51,520
It's literally just the key
"vimInsertModeRemaps" pointing to an object where "jj"

15
00:00:51,573 --> 00:00:52,800
is mapped to the string "<Esc>".

16
00:00:53,128 --> 00:00:53,992
Fair dinkum, mate.

17
00:00:54,125 --> 00:00:55,432
It's a lifesaver.

18
00:00:55,592 --> 00:01:00,712
Let me make sure I- I don't butcher the
syntax here, it's- it's just open curly

19
00:01:00,772 --> 00:01:07,032
bracket, quote vim-insert-mode-remaps
quote, colon, nested curly bracket,

20
00:01:07,125 --> 00:01:13,672
quote jj quote, colon, quote
left-angle-bracket Esc right-angle-bracket

21
00:01:13,739 --> 00:01:15,592
quote, and close them up.

22
00:01:15,992 --> 00:01:20,552
If you mess up a comma, the CLI will let
you know, but once it's in,

23
00:01:20,632 --> 00:01:21,912
you're flying.

24
00:01:22,019 --> 00:01:23,832
No more awkward hand stretches.

25
00:01:24,187 --> 00:01:28,153
Beyond Vim binds, they also introduced a
major accessibility toggle with the

26
00:01:28,199 --> 00:01:30,473
double-dash-ax-screen-reader flag.

27
00:01:30,633 --> 00:01:34,793
If you boot up Claude Code with that
option, it completely strips out the heavy

28
00:01:34,840 --> 00:01:36,153
interactive elements.

29
00:01:36,286 --> 00:01:41,513
No- no spinny loading animations, no
complex ANSI escape sequences that muck up

30
00:01:41,570 --> 00:01:42,633
screen readers.

31
00:01:42,740 --> 00:01:46,473
It just pipes out clean, sequential,
plain-text lines.

32
00:01:46,666 --> 00:01:48,138
Oh, that's brilliant.

33
00:01:48,250 --> 00:01:53,898
Even if you don't use a screen reader,
that clean output is gold if you're trying

34
00:01:54,031 --> 00:01:59,258
to, uh, pipe Claude's output into another
terminal utility or- or dump it straight

35
00:01:59,290 --> 00:02:00,218
into a log file.

36
00:02:00,398 --> 00:02:06,858
But the big news for the v2.1.209 hotfix
is really the- the bug squashing.

37
00:02:07,018 --> 00:02:12,778
They had this bizarre token-limit bug
where high token counts were being represented

38
00:02:12,831 --> 00:02:19,258
in scientific notation-like, uh, 1e5 or
whatever-and it completely broke the token

39
00:02:19,315 --> 00:02:20,698
parser's calculations.

40
00:02:21,095 --> 00:02:25,668
Right, because the engine was expecting an
absolute integer and instead got this

41
00:02:25,730 --> 00:02:30,628
floating scientific string, which caused
it to throw a boundary error and stall out.

42
00:02:30,908 --> 00:02:34,468
v2.1.209 squashed that completely.

43
00:02:34,564 --> 00:02:37,268
Plus, they fixed the background agent
dialogs.

44
00:02:37,348 --> 00:02:41,188
Before this patch, if you had an agent
running a task in the background and it

45
00:02:41,234 --> 00:02:45,748
needed permission to run a command, the
prompt dialog was- was essentially getting

46
00:02:45,804 --> 00:02:47,188
swallowed or frozen.

47
00:02:47,348 --> 00:02:52,308
Now, the CLI properly surfaces those
confirmation prompts so your agents don't just

48
00:02:52,404 --> 00:02:53,508
hang indefinitely.

49
00:02:53,756 --> 00:02:54,140
Spot on.

50
00:02:54,433 --> 00:02:58,380
My background linter agent was just
sitting there spinning its wheels before this

51
00:02:58,433 --> 00:02:58,780
patch.

52
00:02:58,913 --> 00:03:00,700
Absolute nightmare.

53
00:03:01,047 --> 00:03:07,740
So, quick actionable tip to wrap this up:
run npm i minus-g at-anthropic-ai slash

54
00:03:07,820 --> 00:03:14,540
claude-code right now to pull down
v2.1.209, then open up your local settings JSON

55
00:03:14,640 --> 00:03:16,780
and drop in those Vim remaps.