Moadim.
~/.config/moadim folder.How the deployment workflow actually works
Since this is a local daemon, the "deployment" is basically just Git ops for your LLM agents. Here is the general flow for getting a routine running from scratch:
1. Install the Rust-based daemon on your target OS (it's system-agnostic, so it doesn't matter if you're on Linux or macOS).
2. Initialize the daemon and point it to your configuration repository.
3. Create a configuration file for your agent routine in your repo.
4. Push the change and merge the PR.
5. The daemon detects the update in ~/.config/moadim and schedules the task.
Model support and flexibility
One of the biggest pain points with schedulers is being locked into one provider. Moadim.io is agent-agnostic and currently supports Claude, Codex, Hermes, and Pi. Because it's 100% configurable, you can essentially plug in any agent that fits the interface. It also supports MCP, UI, and HTTP, which makes it flexible enough to trigger different types of agentic workflows without needing a massive middleware stack.
Performance and reliability
The fact that this is written in Rust means the overhead is negligible. It's designed for "cron-like" work—tasks that need to happen on a fixed schedule without manual intervention. I've noticed it handles unlimited routines without the typical memory leak issues you see in Node-based schedulers. With over 1,000 users already running this in production, the stability seems solid.
If you want to see how the daemon is structured or contribute a new agent provider, the source is available here:
http://github.com/moadim-io/daemonFinal take on the architecture
I really appreciate that the developer isn't trying to turn this into a "platform" with bloated features like webhooks. It stays focused on being a scheduler. For anyone building a complex AI workflow, having your schedules version-controlled in Git is a massive win for auditability. You can see exactly when a prompt was changed or when a routine's frequency was altered just by looking at the commit history, rather than guessing based on a database timestamp.