Projects

Read Projects: one project by id (with its task rows), projects filtered by text, status, priority, tag or area, or with type 'task' project tasks by projectId, text, status, priority, tag or dueOnOrBefore. ALWAYS pass dueOnOrBefore when the question concerns near-term work. Compact rows unless detail is 'full'.

Note: type 'task' reads project tasks; one project by id comes with its task rows.

{
  "status": "active"
}

Add a project for a serious multi-step outcome (never for a one-off task): name, summary, outcome (definition of done), status, priority, area, startDate/targetDate (YYYY-MM-DD), tags and milestones. Or a work item on a project's board: task with projectId and title, plus status, priority, dueDate, effortPoints, assignees and tags. Example: project { name 'Launch Vritto beta', status 'active', targetDate '2026-08-01', tags ['work'] }.

Note: type 'task' with task { projectId, title } adds a work item to a project's board.

{
  "project": {
    "name": "Kitchen remodel",
    "outcome": "A kitchen we cook in every night",
    "status": "active",
    "targetDate": "2027-03-01"
  }
}

Change one project by id, or with type 'task' one project task: only the fields in patch change (status 'done' finishes a task; progress is task-weighted on its own). publishToTasks copies and links a project task into the general Tasks list, only when the user explicitly asks. Resolve the id with projects_find first.

Note: type 'task' changes a project task; publishToTasks copies and links it into Tasks.

{
  "id": "proj_kitchen",
  "patch": {
    "targetDate": "2027-04-01",
    "status": "paused"
  }
}

Delete a project (cancelled and archived with its board), or with type 'task' cancel one project task. Only for explicit deletion requests. Resolve the id with projects_find first.

Note: type 'task' cancels one project task; a project goes with its board.