1 00:00:00,119 --> 00:00:02,419 So, I- I was out in the shed the other night, right? 2 00:00:02,799 --> 00:00:06,500 Working on the carburetor for the old DT175, and... 3 00:00:07,500 --> 00:00:10,939 and I had this massive local test suite running on my laptop. 4 00:00:11,039 --> 00:00:11,979 Just... 5 00:00:12,039 --> 00:00:18,079 sitting there, fan screaming like a gecko, totally locking up my terminal. 6 00:00:18,100 --> 00:00:23,019 And it got me thinking, why are we- we still doing this to ourselves with local AI 7 00:00:23,159 --> 00:00:25,299 code reviews when we've got the cloud? 8 00:00:25,574 --> 00:00:26,294 Exactly! 9 00:00:26,754 --> 00:00:28,394 It is that local bottleneck. 10 00:00:28,914 --> 00:00:33,694 When you run /code-review locally, it completely eats up your terminal session and 11 00:00:33,734 --> 00:00:35,155 your interactive context window. 12 00:00:35,694 --> 00:00:37,034 But /ultrareview... 13 00:00:37,054 --> 00:00:38,754 that's a whole different animal. 14 00:00:38,814 --> 00:00:43,235 It runs a multi-agent cloud review of your current branch or a GitHub PR, 15 00:00:43,715 --> 00:00:47,654 offloading all that heavy lifting to Anthropic's server infrastructure. 16 00:00:47,848 --> 00:00:48,787 Yeah, nah, it's brilliant. 17 00:00:48,847 --> 00:00:50,487 It kicks off a whole swarm, mate. 18 00:00:50,607 --> 00:00:55,467 Like, parallel agents for security, performance, correctness... 19 00:00:56,647 --> 00:01:00,487 but- but look, it used to have some real, uh, rough edges. 20 00:01:00,527 --> 00:01:05,827 Like, if you tried to run /ultrareview on a brand new repo or an isolated branch 21 00:01:05,867 --> 00:01:07,687 with no common git merge base... 22 00:01:09,647 --> 00:01:10,047 bam. 23 00:01:10,647 --> 00:01:11,347 Hard crash. 24 00:01:11,647 --> 00:01:12,467 Refused to run. 25 00:01:12,619 --> 00:01:14,339 Oh, I remember that error. 26 00:01:14,379 --> 00:01:15,639 It was so frustrating. 27 00:01:16,240 --> 00:01:18,119 But they just resolved that in the latest patch! 28 00:01:18,839 --> 00:01:23,100 Now, instead of throwing a fit, if there's no merge base, it actually offers to 29 00:01:23,139 --> 00:01:24,899 review all tracked files. 30 00:01:24,960 --> 00:01:26,159 It just falls back gracefully. 31 00:01:26,167 --> 00:01:27,127 Tracked files! 32 00:01:27,175 --> 00:01:29,127 That's- that's a massive win. 33 00:01:29,260 --> 00:01:33,447 Saves you having to, like, fake a commit or merge main in just to get a quick sanity 34 00:01:33,500 --> 00:01:33,927 check. 35 00:01:34,327 --> 00:01:36,167 And... 36 00:01:36,187 --> 00:01:37,607 and the branch parsing too. 37 00:01:37,707 --> 00:01:40,967 You don't have to get the formatting absolutely spot-on anymore. 38 00:01:41,154 --> 00:01:47,447 It- it takes human formats, like, uh, #123, or even just raw copy-pasted PR 39 00:01:47,559 --> 00:01:48,247 URLs. 40 00:01:48,250 --> 00:01:52,250 Yeah, PR 123, #123, whatever you throw at it. 41 00:01:52,370 --> 00:01:58,170 And if you make a typo on a branch name, it'll actually search the remote origin and 42 00:01:58,260 --> 00:02:00,250 suggest the closest match. 43 00:02:00,370 --> 00:02:02,970 But wait, did you see the security fix? 44 00:02:03,050 --> 00:02:06,730 There was this really wild edge case with the /clear command. 45 00:02:06,829 --> 00:02:07,629 Wait, /clear? 46 00:02:07,929 --> 00:02:08,950 What- what was happening there? 47 00:02:09,083 --> 00:02:14,123 So, if you ran /clear in an interactive session, it would sneakily bypass the cloud 48 00:02:14,163 --> 00:02:17,963 billing confirmation on any subsequent /ultrareview runs. 49 00:02:18,016 --> 00:02:21,723 So you could end up with unexpected billing spikes because it didn't ask you "Are 50 00:02:21,763 --> 00:02:22,763 you sure?" 51 00:02:22,803 --> 00:02:23,483 the next time. 52 00:02:23,500 --> 00:02:23,980 Crikey. 53 00:02:24,012 --> 00:02:25,420 That's a- a nasty one. 54 00:02:25,660 --> 00:02:27,660 Glad they patched that up. 55 00:02:27,940 --> 00:02:32,220 I don't want a rogue swarm running up a massive bill while I'm off making a cuppa. 56 00:02:32,587 --> 00:02:33,688 Definitely not. 57 00:02:33,828 --> 00:02:38,327 Especially now that the underlying engine has transitioned to claude-opus-4-8. 58 00:02:38,887 --> 00:02:42,827 The findings quality is way higher now, but you definitely want to keep an eye on 59 00:02:42,847 --> 00:02:43,927 those API costs. 60 00:02:43,958 --> 00:02:46,518 Yeah, claude-opus-4-8 is a beast. 61 00:02:46,738 --> 00:02:51,398 But that's also why /ultrareview is metered completely separately from your standard 62 00:02:51,445 --> 00:02:52,518 interactive limits. 63 00:02:52,678 --> 00:02:57,478 And get this--you can't have, like, automated subagents or loops trigger it. 64 00:02:57,558 --> 00:03:01,318 They locked that down so you don't get some runaway recursive loop eating your 65 00:03:01,375 --> 00:03:01,798 wallet. 66 00:03:01,891 --> 00:03:03,251 Which makes total sense. 67 00:03:03,751 --> 00:03:07,411 You want that human-in-the-loop confirmation before you launch a premium cloud 68 00:03:07,451 --> 00:03:07,732 swarm. 69 00:03:08,331 --> 00:03:12,491 It's perfect for running right before you open a PR, or just pointing it directly at 70 00:03:12,531 --> 00:03:14,951 a PR URL to let it run asynchronously. 71 00:03:15,000 --> 00:03:15,640 Spot on. 72 00:03:15,827 --> 00:03:18,920 No more waiting around the shed for local terminal spinners. 73 00:03:19,030 --> 00:03:21,880 Alright, I'm off to actually finish that carburetor. 74 00:03:21,992 --> 00:03:23,000 Talk soon, mate. 75 00:03:23,000 --> 00:03:23,640 Later, Lachlan.