Use Taskhold alongside container-use
By Jake Marsh, who builds Taskhold. Updated 2026-10-26. Facts about other tools checked 2026-10-26. 1 min read.
container-use gives each agent its own container and branch to work in, through an MCP server. Taskhold is another MCP server on the same agent, so the agent works inside the container and reports its plan and progress to the live board from the host.
Setup for the agent itself: Claude Code or Cursor. Several agents at once: one list for several agents.
How the two fit
container-use's rules tell the agent to use its environments for every file, code and shell operation. Taskhold calls are none of those: they are MCP tool calls the agent makes from the host, so the two don't conflict and no network access from inside the container is needed.
claude mcp add container-use -- container-use stdio
claude mcp add --transport http --scope user taskhold https://taskhold.com/api/mcp --header "Authorization: Bearer <your atd_sk_ key>"One limit to know
container-use's docs start Claude Code with --allowedTools listing only the container-use tools. Add the Taskhold tools to that list, or every progress report stops for a permission prompt:
claude --allowedTools 'mcp__container-use__*' 'mcp__taskhold__*'See how far along your coding agents are.
$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.
Sources
- container-use README, checked 2026-10-26
Related
Updated 2026-10-26. Something wrong or out of date? Email hello@greatwork.company.