You jest, but for some reason the industry stubbornly refuses to solve the "cron job as a service" problem for end-users, whether on the web or in the OS.

I feel this is rooted in problems that extend beyond computing. Regular people are not allowed to automate things in their life. Consider that for most people, the only devices designed to allow unattended execution off a timer are a washing machine, some ovens and dishwashers, and an alarm clock (also VCRs in the previous era). Anything else requires manual actuation and staying in a synchronous loop.

I built this last year because I thought it was overdue back then already.

https://imgur.com/a/apero-TWHSKmJ

Cron triggers (or specific triggers per connector like new email in Gmail, new linear issue, etc for built in connectors).

Then you can just ask in natural language when (whatever trigger+condition) happens do x,y and z with any configuration of connectors.

It creates an agentic chain to handle the events. Parent orchestrator with limited tools invoking workers who had access to only their specific MCP servers.

Official connectors are just custom MCP servers and you could add your own MCP servers.

I definitely had the most advanced MCP client on the planet at that point, supporting every single feature of the protocol.

I think that's why I wasn't blown away by OpenClaw, I had been doing my own form of it for a while.

I need to release more stuff for people to play around with.

My friends had use cases like "I get too many emails from my kids school I can't stay on top of everything".

So the automation was just asking "when I get an email from my kids school, let me know if there's anything actionable for me in it"

[dead]