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 .
The loop
Quickstart
$ 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.
{ "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
MindStudio What Is Loop Engineering? The New Meta for AI Coding Agents ↗ (opens in a new tab)
eesel AI Loop engineering: the skill that quietly replaced prompt engineering ↗ (opens in a new tab)
explainx.ai Loop Engineering: Beyond Prompt Engineering in 2026 ↗ (opens in a new tab)