logoalt Hacker News

Show HN: Moadim.io – A scheduler for agents

20 pointsby tupe12334yesterday at 11:50 PM11 commentsview on HN

Why can't we get an agent scheduler that supports all of the following:

- git compatible

- agent agnostic

- 100% open source

- os and system-agnostic

- multi-runner support

- support mcp/ui/http

- unlimited routines/crons

So I built one, moadim.io is a local Rust daemon you install in the target machine, give it a name and manage its routines via a Git repository, wants a new routine that send you a daily message from this machine? Create a pr and merge, have another routine that run every hour to pull the latest changes to the ~/.config/moadim folder.

With more than 1,000 users, I define this project as almost "done" and ready for production. Me and thousand more people are use it in a daily manner.

It currently supports Claude, Codex, Hermes, and Pi, and you are welcome to add your agent of choice as well because it's 100% configurable.

You are welcome to have a look at the source code of the daemon in "http://github.com/moadim-io/daemon"

Feel free to provide me with suggestions for more features around this topic. I don't want to branch out to new off road topics likt webhooks, this is a "done" software in the realm of agents schedulers that focus on cron-like work.

Also feel free to start the github repository and open issues and PRs for your suggestions.


Comments

tupe12334today at 2:22 AM

BTY, I monitor this thread via moadim.io, I have a routine that ping this page every 10 minutes and ping me on discord for every message that I didn’t responded to yet

aliasxneotoday at 12:58 AM

How do I know this won't just eat through my token budget? It's hard to understand from the website how "done" is derived in the loop. If it's not deterministic then it seems like it would be prone to over-engineering.

show 2 replies
hankbondtoday at 1:01 AM

Concretely and Simply, what are you actually building with this?

show 2 replies
esafaktoday at 3:12 AM

I think the actual loop engineering lives in skills and workflows. The trigger is the creation of a ticket, manual or programmatic; e.g., through an incident.

show 1 reply
quantivaiatoday at 1:29 AM

[dead]