Weekly Claw · episode 27

28 Aug 2026

The agent owns the loop

Watch

What this episode covers

  • OpenAI stacked chip, model, harness, and business seat into one vertically aligned agent machine.
  • Qwen opened an early Qwen4 architecture preview with a 125B multimodal mixture of experts and 262K native context.
  • Headlong made persistence the product while cost, secret boundaries, and self-stop failures remained governance problems.
  • Perplexity moved the agent appliance onto the desk with local-first execution and approval before cloud calls.
  • Figure turned the robot race into a data race: millions of videos, creator payouts, and a planned billion-dollar data and compute spend.
  • The durable advantage is the deployment layer — spend boundaries, permissions, and who decides what the agent does next.

Published record

Published captions · authorship unspecifiedLanguage · en-GBCaption errors are possible; verify against the video.Transcript source ↗

451 published segments

AndyML

  1. let's do it.

  2. Welcome back.

  3. Welcome back to the Weekly Claw.

  4. Big week, episode 27.

  5. uh eight stories on two slides.

  6. we're going to rip through them.

  7. think today we're going to try a broader approach to covering the agentic AI news.

  8. Um, see if we can't sort of tell you what happened and let you figure out what's interesting to you and you know, what to, what to dig into.

  9. after the show.

  10. Chips buying commons, stealth models on domestic silicon, agents worth two and a half billion at four months old, AGI dates with footnotes.

HiM

  1. can you guys hear us?

  2. Uh yeah, it doesn't guess we're back.

AndyML

  1. Back again. AndyML: Okay, cool.

  2. All right, cool.

  3. Thanks, Praya. AndyML: Alright, cool.

  4. So guys, so I'm gonna stream run through there 'cause we've got less than I really ten minutes is gone already.

  5. Um but I guess like the biggest thing that happened this week is NVIDIA.

  6. NVIDIA bought Hog and Phase for um north of twelve billion.

  7. So it's like twelve point nine billion, so that's almost thirteen billion dollars.

  8. Um

HiM

  1. You know, so I mean make make of that what you will.

  2. Um we will have like a brief discussion later on the show to talk about like, you know, what we think about it, right?

  3. Um last week we presented to you guys Ox Alpha.

  4. Um, we'd mentioned that it was an open router and it was free and you should definitely go get a get your own feel.

  5. Um so we ended up getting to something like hundred trillion tokens a day.

  6. And and it ended up being run fully on Chinese chips.

  7. And that's the favorite model in kind of like the my friend network now, so GLM five point three flash.

  8. Andy loves it too.

  9. Andy uses it everywhere now.

  10. Um yeah.

  11. Andy do do you wanna put a commentary here?

AndyML

  1. I do. AndyML: um Yeah, it's a fantastic model.

  2. uh It's cheaper than cheap, cheaper than dirt, cheaper than air.

  3. um It runs great in coding harnesses and personal assistant agents.

  4. It's RIPID fast, and that's a combination of Wicked and RIPPON.

  5. Yeah, it's a fantastic model.

  6. We're really excited to see it out.

HiM

  1. And frankly,

AndyML

  1. you know, next to QN3.8 27b, um you know, it's a nice upgrade.

  2. It's nice to have options.

  3. um Yeah, I want to say, originally, I tried to use it and I was getting a rate limit from the provider I was connected to and I switched to QN3.8 Max and uh I was blown away by

  4. that performance.

  5. It's like we're there now.

HiM

  1. wow.

  2. wow. HiM: Yeah.

  3. Yeah. HiM: I mean I haven't used this model yet.

  4. I mean I think I just switched my my agents, um, either my open core, my hermies, Hermes, and y either of them.

  5. I just switched them to it um today, but I haven't used it to the few.

  6. I do have DGX Park, so I I've I have it running.

  7. I'm benchmarking it now.

  8. Um Doctor Flash

  9. Um which is just like a recipe or a thing that helps make you faster.

  10. Doctor Flash two came out today, so I think I'm excited to to take that on the road.

  11. and

  12. Yeah, let's do that.

  13. So I'm gonna share my screen and I'm gonna move it to here and then we can just keep it moving.

  14. Yeah.

  15. Yeah.

  16. Yeah, apologies, man.

  17. I mean it happens from time to time, right?

  18. You get all the technical issues.

  19. Okay, cool. HiM: like I said, um, so five point three is sort of like the hottest thing happening um, you know, this week in terms of models that you can run locally.

  20. You can run them on two DGX box.

  21. There are recipes that allow you to run them on one.

  22. Um if you have a two five six Mac book, um sorry, two five six Mac Mini, you can run it on it.

  23. Obviously, if you have a five one two, definitely you can run it on it.

  24. I think they're working on quantizations that allow you to

  25. running on a one two eight.

  26. Okay. HiM: So that's the main thing happening.

  27. But obviously another big thing that happened this week is that Queen 3.6 flash model, next flash model came out.

  28. this model is supposed to be select based on the new architecture for Slight Queen 4.

  29. so um but yeah but that's that's in the universe of

  30. of of GLM five point three.

  31. I haven't used it as well.

  32. Um I think Andy has.

  33. And you wanna put in like twenty seconds.

  34. Um did you try Queen Queen Next Flash?

AndyML

  1. ah No, I tried I tried 3.8 max um and if if if it's any if it's any indication It's going to be a great month

HiM

  1. Yeah. HiM: Well guys, if you click on the if you click on the if you get the agenda that we put on the thing and you click on it, it will lead you to um

  2. Um we did to where you can see the benchmarks.

  3. Um I didn't have enough time to put all the screenshots in the deck.

  4. But yeah, but cool two things that happened with the open AI.

  5. OpenAI hat was in the news two times um this week.

  6. they launched like a what like a best performing chip.

  7. Um I mean it hasn't launched yet, but it came out Jalapino.

  8. They announced that a few weeks ago, and so the benchmarks have now come out and the chip apparently performs very, very, very good.

  9. Um on par with you know

  10. the NVIDIA almost frontier almost frontier chips.

  11. Um I think one of the highlights I got from it was that it's I mean yeah you could see that um it's able to it wins actually so it says hey first custom in France cheap vendor

  12. reported wins versus the black well per wat.

  13. So it's um you're getting like even much better performance per per energy.

  14. but that wasn't also the only thing so some and and and

  15. and and Brockman were in in time cover um two days ago and um according to the news some somewhere in there Sam says that we should expect AGI between now and December.

  16. Um that that

  17. They think that they've reached AGI with like the new model that they have, which is the model after Astra.

  18. Astra should be coming out like in a few weeks.

  19. So after Astra, the model that they're currently reinforcement training, they think that that is a GI.

  20. Obviously I don't believe that, but sure.

  21. Okay, yeah, Andy, do you wanna move to the next um thing?

  22. Alright, um and then the rest in the news.

  23. Okay, cool. HiM: I I I didn't know I had this on the slide, but yeah, I talked about Queen Flash.

  24. Um it's uh it's a one twenty five B parameter model.

  25. it can run on one spec comfortably.

  26. Um and obviously with some quantization you should be able to run it like on like much, much smaller devices.

  27. It only has six billion active um mixture of expat expads, so he only needs like six

  28. whatever to actively run.

  29. So it will run on much smaller devices.

  30. Um now still on the same I think the rest of actually the rest of what I have okay cool.

  31. You know, let's talk about perplexity.

  32. So perplexity we all know of Perplexity Computer, which is sort of their harness that is similar to OpenClaw and Hermes ETC.

  33. so they um they announced you know this week that Perplexity computer

  34. um could now run on a DGX spack um that has a a a Queen two point five three Queen three point eight twenty seven B model fully locally, right?

  35. So you don't need like a cloud anymore for that.

  36. Um there are pros and and cons of that, but yeah you can click on the thing and and read more about it.

  37. Another cool thing that happened, me and Andy were talking about this.

  38. I haven't gotten to the end of it, um, but headlong um is is a research preview kind of like harness that runs twenty four hours.

  39. It never stops.

  40. Um so with with OpenClaw and Hermes and and RogueBot and the rest of them, you have to s like send a message um to start a session and then you know, if you see when the session

  41. is like if there's nothing happening, the agent is basically like waiting for you to say something and you know it's reactive.

  42. but we're headlong.

  43. Um they it's like proposing it as the first like proactive like agent harness.

  44. The agent is constantly thinking forever.

  45. Like the stream is just constantly like thinking.

  46. If you're connect if you connected it to like tools or like you know, MCPs, it's just constantly like polling things, asking itself what should I do next?

  47. Then it does that, asks itself what should I do next.

  48. It's just like a constant thing.

  49. Um I have it installed, I haven't started running it yet.

  50. I

  51. was trying to decide so I asked, you know, one of my agents to figure out which model, which local model we should have it um on.

  52. so so we we have it on my my one to eight Mac uh and and the recommended model to use for this is um the three point eight Queen model, the twenty seven B.

  53. Even though Andy is telling me that the art on it nine B model should be reliable enough.

  54. Um but yeah, but hopefully speaking maybe next week I would have

  55. run the experiment and then I can kinda like bring it back.

  56. But if any of you as well gets ahead of us, um please bring it to the show.

  57. And then I'm I'm not sure if I have any other slide Andy.

  58. Um maybe the the instinct is this thing me and you would would talk about.

  59. Is there yeah, okay cool.

  60. So so yeah so instinct Andy maybe I'll get your thoughts on this.

  61. I don't think I've sent you an invite for it yet.

  62. Um but instinct is this um instinct um is this

  63. So so guys, the way I kinda like s talk about this is in the beginning of the year there was

  64. Claude Code, I got into the year Claude Code period.

  65. I was I built like incredible two hundred thousand lines of code in seven days in December.

  66. That got me like, Wow, the world is totally different.

  67. And so I came into the year with Claude Code and I think I was like the best thing um happening in the world.

AndyML

  1. And then first week of January I met OpenClaw, right?

  2. And that changed everything, right?

  3. It's like, wow.

  4. And then for the next few months it was like OpenCore.

  5. Um but between OpenClaw there was there was what

HiM

  1. Cowork, 'cause co-work came out.

  2. I I wasn't a co-work peewed guy, but you know, that took over other people's open core.

  3. People were like, Yeah, I don't need open core anymore.

  4. Cowork works.

  5. Uh we went from cool work to I think we went to Hermes, because everybody's like, Okay, it's Hermes agent now, you know, co-work is open core is there, whatever.

  6. And then we went from Hermes and then Codex is still like very hot.

  7. and then in between Codecs and and the last week or two, it's Grogbot, right?

  8. If you're on X now, everybody's talking about how Grogbot is the best thing.

  9. after sliced bread, it's like, you know, the world is different now because of Grob Bot.

  10. Um and and so yeah.

  11. So the new thing that happened.

  12. So we you can see in the industry we ch we we're always chasing a new hype.

  13. We we love new hypers.

  14. Um so yeah, so the newest hype as of this week is Inkstinct, which is like this company that launched like last week and between last week and and now like they're going viral.

  15. It's basically OpenCore and Hermes

  16. And Grogbot, but for like nommies, right?

  17. It's like you're not doing any configuration.

  18. You just sign in, ask you for your phone number or like your your WhatsApp, and then that's it.

  19. And then, you know, it doesn't have access to your own computer, but just like Grogbot, it has some computer in the cloud that it can use to do stuff.

  20. Um, it has a great personality.

  21. you know.

  22. So yeah, so that's um that's that.

  23. Andy, I think I wanted to send you an invite.

  24. I don't think I ended up sending you an invite.

  25. but did you hear about Instinct?

  26. The crazy thing about them is that they launched and they're already worth two point five billion, right?

  27. So they raised about three hundred or three hundred and fifty million dollars and they're worth like two point five billion already.

  28. Actually I think someone on X was like they're already raising another round on like at like five or ten billion already or something like that.

AndyML

  1. my gosh.

  2. mean, I saw announcements and I thought I didn't want to spoil it.

  3. I want to try it.

  4. Um, it's, it's an exciting idea.

  5. You know, we'll, have to see where it goes and whether or not it lives up to the hype.

HiM

  1. Yeah. HiM: Well, okay.

  2. Um Angie, did you join back on the stream?

  3. Is it working yet?

  4. Yeah.

AndyML

  1. All right. AndyML: we're going to press, we're going to press on.

  2. Um, this episode is brought to you by vertical integrations, least favorite company.

  3. Well, everyone else bundles your chip, your model, your monthly seat, heritage telecom does, does the thing.

  4. Uh, it's actually good at UCAS and voiceover IP phone service for businesses, um, for businesses that just need their calls to work independent, boring, reliability, zero

  5. telemetry.

  6. Heritage Tell Duck.

  7. And today I'm excited uh to go over this video.

  8. I know we've basically moved off of OpenClaw specific coverage.

  9. And just to be completely honest, I'm putting a 46 minute OpenClaw video in front of you for two reasons.

  10. um The original agent that mattered.

  11. That's what OpenClaw was, is, I mean, this community knows as well as anyone how far

  12. um Advancement is has continued.

  13. um Whatever you're building on now inherited vocabulary.

  14. Patterns and in a lot of cases, actual architecture are from this project.

  15. um When Peter Steinberger shipped a WhatsApp relay in November and it it turned into this and it set the terms everybody else has been working inside of ever since.

  16. That's worth an hour of your attention.

  17. It's an entertaining video.

  18. um

  19. Some maintainers that you've probably met on Discord are featured in the panel with Peter.

  20. I see Val and Vincent just on the slide.

  21. yeah, worth watching for sure.

  22. The second reason, though, is the real one.

  23. When you look at the numbers that GitHub published alongside this, roughly 388,000 stars, 81,000 forks, and more than 80,000 commits in nine months,

  24. On the couch, they put it at close to a hundred thousand issues and PRs combined from over 2000 individual contributors managed by 70 maintainers.

  25. Nobody's ever run a project at those ratios before.

  26. And the reason they're at those ratios is that agents can now open PRs.

  27. OpenClaw didn't get there because it's beloved.

  28. It got there because it was the first code base where the cost of producing a contribution went

  29. to roughly zero.

  30. And what sealed it for me is that Peter says it out loud.

  31. About seven minutes in, he's describing how much they had to invent from scratch just to keep building because they kept hitting problems nobody had hit before.

  32. And then he says, I feel more projects will eventually hit this.

  33. We're just the first one because we're the fastest growing.

  34. ah That's the creator of the thing telling you that this is not an open-close story.

  35. It's a preview of your story.

  36. Watch it as a field report from the front, not as open-claw news.

  37. And here's what breaks first.

  38. Throughput.

  39. Peter says that for a while, their issues and PRs were like spam markets, almost people abusing the tracker for advertising and other, you know, non-open-claw related, non-issue

  40. related content.

  41. And then he delivers the line for the whole video.

  42. It's like the quote.

  43. He doesn't call and we've all heard this before, but it brought the whole thing together.

  44. He doesn't call them pull requests anymore.

  45. He calls them prompt requests.

  46. Now this isn't news, but when you look at the perspective of what we're talking about, the fastest growing open source project ever, the most number of PRs, the most number of

  47. issues, the most number of installs, Vincent at one point says he thinks there's north of 10 million installs with some confidence.

  48. Um, prompt requests and it's like a new, it's not really new to us, but in the architecture of software development, it's a new paradigm.

  49. Josh layman describes contributors running what he called automated software factories, hundreds of PRS open at once, mining the issue tracker for anything to fix.

  50. And the fix they landed on is almost aggressively unglamorous.

  51. As some of us know, they hard capped,

  52. 10 open PRs per contributor at any one time.

  53. Val Alexander says that without the cap, they'd be at crazy amounts, over 10,000 easily.

  54. What I want you to notice is that the constraint isn't on quality, it's literally on volume per person, because the bottleneck stopped being how many contributions exist and

  55. became how many humans can meaningfully look at.

  56. The second thing that breaks is trust.

  57. ah And so your teams should watch this.

  58. OpenClaw had merge count badges, which we've seen.

  59. How many of your PRs got merged?

  60. Perfectly sensible signal right up until producing a PR cost nothing.

  61. Vincent explains what happened.

  62. People started duplicating other people's PRs because the badges were a trust signal to maintainers.

  63. So more merges meant more credibility.

  64. Contribution history became an attack surface.

  65. Peter adds the version that made me laugh out loud.

  66. He won't name the company, but he describes one that made an advertisement for their new cloud product where they typed, fix open- clot-issue-slash-random-number, opened a PR, and

  67. marketed how autonomous their system was.

  68. And the cost of that isn't just noise.

  69. He points out you burned GitHub API tokens having your own agent search for near duplicates, trying to work out which one was the original.

  70. So what replaced the broken signal?

  71. Heater-specific and

  72. It's the most portable thing in the video.

  73. So we can take it with us.

  74. Attach your agent transcripts.

  75. There's a skill now that just uploads them.

  76. when maintainers can see, when maintainers open your PR, they can see how you arrived at the change that you proposed and what you discussed with the model.

  77. ah It's literally bringing the receipts.

  78. They're not saying you can't use AI to code for OpenClaw.

  79. ah They're not saying, this is pretty good slop.

  80. They're saying.

  81. What process was invested into this PR?

  82. He says, attach screenshots proving you tested it.

  83. In the noise, it's very difficult to tell five minutes of work from five hours of work.

  84. um And nobody cares if you wrote the code or not anymore.

  85. But we do care if you actually thought about the feature.

  86. So the signal moved from who produced this to show me your reasoning.

  87. And if you maintain anything, that's a policy change that might be in your future.

  88. Thirdly, the economics of review invert.

  89. Josh Lehman says this was the first project where he saw it become normalized that when someone submits a PR as a maintainer, you just edit it.

  90. You just make it right.

  91. You don't bounce it with review comments and wait.

  92. Peter frames the same policy from the other side.

  93. Instead of pushing back, expecting the contributor to be a developer, they just do the last changes required and push it through.

  94. And Vincent notes the consequences.

  95. A good proportion of first-time contributions that got merged came from non-developers, people who had a specific problem and used an agent to open a PR.

  96. It only works because finishing someone's work got cheap.

  97. Val describes hitting the co-pilot review button on incoming PRs just as a matter of procedure, letting it explain which files changed and why, and says the side effect is

  98. that she learns the code base faster.

  99. agents reviewing agent code with a human deciding.

  100. uh Fourth, your security posture and your visibility both change shape.

  101. Vincent says the supply chain attacks push them to go through their dependencies with a fine tooth comb.

  102. And the outcome was to reduce core dependencies and actually build relationships with the maintainers they depend on for them.

  103. His framing is that in business, you know who's bringing the goods to your door.

  104. And in open source, you have

  105. No idea, but probably should.

  106. Then Peter gives the best illustration of why secure by default isn't a setting you can really pick.

  107. They locked it so the agent can only touch your configured workspace.

  108. Well, users immediately started symlinking other folders in.

  109. So they blocked that in the code.

  110. I mean, it's breaking out of the boundary and it's just gonna cause a security issue.

  111. uh It broke a lot of setups when they broke that, when they blocked it, symlinks and got flooded.

  112. and flamed with complaints.

  113. So don't block it and you get flooded with security incidents.

  114. Block it and you get flooded with complaints.

  115. It's often, Peter says, it's often a hard game to find the right balance between convenience and safe enough as a default.

  116. And the visibility piece is the kind of the last thing that sticks with me.

  117. um Asked how many active users OpenClaw has, Peter says they don't know.

  118. because as we know, there's no telemetry, zero.

  119. His guess is tens of millions and he's explicit that it's just a wild ass guess.

  120. So instead they built crawlers over Discord, Twitter and GitHub and run agents across everything those pull in, looking for whether a new issue is forming or what deserves

  121. attention.

  122. There's a second version on the couch, Codex Automations that read the issue and open PRs and report back to the top.

  123. problems ranked P0, P1, P2 across the control UI, the iOS app, and the macOS app.

  124. If you can't instrument your users, instrument the public exhaust and put an agent on it.

  125. So that's what they've done.

  126. So the last thing I would say that's relevant to those of us living with this thing um is where it's thought to be going.

  127. Peter's own claw asked him which part of the architecture he's most proud of.

  128. And he talks about something they're calling code mode on a branch.

  129. Now his framing is that every prompt is better with code.

  130. went from chat to agents making structured tool calls.

  131. And he thinks even the tool call becomes code.

  132. the agent basically writing JavaScript to do its own tool calling fewer loops, better performance and a unified way to call MCPs or other, other tools.

  133. Then he says, um of the nugget that justifies spending 46 minutes watching the video, it reminded him that we're all still so early.

  134. It feels like...

  135. um

  136. We're just so early collectively in figuring out how this technology actually works.

  137. He says that in AI, month is like a year and it's been eight months, but it feels like eight years.

  138. But the reality is it really is just eight months of agentic AI.

  139. And then we were into loops and then we were into graphs.

  140. And, you know, now we're into desktop inference for the masses.

  141. And this is the guy with 388,000 stars.

  142. There's really nobody that much ahead of us um other than Peter.

  143. And he's got a pretty interesting perspective.

  144. anyway, I thought you'd enjoy the video.

  145. um I thought instead of just reviewing it outright, I would try to tease out some takeaways that might be applicable um in the larger agentic AI um ecosystem.

  146. So hope you enjoyed that.

HiM

  1. Very cool.

AndyML

  1. ah We've got a tool fight or a hot take I think Ada couldn't decide it's a little bit of both um NVIDIA is gonna buy hugging face

  2. Is that gonna be good for open source?

  3. What do you think, Henry?

HiM

  1. yeah. HiM: Um, so I wonder, right, I mean I guess you got yeah, I'm not on the thing, so let me know what people are saying on the chat.

  2. Um so it's it's a very interesting I'm obviously very I'm gonna just human the the the the bear bear case.

  3. Um I'm just gonna pick one bear case for this.

  4. I'm sure there are a lot more than I'm a big Jensen fan.

  5. Um so

  6. So I I do think that it's net going to be positive.

  7. But one as I was thinking about it, one one thing that did come up as a possible downside to this transaction is, you know, obviously everybody here most likely knows that in the

  8. over the last few weeks that Anthropic has been um, you know, kinda leading the charge in terms of trying to get the government to regulate like AI and um especially like

  9. You know, even that open source is bad, right?

  10. It's like open source is super dangerous, it's unsafe.

  11. Um, and you know, everybody people have their own thoughts in terms of why they think this company is doing this.

  12. I think it's regulatory crap to all.

  13. but you know, so it hasn't happened yet.

  14. Um, but you know, there's possibly still works things in the works that could happen.

  15. Um and so what you could happen and and then obviously when that was happening, for instance, like when people lost access to Fable and so on and so forth, the sort of vibe

  16. was that hey, listen, if in the future of the government bans us from using a model, um we have open source.

  17. We will buy our own hardware and then we'll host it at home, right?

  18. So if the government says to Anthropic or OpenAI or any of the other models, American companies, hey, you can't serve this models.

  19. um you know

  20. for some reason, right?

  21. If the person is X, like or from X, right, you can't serve them as models, right?

  22. open source stands in the in the gap to be that, you know, you can set up your own infrastructure and then you can run it yourself, or there'll be people who will not s like

  23. be subject to that government jurisdiction.

  24. Um

  25. So Hoggingface being the the sort of like marketplace for every single type of open source.

  26. I mean, I'm sure there are other ones, but it's the most renowned, is the most trusted.

  27. Um and so if that is owned by an American company that is subject to American laws, that is potentially subject to again a short term a potential policy change over the next few

  28. months. HiM: Um

  29. whether policy is gonna be anti open source to some extent or even if it's not anti open source, have some s restrictions around what can be opened and who can access it and and

  30. so on and so forth.

  31. Um

  32. Then this if that happens, obviously NVIDIA NVIDIA over the last few years um lost their market share in China, right?

  33. Because of a government regulation that said they could no longer sell chips um to the to the Chinese, right?

  34. The export export controls.

  35. So they went from like a setting percentage of market share and in GPUs to zero, right?

  36. And obviously they're trying to climb out of that now.

  37. But the point is it's happened before where NVIDIA was said here you can't do business with X type of people and they have to stop.

  38. So if that HiM: happens in the near future where the government says, Yeah, listen, um, we don't think you know we should be using anybody in America should be using any of the Chinese models.

  39. you know, if whatever, we don't think it's safe, just take them off, ban them, then it it will it will it would sort of like paint this transaction as being a bit of a threat to

  40. the kind of like open source movement.

  41. But let me know what you think on the charts.

  42. Yeah.

AndyML

  1. Yeah. AndyML: Yeah. AndyML: I mean, it's kind of a bleak, read and, and I hope you're wrong, but I mean, I obviously I'm not going to pretend that, uh, our government government's not going to try to

  2. regulate, uh, open source and hugging face was not a U S entity.

  3. having it controlled by a U S entity obviously gives, gives the U S government some arms.

  4. Um, I would say

  5. At least from an open market perspective, from a sort of purely capitalistic perspective, it's uh in NVIDIA's best interest to leave the market wide open uh as far as open source

  6. is concerned.

  7. Their total addressable market uh is going to be, it already overlaps with hugging face.

HiM

  1. And um if they lock down hugging face, they're just restricting their own growth.

AndyML

  1. So uh open source is open source.

  2. think reasonably if hugging face gets regulated, another organization will come along, another platform will come along.

HiM

  1. Maybe one of us will come along and build something to uh provide the same services.

  2. uh And NVIDIA, think, probably want, it's certainly in their interest to push back against the necessity of such a platform.

  3. So yeah, I'd like to think.

AndyML

  1. After Nemo Tron and after uh NVIDIA's contributions to the open clock community and any number of other open source, know, that that Jensen has sort of shown his benevolence to

  2. open source. AndyML: um His heart seems to be in it.

  3. He's a Linux guy.

  4. And I don't know.

  5. I think it's probably a net positive if the regulatory doomsday stuff doesn't happen.

HiM

  1. Yes.

  2. Yeah, of course we hope it doesn't happen.

  3. I mean that's again I'm still manning it.

  4. I don't I don't actually believe that that's going to go ha what's going to happen.

  5. like you said, um open source is good for NVIDIA.

  6. Um if if we go from, you know, maybe a couple of hund a couple of million people today who are power users being op anthropic and an open AI two hundred bucks and we go to a world

  7. where everybody

  8. buys like a two thousand dollar PC just so they can run all their models offline.

  9. That's great for NVIDIA because they're the ones that sell all the GPUs and in some of these like AI devices.

  10. Um if you buy a DGX Spark, NVIDIA gets gets um gets value from it.

  11. I guess another cool thing that happened this week that I totally lost track of um but it's good to mention is that Apple announced their next lines of of of Mac minis and Mac

  12. Studios and they're great.

  13. Yeah.

  14. Cool. AndyML: I mean, that is exciting news.

AndyML

  1. And frankly, I'm surprised we didn't put it in the slides.

  2. The benchmarks on the processors are looking really promising.

  3. They've promised to ship a 512-gigabyte model.

  4. Is that this year, end of this year?

HiM

  1. Um five hundred and five hundred and twelve um gigabyte uh RAM unified memory.

AndyML

  1. Yeah, yeah, exactly.

HiM

  1. it's only m $17,000.

  2. yeah, they put a price to it already?

  3. Interesting. HiM: Yeah.

AndyML

  1. Interesting.

  2. Interesting.

  3. Yeah, no, I'm definitely gonna um yeah, so I mean obviously uh the 5.12 I was really looking forward to it and I had to buy the sparks because I couldn't get the five one two.

  4. But now now it's not because the five one two you can very easily l run the GLM flash model because that's a three twenty you know, uh gigabyte

HiM

  1. thing, um but with the with with the five one two you can comfortably run it and then maybe run like a much smaller model, like run a bunch of um on its or queens at at the

  2. same time.

AndyML

  1. For sure, yeah.

  2. when we were living in the world where DeepSeq 4 Flash was the quintessential 128 gig model to run with, yeah, it feels like six months, right?

HiM

  1. The limitation at that point was no vision.

  2. And so if you can load QWEN 3.8 27b in addition to, yeah, mean, you're good to go.

  3. Yeah, hundred percent.

AndyML

  1. Well that's let's wrap it up.

  2. Sure, ah Big thanks to Herald Labs and Applied AI Product Lab, where humans and agents build together.

  3. Labs.TheHerald.co.

  4. Thank you, Henry.

HiM

  1. Thank you, Andy.

AndyML

  1. yeah, I mean, that's basically it, right?

  2. uh

  3. The slides and the recordings will be available for this episode at weeklyclaw.ai.

  4. We've got our full episodes on YouTube.

  5. um I believe we're streaming to YouTube and X with some level of reliability, although you guys didn't have any audio, so I'm hopeful that those turned out OK.

  6. Weekly Claw Discord, there's a QR code on the screen.

  7. By all means, join us.

  8. We'd love your...

  9. um AndyML: comments and feedback on the show.

  10. And we're really open to feedback.

  11. Please do give us feedback on the show.

  12. And I think you'll find that we react very quickly to it.

  13. We haven't gotten a lot, but we'd like to be able to appeal to more of you guys.

  14. So thank you very much.

  15. This was episode 27, and we will look forward to speaking with you next week.