Show HN: Moadim.io – A scheduler for agents

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.

Show HN: Moadim.io – A scheduler for agents
moadim.io

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.

Great question but the goal is not to handle tokens economy management, this is cupeled to the agent, I want to stay agent agnostic, you tell the agent what you want it to run in the routine, for example i have a routine that split a codebase to max 50 lines a file, I told it in the routine, when finish the refactor, change the routine to run every week and check for regression and if there is take it back to run every 30 minutes and work file after file.

[dead]

You got it just right, but the idea is that the user don’t need to care about the configuration of the cron in the lower level and the agent spawning and the worktree setup etc… the daemon does it for us.

I would love to hear your feedback and features suggestions, feel free to contact me in LinkedIn https://www.linkedin.com/in/ofek-gabay/