Notifications guide
How ROST should notify humans about decisions, escalations, stale work, and agent boundaries.
Notifications should move decisions to the right human without turning ROST into noisy chat. Notify for exceptions, approvals, and stale commitments.
Notify when
- An agent hits a must-escalate condition.
- A tool or credential approval is needed.
- A Signal is broken or stale.
- A Friction item needs a decision.
- A Sync decision creates a handoff.
Diagnose failed deliveries
rost notification errors --limit 10 / notification.list_errors / rost_list_notification_errors returns recent failed deliveries. When a failed notification links to a product error, it includes error_log_id, source, and any linked seat_id / run_id; source=run means the notification is tied to an agent run and can be followed with agent.get_run for the transcript reference and run errors.
Keep notifications useful
Every notification should include the seat, cause, evidence, and requested decision. Avoid status-only messages when no action is needed.