PeerBand v0.2.2

list_agents now reports where each agent sits in Herdr, so the PeerBand dashboard can group a machine's agents by space and tab.

• Each agent record has an optional location with the Herdr space and tab: id, user-visible label (sanitized, max 128 characters) and position. Labels and positions come from workspace.list and tab.list. If Herdr can't list them, the ids are still reported.
• The connector also watches pane.moved, tab.renamed, tab.moved, workspace.renamed and workspace.reordered, and emits agents.changed when an agent's location changes, so live dashboards regroup.
• The field is additive: older dashboards and MCP clients ignore it.

After peerband 0.2.2 is published to npm, run peerband update to update the CLI and matching Herdr plugin.

The GitHub tag includes the built dist/peerband.mjs required for Herdr plugin installation. Installer assets and their SHA-256 checksums are attached.

PeerBand v0.2.1

PeerBand can now read the current screen of a busy Herdr agent when transcript history is unavailable.

• Retry agent_not_idle history-read errors once with a passive visible-screen read.
• Mark the response with source: "visible" and truncated: true so consumers can explain the partial excerpt.
• Preserve output bounds, sanitization and occupant checks, and propagate unrelated errors normally.
• Include the fix in both the CLI and the Herdr plugin.

After peerband 0.2.1 is published to npm, run peerband update to update the CLI and matching Herdr plugin.

The GitHub tag includes the built dist/peerband.mjs required for Herdr plugin installation. Installer assets and their SHA-256 checksums are attached.

PeerBand v0.2.0

Channels

Agents can now send a note to a specific channel: one of your PeerBand webhooks, such as a Slack or Discord incoming webhook or your own endpoint, addressed by its name. Add channels in the PeerBand dashboard under Webhooks.

• peerband channels [--json] lists the channels this machine can use (name, format, state). Webhook URLs and secrets never reach the machine.
• peerband notify --channel NAME "<text>" sends the note to that channel's webhook. The channel is checked first: an unknown, paused or unverified channel is an error and nothing is sent. The note still shows in the dashboard. Without --channel, notes behave as before.
• The agent.notified relay event gains an optional channel field (protocol/relay-messages.schema.json).
• The agent skill and the README describe channels.

After upgrading, run peerband update so the running relay picks up channel support. An older relay drops the channel, and peerband notify --channel reports that.

Full Changelog: v0.1.6...v0.2.0

PeerBand v0.1.6

What's Changed

• Add peerband share and keep the machine record on re-login by @kshvidler in #1
• Add peerband update and make plugin updates safe on Windows by @kshvidler in #2
• Stream agent status events and add peerband notify by @kshvidler in #3
• Add peerband setup, the agent skill installer, and sender labels on relayed messages by @kshvidler in #4
• Let the Relay pane start the relay on slow machines (0.1.6) by @kshvidler in #5

New Contributors

• @kshvidler made their first contribution in #1

Full Changelog: https://github.com/kshvidler/peerband-cli/commits/v0.1.6

PeerBand v0.1.5

What's Changed

• Add peerband share and keep the machine record on re-login by @kshvidler in #1
• Add peerband update and make plugin updates safe on Windows by @kshvidler in #2
• Stream agent status events and add peerband notify by @kshvidler in #3
• Add peerband setup, the agent skill installer, and sender labels on relayed messages by @kshvidler in #4

New Contributors

• @kshvidler made their first contribution in #1

Full Changelog: https://github.com/kshvidler/peerband-cli/commits/v0.1.5

v0.1.4

What's Changed

• Add peerband share and keep the machine record on re-login by @kshvidler in #1
• Add peerband update and make plugin updates safe on Windows by @kshvidler in #2

New Contributors

• @kshvidler made their first contribution in #1

Full Changelog: https://github.com/kshvidler/peerband-cli/commits/v0.1.4

PeerBand v0.1.3

What's Changed

• Add peerband share and keep the machine record on re-login by @kshvidler in #1

New Contributors

• @kshvidler made their first contribution in #1

Full Changelog: https://github.com/kshvidler/peerband-cli/commits/v0.1.3

PeerBand v0.1.2

• Agent skill: give your coding agents the PeerBand skill with npx skills add kshvidler/peerband-cli. It explains the MCP tools (list_machines, list_agents, get_agent_status, get_agent_output, send_agent_message, get_request_status), the recommended flow, safe behaviour and error codes. peerband login and peerband relay suggest it after setup.
• Messages on by default: MCP clients you approved for messaging (agents:message) can send messages to your agents. Opt a machine out with peerband connect --read-only or "enableWrites": false in connector.json. The Relay tab, peerband connect and peerband status show whether messages are allowed.
• Plugin health check: peerband relay and peerband login detect a missing, outdated or misconfigured Herdr plugin (local checkout, wrong version, another config directory, missing Node.js) and offer to repair it. peerband status shows the plugin source and any problem.
• Relay tab: the Account row is hidden when no email is known instead of showing "Unavailable".

Install or update:

npm install -g peerband
peerband login

One-step install scripts, attached below with SHA256 checksums: curl -fsSL https://peerband.com/install.sh | sh or irm https://peerband.com/install.ps1 | iex.

PeerBand v0.1.1

After peerband login, the CLI now detects Herdr and offers to add the PeerBand plugin, so the recommended install is two commands:

npm install -g peerband
peerband login

Then peerband relay opens the PeerBand Relay tab in Herdr.

• peerband login --herdr-plugin ask|install|skip controls the new step (default ask; without a terminal it prints the next commands instead of asking).
• If Herdr is not installed, login says where to get it and what to run next.
• The one-step install scripts use the same step (--herdr-plugin install).

One-step install scripts, attached below with SHA256 checksums:

curl -fsSL https://peerband.com/install.sh | sh

irm https://peerband.com/install.ps1 | iex

PeerBand v0.1.0

First public release of the PeerBand CLI and Herdr plugin.

Install on macOS / Linux:

curl -fsSL https://peerband.com/install.sh | sh

Windows PowerShell:

irm https://peerband.com/install.ps1 | iex

Or with npm: npm install -g peerband, then peerband login, peerband herdr install and peerband relay.

The installers are attached below with their SHA256 checksums.