agent-cli 0.86.1__tar.gz → 0.88.0__tar.gz

{agent_cli-0.86.1/agent_cli/dev/skill → agent_cli-0.88.0/.claude/skills/agent-cli-dev}/SKILL.md

@@ -9,7 +9,7 @@ This skill teaches you how to spawn parallel AI coding agents in isolated git wo
 
 `agent-cli dev` supports two complementary patterns:
 - Separate worktrees for isolated implementation/review tasks
-- Multiple agents on the same worktree using `dev agent -m tmux`
+- Multiple agents on the same worktree using `dev agent --tmux-session <unique-name>` for autonomous launches, or `-m tmux` when a human explicitly wants shared tmux windows
 
 ## Installation
 
@@ -20,7 +20,7 @@ If `agent-cli` is not available, install it first:
 uv tool install agent-cli -p 3.13
 
 # Or run directly without installing
-uvx --python 3.13 agent-cli dev new <branch-name> --agent --prompt "..."
+uvx --python 3.13 agent-cli dev new <branch-name> --prompt "..."
 ```
 
 ## When to spawn parallel agents
@@ -40,17 +40,17 @@ Do NOT spawn when:
 
 For new features (starts from origin/main):
 ```bash
-agent-cli dev new <branch-name> --agent --prompt "Implement the new feature..."
+agent-cli dev new <branch-name> --prompt "Implement the new feature..."
 ```
 
 For work on current branch (review, test, fix) - use `--from HEAD`:
 ```bash
-agent-cli dev new <branch-name> --from HEAD --agent --prompt "Review/test/fix..."
+agent-cli dev new <branch-name> --from HEAD --prompt "Review/test/fix..."
 ```
 
 For longer prompts (recommended for multi-line or complex instructions):
 ```bash
-agent-cli dev new <branch-name> --from HEAD --agent --prompt-file path/to/prompt.md
+agent-cli dev new <branch-name> --from HEAD --prompt-file path/to/prompt.md
 ```
 
 This creates:
@@ -67,10 +67,10 @@ This creates:
 When an assistant is executing this workflow on the user's behalf, the spawn is not complete unless the agent receives a prompt at launch time.
 
 - Prefer `--prompt-file`; create the prompt file first, then launch the agent
-- Use `dev new ... --agent --prompt-file ...` for a new delegated task
+- Use `dev new ... --prompt-file ...` for a new delegated task
 - Use `dev agent ... --prompt-file ...` for another agent in an existing worktree
 - Do not stop after `dev new ...` alone if the user's intent was to delegate work immediately
-- Do not run `dev new ... --agent` or `dev agent ... -m tmux` without `--prompt` or `--prompt-file` unless the user explicitly wants an interactive session that they will drive manually
+- Do not run `dev new ... --start-agent`, `dev new ... --agent <name>`, or `dev agent ... -m tmux` without `--prompt` or `--prompt-file` unless the user explicitly wants an interactive session that they will drive manually
 
 ## Writing effective prompts for spawned agents
 
@@ -92,7 +92,7 @@ Example workflow:
 ```bash
 # 1. Write prompt to file
 # 2. Spawn agent with the file
-agent-cli dev new my-feature --agent --prompt-file .claude/spawn-prompt.md
+agent-cli dev new my-feature --prompt-file .claude/spawn-prompt.md
 # 3. Optionally clean up
 rm .claude/spawn-prompt.md
 ```
@@ -136,17 +136,26 @@ Use this when several agents should inspect or validate the same code at once wi
 # Create the worktree once. This step only prepares the shared workspace.
 agent-cli dev new review-auth --from HEAD
 
-# Then launch the actual agents with prompts.
-agent-cli dev agent review-auth -m tmux --prompt-file .claude/review-security.md
-agent-cli dev agent review-auth -m tmux --prompt-file .claude/review-performance.md
-agent-cli dev agent review-auth -m tmux --prompt-file .claude/review-tests.md
+# Then launch the actual agents with prompts. Give each agent its own tmux session.
+agent-cli dev agent review-auth \
+  --tmux-session review-auth-security-20260402-1530 \
+  --prompt-file .claude/review-security.md
+agent-cli dev agent review-auth \
+  --tmux-session review-auth-performance-20260402-1530 \
+  --prompt-file .claude/review-performance.md
+agent-cli dev agent review-auth \
+  --tmux-session review-auth-tests-20260402-1530 \
+  --prompt-file .claude/review-tests.md
 ```
 
 Key rules for same-worktree launches:
 - Use `dev agent`, not `dev new`, after the worktree already exists
-- Use `dev agent -a <agent>` to select a specific agent for an existing worktree; `--with-agent` remains a deprecated alias on this subcommand
-- Use `-m tmux` for headless or scripted launching; it works even when not already inside tmux
-- Each launch joins the same deterministic repo-scoped tmux session, so related agents stay grouped together
+- Use `dev agent --agent <agent>` to select a specific agent for an existing worktree; `--with-agent` remains a deprecated alias on this subcommand
+- For autonomous agents, prefer `--tmux-session <unique-name>` and use a different session name for each launch
+- Reserve bare `-m tmux` for human-driven grouped windows or when the user explicitly wants agents to share one tmux session
+- Outside tmux, bare `-m tmux` joins the deterministic repo-scoped tmux session
+- Inside tmux, bare `-m tmux` opens a new window in the current session unless you pass `--tmux-session <name>`, which reuses or creates a specific tmux session and also implies `-m tmux`
+- tmux session names cannot contain `.` or `:`
 - Ask each agent to write to a unique report path such as `.claude/REPORT-security-<run-id>.md` or `.claude/REPORT-tests-<run-id>.md`
 - If you rerun the same prompt repeatedly, include a timestamp or other run id in the report filename so later runs do not overwrite earlier ones
 - Each agent launch gets its own unique task file in `.claude/` (e.g., `TASK-{timestamp}-{hex}.md`), so parallel launches do not overwrite each other
@@ -168,14 +177,21 @@ When complete, write findings to .claude/REPORT-security-20260319-153045-123.md
 
 ## Headless/scripted orchestration
 
-For non-interactive contexts (scripts, cron jobs, other assistants), combine `--prompt-file` with `-m tmux`:
+For non-interactive contexts (scripts, cron jobs, other assistants), combine `--prompt-file` with `--tmux-session`:
 
 ```bash
-agent-cli dev new validation-a --from HEAD --agent --with-agent codex -m tmux \
+agent-cli dev new validation-a --from HEAD --agent codex \
+  --tmux-session validation-a-20260402-1530 \
   --prompt-file .claude/validation-a.md
 ```
 
-This works without an attached terminal. `agent-cli` creates or reuses a detached tmux session and returns a pane handle plus attach command. Launches may also run pre-launch preparation by default; use `--no-hooks` only when you explicitly need to bypass that behavior.
+This works without an attached terminal. For autonomous or scripted launches, prefer a unique `--tmux-session` per agent so separate runs do not trample each other by sharing one tmux session. Use bare `-m tmux` only when you explicitly want shared tmux grouping. Launches may also run pre-launch preparation by default; use `--no-hooks` only when you explicitly need to bypass that behavior.
+
+## Cleanup behavior
+
+- `dev rm` and `dev clean` also clean up tmux windows that `agent-cli` tagged for the worktree
+- If git worktree removal succeeds but tmux cleanup is partial, the command warns and still removes the worktree
+- Session isolation prevents agents from interfering with each other's tmux windows during execution, but cleanup still applies to all tagged windows for the worktree
 
 ## Example: Multi-feature implementation
 
@@ -183,9 +199,9 @@ If asked to implement auth, payments, and notifications:
 
 ```bash
 # Spawn three parallel agents
-agent-cli dev new auth-feature --agent --prompt "Implement JWT authentication..."
-agent-cli dev new payment-integration --agent --prompt "Add Stripe payment processing..."
-agent-cli dev new email-notifications --agent --prompt "Implement email notification system..."
+agent-cli dev new auth-feature --prompt "Implement JWT authentication..."
+agent-cli dev new payment-integration --prompt "Add Stripe payment processing..."
+agent-cli dev new email-notifications --prompt "Implement email notification system..."
 ```
 
 Each agent works independently in its own branch. Results can be reviewed and merged separately.
@@ -194,11 +210,12 @@ Each agent works independently in its own branch. Results can be reviewed and me
 
 | Option | Description |
 |--------|-------------|
-| `--agent` / `-a` | Start AI coding agent after creation |
+| `--start-agent` | Start the default/auto-detected agent without an initial prompt |
 | `--prompt` / `-p` | Initial prompt for the agent (short prompts only) |
 | `--prompt-file` / `-P` | Read prompt from file (recommended for longer prompts) |
 | `--from` / `-f` | Base ref (default: origin/main). **Use `--from HEAD` when reviewing/testing current branch!** |
-| `--with-agent` | Specific agent: claude, aider, codex, gemini |
+| `--agent` | Specific agent (or `auto`): claude, aider, codex, gemini |
 | `--agent-args` | Extra arguments for the agent |
+| `--tmux-session` | Reuse or create a specific tmux session. For autonomous agents, prefer a unique name per launch |
 
 @examples.md

{agent_cli-0.86.1 → agent_cli-0.88.0}/.claude/skills/agent-cli-dev/examples.md

@@ -6,7 +6,7 @@ Real-world scenarios for spawning parallel AI coding agents, optimized for Claud
 >
 > ```bash
 > # Write prompt to file, then spawn
-> agent-cli dev new my-feature --agent --prompt-file .claude/spawn-prompt.md
+> agent-cli dev new my-feature --prompt-file .claude/spawn-prompt.md
 > ```
 >
 > When an assistant is executing these commands, do not launch `dev new` or `dev agent` without `--prompt` or `--prompt-file` unless the user explicitly wants a manual interactive session.
@@ -31,7 +31,7 @@ Each prompt for a spawned agent should follow this structure:
 
 ```bash
 # Review the current branch - MUST use --from HEAD
-agent-cli dev new review-changes --from HEAD --agent --prompt "Review the code changes on this branch.
+agent-cli dev new review-changes --from HEAD --prompt "Review the code changes on this branch.
 
 <workflow>
 - Run git diff origin/main...HEAD to identify all changes
@@ -91,7 +91,7 @@ Write your review to .claude/REPORT.md:
 **Strategy**: Three independent features → spawn three agents.
 
 ```bash
-agent-cli dev new auth-feature --agent --prompt "Implement JWT-based user authentication.
+agent-cli dev new auth-feature --prompt "Implement JWT-based user authentication.
 
 <workflow>
 - Read multiple files in parallel when exploring the codebase
@@ -144,7 +144,7 @@ How to verify the implementation works
 Any items needing review
 </report>"
 
-agent-cli dev new payment-integration --agent --prompt "Integrate Stripe payment processing.
+agent-cli dev new payment-integration --prompt "Integrate Stripe payment processing.
 
 <workflow>
 - Read multiple files in parallel when exploring the codebase
@@ -195,7 +195,7 @@ After verifying tests pass, write to .claude/REPORT.md:
 [Any items for review]
 </report>"
 
-agent-cli dev new email-notifications --agent --prompt "Implement email notification system.
+agent-cli dev new email-notifications --prompt "Implement email notification system.
 
 <workflow>
 - Read multiple files in parallel when exploring the codebase
@@ -240,7 +240,7 @@ After verifying tests pass, write to .claude/REPORT.md with summary, files chang
 **Strategy**: One agent writes tests first, another implements.
 
 ```bash
-agent-cli dev new cache-tests --agent --prompt "Write comprehensive tests for a caching layer.
+agent-cli dev new cache-tests --prompt "Write comprehensive tests for a caching layer.
 
 <task>
 Create a complete test suite that drives the implementation of a caching system. The tests define the interface - write them as if the implementation already exists.
@@ -306,7 +306,7 @@ When complete, write to .claude/REPORT.md:
 After reviewing the tests:
 
 ```bash
-agent-cli dev new cache-impl --from cache-tests --agent --prompt "Implement the caching layer to pass existing tests.
+agent-cli dev new cache-impl --from cache-tests --prompt "Implement the caching layer to pass existing tests.
 
 <workflow>
 - Read all test files first to understand the complete interface
@@ -360,7 +360,7 @@ After ALL tests pass, write to .claude/REPORT.md:
 **Strategy**: Split by module, each agent handles one area.
 
 ```bash
-agent-cli dev new refactor-users-errors --agent --prompt "Refactor error handling in the users module.
+agent-cli dev new refactor-users-errors --prompt "Refactor error handling in the users module.
 
 <workflow>
 - Read all relevant files in parallel before making any changes
@@ -428,7 +428,7 @@ After tests pass and linting is clean, write to .claude/REPORT.md:
 **Strategy**: One agent implements, another writes docs simultaneously.
 
 ```bash
-agent-cli dev new plugin-system --agent --prompt "Implement a plugin system.
+agent-cli dev new plugin-system --prompt "Implement a plugin system.
 
 <workflow>
 - Read existing codebase structure in parallel before designing
@@ -483,7 +483,7 @@ class Plugin:
 [How to create and register a plugin]
 </report>"
 
-agent-cli dev new plugin-docs --agent --prompt "Write documentation for the plugin system.
+agent-cli dev new plugin-docs --prompt "Write documentation for the plugin system.
 
 <context>
 Implementation is happening in parallel in another branch. Write documentation based on a standard plugin system design. The implementation agent will adapt if needed, or you can update docs after reviewing their work.
@@ -595,7 +595,7 @@ Write findings to .claude/REPORT-tests-$run_id.md:
 
 ```bash
 for section in 1 2 3 4 5 6 7 8; do
-  agent-cli dev new "test-section-$section" --from HEAD --agent --with-agent codex -m tmux \
+  agent-cli dev new "test-section-$section" --from HEAD --agent codex -m tmux \
     --prompt-file ".claude/test-section-$section.md"
 done
 ```

{agent_cli-0.86.1/.claude → agent_cli-0.88.0/.claude-plugin}/skills/agent-cli-dev/SKILL.md

@@ -9,7 +9,7 @@ This skill teaches you how to spawn parallel AI coding agents in isolated git wo
 
 `agent-cli dev` supports two complementary patterns:
 - Separate worktrees for isolated implementation/review tasks
-- Multiple agents on the same worktree using `dev agent -m tmux`
+- Multiple agents on the same worktree using `dev agent --tmux-session <unique-name>` for autonomous launches, or `-m tmux` when a human explicitly wants shared tmux windows
 
 ## Installation
 
@@ -20,7 +20,7 @@ If `agent-cli` is not available, install it first:
 uv tool install agent-cli -p 3.13
 
 # Or run directly without installing
-uvx --python 3.13 agent-cli dev new <branch-name> --agent --prompt "..."
+uvx --python 3.13 agent-cli dev new <branch-name> --prompt "..."
 ```
 
 ## When to spawn parallel agents
@@ -40,17 +40,17 @@ Do NOT spawn when:
 
 For new features (starts from origin/main):
 ```bash
-agent-cli dev new <branch-name> --agent --prompt "Implement the new feature..."
+agent-cli dev new <branch-name> --prompt "Implement the new feature..."
 ```
 
 For work on current branch (review, test, fix) - use `--from HEAD`:
 ```bash
-agent-cli dev new <branch-name> --from HEAD --agent --prompt "Review/test/fix..."
+agent-cli dev new <branch-name> --from HEAD --prompt "Review/test/fix..."
 ```
 
 For longer prompts (recommended for multi-line or complex instructions):
 ```bash
-agent-cli dev new <branch-name> --from HEAD --agent --prompt-file path/to/prompt.md
+agent-cli dev new <branch-name> --from HEAD --prompt-file path/to/prompt.md
 ```
 
 This creates:
@@ -67,10 +67,10 @@ This creates:
 When an assistant is executing this workflow on the user's behalf, the spawn is not complete unless the agent receives a prompt at launch time.
 
 - Prefer `--prompt-file`; create the prompt file first, then launch the agent
-- Use `dev new ... --agent --prompt-file ...` for a new delegated task
+- Use `dev new ... --prompt-file ...` for a new delegated task
 - Use `dev agent ... --prompt-file ...` for another agent in an existing worktree
 - Do not stop after `dev new ...` alone if the user's intent was to delegate work immediately
-- Do not run `dev new ... --agent` or `dev agent ... -m tmux` without `--prompt` or `--prompt-file` unless the user explicitly wants an interactive session that they will drive manually
+- Do not run `dev new ... --start-agent`, `dev new ... --agent <name>`, or `dev agent ... -m tmux` without `--prompt` or `--prompt-file` unless the user explicitly wants an interactive session that they will drive manually
 
 ## Writing effective prompts for spawned agents
 
@@ -92,7 +92,7 @@ Example workflow:
 ```bash
 # 1. Write prompt to file
 # 2. Spawn agent with the file
-agent-cli dev new my-feature --agent --prompt-file .claude/spawn-prompt.md
+agent-cli dev new my-feature --prompt-file .claude/spawn-prompt.md
 # 3. Optionally clean up
 rm .claude/spawn-prompt.md
 ```
@@ -136,17 +136,26 @@ Use this when several agents should inspect or validate the same code at once wi
 # Create the worktree once. This step only prepares the shared workspace.
 agent-cli dev new review-auth --from HEAD
 
-# Then launch the actual agents with prompts.
-agent-cli dev agent review-auth -m tmux --prompt-file .claude/review-security.md
-agent-cli dev agent review-auth -m tmux --prompt-file .claude/review-performance.md
-agent-cli dev agent review-auth -m tmux --prompt-file .claude/review-tests.md
+# Then launch the actual agents with prompts. Give each agent its own tmux session.
+agent-cli dev agent review-auth \
+  --tmux-session review-auth-security-20260402-1530 \
+  --prompt-file .claude/review-security.md
+agent-cli dev agent review-auth \
+  --tmux-session review-auth-performance-20260402-1530 \
+  --prompt-file .claude/review-performance.md
+agent-cli dev agent review-auth \
+  --tmux-session review-auth-tests-20260402-1530 \
+  --prompt-file .claude/review-tests.md
 ```
 
 Key rules for same-worktree launches:
 - Use `dev agent`, not `dev new`, after the worktree already exists
-- Use `dev agent -a <agent>` to select a specific agent for an existing worktree; `--with-agent` remains a deprecated alias on this subcommand
-- Use `-m tmux` for headless or scripted launching; it works even when not already inside tmux
-- Each launch joins the same deterministic repo-scoped tmux session, so related agents stay grouped together
+- Use `dev agent --agent <agent>` to select a specific agent for an existing worktree; `--with-agent` remains a deprecated alias on this subcommand
+- For autonomous agents, prefer `--tmux-session <unique-name>` and use a different session name for each launch
+- Reserve bare `-m tmux` for human-driven grouped windows or when the user explicitly wants agents to share one tmux session
+- Outside tmux, bare `-m tmux` joins the deterministic repo-scoped tmux session
+- Inside tmux, bare `-m tmux` opens a new window in the current session unless you pass `--tmux-session <name>`, which reuses or creates a specific tmux session and also implies `-m tmux`
+- tmux session names cannot contain `.` or `:`
 - Ask each agent to write to a unique report path such as `.claude/REPORT-security-<run-id>.md` or `.claude/REPORT-tests-<run-id>.md`
 - If you rerun the same prompt repeatedly, include a timestamp or other run id in the report filename so later runs do not overwrite earlier ones
 - Each agent launch gets its own unique task file in `.claude/` (e.g., `TASK-{timestamp}-{hex}.md`), so parallel launches do not overwrite each other
@@ -168,14 +177,21 @@ When complete, write findings to .claude/REPORT-security-20260319-153045-123.md
 
 ## Headless/scripted orchestration
 
-For non-interactive contexts (scripts, cron jobs, other assistants), combine `--prompt-file` with `-m tmux`:
+For non-interactive contexts (scripts, cron jobs, other assistants), combine `--prompt-file` with `--tmux-session`:
 
 ```bash
-agent-cli dev new validation-a --from HEAD --agent --with-agent codex -m tmux \
+agent-cli dev new validation-a --from HEAD --agent codex \
+  --tmux-session validation-a-20260402-1530 \
   --prompt-file .claude/validation-a.md
 ```
 
-This works without an attached terminal. `agent-cli` creates or reuses a detached tmux session and returns a pane handle plus attach command. Launches may also run pre-launch preparation by default; use `--no-hooks` only when you explicitly need to bypass that behavior.
+This works without an attached terminal. For autonomous or scripted launches, prefer a unique `--tmux-session` per agent so separate runs do not trample each other by sharing one tmux session. Use bare `-m tmux` only when you explicitly want shared tmux grouping. Launches may also run pre-launch preparation by default; use `--no-hooks` only when you explicitly need to bypass that behavior.
+
+## Cleanup behavior
+
+- `dev rm` and `dev clean` also clean up tmux windows that `agent-cli` tagged for the worktree
+- If git worktree removal succeeds but tmux cleanup is partial, the command warns and still removes the worktree
+- Session isolation prevents agents from interfering with each other's tmux windows during execution, but cleanup still applies to all tagged windows for the worktree
 
 ## Example: Multi-feature implementation
 
@@ -183,9 +199,9 @@ If asked to implement auth, payments, and notifications:
 
 ```bash
 # Spawn three parallel agents
-agent-cli dev new auth-feature --agent --prompt "Implement JWT authentication..."
-agent-cli dev new payment-integration --agent --prompt "Add Stripe payment processing..."
-agent-cli dev new email-notifications --agent --prompt "Implement email notification system..."
+agent-cli dev new auth-feature --prompt "Implement JWT authentication..."
+agent-cli dev new payment-integration --prompt "Add Stripe payment processing..."
+agent-cli dev new email-notifications --prompt "Implement email notification system..."
 ```
 
 Each agent works independently in its own branch. Results can be reviewed and merged separately.
@@ -194,11 +210,12 @@ Each agent works independently in its own branch. Results can be reviewed and me
 
 | Option | Description |
 |--------|-------------|
-| `--agent` / `-a` | Start AI coding agent after creation |
+| `--start-agent` | Start the default/auto-detected agent without an initial prompt |
 | `--prompt` / `-p` | Initial prompt for the agent (short prompts only) |
 | `--prompt-file` / `-P` | Read prompt from file (recommended for longer prompts) |
 | `--from` / `-f` | Base ref (default: origin/main). **Use `--from HEAD` when reviewing/testing current branch!** |
-| `--with-agent` | Specific agent: claude, aider, codex, gemini |
+| `--agent` | Specific agent (or `auto`): claude, aider, codex, gemini |
 | `--agent-args` | Extra arguments for the agent |
+| `--tmux-session` | Reuse or create a specific tmux session. For autonomous agents, prefer a unique name per launch |
 
 @examples.md

{agent_cli-0.86.1 → agent_cli-0.88.0}/.claude-plugin/skills/agent-cli-dev/examples.md

@@ -6,7 +6,7 @@ Real-world scenarios for spawning parallel AI coding agents, optimized for Claud
 >
 > ```bash
 > # Write prompt to file, then spawn
-> agent-cli dev new my-feature --agent --prompt-file .claude/spawn-prompt.md
+> agent-cli dev new my-feature --prompt-file .claude/spawn-prompt.md
 > ```
 >
 > When an assistant is executing these commands, do not launch `dev new` or `dev agent` without `--prompt` or `--prompt-file` unless the user explicitly wants a manual interactive session.
@@ -31,7 +31,7 @@ Each prompt for a spawned agent should follow this structure:
 
 ```bash
 # Review the current branch - MUST use --from HEAD
-agent-cli dev new review-changes --from HEAD --agent --prompt "Review the code changes on this branch.
+agent-cli dev new review-changes --from HEAD --prompt "Review the code changes on this branch.
 
 <workflow>
 - Run git diff origin/main...HEAD to identify all changes
@@ -91,7 +91,7 @@ Write your review to .claude/REPORT.md:
 **Strategy**: Three independent features → spawn three agents.
 
 ```bash
-agent-cli dev new auth-feature --agent --prompt "Implement JWT-based user authentication.
+agent-cli dev new auth-feature --prompt "Implement JWT-based user authentication.
 
 <workflow>
 - Read multiple files in parallel when exploring the codebase
@@ -144,7 +144,7 @@ How to verify the implementation works
 Any items needing review
 </report>"
 
-agent-cli dev new payment-integration --agent --prompt "Integrate Stripe payment processing.
+agent-cli dev new payment-integration --prompt "Integrate Stripe payment processing.
 
 <workflow>
 - Read multiple files in parallel when exploring the codebase
@@ -195,7 +195,7 @@ After verifying tests pass, write to .claude/REPORT.md:
 [Any items for review]
 </report>"
 
-agent-cli dev new email-notifications --agent --prompt "Implement email notification system.
+agent-cli dev new email-notifications --prompt "Implement email notification system.
 
 <workflow>
 - Read multiple files in parallel when exploring the codebase
@@ -240,7 +240,7 @@ After verifying tests pass, write to .claude/REPORT.md with summary, files chang
 **Strategy**: One agent writes tests first, another implements.
 
 ```bash
-agent-cli dev new cache-tests --agent --prompt "Write comprehensive tests for a caching layer.
+agent-cli dev new cache-tests --prompt "Write comprehensive tests for a caching layer.
 
 <task>
 Create a complete test suite that drives the implementation of a caching system. The tests define the interface - write them as if the implementation already exists.
@@ -306,7 +306,7 @@ When complete, write to .claude/REPORT.md:
 After reviewing the tests:
 
 ```bash
-agent-cli dev new cache-impl --from cache-tests --agent --prompt "Implement the caching layer to pass existing tests.
+agent-cli dev new cache-impl --from cache-tests --prompt "Implement the caching layer to pass existing tests.
 
 <workflow>
 - Read all test files first to understand the complete interface
@@ -360,7 +360,7 @@ After ALL tests pass, write to .claude/REPORT.md:
 **Strategy**: Split by module, each agent handles one area.
 
 ```bash
-agent-cli dev new refactor-users-errors --agent --prompt "Refactor error handling in the users module.
+agent-cli dev new refactor-users-errors --prompt "Refactor error handling in the users module.
 
 <workflow>
 - Read all relevant files in parallel before making any changes
@@ -428,7 +428,7 @@ After tests pass and linting is clean, write to .claude/REPORT.md:
 **Strategy**: One agent implements, another writes docs simultaneously.
 
 ```bash
-agent-cli dev new plugin-system --agent --prompt "Implement a plugin system.
+agent-cli dev new plugin-system --prompt "Implement a plugin system.
 
 <workflow>
 - Read existing codebase structure in parallel before designing
@@ -483,7 +483,7 @@ class Plugin:
 [How to create and register a plugin]
 </report>"
 
-agent-cli dev new plugin-docs --agent --prompt "Write documentation for the plugin system.
+agent-cli dev new plugin-docs --prompt "Write documentation for the plugin system.
 
 <context>
 Implementation is happening in parallel in another branch. Write documentation based on a standard plugin system design. The implementation agent will adapt if needed, or you can update docs after reviewing their work.
@@ -595,7 +595,7 @@ Write findings to .claude/REPORT-tests-$run_id.md:
 
 ```bash
 for section in 1 2 3 4 5 6 7 8; do
-  agent-cli dev new "test-section-$section" --from HEAD --agent --with-agent codex -m tmux \
+  agent-cli dev new "test-section-$section" --from HEAD --agent codex -m tmux \
     --prompt-file ".claude/test-section-$section.md"
 done
 ```

{agent_cli-0.86.1 → agent_cli-0.88.0}/.pre-commit-config.yaml

@@ -11,7 +11,7 @@ repos:
       - id: end-of-file-fixer
       - id: mixed-line-ending
   - repo: https://github.com/astral-sh/ruff-pre-commit
-    rev: "v0.15.7"
+    rev: "v0.15.8"
     hooks:
       - id: ruff
         args: ["--fix"]

agent_cli-0.88.0/LLAMA_SERVER_USAGE.md

@@ -0,0 +1,90 @@
+# Using agent-cli with llama-server (llama-cpp)
+
+This guide explains how to use agent-cli with llama-server, which provides an OpenAI-compatible API for running local LLM models.
+
+## Prerequisites
+
+1. Install and set up llama-cpp with llama-server support
+2. Download a compatible GGUF model file
+
+## Starting llama-server
+
+Start the llama-server with your model:
+
+```bash
+# Example with a 3B parameter model
+llama-server \
+  -m /path/to/your/model.gguf \
+  -c 2048 \
+  --host 0.0.0.0 \
+  --port 8080
+```
+
+## Configuration
+
+### Option 1: Using Configuration File
+
+Add to your `~/.config/agent-cli/config.toml` or `./agent-cli-config.toml`:
+
+```toml
+[defaults]
+llm-provider = "openai"
+llm-openai-model = "your-model-name"  # Can be anything, llama-server ignores this
+openai-base-url = "http://localhost:8080/v1"
+# openai-api-key is not required for llama-server
+```
+
+### Option 2: Using Command Line
+
+```bash
+# Example: Autocorrect text
+agent-cli autocorrect \
+  --llm-provider openai \
+  --llm-openai-model llama-3.2-3b \
+  --openai-base-url http://localhost:8080/v1
+
+# Example: Transcribe and process audio
+agent-cli transcribe \
+  --llm-provider openai \
+  --llm-openai-model llama-3.2-3b \
+  --openai-base-url http://localhost:8080/v1 \
+  --llm
+
+# Example: Chat assistant
+agent-cli chat \
+  --llm-provider openai \
+  --llm-openai-model llama-3.2-3b \
+  --openai-base-url http://localhost:8080/v1
+```
+
+## Notes
+
+- The `--llm-openai-model` parameter is sent to llama-server but typically ignored (the model is already loaded)
+- No API key is required when using llama-server
+- Make sure the base URL includes the `/v1` suffix for OpenAI API compatibility
+- Performance depends on your hardware and the model size
+
+## Advantages
+
+- Complete privacy - all processing happens locally
+- No API costs
+- No internet connection required (after model download)
+- Full control over the model and parameters
+- Can use any GGUF-compatible model
+
+## Troubleshooting
+
+If you encounter issues:
+
+1. Verify llama-server is running: `curl http://localhost:8080/v1/models`
+2. Check the llama-server logs for errors
+3. Ensure the base URL includes `/v1` at the end
+4. Try a simple curl test:
+   ```bash
+   curl http://localhost:8080/v1/chat/completions \
+     -H "Content-Type: application/json" \
+     -d '{
+       "model": "test",
+       "messages": [{"role": "user", "content": "Hello"}]
+     }'
+   ```

{agent_cli-0.86.1 → agent_cli-0.88.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: agent-cli
-Version: 0.86.1
+Version: 0.88.0
 Summary: A suite of AI-powered command-line tools for text correction, audio transcription, and voice assistance.
 Project-URL: Homepage, https://github.com/basnijholt/agent-cli
 Author-email: Bas Nijholt <bas@nijho.lt>