herdsman-pi

Pi >= 0.80.6 extension for Herdsman agent history and automatic agent-update wake.

This package contains the runtime extension only. The Agent Skill remains at the repository root.

Install the Herdsman CLI and Pi package, then check that the daemon is running:

npm install --global @dorokuma/herdsman
pi install npm:@dorokuma/herdsman-pi
herdsman daemon status

Herdsman has no CLI start/stop command. On the production host the daemon runs under the systemd unit herdsman.service and stays running (systemctl restart herdsman.service); for a development or throwaway environment, run the daemon entrypoint in the foreground with an explicit temporary data directory (HERDSMAN_HOME=/tmp/<name> node <package>/dist/src/cli/herdsman-daemon.js) instead of the production one.

When Pi runs inside Herdr, this extension connects to the Herdsman daemon and registers its exact Pi session path as presence identity. After register it sends agent.ping at least every 30 seconds so an idle owner is not dropped by the daemon heartbeat. It does not send per-turn tool-result or final-message telemetry.

Enter these commands in Pi, not in a shell:

/herdsman on
/herdsman
/herdsman status
/herdsman off

on enables both cached agent context and automatic agent-update wake for this Pi. It makes this terminal the sole owner in its current Herdr session/workspace and replaces any existing owner. Only the owner receives cached context, pending counts, updates, and wake. Context excludes the owner Pi and includes other Pi terminals. A normal prompt uses the local cached snapshot without daemon RPC or history reads, so context can be temporarily absent after startup, reconnect, or scope movement until a snapshot arrives.

off disables both context and wake for this Pi while keeping the daemon connection available for a later claim. It does not release another Pi's ownership. Bare /herdsman and /herdsman status report whether the current Pi is on.

An agent outcome starts one visible Herdsman turn. If a normal user run is active, wake waits for it to settle. The themed card shows up to three outcomes with agent identity, completion state, and pane ID. A named agent appears as reviewer · Codex; an unnamed agent appears as Codex. Pi's expand key reveals every complete final response. Agent output is untrusted evidence, so Pi continues only the existing user request and does not create unrelated work.

Only the active Pi displays ◆ Herdsman in the footer. Pending outcomes add · N agent updates until Pi produces a final assistant response, settles, and acknowledges every event included in that turn. A previously active Pi displays ◇ Herdsman · reconnecting during transport recovery.

With no owner, outcomes are not delivered, and outcomes created during that ownerless period are not replayed by a later claim. The daemon persists ownership across brief reconnects and Pi session replacement. Reloads, reconnects, and direct owner replacement preserve unacknowledged outcomes. Ownership follows the same Herdr terminal when its pane moves to another workspace; it clears after the terminal remains disconnected beyond the grace period.