Automating End-to-End Development with Claude Task Master
Claude Task Master (claudetm) is a command-line tool built on the Claude Agent SDK that keeps Claude working until a goal is achieved. It is designed for teams that already use Claude Code and want a fully automated PR-based workflow. In this article we walk through the core concepts, installation steps, and how to integrate it into existing CI pipelines.
Core Workflow
The tool follows a clear lifecycle:
- Planning - It scans the repository, creates a task list, and defines success criteria.
- Working - For each task it writes code, runs tests, commits changes, and pushes to a branch.
- PR Lifecycle - It opens a pull request, waits for CI, fixes any failures, addresses review comments, and merges when approved.
- Verification - After merge it runs a final verification suite to ensure all criteria are met.
Each stage persists its state, so if the runner is stopped the next invocation resumes exactly where it left off.
Installation
Claude Task Master can be installed via uv, pip, or Docker. The minimum requirements are Python 3.10, an authenticated Claude CLI (claude /login), and the GitHub CLI (gh auth login). A quick start looks like this:
uv tool install claude-task-master
claude /login
cd my-project
claudetm start "Add user authentication with tests"
The command reads the goal, plans the work, and begins the autonomous loop.
Profiles for Multi-Instance Coordination
By default claudetm uses the global Claude Code session, but you can create isolated profiles for parallel execution. A profile stores its own Claude configuration under ~/.claudetm/profiles/<name>/. This allows multiple Claude subscriptions to run on the same repository without clobbering each other.
claudetm --profile dev-team start "Implement feature X"
claudetm --profile qa-team start "Run full regression suite"
Each profile maintains its own state and mailbox, enabling safe concurrent operation.
Extending with REST API, MCP Server, and Webhooks
Claude Task Master exposes a REST API and an MCP server that mirror the CLI’s functionality. You can dispatch a task by sending a JSON payload to /tasks and receive updates via HMAC-signed webhooks. This makes it easy to embed the tool in dashboards, chatops, or custom CI pipelines.
{
"goal": "Migrate legacy auth to OAuth2",
"profile": "devops",
"webhook_url": "https://example.com/webhook"
}
The server will post status events such as planning, working, pr_opened, ci_failed, and merged.
Handling CI Failures and Review Comments
When a CI check fails, Claude Task Master automatically reads the error, applies a fix, and re-runs the checks. If a reviewer leaves a comment, the tool can incorporate the feedback and push a new commit to the same PR. This loop continues until the PR passes all checks and receives approval, at which point it can auto-merge.
Open Source and Community
Claude Task Master is MIT licensed and hosted on GitHub at https://github.com/developerz-ai/claude-task-master. Contributions are welcome, and the repository includes Dockerfiles, CI configurations, and examples for custom integrations.
When to Use Claude Task Master
- Teams already using Claude Code that want a hands-off PR workflow.
- Projects with well-scoped goals that can be verified against explicit success criteria.
- Organizations running multiple Claude subscriptions that need isolation.
- Scenarios where you want to embed autonomous coding into existing tooling via API or webhooks.
If these points describe your workflow, give Claude Task Master a try and let autonomous agents handle the repetitive parts of development while you focus on architecture and design.
This article was written with the help of Claude Task Master and follows the knowledge base provided by the project.
Top comments (0)