Yes -- this is getting very close to ClaudeClaw. Next they'll offer cloud hosting of persistent execution.

I would rather they build something similar to openclaw than all these individual features that replicate functionality.

Maybe it's less risk for them to offer the individual features. That way if people get inadvertent results, it's easier to blame the user, not the tool/company

OpenClaw's core achievement is that it was first, and that's not a moat.

The code/product itself is an absolute nightmare of overengineering, riddled with bugs and undocumented behavior changes across versions.

And unfortunately I think hearbeats are a little cost prohibitive. I burn through my plus plan with half hour cadence heartbeats checking email.

All *Claw implementations should use a local model for heartbeat, it doesn't need to do anything complex, pretty much just read a text file and do a true/false decision if there's something in there to do when it wakes up.

If so, it can either just shove the full heartbeat file to a smarter model or try to intelligently spread the tasks to the correct models.

Heartbeat should be set to be a cheaper model.

I mean you can just use /loop in both Claude Code and Codex for heartbeats.