task_update
Update a task's status, progress, or notes on a board. Pass only the fields to change; notes append, metadata merges.
Instructions
Patch one task on a board — status, progress, a note, or any other field. Only the arguments you pass are changed.
Push every meaningful change the moment it happens: the user's board polls
the same list, so a note or a progress bump is how they see you're alive
and steer you before you go too far. note appends to the task's thread
(nothing is overwritten) and metadata merges key-wise.
Input Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
| note | No | A line to append to the task's thread — what you did, what you found, why you're blocked. | |
| title | No | New title. | |
| parent | No | Re-parent under this epic's task id. | |
| status | No | "todo", "in_progress", "blocked", "review", "done", or "cancelled". Setting "done" also releases your lock. | |
| project | Yes | The board's project id, data slug, or URL. | |
| task_id | Yes | The task to patch (from tasklist_get). | |
| metadata | No | Keys to merge into the task's metadata. | |
| priority | No | "low", "medium", "high", or "critical". | |
| progress | No | 0–100. | |
| agent_name | No | Stable, readable name for you. | |
| agent_type | No | Optional agent family. | |
| active_form | No | New present-tense label. | |
| description | No | New description. | |
| expected_version | No | The list `version` you're writing against — pass it whenever you have one. |
Output Schema
TableJSON Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||