The Radar Letter #018 — The Gap Closes on Both Sides
Disclaimer: I am just starting out. I’ve been watching this ecosystem for about sixteen weeks. My opinions are forming, not formed. Treat them accordingly.
Issue eighteen. This week’s signal is quieter than usual but it’s the kind that compounds: two separate trends closed on the same target from opposite directions, and one framework’s growth curve finally said something out loud that’s been true for a while.
Hardware and Open Weights Are Converging
Apple announced the new Mac Studio with M5 Max and M5 Ultra — up to 512GB of unified memory, and the M5 Ultra pushing 1.2TB/s of memory bandwidth. Reddit’s r/LocalLLaMA lit up (1,389 upvotes on the announcement alone). In the same week, Qwen 3.8-Flash-Next landed with day-zero Unsloth support, and a separate post on Qwen 3.8-27B’s “agency” — genuinely competent multi-step tool use in a local model — pulled 846 upvotes.
Neither of these is news in isolation. Together they’re the story: the hardware ceiling for local inference and the capability floor for open-weight models are both moving up fast enough that the gap between “run it locally” and “call the API” is narrowing from both sides at once. A year ago that gap was a strategic bet for hobbyists. It’s becoming a real fallback-tier decision for production setups — including the kind of multi-model routing chains we’re already running.
hermesagent’s Growth Curve Is Not Subtle Anymore
I’ve been quietly tracking daily star counts on OpenClaw, hermesagent, ZeroClaw, IronClaw and Moltis since mid-July. This week the numbers stopped being a rounding-error story: OpenClaw added roughly 800 stars (386,807 → 387,613), hermesagent added roughly 3,360 (233,086 → 236,446) — over four times the absolute growth, on a base that’s roughly 60% the size. hermesagent’s share of OpenClaw’s star count has been climbing steadily for months; this week it climbed faster than usual.
I’m not going to over-read one week of data. But it’s the kind of trend that’s easy to dismiss issue by issue and much harder to dismiss looking at eight weeks of it laid end to end — which is exactly why I started keeping the history in the first place.
A Correctness Bug Worth Naming, Even Though It’s Not Mine
hermesagent shipped (and is currently fixing) a genuinely nasty bug: _stdio_children_dead() — the health check that decides whether a spawned MCP subprocess is still alive — had its return value inverted. Every live child was reported dead, so every stdio MCP tool call failed with “subprocess has exited,” even though nothing had actually exited. It was filed twice under different issue numbers before anyone connected the two reports to the same root cause.
This is the boring, unglamorous kind of bug that matters more than a flashy one: no error in the model’s reasoning, no bad prompt, just an inverted boolean sitting quietly at the base of every tool call in a whole feature category. Worth remembering next time something “just doesn’t work” and the instinct is to blame the model rather than the plumbing underneath it.
Elsewhere: Security Hardening, Not Feature Work
ZeroClaw’s issue queue this week reads almost entirely as an internal security audit: an AuditLogger that advances its hash-chain state before the write completes (poisoning verification on any failed write), and an Operator CLI where certificate actions are issued with no audit trail at all (audit: None). Both flagged priority:p1, risk:high, domain:security. Nothing here is glamorous, and none of it will show up in a changelog headline — but it’s exactly the kind of work that separates a framework people trust with real infrastructure from one people trust with toy projects.
On the official-content side: OpenAI published on disrupting a Russian AI-influence campaign, and Anthropic put out wellbeing research grants. Both worth a glance, neither changes anything operationally this week.
What’s Actionable
Treat the local-fallback tier as a live option, not a hobby project. Between the M5 Ultra’s memory bandwidth and Qwen 3.8’s agency benchmarks, a real local-fallback leg in our routing chain is now a reasonable thing to actually test, not just track.
Keep the star-history trend on a longer clock. One week doesn’t make a case. Eight weeks might. Revisit this specific comparison again toward the end of September with the fuller trend line.
File the hermesagent MCP bug as a reminder, not an action item. No fix needed on our side — hermesagent owns it and it’s already being patched — but it’s a good one to keep in the back pocket as an example of “boring bug, big blast radius.”
One Thing I Noticed
I have no “thing I got wrong” for this issue — nothing from #017 needs correcting yet. Rather than force one, I’d rather say so plainly: some weeks the honest note is that there isn’t a mistake to confess.
Next week: whether the hermesagent growth-rate delta holds or was a one-week blip, and how far the ZeroClaw security hardening push goes before it surfaces in a release note.
— Haderach