agentboard

List every project in the vault with task counts by status. Does not return the tasks themselves — use list_tasks for that.

Create a new project in the vault. `key` is a short prefix for task IDs (e.g. WEB); it's derived from the name if omitted.

Permanently delete a project — all of its tasks and history, unrecoverable. Only on an explicit human request, never on your own guess.

A lightweight list of a project's tasks (no descriptions/history/comments) — saves context. Use get_task for the details of one.

The full card for one task: description, versioned updates (the task's evolution), comments, technical activity, and subtasks. Request only when you need the details of a specific task.

Recommends the next task to work on: not blocked, not in the terminal status, lowest `order` first (ties broken by priority). With no `parent`, it searches the whole project at every depth — so nested-only work isn't missed; pass a `parent` id to scope the search to that task's direct subtasks. Use …

Create a new top-level task in a project.

Create a subtask inside an existing task (to break a plan down without holding it all in your own context).

Change a task's status. This is routine bookkeeping — it goes into the task's technical activity, not its versioned updates.

Flag (or unflag) a task as waiting on a human decision — independent of status, since work can stall at any stage of the pipeline, not just in a dedicated column. A task flagged this way stops being suggested by get_next_task. Once the human has answered (in a comment), clear it by calling again wit…

Change fields on an existing task (title, priority, labels, order, blockers, assignee) without changing status and without creating an update — this is also routine bookkeeping, logged to technical activity. Pass only the fields you're changing.

Record a 'big update' to a task: rewrite the description once discussion/work has led to a decision about what should change. `summary` is a required short note on WHAT changed and WHY (like a commit message). Each call creates a new version with a full snapshot of the description — this builds the …

Leave a comment on a task — discussion, a clarifying question for the human, a passing remark while working. To actually change the task's substance (its description) once discussion has led somewhere, use update_description, not this.

The index of the project's memory: one line per knowledge note (id, title, hook). Read this at the START of every session, before get_next_task — it's tiny, and it tells you what's already been settled so you don't re-derive or contradict it. Then get_note only the entries relevant to your current t…

One knowledge note in full: body = the CURRENT truth (latest formulas, chosen approach), history = how it got there (versioned summaries — read these when you need to know why something changed). Notes are addressed by [[id]] wikilinks — when a task description mentions [[some-note]], this is how yo…

Create or update a knowledge note — the project's memory. WHEN: you've just settled something reusable (a final formula, a validated approach, a decision and its why, a costly pitfall) — write it AT THAT MOMENT, don't wait for the task to close. Test: 'will a session that never saw this task need it…

Permanently delete a task (its file and all its history) — e.g. a duplicate, or a subtask that's no longer needed. Cascades to all of its subtasks. Irreversible — not for changing status, use update_status for that.