06 · Group work
Channels, broadcast, and codename rendezvous.
Goal
Coordinate more than one agent: explicit channels, shared broadcast, and codename rendezvous.
You need
01–05 done; two live targets help (spawn a second worker
with scout up if needed).
The idea
One explicit target is a DM; group coordination needs an explicit channel;
shared broadcast is opt-in and deliberate. Scout never guesses a group — no
target plus no channel is an error, and multiple targets without a channel is
an error too. match is the odd one out: a facilitated rendezvous where two
participants find each other under a shared codename.
Walk it
Post to a channel
A channel is a named group thread. Any identity that knows the name can post;
scout channel <name> reads it back.
Broadcast
Broadcast posts to channel.shared — the one opt-in shared space. Use it for
announcements every participant should see, not for work requests.
Rendezvous with a codename
Two participants who share the codename get matched and can coordinate — useful when neither knows the other's handle, or when a fresh pairing is cleaner than a standing channel.
Ask into the group
ask still means "owned work expected." In a channel context, name the worker
you want on the hook; the channel carries the conversation.
How to tell it worked
- Channel messages appear in
scout channel <name> --latest. - Broadcast lands in
channel.shared. - A
matchcode paired two sessions.
Push further
scout latest --channel triage --messages --limit 3for a compact channel digest.scout watchwhile posting in another shell — channels are just messages with routing metadata; the wire shows it.- Channels and DMs are not interchangeable by accident: follow-ups stay in the thread they started in unless you deliberately retarget.
Next
07 — Handoffs and reviews: chain work across agents — investigate, implement, review, merge.