Taskhold vs Backlog.md
By Jake Marsh, who builds Taskhold. Updated 2026-10-31. Facts about other tools checked 2026-10-26. 3 min read.
We make Taskhold. Facts about other tools come from their own sites and docs, checked 2026-10-26. Where a tool doesn't describe a feature, we say so rather than saying it lacks it. Something out of date? Email hello@greatwork.company.
Short answer: Backlog.md is a free, MIT-licensed task manager that keeps each task as a markdown file in the repo, with a terminal board, a local web UI and an MCP server. Pick it to version tasks with your code. Taskhold is a hosted list across repos at $12 a month, with a live board of each agent's steps that works from a phone.
Backlog.md is a free, MIT-licensed task manager where every task is a markdown file in the repo, with a terminal board, a local web UI and an MCP server. It's actively maintained and it's good. If you want tasks versioned with your code, use it. Taskhold is a hosted list across repos with a live board of each agent's progress, closer to one task list across all your repos. A TODO.md file is the even simpler option, and the roundup compares them all.
Side by side
| Item | Backlog.md | Taskhold |
|---|---|---|
| Price | Free (MIT) | $12/month or $120/year per person |
| Where tasks live | Markdown files in the repo, versioned with git | Hosted list |
| Human view | Terminal board and local web UI with real-time updates, bound to 127.0.0.1 | Web app on any device, including a phone |
| Agent progress inside a task | Task status and acceptance criteria checkboxes | Steps with a progress bar, percent or N of M, and the agent's current message |
| Agent asks you something | Not described in the README | Blocked question on the live board with a reply box |
| Across repos | One backlog per repo (one MCP server can serve them all) | One list, grouped by project |
| Offline | Yes | No |
| History | Git history, comment authors | Every change, marked human or agent |
| Acceptance criteria, milestones, dependencies | Yes | No (description and priority only) |
| Setup | Install the CLI, backlog init per repo | Paste a setup URL |
| Run your own code when a task changes | Not described in the README | Server-sent event stream and REST API; the docs include a Slack alert recipe |
Backlog.md facts from its GitHub README, checked 2026-10-26.
When is Backlog.md the better choice?
- You want tasks in git next to the code they describe.
- You work offline or don't want a third party holding task data.
- You want acceptance criteria and dependencies.
When is Taskhold the better choice?
- Your tasks span several repos, or aren't tied to a repo.
- You want to queue and review work from a phone or another machine without running a local server.
- You don't want task files committed alongside code.
Moving tasks over
Your agent can move them in one go. Each Backlog.md task is a markdown file with YAML frontmatter, so the Backlog.md import prompt has the agent read the files, file each open task with taskhold_create (acceptance criteria in the description) and turn subtasks into steps with taskhold_plan. The files stay in git if you want the history.
Answer your coding agents from anywhere.
$12/month or $120/year after the trial. Card up front. Cancel before day 7 and you pay nothing. Every agent you run is included.
Or connect your agent first, no sign-up: add https://taskhold.com/api/mcp as an MCP server. The first time it uses Taskhold, it gives you the trial link.
Questions
- Can I import my Backlog.md tasks?
- Yes, through your agent. The import guide has a prompt that reads the task files, files each open task with taskhold_create and turns subtasks into steps. Nothing in backlog/ changes.
Sources
- Backlog.md README, checked 2026-10-26
- Taskhold events stream docs, checked 2026-10-26
Related
Updated 2026-10-31. Something wrong or out of date? Email hello@greatwork.company.