vibedoc_update_task

Update task status. Call when starting, finishing, or blocking a task. UI updates in real time. When moving a task to done, include manualTests: a checklist of what a human should click through to trust it, written from what you actually changed. If items are left for a human (manual ones, or 🤖 ones no passing run proved), the task lands in review instead of done; that is expected: carry on, its dependents can still start.

Parameters

Name	Type	Required	Description
taskId	string	yes
status	one of "todo" "in-progress" "review" "done" "blocked" "paused" "cancelled"	yes
manualTests	string	no	Optional manual test report, saved as the task's `## Manual tests` section (replaces an older one). Markdown checklist: `### Steps` items as `- [ ] <what to do> → <what you should see>`, then `### Regression risk` items for existing features worth re-checking. Plain lines become unticked steps. Prefix an item with `🤖 ` (`- [ ] 🤖 Open / → board loads`) when a Playwright spec covers it.
spec	string	no	Optional Playwright spec covering the 🤖 items, a path relative to the repo root (e.g. `e2e/vibedoc/T145-foo.spec.ts`). Written in the manual tests header. Without manualTests it updates the existing section's header only.
autoResult	one of "passed" "failed"	no	Optional result of the spec's last run (dated today). Without manualTests it updates the existing section's header only.
agent	string	no	Your name as the owner of the task, e.g. "claude" (defaults to the MCP client's name). Starting a task makes you its owner.

Call it

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "vibedoc_update_task",
    "arguments": {
      "taskId": "<string>",
      "status": "<\"todo\" | \"in-progress\" | \"review\" | \"done\" | \"blocked\" | \"paused\" | \"cancelled\">"
    }
  }
}