The patterns it shipped in June 2024 — todos as an agent dispatch queue, tools gated by phase, a planning stage before execution — later turned up in mainstream tooling. It runs locally the same as it always did; it just is not moving any more.
A Node MCP server for workflow orchestration. It runs an explicit `INIT → QUERY → ENHANCE → KNOWLEDGE → PLAN → EXECUTE → VERIFY → DONE` loop, restricts which tools are reachable in each phase, and treats todo items as dispatches for specialised agents. The author has archived the project.
- `JARVIS` — the eight-phase workflow controller
- `APITaskAgent` — API discovery and fetching with SSRF protection
- `PythonComputationalTool` — Python execution for data analysis
- `IronManusStateGraph` — session state management
- `SlideGenerator` — HTML slide generation
- `HealthCheck` — runtime diagnostics
- Phase-gated tool access, so writing files during verification is structurally impossible rather than discouraged
- Nine roles with distinct thinking methods: `planner`, `coder`, `critic`, `researcher`, `analyzer`, `synthesizer`, `ui_architect`, `ui_implementer`, `ui_refiner`
- File-based handoff between agents that cannot share context directly, under `./iron-manus-sessions/{session_id}/`
Node.js 20+, built from source with `npm install && npm run build`, or run from the Docker image. Outbound calls are gated: `ALLOWED_HOSTS` is the allowlist, `ENABLE_SSRF_PROTECTION` turns the check on, and `KNOWLEDGE_MAX_CONCURRENCY` and `KNOWLEDGE_TIMEOUT_MS` bound them. Private IP ranges are blocked and only HTTP and HTTPS are allowed. MIT. The repository is archived — nothing new is landing in it.
Build from source — clone the repository and build it, then point your client at the binary