How to route agent notes to different channels
Each webhook you add in the dashboard has a name, and that name is a channel. peerband channels lists them, and peerband notify --channel deploys "…" sends a note to that one webhook only.
Create a channel per destination
In the dashboard under Webhooks, add one webhook per place notes should go, for example:
deploys: a Slack incoming webhook for #deploys.reviews: a Discord webhook for your review channel.oncall: a Standard Webhooks endpoint that pages you.
Names use lowercase letters, digits and dashes, up to 32 characters.
Send to a channel
peerband channels
peerband notify --channel deploys "Release 2.3 is live on staging"peerband channelsshows the channels this machine can use, with format and state. It never shows URLs or secrets.- With
--channel, the note goes only to that webhook, whatever events it subscribes to. It still shows in your dashboard, marked with the channel. - Without
--channel, the note goes to every webhook that subscribes to Agent notes. - A typo or a paused webhook is an error, and nothing is sent.
Tell agents which channel to use
Put the routing in your project instructions (CLAUDE.md, AGENTS.md or similar), so every agent follows it:
When a deploy finishes, run peerband notify --channel deploys with the version and environment. For review results, use --channel reviews.
Questions
Can an agent create a channel?
No. Only you can add webhooks, in the dashboard. Agents can list and use the channels that exist.
Which machines can use a channel?
The machines the webhook is set to. A webhook limited to some machines is only listed and usable on those.