takt 0.2.2 → 0.3.0

package/README.md

@@ -11,6 +11,7 @@ TAKT is built with TAKT (dogfooding).
 ## Requirements
 
 - [Claude Code](https://docs.anthropic.com/en/docs/claude-code) or Codex must be installed and configured
+- [GitHub CLI](https://cli.github.com/) (`gh`) — required only for `takt "#N"` (GitHub Issue execution)
 
 TAKT supports both Claude Code and Codex as providers; you can choose the provider during setup.
 
@@ -23,9 +24,12 @@ npm install -g takt
 ## Quick Start
 
 ```bash
-# Run a task (will prompt for workflow selection and optional worktree creation)
+# Run a task (will prompt for workflow selection and optional isolated clone)
 takt "Add a login feature"
 
+# Run a GitHub issue as a task
+takt "#6"
+
 # Add a task to the queue
 takt /add-task "Fix the login bug"
 
@@ -35,95 +39,180 @@ takt /run-tasks
 # Watch for tasks and auto-execute
 takt /watch
 
-# Review worktree results (merge or delete)
-takt /review-tasks
+# List task branches (merge or delete)
+takt /list-tasks
 
 # Switch workflow
 takt /switch
 ```
 
+### What happens when you run a task
+
+When you run `takt "Add a login feature"`, TAKT guides you through an interactive flow:
+
+**1. Workflow selection**
+
+```
+Select workflow:
+  (↑↓ to move, Enter to select)
+
+  ❯ default (current) (default)
+    expert
+    expert-cqrs
+    magi
+    research
+    simple
+    Cancel
+```
+
+**2. Isolated clone** (optional)
+
+```
+? Create worktree? (y/N)
+```
+
+Choose `y` to run in a `git clone --shared` isolated environment, keeping your working directory clean.
+
+**3. Execution** — The selected workflow orchestrates multiple agents to complete the task.
+
+### Recommended workflows
+
+| Workflow | Best for |
+|----------|----------|
+| `default` | Full development tasks. Used for TAKT's own development. Multi-stage review with parallel architect + security review. |
+| `simple` | Lightweight tasks like README updates or small fixes. Reviews without fix loops. |
+| `expert` / `expert-cqrs` | Web development projects. Sequential multi-expert review with fix loops (`expert`: Architecture, Frontend, Security, QA; `expert-cqrs`: CQRS+ES, Frontend, Security, QA). |
+| `research` | Research and investigation. Autonomous research without asking questions. |
+| `magi` | Fun deliberation. Three AI personas analyze and vote (Evangelion-inspired). |
+
 ## Commands
 
 | Command | Alias | Description |
 |---------|-------|-------------|
-| `takt "task"` | | Execute task with current workflow (continues session) |
-| `takt -r "task"` | | Execute task, resuming previous session |
+| `takt "task"` | | Execute task with current workflow (session auto-continued) |
+| `takt "#N"` | | Execute GitHub issue #N as a task |
 | `takt /run-tasks` | `/run` | Run all pending tasks from `.takt/tasks/` |
 | `takt /watch` | | Watch `.takt/tasks/` and auto-execute tasks (stays resident) |
 | `takt /add-task` | `/add` | Add a new task interactively (YAML format, multiline supported) |
-| `takt /review-tasks` | `/review` | Review worktree task results (try merge, merge & cleanup, or delete) |
-| `takt /switch` | | Switch workflow interactively |
+| `takt /list-tasks` | `/list` | List task branches (try merge, merge & cleanup, or delete) |
+| `takt /switch` | `/sw` | Switch workflow interactively |
 | `takt /clear` | | Clear agent conversation sessions |
+| `takt /eject` | | Copy builtin workflow/agents to `~/.takt/` for customization |
 | `takt /refresh-builtin` | | Update builtin agents/workflows to latest version |
-| `takt /config` | | Display current configuration |
+| `takt /config` | | Configure permission mode |
 | `takt /help` | | Show help |
 
 ## Workflows
 
-TAKT uses YAML-based workflow definitions. Place them in:
-- `~/.takt/workflows/*.yaml`
+TAKT uses YAML-based workflow definitions with rule-based routing. Builtin workflows are embedded in the package; user workflows in `~/.takt/workflows/` take priority. Use `/eject` to copy a builtin to `~/.takt/` for customization.
 
 ### Example Workflow
 
 ```yaml
 name: default
 max_iterations: 10
+initial_step: plan
 
 steps:
   - name: plan
-    agent: planner
-    provider: claude         # Optional: claude or codex
-    model: opus              # Claude: opus/sonnet/haiku, Codex: gpt-5.2-codex/gpt-5.1-codex
+    agent: ../agents/default/planner.md
+    model: opus
+    edit: false
+    rules:
+      - condition: Plan complete
+        next: implement
     instruction_template: |
-      {task}
-    transitions:
-      - condition: done
-        next_step: implement
+      Analyze the request and create an implementation plan.
 
   - name: implement
-    agent: coder
-    provider: codex
-    model: gpt-5.2-codex     # Codex model example
+    agent: ../agents/default/coder.md
+    edit: true
+    permission_mode: acceptEdits
+    rules:
+      - condition: Implementation complete
+        next: review
+      - condition: Cannot proceed
+        next: ABORT
     instruction_template: |
-      {task}
-    transitions:
-      - condition: done
-        next_step: review
-      - condition: blocked
-        next_step: ABORT
+      Implement based on the plan.
 
   - name: review
-    agent: architect
-    model: sonnet            # Model alias (no provider = uses global default)
-    transitions:
-      - condition: approved
-        next_step: COMPLETE
-      - condition: rejected
-        next_step: implement
+    agent: ../agents/default/architecture-reviewer.md
+    edit: false
+    rules:
+      - condition: Approved
+        next: COMPLETE
+      - condition: Needs fix
+        next: implement
+    instruction_template: |
+      Review the implementation for architecture and code quality.
 ```
 
+### Parallel Steps
+
+Steps can execute sub-steps concurrently with aggregate evaluation:
+
+```yaml
+  - name: reviewers
+    parallel:
+      - name: arch-review
+        agent: ../agents/default/architecture-reviewer.md
+        rules:
+          - condition: approved
+          - condition: needs_fix
+        instruction_template: |
+          Review architecture and code quality.
+      - name: security-review
+        agent: ../agents/default/security-reviewer.md
+        rules:
+          - condition: approved
+          - condition: needs_fix
+        instruction_template: |
+          Review for security vulnerabilities.
+    rules:
+      - condition: all("approved")
+        next: supervise
+      - condition: any("needs_fix")
+        next: fix
+```
+
+- `all("X")`: true if ALL sub-steps matched condition X
+- `any("X")`: true if ANY sub-step matched condition X
+- Sub-step `rules` define possible outcomes; `next` is optional (parent handles routing)
+
+### Rule Condition Types
+
+| Type | Syntax | Description |
+|------|--------|-------------|
+| Tag-based | `"condition text"` | Agent outputs `[STEP:N]` tag, matched by index |
+| AI judge | `ai("condition text")` | AI evaluates the condition against agent output |
+| Aggregate | `all("X")` / `any("X")` | Aggregates parallel sub-step results |
+
 ## Built-in Workflows
 
 TAKT ships with several built-in workflows:
 
 | Workflow | Description |
 |----------|-------------|
-| `default` | Full development workflow: plan → implement → architect review → AI review → security review → supervisor approval. Includes fix loops for each review stage. |
+| `default` | Full development workflow: plan → implement → AI review → parallel reviewers (architect + security) → supervisor approval. Includes fix loops for each review stage. |
 | `simple` | Simplified version of default: plan → implement → architect review → AI review → supervisor. No intermediate fix steps. |
 | `research` | Research workflow: planner → digger → supervisor. Autonomously researches topics without asking questions. |
-| `expert-review` | Comprehensive review with domain experts: CQRS+ES, Frontend, AI, Security, QA reviews with fix loops. |
+| `expert` | Sequential review with domain experts: Architecture, Frontend, Security, QA reviews with fix loops. |
+| `expert-cqrs` | Sequential review with domain experts: CQRS+ES, Frontend, Security, QA reviews with fix loops. |
 | `magi` | Deliberation system inspired by Evangelion. Three AI personas (MELCHIOR, BALTHASAR, CASPER) analyze and vote. |
 
 Switch between workflows with `takt /switch`.
 
 ## Built-in Agents
 
-- **coder** - Implements features and fixes bugs
-- **architect** - Reviews code and provides feedback
-- **supervisor** - Final verification and approval
-- **planner** - Task analysis and implementation planning
-- **ai-reviewer** - AI-generated code quality review
-- **security** - Security vulnerability assessment
+| Agent | Description |
+|-------|-------------|
+| **planner** | Task analysis, spec investigation, and implementation planning |
+| **coder** | Implements features and fixes bugs |
+| **ai-antipattern-reviewer** | Reviews for AI-specific anti-patterns (hallucinated APIs, incorrect assumptions, scope creep) |
+| **architecture-reviewer** | Reviews architecture and code quality, verifies spec compliance |
+| **security-reviewer** | Security vulnerability assessment |
+| **supervisor** | Final verification, validation, and approval |
 
 ## Custom Agents
 
@@ -136,63 +225,54 @@ agents:
     allowed_tools: [Read, Glob, Grep]
     provider: claude             # Optional: claude or codex
     model: opus                  # Claude: opus/sonnet/haiku or full name (claude-opus-4-5-20251101)
-    status_patterns:
-      approved: "\\[APPROVE\\]"
-      rejected: "\\[REJECT\\]"
-
-  - name: my-codex-agent
-    prompt_file: .takt/prompts/analyzer.md
-    provider: codex
-    model: gpt-5.2-codex         # Codex: gpt-5.2-codex, gpt-5.1-codex, etc.
 ```
 
-## Model Selection
+Or create agent prompt files as Markdown:
+
+```markdown
+# ~/.takt/agents/my-agents/reviewer.md
 
-### Claude Models
+You are a code reviewer focused on security.
+
+## Your Role
+- Check for security vulnerabilities
+- Verify input validation
+- Review authentication logic
+```
+
+## Model Selection
 
-You can specify models using either **aliases** or **full model names**:
+The `model` field in workflow steps, agent configs, and global config is passed directly to the provider (Claude Code CLI or Codex SDK). TAKT does not resolve model aliases — the provider handles that.
 
-**Aliases** (recommended for simplicity):
-- `opus` - Claude Opus 4.5 (highest reasoning capability)
-- `sonnet` - Claude Sonnet 4.5 (balanced, best for most tasks)
-- `haiku` - Claude Haiku 4.5 (fast and efficient)
-- `opusplan` - Opus for planning, Sonnet for execution
-- `default` - Recommended model for your account type
+### Claude Code
 
-**Full model names** (recommended for production):
-- `claude-opus-4-5-20251101`
-- `claude-sonnet-4-5-20250929`
-- `claude-haiku-4-5-20250101`
+Claude Code supports aliases (`opus`, `sonnet`, `haiku`, `opusplan`, `default`) and full model names (e.g., `claude-sonnet-4-5-20250929`). See [Claude Code documentation](https://docs.anthropic.com/en/docs/claude-code) for available models.
 
-### Codex Models
+### Codex
 
-Available Codex models:
-- `gpt-5.2-codex` - Latest agentic coding model (default)
-- `gpt-5.1-codex` - Previous generation
-- `gpt-5.1-codex-max` - Optimized for long-running tasks
-- `gpt-5.1-codex-mini` - Smaller, cost-effective version
-- `codex-1` - Specialized model aligned with coding preferences
+The model string is passed to the Codex SDK. Defaults to `codex` if not specified. See Codex documentation for available models.
 
 ## Project Structure
 
 ```
 ~/.takt/
 ├── config.yaml          # Global config (provider, model, workflows, etc.)
-├── workflows/           # Workflow definitions
-└── agents/              # Agent prompt files
+├── workflows/           # User workflow definitions (override builtins)
+└── agents/              # User agent prompt files
 
 .takt/                   # Project-level config
 ├── agents.yaml          # Custom agent definitions
 ├── tasks/               # Pending task files (.yaml, .md)
 ├── completed/           # Completed tasks with reports
-├── worktrees/           # Git worktrees for isolated task execution
 ├── reports/             # Execution reports (auto-generated)
-└── logs/                # Session logs (incremental)
+└── logs/                # Session logs in NDJSON format
     ├── latest.json      # Pointer to current/latest session
     ├── previous.json    # Pointer to previous session
-    └── {sessionId}.json # Full session log per workflow run
+    └── {sessionId}.jsonl # NDJSON session log per workflow run
 ```
 
+Builtin resources are embedded in the npm package (`dist/resources/`). User files in `~/.takt/` take priority.
+
 ### Global Configuration
 
 Configure default provider and model in `~/.takt/config.yaml`:
@@ -217,92 +297,70 @@ trusted_directories:
 
 ## Practical Usage Guide
 
-### Resuming Sessions with `-r`
-
-When TAKT prompts for additional input during execution (e.g., "Please provide more details"), use the `-r` flag to continue the conversation:
-
-```bash
-# First run - agent might ask for clarification
-takt "Fix the login bug"
-
-# Resume the same session to provide the requested information
-takt -r "The bug occurs when the password contains special characters"
-```
-
-The `-r` flag preserves the agent's conversation history, allowing for natural back-and-forth interaction.
-
 ### Interactive Workflow
 
 When running `takt "task"`, you are prompted to:
 
 1. **Select a workflow** - Choose from available workflows (arrow keys, ESC to cancel)
-2. **Create a worktree** (optional) - Optionally run the task in an isolated git worktree
+2. **Create an isolated clone** (optional) - Optionally run the task in a `git clone --shared` for isolation
 
 This interactive flow ensures each task runs with the right workflow and isolation level.
 
 ### Adding Custom Workflows
 
-Create your own workflow by adding YAML files to `~/.takt/workflows/`:
+Create your own workflow by adding YAML files to `~/.takt/workflows/`, or use `/eject` to customize a builtin:
+
+```bash
+# Copy the default workflow to ~/.takt/workflows/ for editing
+takt /eject default
+```
 
 ```yaml
 # ~/.takt/workflows/my-workflow.yaml
 name: my-workflow
 description: My custom workflow
-
 max_iterations: 5
+initial_step: analyze
 
 steps:
   - name: analyze
     agent: ~/.takt/agents/my-agents/analyzer.md
+    edit: false
+    rules:
+      - condition: Analysis complete
+        next: implement
     instruction_template: |
-      Analyze this request: {task}
-    transitions:
-      - condition: done
-        next_step: implement
+      Analyze this request thoroughly.
 
   - name: implement
     agent: ~/.takt/agents/default/coder.md
-    instruction_template: |
-      Implement based on the analysis: {previous_response}
+    edit: true
+    permission_mode: acceptEdits
     pass_previous_response: true
-    transitions:
-      - condition: done
-        next_step: COMPLETE
+    rules:
+      - condition: Done
+        next: COMPLETE
+    instruction_template: |
+      Implement based on the analysis.
 ```
 
+> **Note**: `{task}`, `{previous_response}`, and `{user_inputs}` are auto-injected into instructions. You only need explicit placeholders if you want to control their position in the template.
+
 ### Specifying Agents by Path
 
 Agents are specified using file paths in workflow definitions:
 
 ```yaml
-# Use built-in agents
-agent: ~/.takt/agents/default/coder.md
-agent: ~/.takt/agents/magi/melchior.md
+# Relative to workflow file directory
+agent: ../agents/default/coder.md
 
-# Use project-local agents
-agent: ./.takt/agents/my-reviewer.md
+# Home directory
+agent: ~/.takt/agents/default/coder.md
 
-# Use absolute paths
+# Absolute paths
 agent: /path/to/custom/agent.md
 ```
 
-Create custom agent prompts as Markdown files:
-
-```markdown
-# ~/.takt/agents/my-agents/reviewer.md
-
-You are a code reviewer focused on security.
-
-## Your Role
-- Check for security vulnerabilities
-- Verify input validation
-- Review authentication logic
-
-## Output Format
-- [REVIEWER:APPROVE] if code is secure
-- [REVIEWER:REJECT] if issues found (list them)
-```
-
 ### Task Management
 
 TAKT supports batch task processing through task files in `.takt/tasks/`. Both `.yaml`/`.yml` and `.md` file formats are supported.
@@ -310,10 +368,13 @@ TAKT supports batch task processing through task files in `.takt/tasks/`. Both `
 #### Adding Tasks with `/add-task`
 
 ```bash
-# Quick add (no worktree)
+# Quick add (no isolation)
 takt /add-task "Add authentication feature"
 
-# Interactive mode (prompts for worktree, branch, workflow options)
+# Add a GitHub issue as a task
+takt /add-task "#6"
+
+# Interactive mode (prompts for isolation, branch, workflow options)
 takt /add-task
 ```
 
@@ -324,7 +385,7 @@ takt /add-task
 ```yaml
 # .takt/tasks/add-auth.yaml
 task: "Add authentication feature"
-worktree: true                  # Run in isolated git worktree
+worktree: true                  # Run in isolated shared clone
 branch: "feat/add-auth"         # Branch name (auto-generated if omitted)
 workflow: "default"             # Workflow override (uses current if omitted)
 ```
@@ -342,16 +403,18 @@ Requirements:
 - Error handling for failed attempts
 ```
 
-#### Git Worktree Isolation
+#### Isolated Execution (Shared Clone)
 
-YAML task files can specify `worktree` to run each task in an isolated git worktree, keeping the main working directory clean:
+YAML task files can specify `worktree` to run each task in an isolated `git clone --shared`, keeping the main working directory clean:
 
-- `worktree: true` - Auto-create at `.takt/worktrees/{timestamp}-{task-slug}/`
+- `worktree: true` - Auto-create a shared clone in a sibling directory (or `worktree_dir` from config)
 - `worktree: "/path/to/dir"` - Create at specified path
 - `branch: "feat/xxx"` - Use specified branch (auto-generated as `takt/{timestamp}-{slug}` if omitted)
 - Omit `worktree` - Run in current working directory (default)
 
-When a worktree task completes successfully, TAKT automatically commits all changes (`auto-commit`). Use `takt /review-tasks` to review, try-merge, or delete completed worktree branches.
+> **Note**: The YAML field is named `worktree` for backward compatibility. Internally, `git clone --shared` is used instead of `git worktree` because git worktrees have a `.git` file with `gitdir:` that points back to the main repository, causing Claude Code to recognize the main repo as the project root. Shared clones have an independent `.git` directory that avoids this issue.
+
+Clones are ephemeral. When a task completes successfully, TAKT automatically commits all changes and pushes the branch to the main repository, then deletes the clone. Use `takt /list-tasks` to list, try-merge, or delete task branches.
 
 #### Running Tasks with `/run-tasks`
 
@@ -374,26 +437,29 @@ Watch mode polls `.takt/tasks/` for new task files and auto-executes them as the
 - Automated workflows where tasks are added by external processes
 - Long-running development sessions where tasks are queued over time
 
-#### Reviewing Worktree Results with `/review-tasks`
+#### Listing Task Branches with `/list-tasks`
 
 ```bash
-takt /review-tasks
+takt /list-tasks
 ```
 
-Lists all `takt/`-prefixed worktree branches with file change counts. For each branch you can:
-- **Try merge** - Attempt merge into main (dry-run check, then actual merge)
-- **Merge & cleanup** - Merge and remove the worktree
-- **Delete** - Remove the worktree and branch without merging
+Lists all `takt/`-prefixed branches with file change counts. For each branch you can:
+- **Try merge** - Squash merge into main (stage changes without committing)
+- **Instruct** - Give additional instructions via a temporary clone
+- **Merge & cleanup** - Merge and delete the branch
+- **Delete** - Delete the branch without merging
 
 ### Session Logs
 
-TAKT writes session logs incrementally to `.takt/logs/`. Logs are saved at workflow start, after each step, and at workflow end — so even if the process crashes mid-execution, partial logs are preserved.
+TAKT writes session logs in NDJSON (`.jsonl`) format to `.takt/logs/`. Each record is appended atomically, so even if the process crashes mid-execution, partial logs are preserved and logs can be tailed in real-time with `tail -f`.
 
 - `.takt/logs/latest.json` - Pointer to the current (or most recent) session
 - `.takt/logs/previous.json` - Pointer to the previous session
-- `.takt/logs/{sessionId}.json` - Full session log with step history
+- `.takt/logs/{sessionId}.jsonl` - NDJSON session log with step history
+
+Record types: `workflow_start`, `step_start`, `step_complete`, `workflow_complete`, `workflow_abort`.
 
-Agents can read `previous.json` to pick up context from a prior run (e.g., when resuming with `takt "続けて"`).
+Agents can read `previous.json` to pick up context from a prior run. Session continuity is automatic — simply run `takt "task"` to continue where the previous session left off.
 
 ### Workflow Variables
 
@@ -401,58 +467,49 @@ Available variables in `instruction_template`:
 
 | Variable | Description |
 |----------|-------------|
-| `{task}` | Original user request |
+| `{task}` | Original user request (auto-injected if not in template) |
 | `{iteration}` | Workflow-wide turn count (total steps executed) |
 | `{max_iterations}` | Maximum iterations allowed |
 | `{step_iteration}` | Per-step iteration count (how many times THIS step has run) |
-| `{previous_response}` | Previous step's output (requires `pass_previous_response: true`) |
-| `{user_inputs}` | Additional user inputs during workflow |
-| `{git_diff}` | Current git diff (uncommitted changes) |
-| `{report_dir}` | Report directory name (e.g., `20250126-143052-task-summary`) |
+| `{previous_response}` | Previous step's output (auto-injected if not in template) |
+| `{user_inputs}` | Additional user inputs during workflow (auto-injected if not in template) |
+| `{report_dir}` | Report directory path (e.g., `.takt/reports/20250126-143052-task-summary`) |
+| `{report:filename}` | Resolves to `{report_dir}/filename` (e.g., `{report:00-plan.md}`) |
 
 ### Designing Workflows
 
-Each workflow step requires three key elements:
+Each workflow step requires:
 
 **1. Agent** - A Markdown file containing the system prompt:
 
 ```yaml
-agent: ~/.takt/agents/default/coder.md    # Path to agent prompt file
-agent_name: coder                          # Display name (optional)
-```
-
-**2. Status Rules** - Define how the agent signals completion. Agents output status markers like `[CODER:DONE]` or `[ARCHITECT:REJECT]` that TAKT detects to drive transitions:
-
-```yaml
-status_rules_prompt: |
-  Your final output MUST include a status tag:
-  - `[CODER:DONE]` if implementation is complete
-  - `[CODER:BLOCKED]` if you cannot proceed
+agent: ../agents/default/coder.md    # Path to agent prompt file
+agent_name: coder                    # Display name (optional)
 ```
 
-**3. Transitions** - Route to the next step based on status:
+**2. Rules** - Define how the step routes to the next step. The instruction builder auto-injects status output rules so agents know what tags to output:
 
 ```yaml
-transitions:
-  - condition: done        # Maps to status tag DONE
-    next_step: review      # Go to review step
-  - condition: blocked     # Maps to status tag BLOCKED
-    next_step: ABORT       # End workflow with failure
+rules:
+  - condition: "Implementation complete"
+    next: review
+  - condition: "Cannot proceed"
+    next: ABORT
 ```
 
-Available transition conditions: `done`, `blocked`, `approved`, `rejected`, `improve`, `answer`, `always`.
-Special next_step values: `COMPLETE` (success), `ABORT` (failure).
+Special `next` values: `COMPLETE` (success), `ABORT` (failure).
 
-**Step options:**
+**3. Step options:**
 
 | Option | Default | Description |
 |--------|---------|-------------|
+| `edit` | - | Whether the step can edit project files (`true`/`false`) |
 | `pass_previous_response` | `true` | Pass previous step's output to `{previous_response}` |
-| `on_no_status` | - | Behavior when no status is detected: `complete`, `continue`, `stay` |
 | `allowed_tools` | - | List of tools the agent can use (Read, Glob, Grep, Edit, Write, Bash, etc.) |
 | `provider` | - | Override provider for this step (`claude` or `codex`) |
 | `model` | - | Override model for this step |
 | `permission_mode` | `default` | Permission mode: `default`, `acceptEdits`, or `bypassPermissions` |
+| `report` | - | Report file configuration (name, format) for auto-generated reports |
 
 ## API Usage
 

package/dist/agents/runner.d.ts

@@ -14,8 +14,8 @@ export interface RunAgentOptions {
     agentPath?: string;
     /** Allowed tools for this agent run */
     allowedTools?: string[];
-    /** Status output rules to inject into system prompt */
-    statusRulesPrompt?: string;
+    /** Maximum number of agentic turns */
+    maxTurns?: number;
     /** Permission mode for tool execution (from workflow step) */
     permissionMode?: PermissionMode;
     onStream?: StreamCallback;
@@ -24,8 +24,6 @@ export interface RunAgentOptions {
     /** Bypass all permission checks (sacrifice-my-pc mode) */
     bypassPermissions?: boolean;
 }
-/** Get git diff for review context */
-export declare function getGitDiff(cwd: string): string;
 /** Run a custom agent */
 export declare function runCustomAgent(agentConfig: CustomAgentConfig, task: string, options: RunAgentOptions): Promise<AgentResponse>;
 /** Run an agent by name or path */

package/dist/agents/runner.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"runner.d.ts","sourceRoot":"","sources":["../../src/agents/runner.ts"],"names":[],"mappings":"AAAA;;GAEG;AAUH,OAAO,EAAE,KAAK,cAAc,EAAE,KAAK,iBAAiB,EAAE,KAAK,sBAAsB,EAAE,MAAM,sBAAsB,CAAC;AAKhH,OAAO,KAAK,EAAE,aAAa,EAAE,iBAAiB,EAAE,cAAc,EAAE,MAAM,oBAAoB,CAAC;AAK3F,YAAY,EAAE,cAAc,EAAE,CAAC;AAE/B,wCAAwC;AACxC,MAAM,WAAW,eAAe;IAC9B,GAAG,EAAE,MAAM,CAAC;IACZ,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,QAAQ,CAAC,EAAE,QAAQ,GAAG,OAAO,GAAG,MAAM,CAAC;IACvC,yCAAyC;IACzC,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,uCAAuC;IACvC,YAAY,CAAC,EAAE,MAAM,EAAE,CAAC;IACxB,uDAAuD;IACvD,iBAAiB,CAAC,EAAE,MAAM,CAAC;IAC3B,8DAA8D;IAC9D,cAAc,CAAC,EAAE,cAAc,CAAC;IAChC,QAAQ,CAAC,EAAE,cAAc,CAAC;IAC1B,mBAAmB,CAAC,EAAE,iBAAiB,CAAC;IACxC,iBAAiB,CAAC,EAAE,sBAAsB,CAAC;IAC3C,0DAA0D;IAC1D,iBAAiB,CAAC,EAAE,OAAO,CAAC;CAC7B;AA6BD,sCAAsC;AACtC,wBAAgB,UAAU,CAAC,GAAG,EAAE,MAAM,GAAG,MAAM,CAoB9C;AAED,yBAAyB;AACzB,wBAAsB,cAAc,CAClC,WAAW,EAAE,iBAAiB,EAC9B,IAAI,EAAE,MAAM,EACZ,OAAO,EAAE,eAAe,GACvB,OAAO,CAAC,aAAa,CAAC,CA4DxB;AAqCD,mCAAmC;AACnC,wBAAsB,QAAQ,CAC5B,SAAS,EAAE,MAAM,EACjB,IAAI,EAAE,MAAM,EACZ,OAAO,EAAE,eAAe,GACvB,OAAO,CAAC,aAAa,CAAC,CAoDxB"}
+{"version":3,"file":"runner.d.ts","sourceRoot":"","sources":["../../src/agents/runner.ts"],"names":[],"mappings":"AAAA;;GAEG;AASH,OAAO,EAAE,KAAK,cAAc,EAAE,KAAK,iBAAiB,EAAE,KAAK,sBAAsB,EAAE,MAAM,sBAAsB,CAAC;AAKhH,OAAO,KAAK,EAAE,aAAa,EAAE,iBAAiB,EAAE,cAAc,EAAE,MAAM,oBAAoB,CAAC;AAK3F,YAAY,EAAE,cAAc,EAAE,CAAC;AAE/B,wCAAwC;AACxC,MAAM,WAAW,eAAe;IAC9B,GAAG,EAAE,MAAM,CAAC;IACZ,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,QAAQ,CAAC,EAAE,QAAQ,GAAG,OAAO,GAAG,MAAM,CAAC;IACvC,yCAAyC;IACzC,SAAS,CAAC,EAAE,MAAM,CAAC;IACnB,uCAAuC;IACvC,YAAY,CAAC,EAAE,MAAM,EAAE,CAAC;IACxB,sCAAsC;IACtC,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB,8DAA8D;IAC9D,cAAc,CAAC,EAAE,cAAc,CAAC;IAChC,QAAQ,CAAC,EAAE,cAAc,CAAC;IAC1B,mBAAmB,CAAC,EAAE,iBAAiB,CAAC;IACxC,iBAAiB,CAAC,EAAE,sBAAsB,CAAC;IAC3C,0DAA0D;IAC1D,iBAAiB,CAAC,EAAE,OAAO,CAAC;CAC7B;AA8BD,yBAAyB;AACzB,wBAAsB,cAAc,CAClC,WAAW,EAAE,iBAAiB,EAC9B,IAAI,EAAE,MAAM,EACZ,OAAO,EAAE,eAAe,GACvB,OAAO,CAAC,aAAa,CAAC,CAyDxB;AAqCD,mCAAmC;AACnC,wBAAsB,QAAQ,CAC5B,SAAS,EAAE,MAAM,EACjB,IAAI,EAAE,MAAM,EACZ,OAAO,EAAE,eAAe,GACvB,OAAO,CAAC,aAAa,CAAC,CAgDxB"}