OpenClaw native plugin that makes AgentPlane visible as the workflow and evidence layer for repository, Context, prompt, policy, and infrastructure changes.
Initial native OpenClaw integration. It registers:
- prompt guidance through OpenClaw prompt hooks;
- optional mutation blocking through
before_tool_call; - agent tools:
agentplane_doctor,agentplane_task_brief,agentplane_next_action,agentplane_work_resume; - gateway method
agentplane.doctor; - lightweight runtime service lifecycle logs.
This plugin does not copy the Hermes Kanban bridge. OpenClaw stays the runner, AgentPlane stays the repository-local workflow, route, verification, and evidence system.
The OpenClaw runtime must provide:
- Node.js 20+;
agentplaneonPATH, or plugin configagentplaneBin;- a workspace with an initialized
.agentplaneharness; - optional
allowedRootsfor fail-closed workspace path validation.
The plugin expects ordinary AgentPlane, not AgentPlane Context. Initialize target repositories with a normal AgentPlane harness and keep durable agent memory in the external Context repository managed by the surrounding Arkady runtime.
Example openclaw.json fragment:
{
"plugins": {
"allow": ["agentplane"],
"entries": {
"agentplane": {
"enabled": true,
"config": {
"agentplaneBin": "agentplane",
"defaultRoot": "/workspace",
"allowedRoots": ["/workspace"],
"mutationMode": "advise",
"injectPromptGuidance": true,
"commandTimeoutMs": 120000
}
}
}
}
}mutationMode:
off: no prompt guidance or mutation blocking beyond registered tools;advise: inject AgentPlane policy guidance, do not block tools;enforce: block likely mutating tools unless the call is an explicitap/agentplanecommand.
Use advise for the first runtime rollout. Move to enforce only after the
live OpenClaw tool envelope is verified for the deployment.
For local development:
openclaw plugins install /path/to/agentplane-openclaw-plugin
openclaw plugins inspect agentplane --runtime --jsonFor a container image, copy this repository into the OpenClaw plugin root and
enable agentplane in config. Native OpenClaw plugin metadata lives in
openclaw.plugin.json; runtime entrypoints live in package.json#openclaw.
The agent should use:
agentplane_doctor
agentplane_task_brief
agentplane_next_action
agentplane_work_resume
Typical mutating flow:
- Find or create the AgentPlane task through the surrounding workflow.
- Run
agentplane_next_actionfor the task id. - Resume or execute through AgentPlane.
- Verify and finish through AgentPlane, not by directly committing unrelated workspace state.
npm test
npm run checkThe test suite uses a fake OpenClaw plugin API. It checks registration behavior, prompt guidance, and conservative tool-policy decisions without requiring a live Gateway.
- No direct writes to AgentPlane internal JSON stores.
- No OpenClaw-specific task database is introduced.
- OpenClaw session state is runner state; AgentPlane task state remains the workflow source of truth.
- Hard enforcement depends on OpenClaw hook coverage for the active tool runtime, so live runtime verification is required before production enforce mode.