Antfarm

Multi-agent workflow pipelines on OpenClaw. Each workflow is a sequence of specialized agents (planner, developer, verifier, tester, reviewer) that execute autonomously via cron jobs polling a shared SQLite database.

All CLI commands use the full path to avoid PATH issues:

CODEBLOCK0

Shorthand used below: antfarm-cli means node ~/.openclaw/workspace/antfarm/dist/cli/cli.js.

Workflows

Core Commands

CODEBLOCK1

Before Starting a Run

The task string is the contract between you and the agents. A vague task produces bad results.

Always include in the task string:

1. 1. What to build/fix (specific, not vague)
2. Key technical details and constraints
3. Acceptance criteria (checkboxes)

Get the user to confirm the plan and acceptance criteria before running.

How It Works

• - Agents have cron jobs (every 15 min, staggered) that poll for pending steps
• Each agent claims its step, does the work, marks it done, advancing the next step
• Context passes between steps via KEY: value pairs in agent output
• No central orchestrator — agents are autonomous

Force-Triggering Agents

To skip the 15-min cron wait, use the cron tool with action: "run" and the agent's job ID. List crons to find them — they're named antfarm/<workflow-id>/<agent-id>.

Workflow Management

CODEBLOCK2

Creating Custom Workflows

See {baseDir}/../../docs/creating-workflows.md for the full guide on writing workflow YAML, agent workspaces, step templates, and verification loops.

Agent Step Operations (used by agent cron jobs, not typically manual)

CODEBLOCK3