1 00:00:00,000 --> 00:00:02,160 G'day everyone, welcome to the show! 2 00:00:02,200 --> 00:00:04,560 I'm Lachlan Reed, here with James Turner. 3 00:00:04,620 --> 00:00:09,359 And before we get stuck into the weeds today, a quick shoutout -- thanks to Jellypod 4 00:00:09,394 --> 00:00:11,367 to help make this daily show a reality. 5 00:00:11,487 --> 00:00:15,127 Now, James, I was tinkering with the latest Claude Code update, 6 00:00:15,177 --> 00:00:21,207 version 2.1.176, and they've finally sorted out a massive headache with hook path 7 00:00:21,251 --> 00:00:22,007 matching. 8 00:00:23,000 --> 00:00:24,040 Oh, thank goodness. 9 00:00:24,386 --> 00:00:27,406 You're talking about the `if` conditions for tool-path matching, 10 00:00:27,446 --> 00:00:27,726 right? 11 00:00:27,886 --> 00:00:29,646 It was so finicky before. 12 00:00:29,806 --> 00:00:34,926 If you wanted to set up a rule for something like `Edit(src/**)` or restrict access 13 00:00:34,974 --> 00:00:39,246 with `Read(.env)`, it felt like rolling the dice on whether the glob pattern 14 00:00:39,299 --> 00:00:40,286 actually triggered. 15 00:00:41,000 --> 00:00:41,720 Spot on! 16 00:00:41,853 --> 00:00:43,800 It was like trying to herd frogs. 17 00:00:44,660 --> 00:00:49,560 But now, in v2.1.176, it's rock solid. 18 00:00:49,700 --> 00:00:53,320 You set these hooks up in your `.claude/settings.json` file. 19 00:00:53,427 --> 00:00:57,880 So if Claude tries to touch your `.env` file, the `Read(.env)` hook immediately 20 00:00:57,930 --> 00:01:01,960 catches it and can block it, or if it edits anything in `src/`, 21 00:01:01,980 --> 00:01:04,520 you can automatically run a linter or formatter. 22 00:01:05,000 --> 00:01:06,600 That's huge for team environments. 23 00:01:06,620 --> 00:01:10,680 You can literally write a rule that says, "Hey, if Claude tries to run `Edit` on any 24 00:01:10,776 --> 00:01:15,160 file in our core database directory, trigger a test runner first to make sure it 25 00:01:15,187 --> 00:01:16,680 doesn't break schema migrations." 26 00:01:16,840 --> 00:01:21,480 It makes the AI agent act like a responsible junior dev instead of a cowboy coder. 27 00:01:22,000 --> 00:01:22,720 Exactly. 28 00:01:22,773 --> 00:01:27,040 It stops it from doing a midnight push that tanks the site -- not that I've ever 29 00:01:27,088 --> 00:01:28,480 done that myself, of course. 30 00:01:29,720 --> 00:01:33,920 But look, there are two other sneaky-good updates in this release. 31 00:01:34,040 --> 00:01:38,320 First, they've added conversation-language matching for session titles. 32 00:01:39,000 --> 00:01:39,920 Wait, really? 33 00:01:40,100 --> 00:01:43,807 [genuinely surprised] So if you're chatting with Claude in Spanish or Japanese, 34 00:01:43,827 --> 00:01:47,647 the session title it generates in your history will actually match that language 35 00:01:47,717 --> 00:01:49,647 instead of defaulting to English? 36 00:01:50,000 --> 00:01:51,280 Yes, precisely! 37 00:01:51,333 --> 00:01:54,720 No more weird context-switching when you're looking through your terminal history. 38 00:01:54,840 --> 00:02:00,240 And the second one, which is massive for enterprise devs, is AWS Bedrock credential 39 00:02:00,300 --> 00:02:00,960 caching. 40 00:02:01,072 --> 00:02:04,880 They've extended the caching lifetime to match the actual expiration of the 41 00:02:04,933 --> 00:02:05,760 credentials. 42 00:02:06,000 --> 00:02:07,280 Oh, that's beautiful. 43 00:02:07,807 --> 00:02:12,320 There is nothing worse than having your terminal flow constantly interrupted because 44 00:02:12,352 --> 00:02:17,480 your AWS session tokens expired prematurely in the middle of a complex generation. 45 00:02:17,543 --> 00:02:22,000 Having that persist properly makes local Bedrock workflows so much smoother. 46 00:02:23,000 --> 00:02:23,640 Too right. 47 00:02:23,747 --> 00:02:27,320 It keeps you in the flow state, which is exactly where we want to be. 48 00:02:27,453 --> 00:02:31,640 It's great to see Anthropic polishing these developer quality-of-life features.