1 00:00:00,000 --> 00:00:00,840 G'day everyone! 2 00:00:00,900 --> 00:00:06,240 Lachlan Reed here, joined by James Turner, and first up, we owe a huge thanks to 3 00:00:06,307 --> 00:00:09,520 Jellypod for helping make this daily show a reality. 4 00:00:09,573 --> 00:00:15,120 James, mate, I was poking around the release notes for Claude Code version 2.1.176 5 00:00:15,184 --> 00:00:18,880 last night, and I stumbled on something that wasn't even in the main announcement. 6 00:00:18,976 --> 00:00:23,600 They've snuck in this incredibly cool, undocumented setting called 7 00:00:23,680 --> 00:00:25,280 `footerLinksRegexes`. 8 00:00:26,000 --> 00:00:28,256 Wait, `footerLinksRegexes`? 9 00:00:29,145 --> 00:00:30,640 That sounds like a parser config. 10 00:00:30,784 --> 00:00:33,440 What is it actually doing inside the terminal UI? 11 00:00:34,000 --> 00:00:35,200 It is exactly that! 12 00:00:35,360 --> 00:00:39,440 It lets you write regular expressions to scan your terminal output or session 13 00:00:39,510 --> 00:00:44,400 context, and then dynamically turns matching patterns-like a Jira ticket or an 14 00:00:44,462 --> 00:00:49,760 internal wiki ID-into actual, clickable status-line badges right at the bottom of 15 00:00:49,792 --> 00:00:50,400 your terminal. 16 00:00:50,613 --> 00:00:54,960 It's brilliant for local dev workflows where you're constantly jumping between 17 00:00:55,013 --> 00:00:57,680 terminal prompts and project management tools. 18 00:00:58,000 --> 00:01:00,320 Oh, that is massive for context switching. 19 00:01:00,459 --> 00:01:05,360 So instead of manually copying and pasting ticket IDs, you just click a badge in the 20 00:01:05,520 --> 00:01:06,320 CLI? 21 00:01:06,400 --> 00:01:08,720 How do we actually configure this in the settings? 22 00:01:09,000 --> 00:01:09,720 Spot on. 23 00:01:09,840 --> 00:01:13,000 You just open up your `.claude/settings.json` file. 24 00:01:13,126 --> 00:01:18,440 Inside, you add a key called `footerLinksRegexes`, which takes an array of regex 25 00:01:18,500 --> 00:01:19,160 strings. 26 00:01:19,320 --> 00:01:23,320 So, for example, if your team uses Jira, you'd add something like 27 00:01:23,507 --> 00:01:27,240 `"JIRA-\\d+"` in there. 28 00:01:27,320 --> 00:01:31,000 When Claude Code detects that pattern in your workspace or session, 29 00:01:31,053 --> 00:01:35,880 it parses it and renders a neat, clickable footer link that can map directly to your 30 00:01:35,930 --> 00:01:37,560 company's Jira URL. 31 00:01:37,720 --> 00:01:39,880 No more hunting through browser tabs. 32 00:01:40,000 --> 00:01:41,680 That is incredibly slick. 33 00:01:42,438 --> 00:01:46,651 It's basically a regex-to-hyperlink engine built directly into the status bar. 34 00:01:47,091 --> 00:01:50,251 I'm thinking of mapping this to our internal documentation wiki, 35 00:01:50,311 --> 00:01:55,851 too, like mapping `WIKI-\\d+` to our Confluence space. 36 00:01:56,000 --> 00:01:56,840 Exactly! 37 00:01:56,933 --> 00:02:00,560 It's like having a custom dashboard built into your command line. 38 00:02:00,580 --> 00:02:04,320 And look, while I was digging through the config schemas, I found a couple of other 39 00:02:04,366 --> 00:02:07,040 hidden quality-of-life gems in this release. 40 00:02:07,080 --> 00:02:10,640 First one is `wheelScrollAccelerationEnabled`. 41 00:02:10,667 --> 00:02:14,640 If you've ever used a modern precision trackpad in a terminal tool and felt like a 42 00:02:14,686 --> 00:02:19,120 single nudge sent you flying past five hundred lines of code-you can set that to 43 00:02:19,200 --> 00:02:19,760 `false`. 44 00:02:20,000 --> 00:02:20,800 Thank goodness. 45 00:02:21,644 --> 00:02:25,280 Terminal scroll acceleration on macOS trackpads is usually a nightmare. 46 00:02:25,370 --> 00:02:28,000 Turning that off is going to save my sanity. 47 00:02:28,064 --> 00:02:29,280 What else did you find in there? 48 00:02:30,000 --> 00:02:33,360 They also added automatic localization for session titles. 49 00:02:33,493 --> 00:02:37,520 So instead of just defaulting to English titles for your saved chats, 50 00:02:37,573 --> 00:02:42,240 it'll dynamically translate and name the session to match the actual language you're 51 00:02:42,307 --> 00:02:43,680 using in the chat. 52 00:02:43,860 --> 00:02:48,560 And for the cloud architecture crowd, they completely overhauled AWS Bedrock 53 00:02:48,596 --> 00:02:49,680 credential caching. 54 00:02:50,000 --> 00:02:50,640 Oh, really? 55 00:02:51,169 --> 00:02:55,369 Because previously Bedrock authentication would just expire on a hard, 56 00:02:55,422 --> 00:02:59,529 fixed one-hour timer, which was incredibly annoying if you had long-running 57 00:02:59,582 --> 00:03:00,169 sessions. 58 00:03:01,000 --> 00:03:02,040 Precisely. 59 00:03:02,120 --> 00:03:07,320 Now, it actually respects the real, underlying token expiration date returned by the 60 00:03:07,480 --> 00:03:09,320 AWS STS credentials. 61 00:03:09,613 --> 00:03:15,160 So if your IAM role allows for a twelve-hour session, Claude Code will actually 62 00:03:15,253 --> 00:03:19,720 cache and use it for the full twelve hours without constantly bugging you to 63 00:03:19,773 --> 00:03:20,680 re-authenticate. 64 00:03:21,000 --> 00:03:24,760 That's a huge relief for anyone running deep dev loops on Bedrock. 65 00:03:24,920 --> 00:03:30,120 It's those tiny, undocumented quality-of-life changes that make a tool feel truly 66 00:03:30,189 --> 00:03:30,680 native. 67 00:03:32,000 --> 00:03:32,800 Too right, mate. 68 00:03:32,933 --> 00:03:36,880 It shows they're really listening to how devs actually spend their days in the 69 00:03:36,933 --> 00:03:37,440 terminal. 70 00:03:37,584 --> 00:03:42,080 That's us for today-go tweak those settings, and we'll catch you in the next one! 71 00:03:43,000 --> 00:03:43,400 See ya!