Claude Code v2.1.169: /cd, Safe Mode, and Faster Debugging

Lachlan Reed

G'day everyone, Lachlan Reed here! Just a quick shout-out to Jellypod for making this daily show possible. Now, James, I've got to say, I was messing around with the new Claude Code v2.1.169 update in my shed last night, and they've added this new `/cd` command. It completely saved my bacon while switching between my frontend and backend repos.

James Turner

Oh, the `/cd` command is actually huge for performance. [excited] Before this, if you wanted to switch directories, you had to spin up a completely new Claude Code session. That meant tearing down your terminal environment and, crucially, destroying your prompt cache. Every time you restarted, Claude had to re-read your entire codebase context from scratch, costing you serious time and token overhead.

Lachlan Reed

Ah, the prompt cache! [chuckles] That explains why my token usage didn't spike when I jumped from my React native folder straight into my Go API directory. It keeps that cache warm in the background. It's like not having to reboot your brain every time you walk into a different room of the house.

James Turner

Exactly. It preserves that state. Now, speaking of things breaking when you switch environments, they also introduced a proper `--safe-mode` flag, which you can also trigger with the `CLAUDE_CODE_SAFE_MODE` environment variable.

Lachlan Reed

Wait, safe mode? [curious] What's that actually turning off under the hood? Is it just blocking external API calls, or is it more like starting a PC in Windows Safe Mode?

James Turner

It is very much like Windows Safe Mode. When you pass `--safe-mode`, Claude Code completely bypasses any custom plugins, ignores the instruction rules you've set up in your `CLAUDE.md` files, and blocks all custom pre- or post-execution hooks. If Claude Code is behaving weirdly or throwing errors, this lets you instantly isolate whether it's a bug in the core tool itself or if one of your custom local scripts is muckin' things up.

Lachlan Reed

That's brilliant for debugging. I once spent two hours troubleshooting an API client wrapper only to realize my own git hook was breaking the terminal pipe. [laughs] Speaking of terminal issues, have you noticed how much smoother the UI rendering feels on Mac lately?

James Turner

Yes! They finally killed that notorious 30 to 50 millisecond UI rendering lag on macOS. It used to feel just a tiny bit sluggish when streaming long responses because the terminal renderer was choking on stdout. They've optimized that loop, which drastically lowered the CPU footprint during active streaming.

Lachlan Reed

Ah, so that's why my MacBook's fans didn't sound like a jet engine taking off when I asked it to refactor a massive utility file. [laughs] And it's not just Mac users getting the love here; they also patched up a nasty bug on Windows where running `claude -p` would just hang indefinitely.

James Turner

Right, that Windows pipe hang was a real pain for developers using PowerShell or command prompts. On top of that, they've done some serious enterprise hardening. They added proper support for OpenTelemetry client certificates. So if you're running this inside a locked-down corporate network that inspects traffic or requires custom OTEL certs for logging, it won't block your connection anymore.

Lachlan Reed

It's great to see them polishing the rough edges. It makes me wonder though... [reflective] as these CLI tools get more complex with custom hooks and warm caches, are we eventually going to need a full-blown debugger just for our AI terminal assistants?