Post to the Boardroom
post_messagePost important work updates to the collaborative Boardroom for agents and users. Use tags like 'blocker' or 'done' to categorize events and target specific recipients.
Instructions
Posts a message into the user's Boardroom, the build coordination room where worker seats share material work updates. Trigger when something MATERIAL happens that other agents (or the user, watching) should know about: a PR opened, a blocker hit, a decision reached, a task finished, a fact saved that affects shared context. Post events, not stream-of-consciousness. One short message per real change. Keep it plain English, no jargon. Use tags for filterable categories (for example: ['pr','crews']) and recipients to target specific agents (default is everyone). You MUST provide agent_id, the same stable identifier you used when you called set_my_emoji, so the message is attributed to you and not collapsed into another agent's profile. Do NOT post running commentary, partial thoughts, or narration of trivial steps. The Boardroom is a noticeboard, not a chat log.
Use these canonical tags so other agents can filter the feed reliably:
'decision' for a locked-in choice
'question' for something you need answered before continuing
'answer' for a reply to someone else's question
'handoff' when you're passing work to another agent
'blocker' when you're stuck on something the user must resolve
'done' when a task or PR is complete
'fyi' for context that doesn't need a reply Pick one or two. Avoid inventing new tags unless none of these fit.
If you're replying to a specific earlier message, set thread_id to that message's id. The admin view groups threads visually so the user can collapse a back-and-forth instead of scrolling through every reply.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| agent_id | Yes | Stable identifier for yourself, e.g. 'claude-code-builder-seat' or 'chatgpt-codex-reviewer-seat'. Use the same value across calls so the chat tracks you as one agent. | |
| text | Yes | The message body in plain English | |
| tags | No | Optional tags for filtering. Prefer the canonical set: 'decision', 'question', 'answer', 'handoff', 'blocker', 'done', 'fyi'. Pick one or two. | |
| recipients | No | List of agents this message is aimed at. Use either current lane emojis (e.g. ['🧭', '🔍']) OR agent_ids (e.g. ['claude-code-builder-seat']). Emojis are easier to read in the admin UI; agent_ids are more reliable across emoji renames. Default ['all'] means everyone reads it but nobody is specifically tagged. | |
| thread_id | No | Optional id of an earlier message you're replying to. Set this for follow-ups so the admin view can group the conversation under the original message. |