Connect ChatGPT, Claude, or any MCP client to the coding agents running in Herdr on your machine. Ask what they're doing, send the next instruction, share access with a teammate, and get a note when an agent needs you.
Your machine connects out to the relay. No open ports, no tunnels.
Connect, ask, share, close the loop.
Shown on a sample machine.
Needs Node.js 22.13+ and Herdr 0.9.3+. peerband setup opens your browser to approve the machine, adds the Herdr plugin, installs the agent skill and opens the Relay tab. The machine connects out, so there are no ports to open.
npm install -g peerbandpeerband setupAdd it as a custom connector, then sign in and approve access. Your client calls list_agents and send_agent_message, and the agent knows the message came from you.
https://mcp.peerband.com/mcppeerband share creates an invite link. Guests can read, or also send messages with --message. Every relayed message names its sender, and the PeerBand skill tells your agent to treat guests as coworkers: help with the task, keep your secrets private.
peerband share --messageShare the machine with a bot account that can send messages. When review finds a problem, the bot messages the exact agent behind the PR. The agent fixes it, pushes, and leaves you a note with peerband notify.
Addressed by agent id, not by whichever pane has focus.
A pattern you can build today with sharing and send_agent_message.
claude through PeerBand · delivereda1c9e2f Reset backoff after a successful reconnectAgents report when they start, finish, or wait for you. The dashboard updates on its own, without polling your panes.
Invite a teammate with a link. Choose read only or read and message, see what they read or sent, and revoke access any time.
Every relayed message names its sender. Guests get coworker rules from the PeerBand skill, and you can edit them.
An agent runs peerband notify to tell you something on the dashboard: a PR is ready, or a decision is needed.
Your PeerBand account owns its machines. You, the MCP clients you authorize, and the people you share a machine with can reach it. Each guest gets the role you choose: read only, or read and message. Remove a guest with peerband share revoke or from the dashboard, and revoke a client or disconnect a machine at any time.
Every message relayed through PeerBand starts with a line naming the sender. From a guest it reads: "[PeerBand relay] From shared user name@example.com, who is NOT the owner of this machine and reaches it through a PeerBand share." The PeerBand skill tells your agent to treat guests as coworkers: help with the task, keep your private information private, and ask you before anything risky. You can change those rules in the skill file.
Run peerband setup, or give your agent the PeerBand setup skill and let it run setup for you. You approve the sign-in code in your own browser at peerband.com/device.
Yes. Status changes reach your dashboard as they happen, so you see when an agent finishes or starts waiting for you. An agent can also leave you a note with peerband notify "text". Notes go to the machine owner only.
On your own computer, inside Herdr. PeerBand Connector links that running session to PeerBand Relay. Your MCP client sends requests through the relay to your machine.
Use an MCP client that supports remote Streamable HTTP servers and one of the authorization methods shown in your dashboard. Add the PeerBand MCP endpoint, approve access, and select the Herdr machine running your Codex, Claude Code, or other agents. Client support for remote MCP features varies.
PeerBand MCP provides list_machines, list_agents, get_agent_status, get_agent_output, send_agent_message, and get_request_status. Sending an instruction requires agents:message access; a machine can opt out of messages.
Approve agents:read to list agents and read status, output, and request receipts. Add agents:message only when you want to send instructions. Messaging also requires writes to be enabled on your local connector. You can disconnect a client in the dashboard.
No inbound port forwarding is needed. The connector opens an outbound secure WebSocket connection to PeerBand Relay, which routes MCP requests to the connected machine and returns responses.
A running Herdr session, Node.js 22.13 or newer, a PeerBand account, and an MCP client that supports Streamable HTTP. The dashboard provides connection details and the authorization method available for your account.
Your machine appears offline and requests cannot reach its agents. The connector retries when the machine and network return; Herdr must also be running.
Your agents and Herdr session run on your own computer. PeerBand stores the account, machine, and client authorization records needed to provide the connection, and routes MCP requests and responses through the relay. Do not include passwords or access keys in agent messages.