1
00:00:00,000 --> 00:00:03,440
I was working out in the shed this
morning, trying to get the carburetor on my old

2
00:00:03,497 --> 00:00:08,240
Suzuki trail bike sorted, and I had this
classic moment where I put down a spanner,

3
00:00:08,270 --> 00:00:13,280
reached for my laptop with greasy fingers,
and realized my terminal was just...

4
00:00:13,328 --> 00:00:14,240
dead silent.

5
00:00:14,368 --> 00:00:16,200
Flat out stalled.

6
00:00:16,273 --> 00:00:22,080
Turns out, I'd updated to Claude Code
v2.1.200, which is brought to you by Jellypod

7
00:00:22,213 --> 00:00:26,720
AI, and this new release completely
changes how the tool-use loop handles user

8
00:00:26,780 --> 00:00:27,360
prompts.

9
00:00:27,520 --> 00:00:32,080
It's a massive shift in safety, but man,
it'll catch you out if you're not expecting

10
00:00:32,133 --> 00:00:32,480
it.

11
00:00:33,623 --> 00:00:37,593
Greasy fingers and raw terminal sessions,
classic Lachlan.

12
00:00:37,773 --> 00:00:41,593
But yeah, you're talking about the big
change to the AskUserQuestion tool,

13
00:00:41,633 --> 00:00:41,913
right?

14
00:00:41,993 --> 00:00:45,273
They've completely killed the
auto-continuation default.

15
00:00:45,433 --> 00:00:47,273
It's a major safety pivot.

16
00:00:47,399 --> 00:00:50,713
Before, if Claude hit a wall and needed to
ask you something,

17
00:00:50,766 --> 00:00:52,633
it might make an assumption and keep
rolling.

18
00:00:52,853 --> 00:00:53,593
Now?

19
00:00:54,793 --> 00:00:55,593
It halts.

20
00:00:55,753 --> 00:00:56,793
Indefinitely.

21
00:00:57,006 --> 00:00:59,993
It just sits there waiting for a human
brain to intervene.

22
00:01:00,280 --> 00:01:01,480
Exactly, mate!

23
00:01:01,587 --> 00:01:03,560
It's like pulling the handbrake.

24
00:01:03,853 --> 00:01:09,000
If you're running this in a background tab
or, god forbid, a headless CI pipeline,

25
00:01:09,032 --> 00:01:12,200
that build is going to hang until the heat
death of the universe.

26
00:01:12,328 --> 00:01:17,000
They've also renamed the default
permission mode from "default" to "Manual".

27
00:01:17,240 --> 00:01:22,440
So if you've got scripts using flags,
you've got to pass --permission-mode manual

28
00:01:22,500 --> 00:01:27,880
now, or update your .claude.json to have
"defaultMode": "manual".

29
00:01:28,294 --> 00:01:32,267
Right, and that manual mode rename is
going to break some automated setups if people

30
00:01:32,299 --> 00:01:33,867
were relying on the old string.

31
00:01:34,007 --> 00:01:37,387
But the real headache is the stalling in
automated environments.

32
00:01:37,574 --> 00:01:42,107
If you are running Claude Code in a CI/CD
pipeline or as a background agent,

33
00:01:42,147 --> 00:01:44,347
you *have* to configure the idle timeout.

34
00:01:44,487 --> 00:01:49,627
You do that via the /config command or
directly editing .claude.json.

35
00:01:49,723 --> 00:01:51,627
What's the exact property there, Lachlan?

36
00:01:51,654 --> 00:01:53,307
Is it just a standard timeout value?

37
00:01:53,590 --> 00:01:57,670
Yeah, you go into your /config and you can
set the idle timeout so it doesn't just

38
00:01:57,750 --> 00:01:59,990
sit there burning cloud minutes forever.

39
00:02:00,130 --> 00:02:04,790
You can actually configure it to
auto-approve or fail out after a set duration.

40
00:02:04,950 --> 00:02:07,830
It's a fair dinkum lifesaver for headless
environments.

41
00:02:07,910 --> 00:02:11,990
Otherwise, your GitHub Actions runner is
just going to spin and spin until it hits

42
00:02:12,010 --> 00:02:13,510
the hard repository limit.

43
00:02:13,795 --> 00:02:16,275
Which is incredibly expensive if you're
not paying attention.

44
00:02:16,415 --> 00:02:18,675
Now, what about the terminal rendering
issues?

45
00:02:18,915 --> 00:02:21,315
I saw they finally addressed the tmux bug.

46
00:02:21,475 --> 00:02:25,555
I've been getting terrible screen
flickering on tmux 3.4 plus,

47
00:02:25,599 --> 00:02:29,235
especially when Claude is outputting large
chunks of markdown or file diffs.

48
00:02:29,543 --> 00:02:30,823
Oh, tell me about it!

49
00:02:30,956 --> 00:02:33,703
It was like a 90s rave in my terminal.

50
00:02:33,783 --> 00:02:40,023
But yes, v2.1.200 introduces a
synchronized terminal rendering fix specifically for

51
00:02:40,130 --> 00:02:42,423
tmux 3.4 and above.

52
00:02:42,530 --> 00:02:46,903
It stops that painful flicker by buffering
the writes properly before flushing them

53
00:02:46,930 --> 00:02:48,263
to the terminal emulator.

54
00:02:48,423 --> 00:02:50,103
It's silky smooth now.

55
00:02:50,408 --> 00:02:51,208
Thank goodness.

56
00:02:51,288 --> 00:02:55,448
And they also added diagnostics to the
installer for out-of-memory kills,

57
00:02:55,488 --> 00:02:55,768
right?

58
00:02:55,928 --> 00:03:00,968
I've seen a lot of juniors complain that
the installer just "disappears" mid-run on

59
00:03:01,028 --> 00:03:06,248
low-tier cloud VMs, like a standard
1-gigabyte RAM t2.micro on AWS.

60
00:03:06,388 --> 00:03:11,768
Now, the installer actually runs a
diagnostic check to detect if the OS kernel's OOM

61
00:03:11,825 --> 00:03:16,728
killer stepped in and terminated the Node
process, giving you a clear error message

62
00:03:16,768 --> 00:03:19,208
instead of just exiting with code 137.

63
00:03:19,502 --> 00:03:24,302
Yeah, no more guessing if NPM just threw a
wobbly or if your tiny VM ran out of

64
00:03:24,366 --> 00:03:24,782
puff.

65
00:03:24,862 --> 00:03:28,782
You get a proper warning that you need to
provision more swap space or upgrade your

66
00:03:28,844 --> 00:03:29,502
instance.

67
00:03:29,715 --> 00:03:33,742
It's a bloody good release overall, just
make sure you check your config files

68
00:03:33,788 --> 00:03:35,102
before you push to production.