tasks_update
Update a task's status, title, body, blockers, or gate to track progress and unblock dependents; clearing a gate or final blocker makes dependent work ready.
Instructions
Update a task: change status (open|in_progress|done|dropped), edit title/body, add or remove dependencies, or set, edit or clear its gate. Moving to done/dropped closes it and unblocks its dependents; removing its last unfinished blocker makes it ready. Removing an id that is not one of its blockers changes nothing and is named back in not_depends_on; the ids removed are in removed_depends_on. Setting any gate_* field (re)opens the gate as it then reads; gate_clear=true clears an open gate once the person has acted, recording when, by this session, and gate_note: a step keeps its status and becomes ready once nothing else holds it, and a task of kind gate closes as done, which unblocks every task that depends on it. A task another session holds via a live claim is locked to its holder: updating it fails with 'already claimed' until the lease lapses or the holder releases 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": "tasks_update"
}
}Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | task id | |
| body | No | new body (aliases: content, text) | |
| kind | No | step (the default: work an agent claims and finishes) or gate (a person's action, or an event outside Seamless, that the tasks depending on it wait for: never ready and never claimed; gate_who and gate_what describe it, and clearing it closes it and unblocks its dependents) | |
| title | No | new title | |
| status | No | new status | |
| project | No | reassign the task to another project slug (used when a split moves a project's open work to a child) | |
| session | No | the acting agent's session (the cc/<id> or cx/<id> on your briefing's 'Seam session' line, or a session name); needed only to mutate a task you hold a live claim on when several agents are active | |
| gate_who | No | who must act before this task can go ahead: owner, founder:<name>, sitting:<name>, hardware, sealed:<project>, or free text (one line). With gate_what it gives the task a gate: a step whose gate is open is not ready, and tasks_ready lists it under gated | |
| gate_note | No | optional, with gate_clear: what the person decided or did, kept with the cleared gate | |
| gate_what | No | what must happen, one line (with gate_who) | |
| gate_clear | No | true: clear the task's open gate now that the person has acted (not with the gate_* edits) | |
| session_id | No | the acting agent's session ULID; takes precedence over session and the bound session | |
| gate_decision | No | optional: the open question the person answers, one line | |
| add_depends_on | No | task ids to add as blockers (a comma-separated string is also accepted) | |
| gate_ready_when | No | optional: when the task is ready, one line | |
| remove_depends_on | No | task ids to remove as blockers (a comma-separated string is also accepted); an id that is not a blocker of this task is a no-op, named back in not_depends_on |