Clawion (runbook)
To run Clawion you need OpenClaw cron jobs — the Gateway wakes agents via cron. Clawion is multi-agent; multiple agents ⇒ multiple cron jobs (one per agent). Do NOT call sessions_spawn (no subagents). Official reference: Cron Jobs — OpenClaw.
Mental model (cron-driven)
- Clawion is a file-based mission coordinator. Agents interact with state through the
clawion CLI.
- Cron fires a periodic tick (you must create the job; see Cron jobs (OpenClaw) and the official docs).
- Agent runs
clawion agent wake → receives the authoritative prompt for this turn.
- Agent follows the Turn Playbook in that wake output.
- Next wake reflects the updated workspace state.
Key properties:
- Wake is the only read entrypoint.
- Run Clawion ⇒ cron jobs; multi-agent ⇒ multiple cron jobs (one per agent: manager + each worker).
Core invariants
- Workers complete tasks; managers maintain the board.
- Worker: reports progress and asks questions via
clawion message add; logs process via clawion working add.
- Manager: dispatches and maintains truth via
clawion task create/assign/update; also logs via clawion working add. When the mission is complete, disables all related cron jobs.
- Identity is explicit: every action requires global
--agent <agentId>.
Quickstart (bootstrap a new mission)
0. Pre-flight
Verify the CLI is available:
clawion --help
If the command is not found, install it globally: pnpm install -g clawion
1. Create the mission
clawion mission create --id <MISSION_ID> --name "..."
2. Register the manager (bootstrap rule)
The acting --agent must be the manager itself.
clawion agent add \
--mission <MISSION_ID> \
--id <MANAGER_ID> \
--name "Manager" \
--system-role manager \
--role-description "..." \
--agent <MANAGER_ID>
3. Register worker agents
clawion agent add \
--mission <MISSION_ID> \
--id <WORKER_ID> \
--name "Worker" \
--system-role worker \
--role-description "..." \
--agent <MANAGER_ID>
Repeat per worker.
4. Create and assign tasks (manager-only)
clawion task create \
--mission <MISSION_ID> \
--id <TASK_ID> \
--title "..." \
--description "..." \
--agent <MANAGER_ID>
clawion task assign \
--mission <MISSION_ID> \
--task <TASK_ID> \
--to <WORKER_ID> \
--agent <MANAGER_ID>
5. Write the roadmap (manager-only, one-shot)
clawion mission roadmap --id <MISSION_ID> --set "<markdown>" --agent <MANAGER_ID>
6. Create cron jobs (disabled) and get user approval — mandatory
- You must create one isolated cron job per agent (manager + each worker), all disabled.
- You must not enable any job until the user has reviewed and given explicit approval.
- After creating the jobs, remind the user that they can use the Clawion Web UI (
clawion ui) to review and edit mission content (roadmap, tasks, agents, etc.) before enabling.
See Cron jobs for more rules.
Cron jobs (OpenClaw)
Hard rules
| Rule |
Detail |
| One job per agent |
Multi-agent ⇒ multiple cron jobs. Create one isolated cron job per agent (manager + each worker). No job for an agent ⇒ that agent never runs. |
| Isolation |
Each tick runs in its own isolated OpenClaw session (never main). Context bleed makes the loop unreliable. |
| Wake interval |
If the user didn't specify one, ask and confirm before creating jobs. |
| Minimal payload |
Do not embed mission context, task lists, or SOP text. The authoritative prompt is assembled by clawion agent wake from workspace state at runtime. |
| Disabled first |
Have the user review and confirm before any cron job is enabled. This step is non-negotiable |
Recommended cron message
Worker:
Fetch your instructions by running:
clawion agent wake --mission <MISSION_ID> --agent <AGENT_ID>
Then follow the Turn Playbook in that output.
Manager:
Fetch your instructions by running:
clawion agent wake --mission <MISSION_ID> --agent <AGENT_ID>
Then follow the Turn Playbook in that output.
If the mission is complete, disable all related cron jobs.
Operational tips
- Job naming:
clawion:<MISSION_ID>:manager:<AGENT_ID>
clawion:<MISSION_ID>:worker:<AGENT_ID>
- Stagger ticks when multiple agents share the same interval to avoid bursty runs.
- Given interval =
N minutes and K agents, choose offsets: round(i * N / K) for i = 0..K-1.
- Example:
N=10, K=3 → offsets 0m, 3m, 7m.
CLI reference
Global option: --agent <agentId> (required for all scoped actions below).
| Command |
Purpose |
clawion help [topic...] |
Show detailed command help. Use clawion help <command> for one command (e.g. clawion help agent wake). |
clawion mission create |
Create a new mission from the template. Params: --id <id>, --name <name>. |
clawion mission roadmap |
Set the mission roadmap (manager only, write-once). Params: --id <id>, --set <markdown>, --agent <agentId>. |
clawion mission complete |
Mark a mission completed (manager only). Params: --id <id>, --agent <agentId>. |
clawion task create |
Create a task (manager only). Params: --mission <id>, --id <taskId>, --title <title>, --description <markdown>, --agent <agentId>. |
clawion task update |
Update task status or notes (manager only). Params: --mission <id>, --id <taskId>, --agent <agentId>, optional --status, --status-notes. |
clawion task assign |
Assign a task to an agent (manager only). Params: --mission <id>, --task <taskId>, --to <agentId>, --agent <agentId>. |
clawion agent add |
Register an agent for a mission (manager only). Params: --mission <id>, --id <agentId>, --name <displayName>, --system-role <manager|worker>, --role-description <markdown>, --agent <agentId>. |
clawion agent wake |
Generate the agent prompt and acknowledge unread mentions. Params: --mission <id>, --agent <agentId>. |
clawion message add |
Append a message to a task thread. Params: --mission <id>, --task <taskId>, --content <markdown>, --mentions <agentId,...>, --agent <agentId>. |
clawion thread show |
Show thread messages for a task (manager only). Params: --mission <id>, --task <taskId>, --agent <agentId>. |
clawion working add |
Append a working event for the acting agent. Params: --mission <id>, --content <markdown>, --agent <agentId>. |
1---2name: clawion3description: Multi-agent collaboration powered by OpenClaw cron jobs and the clawion CLI.4metadata:5 source: https://skillmd.com/skills/natllian/clawion6---78# Clawion (runbook)910**To run Clawion you need OpenClaw cron jobs** — the Gateway wakes agents via cron. **Clawion is multi-agent;** multiple agents ⇒ **multiple cron jobs** (one per agent). Do NOT call sessions_spawn (no subagents). Official reference: **[Cron Jobs — OpenClaw](https://docs.openclaw.ai/automation/cron-jobs#cron-jobs)**.1112## Mental model (cron-driven)1314151. Clawion is a **file-based mission coordinator**. Agents interact with state through the **`clawion` CLI**.162. **Cron fires** a periodic tick (you must create the job; see [Cron jobs (OpenClaw)](#cron-jobs-openclaw) and the [official docs](https://docs.openclaw.ai/automation/cron-jobs#cron-jobs)).173. Agent runs **`clawion agent wake`** → receives the authoritative prompt for this turn.184. Agent follows the **Turn Playbook** in that wake output.195. Next wake reflects the updated workspace state.2021Key properties:22- **Wake is the only read entrypoint.**23- **Run Clawion ⇒ cron jobs; multi-agent ⇒ multiple cron jobs** (one per agent: manager + each worker).2425## Core invariants2627- **Workers complete tasks; managers maintain the board.**28 - Worker: reports progress and asks questions via `clawion message add`; logs process via `clawion working add`.29 - Manager: dispatches and maintains truth via `clawion task create/assign/update`; also logs via `clawion working add`. When the mission is complete, **disables all related cron jobs**.30- **Identity is explicit:** every action requires global `--agent <agentId>`.3132---3334## Quickstart (bootstrap a new mission)3536### 0. Pre-flight3738Verify the CLI is available:3940```bash41clawion --help42```4344If the command is not found, install it globally: `pnpm install -g clawion`4546### 1. Create the mission4748```bash49clawion mission create --id <MISSION_ID> --name "..."50```5152### 2. Register the manager (bootstrap rule)5354The acting `--agent` must be the manager itself.5556```bash57clawion agent add \58 --mission <MISSION_ID> \59 --id <MANAGER_ID> \60 --name "Manager" \61 --system-role manager \62 --role-description "..." \63 --agent <MANAGER_ID>64```6566### 3. Register worker agents6768```bash69clawion agent add \70 --mission <MISSION_ID> \71 --id <WORKER_ID> \72 --name "Worker" \73 --system-role worker \74 --role-description "..." \75 --agent <MANAGER_ID>76```7778Repeat per worker.7980### 4. Create and assign tasks (manager-only)8182```bash83clawion task create \84 --mission <MISSION_ID> \85 --id <TASK_ID> \86 --title "..." \87 --description "..." \88 --agent <MANAGER_ID>8990clawion task assign \91 --mission <MISSION_ID> \92 --task <TASK_ID> \93 --to <WORKER_ID> \94 --agent <MANAGER_ID>95```9697### 5. Write the roadmap (manager-only, one-shot)9899```bash100clawion mission roadmap --id <MISSION_ID> --set "<markdown>" --agent <MANAGER_ID>101```102103### 6. Create cron jobs (disabled) and get user approval — **mandatory**104105- You **must** create **one isolated cron job per agent** (manager + each worker), all **disabled**.106- You **must not** enable any job until the user has reviewed and given explicit approval.107- After creating the jobs, **remind the user** that they can use the Clawion Web UI (`clawion ui`) to review and edit mission content (roadmap, tasks, agents, etc.) before enabling.108109See [Cron jobs](#cron-jobs-openclaw) for more rules.110111112---113114## Cron jobs (OpenClaw)115116### Hard rules117118| Rule | Detail |119| ------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------- |120| **One job per agent** | Multi-agent ⇒ multiple cron jobs. Create **one** isolated cron job per agent (manager + each worker). No job for an agent ⇒ that agent never runs. |121| **Isolation** | Each tick runs in its **own isolated OpenClaw session** (never `main`). Context bleed makes the loop unreliable. |122| **Wake interval** | If the user didn't specify one, **ask and confirm** before creating jobs. |123| **Minimal payload** | Do **not** embed mission context, task lists, or SOP text. The authoritative prompt is assembled by `clawion agent wake` from workspace state at runtime. |124| **Disabled first** | Have the user review and confirm before any cron job is enabled. This step is **non-negotiable** |125126### Recommended cron message127128**Worker:**129130```text131Fetch your instructions by running:132133clawion agent wake --mission <MISSION_ID> --agent <AGENT_ID>134135Then follow the Turn Playbook in that output.136```137138**Manager:**139140```text141Fetch your instructions by running:142143clawion agent wake --mission <MISSION_ID> --agent <AGENT_ID>144145Then follow the Turn Playbook in that output.146If the mission is complete, disable all related cron jobs.147```148149### Operational tips150151- **Job naming:**152 - `clawion:<MISSION_ID>:manager:<AGENT_ID>`153 - `clawion:<MISSION_ID>:worker:<AGENT_ID>`154- **Stagger ticks** when multiple agents share the same interval to avoid bursty runs.155 - Given interval = `N` minutes and `K` agents, choose offsets: `round(i * N / K)` for `i = 0..K-1`.156 - Example: `N=10`, `K=3` → offsets `0m`, `3m`, `7m`.157158---159160## CLI reference161162Global option: `--agent <agentId>` (required for all scoped actions below).163164| Command | Purpose |165|---------|---------|166| `clawion help [topic...]` | Show detailed command help. Use `clawion help <command>` for one command (e.g. `clawion help agent wake`). |167| `clawion mission create` | Create a new mission from the template. Params: `--id <id>`, `--name <name>`. |168| `clawion mission roadmap` | Set the mission roadmap (manager only, write-once). Params: `--id <id>`, `--set <markdown>`, `--agent <agentId>`. |169| `clawion mission complete` | Mark a mission completed (manager only). Params: `--id <id>`, `--agent <agentId>`. |170| `clawion task create` | Create a task (manager only). Params: `--mission <id>`, `--id <taskId>`, `--title <title>`, `--description <markdown>`, `--agent <agentId>`. |171| `clawion task update` | Update task status or notes (manager only). Params: `--mission <id>`, `--id <taskId>`, `--agent <agentId>`, optional `--status`, `--status-notes`. |172| `clawion task assign` | Assign a task to an agent (manager only). Params: `--mission <id>`, `--task <taskId>`, `--to <agentId>`, `--agent <agentId>`. |173| `clawion agent add` | Register an agent for a mission (manager only). Params: `--mission <id>`, `--id <agentId>`, `--name <displayName>`, `--system-role <manager\|worker>`, `--role-description <markdown>`, `--agent <agentId>`. |174| `clawion agent wake` | Generate the agent prompt and acknowledge unread mentions. Params: `--mission <id>`, `--agent <agentId>`. |175| `clawion message add` | Append a message to a task thread. Params: `--mission <id>`, `--task <taskId>`, `--content <markdown>`, `--mentions <agentId,...>`, `--agent <agentId>`. |176| `clawion thread show` | Show thread messages for a task (manager only). Params: `--mission <id>`, `--task <taskId>`, `--agent <agentId>`. |177| `clawion working add` | Append a working event for the acting agent. Params: `--mission <id>`, `--content <markdown>`, `--agent <agentId>`. |