Reference
Update a task in place
The REST call PATCH /api/v1/tasks/{id}.
RESTPATCH /api/v1/tasks/{id}
MCPNot on the MCP surface — served over REST only.
One item of update-tasks, addressed by path.
Parameters
- id
Body
This operation takes a JSON body. The spec is the contract and it is what the agent reads every turn — seepackages/server/src/rest/openapi/v1/for the shape.
Responses
200The acknowledgement — `get-task` reads the task back
400The request body or query string does not match the operation's schema, or a `calendar` task names no date (`calendar_requires_date`)
404No such task
409The status change is not one the GTD state table allows. The body's `error.code` is `invalid_transition` and `error.meta` carries `from`, `to` and `allowed` — the statuses this task can actually move to.
Generated from the spec this operation is implemented against, so the two names above cannot disagree with the surface a client sees.