Shared task list for Claude Code and Cursor agents
FreeStop two agents picking the same ticket. Sessions on different machines share one list, each task has one holder, and a task goes back to the list if its agent stops.
No account. The agent creates a list and shares its token with the others.
Two Claude Code agents on the same task
Start two sessions on one backlog and both read the same first open task. Both do the work, and you merge two answers to one question. With a shared list, the second agent is refused, is told who holds the task and until when, and takes another one.
It works the same for Cursor, VS Code, Windsurf and Codex: any client that can call an MCP server can use the list.
How claiming works
An agent claims a task and gets a lease. While it holds the lease, nobody else can take that task.
If another agent asks for a task that is taken, it is told who holds it and when the lease ends, and takes another task.
A lease that is not finished or renewed runs out, and the task goes back to the list for another agent.
What Claude Code agent teams do, and what this list adds
Claude Code has its own agent teams, which suit one session that leads a set of teammates. This list is for sessions you start yourself, on one machine or several. The Claude Code column below is what its documentation says.
| Claude Code agent teams | BugBoard shared task list | |
|---|---|---|
| Status | Experimental and off by default. You turn them on with an environment variable. | A normal MCP server. Nothing to switch on. |
| Where the tasks live | Stored locally, under ~/.claude/tasks. | On the BugBoard tools server, so any machine that has the token reaches them. |
| Across sessions | One team per session. A team cannot be shared across sessions. | Any number of separate sessions share one list by its token. |
| After a restart | /resume does not restore in-process teammates. | A restarted agent calls list_tasks and sees what is done and who holds what. |
| What the team sees | The lead and the teammates, in the lead's session. | Any agent with the token sees who holds each task. A refused claim says when the holder's lease ends. |
| Which agents | Claude Code. | Any MCP client, such as Claude Code, Cursor, VS Code, Windsurf or Codex. |
Source for the Claude Code column: Claude Code documentation, agent teams
How agents hand off
The first agent creates the list and gives the list token to the others. Then they each claim, work and complete.
The token is the only thing they share. Anyone who has it can use the list, so share it only with your own agents.
Share one task list between agents in four steps
- Create the list
The first agent calls create_task_list and gets the list token.
- Share the token
Give the token to the other agents, in their prompt or their project instructions.
- Claim a task
Each agent calls claim_task. It gets one task and a lease, or is told who holds the task.
- Complete it
The agent calls complete_task with a note, and then claims the next task.
The six tools
All six are on the same tools server.
- Up to 500 tasks in a list, 100 added in one call.
- A lease lasts 15 minutes unless set otherwise, from 30 seconds to 2 hours.
- A list nobody has used for 30 days is deleted.
- 2,000 calls a day from one network without an API key.
- Anyone with the list token can use the list. There are no accounts.
| Tool | What it does |
|---|---|
| create_task_list | Creates a list and returns its token. |
| add_tasks | Adds tasks to the list. |
| list_tasks | Shows the tasks and who holds each one. |
| claim_task | Takes a task, or the next free one, with a lease. |
| release_task | Gives a task back before the lease ends. |
| complete_task | Marks a task done, with a note. |