Messaging
How toryo gets your attention. Messaging is the notification spine: a single queue that anything in toryo can send into, delivered to board's inbox and raised as an OS notification.
The case it exists for: a sequence run reaches a gate and needs your decision. Without a notification, an unattended run that parks at 2am is discovered at 9am.
What sends messages today#
- A run reaching a human gate, asking for approval, rejection, or feedback.
- A run finishing, succeeded or failed. A run you cancelled yourself does not notify, since you already know.
- Any part of toryo sending an informational message.
How delivery works#
board holds an ambient subscription, so a notification fires regardless of which screen you are on. Clicking it focuses board and routes straight to the message, with the affected run selected.
Messages move through pending → delivered → acknowledged, and expire if their
window passes unanswered.
Acknowledging a gate from the run itself also acknowledges the message, so the inbox does not accumulate items you have already dealt with.
board is the only delivery surface today. If board is not running, messages queue as pending and are there when you open it. Nothing is lost, but nothing reaches you in the meantime. External destinations (Slack, webhooks, push) are designed for and not yet built.
Answering a gate#
A gate message carries more than text. It can attach:
- Files and links, such as the proposed plan or the pull request, rendered in a tabbed preview so you can read what you are approving without leaving board.
- Questions, either/or prompts the agent wrote itself, rendered as pickable option cards.
Your picks are folded into your typed feedback as ordinary prose and sent back with the acknowledgement, so a planner can ask "Postgres or on-disk?" and get an answer rather than guessing and being corrected a step later.
In board#
The Messaging screen is the inbox: everything sent, its status, and the acknowledgement form.
Full command surface: CLI & contract reference.