I was working out in the shed this morning, trying to get the carburetor on my old
Suzuki trail bike sorted, and I had this classic moment where I put down a spanner,
reached for my laptop with greasy fingers, and realized my terminal was just...
dead silent.
Flat out stalled.
Turns out, I'd updated to Claude Code v2.1.200, which is brought to you by Jellypod
AI, and this new release completely changes how the tool-use loop handles user
prompts.
It's a massive shift in safety, but man, it'll catch you out if you're not expecting
it.
Greasy fingers and raw terminal sessions, classic Lachlan.
But yeah, you're talking about the big change to the AskUserQuestion tool,
right?
They've completely killed the auto-continuation default.
It's a major safety pivot.
Before, if Claude hit a wall and needed to ask you something,
it might make an assumption and keep rolling.
Now?
It halts.
Indefinitely.
It just sits there waiting for a human brain to intervene.
Exactly, mate!
It's like pulling the handbrake.
If you're running this in a background tab or, god forbid, a headless CI pipeline,
that build is going to hang until the heat death of the universe.
They've also renamed the default permission mode from "default" to "Manual".
So if you've got scripts using flags, you've got to pass --permission-mode manual
now, or update your .claude.json to have "defaultMode": "manual".
Right, and that manual mode rename is going to break some automated setups if people
were relying on the old string.
But the real headache is the stalling in automated environments.
If you are running Claude Code in a CI/CD pipeline or as a background agent,
you *have* to configure the idle timeout.
You do that via the /config command or directly editing .claude.json.
What's the exact property there, Lachlan?
Is it just a standard timeout value?
Yeah, you go into your /config and you can set the idle timeout so it doesn't just
sit there burning cloud minutes forever.
You can actually configure it to auto-approve or fail out after a set duration.
It's a fair dinkum lifesaver for headless environments.
Otherwise, your GitHub Actions runner is just going to spin and spin until it hits
the hard repository limit.
Which is incredibly expensive if you're not paying attention.
Now, what about the terminal rendering issues?
I saw they finally addressed the tmux bug.
I've been getting terrible screen flickering on tmux 3.4 plus,
especially when Claude is outputting large chunks of markdown or file diffs.
Oh, tell me about it!
It was like a 90s rave in my terminal.
But yes, v2.1.200 introduces a synchronized terminal rendering fix specifically for
tmux 3.4 and above.
It stops that painful flicker by buffering the writes properly before flushing them
to the terminal emulator.
It's silky smooth now.
Thank goodness.
And they also added diagnostics to the installer for out-of-memory kills,
right?
I've seen a lot of juniors complain that the installer just "disappears" mid-run on
low-tier cloud VMs, like a standard 1-gigabyte RAM t2.micro on AWS.
Now, the installer actually runs a diagnostic check to detect if the OS kernel's OOM
killer stepped in and terminated the Node process, giving you a clear error message
instead of just exiting with code 137.
Yeah, no more guessing if NPM just threw a wobbly or if your tiny VM ran out of
puff.
You get a proper warning that you need to provision more swap space or upgrade your
instance.
It's a bloody good release overall, just make sure you check your config files
before you push to production.