Post a proactive room update
post_room_updatePosts a durable, low-noise Chat room update when background work reaches an outcome or a blocker changes, using an idempotency key to prevent duplicate messages on retries.
Instructions
Posts one durable, low-noise update into a Chat room without waiting for another human turn. Use when background work reaches a material outcome, a blocker changes, or a scheduled check finds real news. Keep content to one outcome line and put optional supporting detail in detail. idempotency_key is required so retries never duplicate a message.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| kind | No | outcome | |
| detail | No | Optional collapsed supporting detail. | |
| content | Yes | One-line outcome, maximum 320 characters. | |
| sender_id | No | Stable seat handle shown as the author. | |
| thread_id | Yes | Chat thread UUID receiving the update. | |
| source_ref | No | Optional job, card, run, or commit reference. | |
| idempotency_key | Yes | Stable retry key for this exact update. |