Agent Messages: peer-to-peer coordination between sessions

Agents can now message another existing session directly, with one-line summaries, activity-feed visibility, and automatic wakeups.

CRHQ agents can now send messages horizontally to another existing agent session. Delegation is still there for parent to child work. Agent Messages is for peer-to-peer coordination.

A CRHQ Agent Messages diagram showing Operator, Developer, Researcher, and Tester sessions exchanging horizontal peer messages by session ID.

What is new

Message an existing peer. An agent can address another running session by session ID and send it a full message.

Keep summaries visible. Every message requires a short one-line summary that appears in activity feeds, so humans can scan what changed.

Wake the recipient. The target session is nudged to read the message and reply.

Wake the sender on reply. Replies automatically wake the original sender, so agents do not need to poll or loop while they wait.

Works inside or outside swarms. If the sessions are in the same swarm, the message is also recorded in the swarm Bridge and Captain's Log. If they are not, the peer message still works.

Why it is useful

Cleaner coordination. A developer agent can ask a researcher agent for source checks without creating a new subordinate worker.

Less duplicate context. Agents can send targeted updates to the session that needs them instead of forcing everything through one parent thread.

More natural teamwork. Delegation handles vertical work splitting. Agent Messages adds the missing horizontal lane between peers.

How to use it

  1. Give the sender the target session ID.
  2. Ask it to use Agent Messages.
  3. Include a short summary for the activity feed.
  4. Let the recipient wake, act, and reply.

Use Delegation when you need to spawn a new child session. Use Agent Messages when an existing peer session should know, review, or respond to something.