Use Taskhold with Claude Squad

What you get

• Each session takes a different task: one an agent has started shows as in progress, so the next session takes the next one.
• One card per session on the live board, labelled with its branch, with its steps, progress and last message.
• Sessions that need you listed first under Needs you, so you know which one to switch to in Claude Squad.

Set it up

Claude Squad starts the normal claude (or codex, gemini) command in a new worktree for every session, so two things must be true for each session to see Taskhold:

1. The MCP server is configured at user scope, not per project. A project-local Claude Code server is stored against the original folder path and doesn't follow a new worktree.
2. The workflow lives in a CLAUDE.md or AGENTS.md that is committed. Worktrees only contain tracked files.

claude mcp add --transport http --scope user taskhold https://taskhold.com/api/mcp --header "Authorization: Bearer <your atd_sk_ key>"

Add the workflow to the repo's CLAUDE.md, with one extra line so each session labels itself by branch:

## Tasks (Taskhold)

The person and I share a task list through the taskhold MCP tools. They watch a live board while I work.
- Session start: taskhold_get_current, then taskhold_updates for replies. Nothing in progress? taskhold_list status:todo and take the highest priority.
- taskhold_start before working on a task (agent: "Claude Code in <repo>").
- More than a couple of steps: taskhold_plan, then taskhold_start and taskhold_complete each step.
- taskhold_progress at milestones (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 check taskhold_updates.
- Done: taskhold_complete with what changed and how I checked it.
- A TODO or bug I'm not fixing now: taskhold_create (or taskhold_create_from_todo with file and line).
- Running in a worktree: use the agent label "Claude Code on <branch>" (git branch --show-current).

Commit it, then start sessions as usual with cs. To see every session's progress without leaving tmux, open a window with taskhold-mcp watch (see tmux).

One limit to know

Claude Squad has no hooks, so Taskhold only knows what each agent reports through the MCP tools. A session that ignores the workflow (or never got CLAUDE.md, because it wasn't committed) does its work but never shows on the board. Claude Squad's own list still tells you a session is running; the board tells you what it is doing.