Welcome to the show everyone!
I'm Lachlan Reed, here with James Turner, and we're recording directly from my
backyard shed today.
A big thank you to Jellypod for making this episode possible.
Now, James, mate, if you've been running the new Claude Code CLI tool,
you know how quickly those API costs can run away from you.
But the v2.1.174 release has completely overhauled the `/usage` command.
Oh, absolutely!
It's not just a basic prompt-and-completion counter anymore.
They've actually broken down the token attribution so you can see exactly which
custom skills, plugins, and background subagents are eating your budget over 24-hour
and 7-day windows.
And it even flags cache misses!
Which is massive for anyone trying to optimize their prompt caching.
If you're paying full price for a massive codebase context because of a minor edit,
`/usage` will show you that exact leak.
That cache miss tracking is a lifesaver.
But what really caught my eye in the very next dot release,
v2.1.175, is this new configuration flag: `enforceAvailableModels`.
Ah, yes, the guardrails!
Because before this, any cheeky developer in your team could just jump into their
local project config and swap out the designated model for a more expensive one,
or completely bypass the company's default fallbacks.
Exactly.
They'd bypass the default and suddenly you're paying for Opus when you wanted Haiku.
With `enforceAvailableModels` turned on, the local system strictly clamps down on
model drift.
It locks the model list to what the admin defined-no widening allowed.
It's brilliant for enterprise control.
Now, they also slipped in some really nice quality-of-life fixes in this cycle.
They finally solved those erratic terminal scroll issues by introducing
`wheelScrollAccelerationEnabled`.
I don't know about you, but my terminal was jumping around like a startled kangaroo
when scrolling through long outputs.
Mine too!
It was unusable on larger outputs.
And thank goodness they fixed the exit lag.
If you interrupted a shell command with a Control-C, the CLI used to hang for a
painful three to four seconds before returning control.
Now it's instant.
A massive relief for developers who can't stand a sluggish terminal.
That's a wrap for this quick update.
We'll catch you in the next one!
See ya!