send_update
Turn raw project details into a concise client-ready update, highlighting only blockers, decisions, and next actions that need attention.
Instructions
Send a concise, client-ready structured update.
brief is the default. Write for a recipient who has not followed the project: put the concrete subject and current result in one self-contained summary using plain everyday language. Replace jargon and internal names with their practical meaning. Add only blockers, decisions, questions, or the next action needed now; completed is omitted when the summary already says what was done. Keep every field inside the exact subject requested by the user; never append unrelated project health. Include a client question only if the answer is not already available, the recipient controls it, and progress on the subject stops without it now. Build the dependency chain internally and ask only the first unresolved dependency, not questions about later steps. Omit the question section when nothing passes this test. Address the recipient directly. For client copy, put a required choice in client_questions, not the internal decisions_needed section. Do not include chronology, review or test logs, implementation details, tool names, or internal reasoning unless they change a client decision, risk, cost, or deadline. The server enforces preset-specific length and item limits and renders safe Telegram HTML.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| agent | Yes | ||
| model | Yes | ||
| route | No | ||
| preset | No | brief | |
| project | Yes | ||
| subject | Yes | ||
| summary | Yes | ||
| blockers | No | ||
| completed | No | ||
| reference | No | ||
| next_steps | No | ||
| client_questions | No | ||
| decisions_needed | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||