New: watch your coding agents work, step by step, on a live board. Try the demo, no account

One todo list for Claude Code and Cursor

By Jake Marsh, who builds Taskhold. Updated 2026-10-31. 4 min read.

If you use Claude Code in the terminal and Cursor in the editor, each has its own idea of what to do next. Their built-in todo lists don't see each other, and neither survives the end of a session.

The fix is one list outside both tools that each of them reads and updates. This guide sets that up with Taskhold, a hosted task list with an MCP server and a live board where you watch both agents' progress, and covers the same idea with a plain file if you'd rather not use a service. Setup details for each tool are on the Claude Code and Cursor pages, and running more coding agents in parallel on one task list covers what changes when a third or fourth joins.

Option 1: a file in the repo

Free and fine for one repo. Create TASKS.md, tell both agents (CLAUDE.md for Claude Code, a rule or AGENTS.md for Cursor) to read it at the start and tick items off when done.

Where it breaks: you have to open the repo to see or change it, there's no record of which tool changed what beyond git, nothing stops both agents picking the same line, and it doesn't span repos.

Option 2: one hosted list over MCP

Make two setup URLs in Taskhold's Settings, one per client, and paste each into its agent. Claude Code runs a claude mcp add command; Cursor gets a ~/.cursor/mcp.json entry. Both point at the same list with separate keys.

Then put the same workflow snippet in CLAUDE.md and in Cursor's rules:

## Tasks (Taskhold)

The person and I share a task list through the taskhold MCP tools. They watch a live board while I work.
Pass project: "<repo folder name>" on every call (created on first use, no ids needed).
- Session start: taskhold_get_current and taskhold_updates, both with project. Keep the cursor.
- New request: taskhold_begin with title, project, steps and agent: "<client> in <repo>". It files the task, plans the steps and starts the first one. Queued work: taskhold_next with project and agent takes the next To Do task and starts it; after each one, call it again until it says To Do is empty.
- Project notes in a reply (stack, commands, what done means, what to avoid) are the person's rules for every task in that project.
- Each step done: taskhold_complete with start_next: true. Steps drive the progress bar.
- Long step: taskhold_progress on the step (N of M, or a percent) with a short message. Every few minutes at most.
- Need a decision: taskhold_block with one specific question, then taskhold_updates with task_id, since and wait: 50 until the reply arrives.
- Done: taskhold_complete on the task with what changed and how I checked it.
- A TODO or bug I'm not fixing now: taskhold_create with project (or taskhold_create_from_todo with file and line).

How they avoid doing the same task

  • An agent calls taskhold_start before working, which moves the task to in progress.
  • The other agent lists todo tasks only, so it takes the next one.
  • If an agent stops partway, taskhold_block records why, and the task stays out of the queue until you unblock it.

This is coordination by convention, not a hard lock: two agents that call start on the same task at the same moment can still collide. In practice, with one person running a few agents, the in-progress status is enough.

Reading what happened

Each task keeps its history and notes, with every change marked as made by you or by an agent. The Agents page shows each agent's current task and step, the questions it's waiting on you for and what it finished this week. Agent notes show up in the live board's activity feed, and tasks agents filed show up there and in the "Since you were here" card. Each agent passes a label when it starts a task, such as "Cursor in web-app", and the live board and each task's timeline show that name next to its changes.

Share this page:XLinkedInBlueskyHacker News

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 use it with only one of the two?
Yes. Most people start with one agent. Adding a second later is one more setup URL.
Does it work across several repos?
Yes. The list is per person, not per repo. Agents pass the repo's folder name as project and the project is created on first use, so each repo's tasks stay together. More in one task list across repos.
What does it cost?
$12 a month or $120 a year per person, with a 7-day trial that starts with a card.

Related

Updated 2026-10-31. Something wrong or out of date? Email hello@greatwork.company.