Open source · Self-hosted · MCP

Plan the work.
Keep the record.

Toodo is a task tracker for people and coding agents. Tasks wait on what they depend on, finish when their criteria pass, and remember every note, decision, and status change along the way.

npx @dubusoft/toodo init
Quickstart

Made by Dubusoft. AGPL-3.0, on GitHub.

The Toodo timeline across two workspaces: completed tasks on the left, tasks in progress and awaiting completion reaching the current time, and two blocked autopilot tasks waiting on them, with lines from each task to the tasks it depends on.

01Dependencies

Tasks wait for what they need. Cycles never get in.

Group tasks in workspaces and point each one at the tasks it depends on. Toodo keeps the graph acyclic, marks a task ready the moment its last prerequisite is done, and links related work that is worth reading together without blocking anything.

Three tasks in the web-shop list: Add the API endpoints awaiting completion with 2 of 3 criteria met, Build the web screens in progress, and Ship the release, marked for autopilot, blocked and waiting on #4 and #5.
add_dependencyWrite the cart migration → Ship the release

Rejected: dependency cycle: 3 -> 7 -> 5 -> 3; task 5 already depends on 3.

02Criteria

Done means checked. By a person, or by a URL.

Each task carries the criteria that finish it. A manual item is checked with its evidence; a URL item passes when Toodo fetches it at completion. Until every one passes, the task stays open and its dependents keep waiting.

Task details of Add the API endpoints: two of its three criteria are checked, each with its evidence and when an agent checked it, and the third, Pagination reviewed with the web team, is still open.

2 of 3 met. complete_task waits for the last one.

03Agents

Your agents report in. Over MCP, with reasons.

toodo init registers the server with Claude Code and Codex. From then on an agent reads the plan, starts a task, writes down its decisions and blockers, and completes the task with its refs, all through the same MCP endpoint. Toodo records what it hears; it never runs the work itself.

Read the agents guide

  1. start_task Add the API endpointsreason: ready, next in the plan
  2. add_progress_note decisioncursor pagination: ids are stable, offsets are not
  3. report_blockerstaging database is read-only until the migration lands
  4. update_task in_reviewrefs: pr:https://github.com/acme/web-shop/pull/57
  5. complete_task ✓ criteria passedShip the release is now ready

04Autopilot

Mark it once. An executor picks it up when it is ready.

Flag a task for autopilot and an executor of your choice may take it up on its own as soon as its dependencies are done. Toodo only keeps the mark and the list of marked tasks; who does the work, and where, stays up to you.

The task list filtered to autopilot: Ship the release in web-shop and Announce the release in billing-api, both blocked until the tasks they wait on are done.

list_tasks { autopilot: true } returns the marked tasks; the ready ones are fair game.

05Timeline

Every task remembers why. Your year, from recorded facts.

Starting, pausing, reviewing, and completing a task each leave a timestamp and a reason. The timeline draws the graph on a time axis, and the review report turns the same history into a week, a month, or a year of work you can export as Markdown or CSV.

Month review across all workspaces: three tasks completed, one awaiting completion, two started, and three planned, with median lead, cycle, and active times, plan versus actual, and the completed tasks listed below.
Review: a month of work from the recorded history, ready to export.
Task list of the web-shop workspace: a task awaiting completion with 2 of 3 criteria met, one in progress, one blocked autopilot task waiting on both, and one ready task.
Task list: a workspace with status, criteria, and what each task waits on.
Task details of Add the API endpoints open beside the timeline: criteria with evidence, dependencies, the pull request ref, when it was planned, started, and sent for review, and a decision note.
Task details: criteria, refs, notes, and each status change with its reason.

And the rest is just there.

One command.

Install the server, open the web app it prints, and plan your first task. Your coding agents are registered on the way.

npx @dubusoft/toodo init

Linux (x64, arm64) or macOS, with Node.js 18 or later. toodo service install keeps the server running with systemd or launchd.

Open source under AGPL-3.0-only. Contributions are welcome under a Contributor License Agreement.