plugin-openclaw
| Version | 2026.246.0100 |
| Repo | box/github.com/opencharly/plugin-openclaw:v2026.246.1626 |
| Plugin | yes — see the plugin reference |
OUT-OF-TREE charly plugin serving the openclaw check verb — a standalone
Go module (go.mod + main.go) that probes a running OpenClaw 2.0 gateway,
served OUT-OF-PROCESS over go-plugin gRPC via the charly plugin SDK
(github.com/opencharly/sdk). charly’s loader fetches this candy’s repo,
go-builds the provider binary on the HOST, and serves it via LocalTransport —
so an authored openclaw: step dispatches through the provider registry
exactly like a built-in.
The verb PROBES the gateway two ways. HTTP probe methods (health/ready/startup)
hit the /healthz /readyz /startupz endpoints — the container-probe surface
OpenClaw 2.0 added for orchestrators — from the charly host against the
resolved gateway endpoint (cc.ResolveEndpoint + cc.HTTPDo, so one authored
step works unchanged against a pod’s published port and a VM’s forwarded one).
CLI methods (status/models/channels/version) run the openclaw binary INSIDE
the venue over the reverse channel (cc.Exec), where the gateway CLI connects
to the loopback gateway over WebSocket. All methods are read-only; there are
no mutating methods in this first cut.
It is NOT a re-skin of the generic http: verb. http: already covers URL +
status + body/header matchers, and this plugin exists for the two things it
structurally cannot do: ENDPOINT RESOLUTION (cc.ResolveEndpoint means one
authored step works unchanged against a pod’s published port and a VM’s
forwarded one) and DOMAIN SEMANTICS (methods map to the gateway’s real probe
surface and return real verdicts, with json_path: to assert one field
instead of pattern-matching a JSON blob; the CLI methods run in-venue where
the gateway CLI lives, which http: cannot reach at all).
The R10 consumer is an openclaw-bearing bed (pod) whose check composes this
plugin alongside the openclaw candy from opencharly/pod-openclaw.
Acceptance plan
Section titled “Acceptance plan”This candy’s plan: — the runnable spec charly check executes against a live deployment. check: steps are idempotent probes; run: steps change state.
| Intent | Step |
|---|---|
check |
the openclaw verb dispatches through the provider registry and the gateway’s /healthz liveness endpoint reports ok on a live deployment |