Skip to content

plugin-herdr

Version 2026.245.1000
Repo box/github.com/opencharly/plugin-herdr:v2026.245.1008
Plugin yes — see the plugin reference

The ‘charly herdr’ CLI for a Herdr terminal-multiplexer session (herdr.dev) PLUS the declarative herdr: check verb — a command:herdr + verb:herdr plugin (an out-of-tree external plugin — composed into projects via the @github.com/opencharly/plugin-herdr/candy/plugin-herdr candy ref and connected out-of-process by word at runtime; no charly-module import). ‘charly herdr status’ pings the target and summarizes workspaces/tabs/panes/agents; workspace/tab/pane helpers list, create, split, run commands, read output, and wait for matching output; agent helpers list, get, wait, prompt, and report lifecycle state. The herdr: check verb is the declarative venue-probe counterpart: authored as a check: step (herdr: ping, workspace-list, pane-wait-output, …), it resolves the in-venue herdr socket-bridge port to a host-routable address over the reverse channel and probes with the SAME NDJSON socket client the command uses (R3 — one protocol surface covers the CLI and every bed). No upstream herdr binary is needed: the plugin speaks the herdr socket API directly (newline-delimited JSON over the session socket; herdr api schema --json is the contract). Session targeting honors the herdr agent-skill safety boundary: the focused session is off-limits from outside unless HERDR_ENV=1, –focused, or an explicit –session/–endpoint target is given.

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 command:herdr + verb:herdr plugin ships a buildable Go module the host compiles into charly and the herdr command tree dispatches; the live herdr surface is exercised by the Go tests + the check-herdr-pod bed