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
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.
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.
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.
- start_task Add the API endpointsreason: ready, next in the plan
- add_progress_note decisioncursor pagination: ids are stable, offsets are not
- report_blockerstaging database is read-only until the migration lands
- update_task in_reviewrefs: pr:https://github.com/acme/web-shop/pull/57
- 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.
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.
And the rest is just there.
- Work memory
Progress, decision, and blocker notes, a completion note, and refs such as
pr:<url>on every task. - Workspaces
One per project, with an optional repository; tasks can move between them and links may cross them.
- Waits and pauses
Pause with a reason, or wait until a time and let the task come back on its own.
- An app on every device
The server serves a web app you can install on a desktop or a phone, with push notifications.
- Your data, one file
Tasks and their history live in a SQLite database on the machine you run the server on.
- Updates that roll back
toodo updaterestarts on the new version and returns to the old one if it does not answer. - Review exports
Copy a report as Markdown, save it as Markdown or CSV, or print it.
- Plans in one call
An agent can create a whole plan, tasks and dependencies together, and you see it on the timeline.
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
npm i -g @dubusoft/toodo
toodo init
toodo service install
Open source under AGPL-3.0-only. Contributions are welcome under a Contributor License Agreement.