@meego-harness/openclaw-worker
v0.8.0
Published
OpenClaw native plugin that bridges a fixed OpenClaw agent to meego-harness workers
Keywords
Readme
@meego-harness/openclaw-worker
OpenClaw native plugin that binds one OpenClaw agent to a Meego Harness WorkerServerSDK.
For most users, prefer @meego-harness/worker-cli and let it drive package discovery, installation, setup, and runtime control. This package still supports direct standalone use through the OpenClaw host CLI.
Install
openclaw plugins install @meego-harness/openclaw-worker
openclaw gateway restartSetup
openclaw meego-harness-worker setup
openclaw meego-harness-worker list --json
openclaw meego-harness-worker doctor --jsonThe plugin binds one OpenClaw agent per configured worker:
| Field | Required | Meaning |
| --- | --- | --- |
| serverUrl | Yes | Worker websocket endpoint, for example ws://127.0.0.1:3000/workers. |
| email | Yes | Stable worker identity email. |
| agent | Yes | OpenClaw agent id to execute tasks. |
| workerId | No | Defaults to the agent id. |
| capabilitySummary | No | Defaults from the agent identity. |
Runtime Behavior
- The worker server treats this bridge as a normal
worker. - First login waits for a
worker-device-authorizationapproval from the target worker server when that server requires authorization. - After approval,
WorkerClientSDKpersists a device identity locally and later logins use challenge-response signing. - Worker tasks are executed by the configured OpenClaw agent.
- OpenClaw sessions are reused by harness
contextId. - Task messages are bridged as
working -> completeorworking -> failed. - Task cancellation tries to abort the active OpenClaw run and suppress late completion writes.
See README.agent.md for the strict install runbook intended for automation agents.
