This document provides a complete reference for all TAKT CLI commands and options.
| Option | Description |
|---|---|
--pipeline |
Enable pipeline (non-interactive) mode -- required for CI/automation |
-t, --task <text> |
Task content (alternative to GitHub Issue) |
-i, --issue <N> |
GitHub issue number (same as #N in interactive mode) |
-w, --workflow <name or path> |
Workflow name or path to workflow YAML file |
-b, --branch <name> |
Specify branch name (auto-generated if omitted) |
--pr <number> |
PR number to fetch review comments and fix |
--auto-pr |
Create PR after execution (pipeline mode only) |
--draft |
Create PR as draft (requires --auto-pr or auto_pr config) |
--skip-git |
Skip branch creation, commit, and push (pipeline mode, workflow-only) |
--repo <owner/repo> |
Specify repository (for PR creation) |
-q, --quiet |
Minimal output mode: suppress AI output (for CI) |
--provider <name> |
Override agent provider (claude-sdk|claude|codex|opencode|cursor|copilot|mock) |
--model <name> |
Override agent model |
--config <path> |
Path to global config file (default: ~/.takt/config.yaml) |
--workflow is the canonical option.
A mode where you refine task content through conversation with AI before execution. Useful when task requirements are ambiguous or when you want to clarify content while consulting with AI.
# Start interactive mode (no arguments)
takt
# Specify initial message (short word only)
takt helloNote: --task option skips interactive mode and executes the task directly. Issue references (#6, --issue) are used as initial input in interactive mode.
- Select workflow
- Select interactive mode (assistant / persona / quiet / passthrough)
- Refine task content through conversation with AI
- Finalize task instructions with
/go(you can also add additional instructions like/go additional instructions), or use/play <task>to execute a task immediately - Execute (run workflow, create PR)
| Mode | Description |
|---|---|
assistant |
Default. AI asks clarifying questions before generating task instructions. |
persona |
Conversation with the first step's persona (uses its system prompt and tools). |
quiet |
Generates task instructions without asking questions (best-effort). |
passthrough |
Passes user input directly as task text without AI processing. |
Workflows can set a default mode via the interactive_mode field in YAML.
$ takt
Select workflow:
> default (current)
Development/
Research/
Cancel
Interactive mode - Enter task content. Commands: /go (execute), /cancel (exit)
> I want to add user authentication feature
[AI confirms and organizes requirements]
> /go
Proposed task instructions:
---
Implement user authentication feature.
Requirements:
- Login with email address and password
- JWT token-based authentication
- Password hashing (bcrypt)
- Login/logout API endpoints
---
Proceed with these task instructions? (Y/n) y
[Workflow execution starts...]
Use the --task option to skip interactive mode and execute directly.
# Specify task content with --task option
takt --task "Fix bug"
# Specify workflow
takt --task "Add authentication" --workflow dualNote: Passing a string as an argument (e.g., takt "Add login feature") enters interactive mode with it as the initial message.
You can execute GitHub Issues directly as tasks. Issue title, body, labels, and comments are automatically incorporated as task content.
# Execute by specifying issue number
takt #6
takt --issue 6
# Issue + workflow specification
takt #6 --workflow dualRequirements: GitHub CLI (gh) must be installed and authenticated.
Batch processing using .takt/tasks.yaml with task directories under .takt/tasks/{slug}/. Useful for accumulating multiple tasks and executing them together later.
Refine task requirements through AI conversation, then add a task to .takt/tasks.yaml.
# Refine task requirements through AI conversation, then add task
takt add
# Add task from GitHub Issue (issue number reflected in branch name)
takt add #28Execute all pending tasks from .takt/tasks.yaml.
# Execute all pending tasks in .takt/tasks.yaml
takt run
# Ignore workflow max_steps and continue until another stop condition occurs
takt run --ignore-exceedWithout --ignore-exceed, a task that reaches workflow max_steps stops with exceeded status and persists retry metadata in .takt/tasks.yaml. With --ignore-exceed, takt run ignores only that iteration limit, continues execution, and does not write exceeded retry metadata.
Monitor .takt/tasks.yaml and auto-execute tasks as a resident process.
# Monitor .takt/tasks.yaml and auto-execute tasks (resident process)
takt watchList task branches and perform actions (merge, delete, merge from root, etc.).
# List task branches (merge/delete)
takt list
# Non-interactive mode (for CI/scripts)
takt list --non-interactive
takt list --non-interactive --action diff --branch takt/my-branch
takt list --non-interactive --action delete --branch takt/my-branch --yes
takt list --non-interactive --format jsonIn interactive mode, Merge from root merges the root repository HEAD into the worktree branch with AI-assisted conflict resolution.
- Run
takt addand confirm a pending record is created in.takt/tasks.yaml. - Open the generated
.takt/tasks/{slug}/order.mdand add detailed specifications/references as needed. - Run
takt run(ortakt watch) to execute pending tasks fromtasks.yaml. - Verify outputs in
.takt/runs/{slug}/reports/using the same slug astask_dir.
Specifying --pipeline enables non-interactive pipeline mode. Automatically creates branch, runs the workflow, commits and pushes. Suitable for CI/CD automation.
# Execute task in pipeline mode
takt --pipeline --task "Fix bug"
# Pipeline execution + auto-create PR
takt --pipeline --task "Fix bug" --auto-pr
# Link issue information
takt --pipeline --issue 99 --auto-pr
# Specify workflow and branch
takt --pipeline --task "Fix bug" -w magi -b feat/fix-bug
# Specify repository (for PR creation)
takt --pipeline --task "Fix bug" --auto-pr --repo owner/repo
# Workflow execution only (skip branch creation, commit, push)
takt --pipeline --task "Fix bug" --skip-git
# Minimal output mode (for CI)
takt --pipeline --task "Fix bug" --quietIn pipeline mode, PRs are not created unless --auto-pr is specified.
GitHub Integration: When using TAKT in GitHub Actions, see takt-action. You can automate PR reviews and task execution.
Run takt without a task argument to choose a workflow interactively.
taktCopy builtin workflows/personas to your local directory for customization.
# Copy builtin workflows/personas to project .takt/ for customization
takt eject
# Copy to ~/.takt/ (global) instead
takt eject --global
# Eject a specific facet for customization
takt eject persona coder
takt eject instruction plan --globalBuiltin and custom workflow lookup uses workflows/.
Initialize and validate custom workflow definitions.
# Create a minimal workflow scaffold in project .takt/workflows/
takt workflow init sample-flow
# Create a faceted scaffold in ~/.takt/workflows/
takt workflow init review-flow --template faceted --global
# Validate workflows by name or path
takt workflow doctor sample-flow
takt workflow doctor .takt/workflows/sample-flow.yamlClear agent conversation sessions (reset state).
takt clearDeploy builtin workflows/personas as a Claude Code Skill.
takt export-ccDeploy TAKT skill files as a Codex Skill (~/.agents/skills/takt/).
This command deploys SKILL.md, references/, agents/, workflows/, and facets/.
takt export-codexList available facets across layers.
takt catalog
takt catalog personasPreview assembled prompts for each step and phase.
takt prompt [workflow]Reset settings to defaults.
# Reset global config to builtin template (with backup)
takt reset config
# Reset workflow categories to builtin defaults
takt reset categoriesShow analytics metrics.
# Show review quality metrics (default: last 30 days)
takt metrics review
# Specify time window
takt metrics review --since 7dManage repertoire packages (external TAKT packages from GitHub).
# Install a package from GitHub
takt repertoire add github:{owner}/{repo}@{ref}
# Install from default branch
takt repertoire add github:{owner}/{repo}
# List installed packages
takt repertoire list
# Remove a package
takt repertoire remove @{owner}/{repo}Installed packages are stored in ~/.takt/repertoire/ and their workflows/facets become available in workflow selection and facet resolution.
When the same workflow name exists in multiple locations, TAKT resolves in this order: .takt/workflows/ → ~/.takt/workflows/ → builtins.
Purge old analytics event files.
# Purge files older than 30 days (default)
takt purge
# Specify retention period
takt purge --retention-days 14