Tools
Agentplane Openclaw
🔌 OpenClaw native plugin for routing workspace-changing work through AgentPlane.
Install
openclaw plugins install /path/to/agentplane-openclaw-plugin
Configuration Example
{
"plugins": {
"allow": ["agentplane"],
"entries": {
"agentplane": {
"enabled": true,
"config": {
"agentplaneBin": "agentplane",
"defaultRoot": "/workspace",
"allowedRoots": ["/workspace"],
"mutationMode": "advise",
"injectPromptGuidance": true,
"commandTimeoutMs": 120000
}
}
}
}
}
README
# AgentPlane OpenClaw Plugin
[](https://github.com/basilisk-labs/agentplane-openclaw-plugin/actions/workflows/ci.yml)
[](LICENSE)
[](https://github.com/basilisk-labs/agentplane)
[](https://github.com/openclaw/openclaw)
OpenClaw native plugin that makes AgentPlane visible as the workflow and
evidence layer for repository, Context, prompt, policy, and infrastructure
changes.
## Status
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.
## Runtime Contract
The OpenClaw runtime must provide:
- Node.js 20+;
- `agentplane` on `PATH`, or plugin config `agentplaneBin`;
- a workspace with an initialized `.agentplane` harness;
- optional `allowedRoots` for 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.
## OpenClaw Config
Example `openclaw.json` fragment:
```json
{
"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 explicit
`ap`/`agentplane` command.
Use `advise` for the first runtime rollout. Move to `enforce` only after the
live OpenClaw tool envelope is verified for the deployment.
## Install
For local development:
```bash
openclaw plugins install /path/to/agentplane-openclaw-plugin
openclaw plugins inspect agentplane --runtime --json
```
For 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`.
## Agent Workflow
The agent should use:
```text
agentplane_doctor
agentplane_task_brief
agentplane_next_action
agentplane_work_resume
```
Typical mutating flow:
1. Find or create the AgentPlane task through the surrounding workflow.
2. Run `agentplane_next_action` for the task id.
3. Resume or execute through AgentPlane.
4. Verify and finish through AgentPlane, not by directly committing unrelated
workspace state.
## Development
```bash
npm test
npm run check
```
The test suite uses a fake OpenClaw plugin API. It checks registration behavior,
prompt guidance, and conservative tool-policy decisions without requiring a live
Gateway.
## Boundaries
- 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.
tools
Comments
Sign in to leave a comment