← 返回原文 ↗
Hacker News 熱門48

Show HN: Moadim.io – A scheduler for agents

· 39天前
跳到正文
AI 摘要

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 URL: https://news.ycombinator.com/item?id=49571537 Points: 3 # Comments: 0

正文

Install$ cargo install --locked moadim$ moadim

Starts the server in the background at http://localhost:5784/. Requires a Unix-like OS with tmux — Moadim's portable in-process scheduler dispatches loops, then launches each agent inside a tmux session. No host cron daemon is required.

Prefer a prebuilt install? Use cargo binstall moadim or npm install -g moadim.

★Star on GitHub(opens in a new tab)crates.io↗(opens in a new tab)

The loop

Animated diagram: an agent reads goals from a goals repository and travels to a routines repository where it creates, edits, and removes routines — each routine itself a small, always-running loop with its own pace. The routines act on external repositories and tasks, and the resulting progress flows back into the goals.

Quickstart

REST — list loops
$ curl http://localhost:5784/api/v1/routines

Every loop is also a documented HTTP endpoint, with an OpenAPI schema and Swagger UI baked into the daemon.

MCP — list loops
{ "name": "list_routines", "arguments": {} }

The same call as an MCP tool, for any MCP-compatible agent connected to /mcp.

Features

  • 01

    A loop runs an agent

    A loop pairs a prompt, a schedule, and an agent — Claude, Codex, Hermes, NanoClaw, or Pi. Each tick launches it in a fresh, isolated workbench, kills hung runs, and reaps the session when it's done.

  • 02

    Runs locally, survives reboot

    Loops fire from Moadim's portable in-process scheduler — no hidden queue, no cloud. Run moadim install to register a launchd / systemd service so the daemon keeps running across logins and reboots.

  • 03

    UI · REST · MCP

    Every loop is an MCP tool and a documented HTTP endpoint — Swagger UI, an iCal feed, and a web UI baked into the daemon.

On loop engineering

FAQ

Is Moadim free? What's the license?
Yes — Moadim is open source under the MIT license, free to use, modify, and self-host. There's no paid tier and no account to create.
Is it self-hosted or a cloud service?
It runs entirely on your own machine. Loops fire from Moadim's portable in-process scheduler — no hidden queue, no cloud, no sign-up. Run moadim install to register a launchd (macOS) or systemd (Linux) service so the daemon survives logins and reboots.
Which agents does it support?
Built-in agents include Claude, Codex, Hermes, NanoClaw, and Pi. Each loop names the agent it runs; NanoClaw queues a one-shot task in its configured agent group, while the others run in Moadim's isolated workbench. The built-in Claude agent additionally needs python3 on your PATH to pre-seed unattended trust and MCP-approval state.
Which operating systems are supported?
macOS and Linux. Moadim schedules loops inside its daemon and runs agents inside tmux; running moadim install registers a launchd (macOS) or systemd (Linux) service that keeps the daemon alive across reboots. tmux needs to be on your PATH, but no host cron daemon is required.
How is each run isolated?
Every tick launches the agent in a fresh, isolated workbench. A watchdog kills hung runs, and the session is reaped once it finishes — so one run can't leak state into the next.
查看原文（Hacker News 熱門）