G'day everyone, welcome to the show!
I'm Lachlan Reed, here with James Turner.
And before we get stuck into the weeds today, a quick shoutout -- thanks to Jellypod
to help make this daily show a reality.
Now, James, I was tinkering with the latest Claude Code update,
version 2.1.176, and they've finally sorted out a massive headache with hook path
matching.
Oh, thank goodness.
You're talking about the `if` conditions for tool-path matching,
right?
It was so finicky before.
If you wanted to set up a rule for something like `Edit(src/**)` or restrict access
with `Read(.env)`, it felt like rolling the dice on whether the glob pattern
actually triggered.
Spot on!
It was like trying to herd frogs.
But now, in v2.1.176, it's rock solid.
You set these hooks up in your `.claude/settings.json` file.
So if Claude tries to touch your `.env` file, the `Read(.env)` hook immediately
catches it and can block it, or if it edits anything in `src/`,
you can automatically run a linter or formatter.
That's huge for team environments.
You can literally write a rule that says, "Hey, if Claude tries to run `Edit` on any
file in our core database directory, trigger a test runner first to make sure it
doesn't break schema migrations."
It makes the AI agent act like a responsible junior dev instead of a cowboy coder.
Exactly.
It stops it from doing a midnight push that tanks the site -- not that I've ever
done that myself, of course.
But look, there are two other sneaky-good updates in this release.
First, they've added conversation-language matching for session titles.
Wait, really?
[genuinely surprised] So if you're chatting with Claude in Spanish or Japanese,
the session title it generates in your history will actually match that language
instead of defaulting to English?
Yes, precisely!
No more weird context-switching when you're looking through your terminal history.
And the second one, which is massive for enterprise devs, is AWS Bedrock credential
caching.
They've extended the caching lifetime to match the actual expiration of the
credentials.
Oh, that's beautiful.
There is nothing worse than having your terminal flow constantly interrupted because
your AWS session tokens expired prematurely in the middle of a complex generation.
Having that persist properly makes local Bedrock workflows so much smoother.
Too right.
It keeps you in the flow state, which is exactly where we want to be.
It's great to see Anthropic polishing these developer quality-of-life features.