Update Task Tool
update_taskEdit an existing task's title, details, status, assignee, project, checklist steps, files, or comments to keep work items current and correctly routed.
Instructions
Changes a task: edit its title or details (title, notes: the whole new text, read it first with start_task or list_tasks; add_steps appends new - [ ] steps), take it (assignee "me", status "doing"), move it (todo, doing, blocked with a reason, done, dropped; todo turns an idea into a task), move it to another project (move_to_project), remove its files you added (remove_files; to swap a changed file, use add_attachment with replaces instead), give it to someone ("none" frees it), tick its steps (check) or comment on it. Progress on a task with steps is shown by ticking the finished steps (check: [numbers]), not by listing them in a comment; a comment is for questions, answers and what the steps do not cover; while working on your own, do not comment on every small change: one comment when there is a result or a question. Before giving a task to someone else, when it has gathered several comments or file versions, ask the person once whether to leave a handoff note (handoff: what is done, what is left, which file is the final one) and mark the earlier files as older versions (old_files); nothing is deleted. Only when the person asked for it.
Tool call template
Replace each placeholder with a value matching the input schema. Only required parameters are included; add optional parameters as needed.
{
"id": 1,
"jsonrpc": "2.0",
"method": "tools/call",
"params": {
"arguments": {
"id": "<id>"
},
"name": "update_task"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Task number, e.g. 12. | |
| due | No | A due date, YYYY-MM-DD, or "none" to remove it. | |
| check | No | Step numbers (from 1, as start_task lists them) to tick in the task's checklist, when they are finished. | |
| notes | No | The task's new details (its description), in Markdown: the whole text, replacing the old one. Read the current details first (start_task or list_tasks) and keep what should stay, including the - [ ] / - [x] steps; an empty string clears them. Only when the person asks. | |
| proof | No | With status done: the proof - the commit, the address where the change shows, or a short note. Kept on the task. | |
| title | No | A new title, when the person wants it renamed. | |
| reason | No | What a blocked task is waiting for. | |
| repeat | No | Makes the task come back: when it is done, the next one is added, due one interval later; "none" stops it. | |
| status | No | todo also turns an idea into a task. | |
| comment | No | A comment on the task (a question, a clarification, an answer), in Markdown; colleagues and, on projects visible to the client, the client see it. Not for reporting finished steps: tick them with check (both can go in the same call). Only when the person asks. | |
| handoff | No | A handoff note, usually with assignee when the task goes to someone else: what is done, what is left, which file is the final one (by name), in Markdown. Whoever opens the task sees it first, above the comments. Only after the person agreed. | |
| uncheck | No | Step numbers to untick, if ticked by mistake. | |
| assignee | No | "me", a colleague's name or email, or "none" to free the task. | |
| add_steps | No | New steps to append to the task's checklist, unticked (just the text of each). Use it instead of notes when only steps are added. | |
| old_files | No | Ids of the task's files that are earlier versions (from read_task): they stay on the task, shown under the current ones as older versions, so whoever takes it over knows which file is the final one. Nothing is deleted. Only after the person agreed. | |
| remove_files | No | Ids of the task's files to remove (from start_task: those with can_replace). Only the files you added, and only while the task is open: on a closed task they stay as reference. To put a new version in place of a file, use add_attachment with replaces instead. | |
| move_to_project | No | Moves the task, with its files, to another project (slug or name) the person can see. Whoever does it stays on it only if they work on that project too. Only when the person asks. |