← All IntelClip / OtherHow OpenClaw's heartbeat bug drove auto-router adoption
From The State of Model Routing — NVIDIA, Cognition, OpenRouter · ≈26:41
“there's this fundamental um idiosyncrasy in open claw where it sends heartbeats every like 10 minutes to your model of choice just to see like if the you know, if the the the client was still active”
“the models the open source models have improved to a point where like it makes sense to segment the market”
What’s in it
- Explains why OpenRouter's auto-router sat unused for two years
- Reveals how an app's heartbeat pings suddenly drove router demand
- Shows why splitting cheap vs. premium model traffic now makes sense
Clip transcript
from like the the marketplace business that exists today. So I'd love to hear. >> So I mean we've been doing like we we've had a an auto router for like 2 years almost. Um but when we launched it, there was like no adoption of it. It was people really wanted to use specific models. Um and the the auto router just had like no real usage. It was it we mostly saw it as like a discovery play point. Like, hey, this is how you discover which model might be good for your prompt. And then um at around like January this year with open claw, it exploded. And the reason it exploded is because there's this fundamental um idiosyncrasy in open claw where it sends heartbeats every like 10 minutes to your model of choice just to see like if the you know, if the the the client was still active. >> [laughter] >> And that means that if you set Opus to be your default model, it would be like using a lot of tokens on this like heartbeat process. And so um this was the very beginning of like a very popular app with two completely different intelligence needs, completely different. And the models the open source models have improved to a point where like it makes sense to segment the market and at at least those two areas. And so that's that was how it got
Comments
Sign in to comment.
Loading comments…