Our take
Activeregular commits- Activity
- 53
- Community
- 41
- Issues
- 69
- Pull requests
- 86
- Merges more pull requests than 99% of the projects we track
TAKT is a capable workflow-control CLI for teams that want explicit review loops and traceable agent work, but its recent activity is heavily concentrated in one contributor and it has no release in the past year.
Good fit if
- You want YAML-defined stages and review feedback loops rather than process instructions left to an agent.
- Your coding tasks can run with Node.js and Git, and you value isolated worktrees and recorded execution artifacts.
- You can work with an MIT-licensed project whose reported status is active and whose recent changes have been handled regularly.
Look elsewhere if
- Your team cannot accommodate the required Node.js version or Git version.
- You need a project whose maintenance is broadly distributed, since most reported contributions come from one person.
- You require recent published releases as a signal of packaged version stability.
All health signals
| Last commit | 2026-11-01 (today) |
|---|---|
| Commits, last 90 days | 100+ |
| Releases, last 12 months | 0 |
| Contributors | 35 (top contributor: 91% of commits) |
| Issues closed, last 90 days | 21+ (typically closed in 3 days) |
| Pull requests merged, last 90 days | 100+ (typically merged in 0 days) |
| Project age | 9 months |
Checked on 2026-11-02 with the GitHub API.
Project history
Daily GitHub snapshots since Nov 2, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
1,433Forks
116More snapshots will appear as the daily collection continues.
Overview
TAKT is a TypeScript CLI for coordinating AI coding agents through explicit, reusable workflows written in YAML. It addresses the difficulty of keeping long-running agent work consistent: instead of relying on one agent to remember a process, workflows assign roles and rules to steps such as planning, implementation, review, and fixing.
Designed primarily for coding tasks, TAKT can run queued work in isolated Git worktrees and retain logs and reports for inspection. Teams can use it with several agent providers, while the workflow controls how steps and review feedback progress.
Key Features
- Define workflow steps, roles, permissions, and transitions in YAML.
- Route review findings back through fix and re-review loops.
- Give each step its own persona, policies, knowledge, instructions, and output contracts.
- Queue tasks and execute them in isolated Git worktrees.
- Inspect execution logs and reports after a task runs.
- Integrate with multiple providers, including Claude, Codex, OpenCode, Pi, Cursor, GitHub Copilot CLI, and Kiro.
- Use CLI commands to manage queued tasks, retry work, and review or merge results.
Use Cases
- A development team wants agent-generated changes to pass through defined planning, implementation, and review stages before completion.
- A maintainer needs agents to work on queued issues in separate worktrees rather than directly in the active project tree.
- A team using different agent providers wants to keep its workflow definition separate from provider selection.
- A developer wants execution traces and reports to help inspect how an agent task reached its result.
What you need
Detected in the repository
- Node.js >=22.22.0 (from package.json)
- A Dockerfile, so it can run in a container; a Compose file sets up the related services
- A test suite and automated checks on GitHub Actions
License in plain words
MITpermissive
- Commercial use: yes
- Modify and redistribute: yes
- You must keep: the copyright and license notice
- Share your changes: no
A summary, not legal advice: the LICENSE file is what applies.
Getting Started
npm install -g takt
takt install claude-sdk
takt
From a Git repository, describe a task, use /go to prepare it, save it as a task, and run takt run. See the README for provider setup and workflow details.
Alternatives
- aidlc-workflows: AI-DLC provides harness-neutral delivery stages and approval gates, while takt runs YAML-defined workflows in isolated worktrees.
- ralph-orchestrator: Ralph Orchestrator uses role-based loops and quality gates across agent CLIs, rather than takt's YAML-defined workflow tasks.
| Project | Language | License | Stars | Status |
|---|---|---|---|---|
| TAKT | TypeScript | MIT | 1.4k | Active |
| aidlc-workflows | TypeScript | MIT-0 | 5.4k | Active |
| ralph-orchestrator | Rust | MIT | 3.2k | Active |
Considerations
TAKT requires Node.js >=22.22.0 and Git >=2.38. SDK-based providers require a separate takt install <provider> step, while CLI-based providers require their external CLI; using the tool also depends on the selected provider's credentials and terms. The project is actively changing, with frequent recent commits and merged pull requests, but it has had no release in the past year and contribution activity is concentrated in one person. Its MIT license permits broad use, subject to the license terms.
Found this useful?
Share it with someone who would like TAKT.