1
00:00:00,179 --> 00:00:03,919
I was running this massive database
migration through Claude Code yesterday,

2
00:00:04,039 --> 00:00:07,779
right, and, uh, usually you just sit there
staring at a frozen cursor,

3
00:00:08,220 --> 00:00:11,439
twiddling your thumbs while the tool call
holds your terminal hostage.

4
00:00:12,149 --> 00:00:16,329
Oh, yeah, the classic two minute terminal
stare where you're terrified to hit

5
00:00:16,369 --> 00:00:18,509
control C because you might corrupt the
schema.

6
00:00:19,121 --> 00:00:20,001
Exactly, mate!

7
00:00:20,681 --> 00:00:26,721
But in the new v2 point 1 point 212
update, MCP tool calls that run longer than two

8
00:00:26,762 --> 00:00:29,081
minutes now move to the background
automatically.

9
00:00:29,741 --> 00:00:33,361
It just, uh, it just frees up your prompt
right away so you can keep chatting or

10
00:00:33,422 --> 00:00:34,081
writing code.

11
00:00:34,224 --> 00:00:36,684
Wait, so two minutes is the built in
default?

12
00:00:37,444 --> 00:00:40,804
That's, uh, what, 120,000 milliseconds?

13
00:00:40,973 --> 00:00:41,472
Spot on.

14
00:00:42,012 --> 00:00:43,732
120,000 milliseconds.

15
00:00:44,412 --> 00:00:47,932
But the beautiful part is you're not stuck
with that two minute wait if you're doing

16
00:00:48,012 --> 00:00:52,692
something like, uh, pulling slow remote
APIs or heavy container builds.

17
00:00:53,572 --> 00:00:59,253
You can set an environment variable,
export CLAUDE CODE MCP AUTO BACKGROUND MS,

18
00:00:59,652 --> 00:01:00,232
and change it.

19
00:01:00,613 --> 00:01:05,892
Right, so if I'm doing network syncs and I
know they drag after 30 seconds,

20
00:01:06,412 --> 00:01:10,652
I can just set CLAUDE CODE MCP AUTO
BACKGROUND MS to 30000.

21
00:01:10,929 --> 00:01:16,210
Yeah, 30000 ms and boom, thirty seconds
in, it drops to the back and gives you

22
00:01:16,269 --> 00:01:16,949
control back.

23
00:01:17,629 --> 00:01:22,389
Or, uh, if you're running sequential batch
scripts where step two absolutely cannot

24
00:01:22,469 --> 00:01:27,349
start until step one finishes, you just
set that environment variable to 0.

25
00:01:27,641 --> 00:01:31,181
Setting it to 0 disables the automatic
backgrounding completely,

26
00:01:31,282 --> 00:01:31,461
right?

27
00:01:32,061 --> 00:01:33,901
So it forces it to stay synchronous.

28
00:01:34,098 --> 00:01:35,318
Completely synchronous.

29
00:01:36,317 --> 00:01:40,317
Which is super critical for those
dependent tool chains where you can't have

30
00:01:40,337 --> 00:01:43,918
downstream commands firing off while the
database is still spinning up.

31
00:01:44,117 --> 00:01:48,057
So when a tool call does get backgrounded
after those 120 seconds,

32
00:01:48,617 --> 00:01:50,337
how do you know when it actually finishes?

33
00:01:50,517 --> 00:01:53,197
Does it, uh, interrupt what you're
currently typing into Claude?

34
00:01:53,530 --> 00:01:55,829
Nah, it doesn't jump scare you mid
sentence.

35
00:01:56,369 --> 00:02:00,549
The background job runs under its native
server timeout, and when it finishes,

36
00:02:00,969 --> 00:02:05,470
Claude Code handles the completion
notification quietly without hijacking your

37
00:02:05,529 --> 00:02:06,609
active prompt input.

38
00:02:06,807 --> 00:02:09,127
That is huge for developer workflow.

39
00:02:09,708 --> 00:02:13,907
And speaking of keeping your flow state,
they snuck in a couple of really nice quick

40
00:02:13,947 --> 00:02:16,287
hit quality of life features in this
release too, didn't they?

41
00:02:16,551 --> 00:02:21,031
Oh, mate, as a vim user, my hands almost
did a happy dance.

42
00:02:21,692 --> 00:02:27,831
They added vimInsertModeRemaps so you can
map two key escape shortcuts like jj

43
00:02:27,891 --> 00:02:29,132
directly in vim mode.

44
00:02:29,949 --> 00:02:30,870
No way!

45
00:02:30,949 --> 00:02:34,210
So no more reaching all the way up to the
actual escape key every time you want to

46
00:02:34,230 --> 00:02:35,369
switch modes in the CLI?

47
00:02:35,636 --> 00:02:39,777
No more reaching at all, just jj and
you're back in normal mode.

48
00:02:40,696 --> 00:02:46,257
And if you do live streams or record video
tutorials, there's CLAUDE CODE HIDE CWD

49
00:02:46,396 --> 00:02:51,116
set to 1, which strips your local file
paths out of the startup banner so you don't

50
00:02:51,196 --> 00:02:53,696
leak your entire private folder directory
on camera.

51
00:02:54,436 --> 00:02:58,337
Plus they added those live ticking elapsed
time counters on active tool calls,

52
00:02:58,756 --> 00:03:02,236
so you can actually see the seconds
counting up in real time instead of guessing if

53
00:03:02,257 --> 00:03:02,736
it froze.

54
00:03:03,051 --> 00:03:03,491
Exactly.

55
00:03:04,111 --> 00:03:09,491
Between the live timers, vim remaps, and
that 120,000 millisecond auto backgrounding

56
00:03:09,531 --> 00:03:12,771
threshold, it's just a way smoother ride
in the terminal.

57
00:03:13,292 --> 00:03:14,191
Good stuff all around.