Tasks

list_tasks

Read-only. Allowed without asking.

Finds tasks. Without filters, it lists every open task. Filters combine: a task must match all of them.

Returns the number of matches and one line per task. When there are more than the limit: …and 12 more. Narrow the filters or raise the limit.

get_task

Read-only. Allowed without asking.

Everything about one task: title, status, priority, where it lives, due and planned dates, estimate, who does it, labels, its folder (its own, marked (its own), else the project's), where its sessions run when that's set, what they need from the computer (Needs on its computer: supabase, Gmail), what its sessions' agents used once they reported it (Agents used: 262k tokens · 1 min working · 1 session), the description, the numbered Done when items, the numbered sub-tasks with their state, the tasks it waits for (Waits for:) and those that wait for it (Before:), the latest session, the latest report an agent handed back, and when it was created, updated and finished.

The report starts with its session, the agent, when it was handed back and its outcome: done, partly done or blocked, needs the user. Then come the summary, each Done when item with the agent's verdict (met, partly met, not met or not answered) and note, the images, each by its caption, size in pixels, type and file size, how to check the result, what changed in git since the session started (Files changed since the session started (from git): 2 files, +3 −0, 1 commit, then up to 10 commits and 30 files, each with its status and lines added and removed), the questions for the user, links, follow-ups, the details, and the changes the user asked for, if any. It's headed Latest report when it comes from the task's latest session, else Last report, from an earlier session. The Latest session line appears only when that session has no report of its own, such as a session still at work on its first hand-back.

For example, with the sample data:

DEV-21 · MCP server skeleton
Status: In review · Priority: High
Where: project Organizer app (organizer) in Dev
Due: 2026-09-25 (Fri) · Planned for: none
Estimate: 1h · Agent: Claude Code
Labels: mcp

Description:
Expose tasks, projects and time blocks over MCP so Claude Code and Codex can read and update them.

Done when:
1. /api/mcp answers tools/list with the task tools
2. Requests without the token get 401
3. Claude Code can create a task through it

Waits for: DEV-19
Before: DEV-22, DEV-24

Latest report · session 3f2a9c1b · Claude Code · 2026-09-24 13:53:07 · done
Summary: MCP endpoint added at /api/mcp. Tests pass.
Done when:
1. [met] /api/mcp answers tools/list with the task tools · 12 tools listed.
2. [met] Requests without the token get 401
3. [partly met] Claude Code can create a task through it · Tried with the MCP inspector, not with Claude Code yet.
How to check:
1. Run npm run dev
2. Open Settings → MCP server and copy the connect command
3. Ask Claude Code to list your tasks
Questions for the user:
- Should agents be allowed to delete tasks without asking?
Details:
- `src/app/api/mcp/route.ts` serves the MCP server with **mcp-handler**.
- Tools for tasks, projects and time blocks live in `src/server/mcp/`.
- Every request needs the bearer token from Settings.

Created 2026-09-21 13:53:07 · updated 2026-09-24 13:53:07

The sub-task numbers are the ones update_task accepts, and the Done when numbers are the ones finish_task accepts in criteria.

create_task

Changes data. Allowed without asking.

Adds a task. Without project and area, it goes to the Inbox.

Returns the new task's line, with its key and the number of Done when items and sub-tasks: Created DEV-43 · Todo · High · Add CSV export to the reports page · Organizer app · 4 Done when items · 3 sub-tasks.

A project together with an area that isn't the project's area is refused: Project … is in …, not …. Leave out the area.

create_tasks

Changes data.

Adds up to 50 tasks at once, for example when breaking a project down. All go to the same place; each has its own details.

All dates are checked before anything is created, so one wrong date doesn't leave half the tasks behind.

update_task

Changes data. Allowed without asking.

Changes anything about a task. Parameters left out keep their value; null clears a date, the project, the area, the agent, runs_in or folder, and an empty list, [], clears done_when or needs. A session PacedMind started can't change its own task's runs_in, folder or needs.

Returns the updated task line; with done_when, the number of Done when items, such as · 3 Done when items; and, with sub-tasks, how many are done, such as · 3/4 sub-tasks done.

bulk_update_tasks

Changes data.

Applies the same change to up to 100 tasks, for rescheduling and triage.

shift_days can't be combined with due or planned. Setting status to done works as in update_task: finished sessions of those tasks count as reviewed, and a repeating task comes back as a new one.

connect_tasks

Changes data.

Makes one task wait for another in the same project: a dependency, the same as an arrow drawn on the Timeline. The waiting task is ready to work on once the other one is done, or in review, unless its agent handed it back partly done or blocked. A dependency only orders the work: nothing starts by itself. get_next_task and get_project follow it.

Returns DEV-23 waits for DEV-22. Refused when:

• from and to are the same task (A task can't wait for itself.);
• the tasks aren't both in the same project (Both tasks have to be in the same project.);
• the dependency would close a loop (DEV-22 already waits for DEV-23, so this would make a loop.).

disconnect_tasks

Deletes.

Removes a dependency: to stops waiting for from. The tasks themselves stay.

Returns DEV-23 no longer waits for DEV-22., or the error DEV-23 doesn't wait for DEV-22. when there's no such dependency.

delete_task

Deletes. Agents ask the user first.

Deletes a task with its sub-tasks, sessions and dependencies, and the reports and images its agents handed back. Setting the status to canceled keeps a record and is often the better choice.