@draht/coding-agent 2026.3.2 → 2026.3.4

package/README.md

@@ -1,32 +1,15 @@
-# 🏖️ OSS Vacation
+<h1 align="center">@draht/coding-agent</h1>
 
-**Issue tracker and PRs reopen March 2, 2026.**
-
-All PRs will be auto-closed until then. Approved contributors can submit PRs after vacation without reapproval. For support, join [Discord](https://discord.com/invite/3cU7Bz4UPx).
-
----
-
-<p align="center">
-  <a href="https://shittycodingagent.ai">
-    <img src="https://shittycodingagent.ai/logo.svg" alt="pi logo" width="128">
-  </a>
-</p>
-<p align="center">
-  <a href="https://discord.com/invite/3cU7Bz4UPx"><img alt="Discord" src="https://img.shields.io/badge/discord-community-5865F2?style=flat-square&logo=discord&logoColor=white" /></a>
-  <a href="https://www.npmjs.com/package/@mariozechner/pi-coding-agent"><img alt="npm" src="https://img.shields.io/npm/v/@mariozechner/pi-coding-agent?style=flat-square" /></a>
-  <a href="https://github.com/badlogic/pi-mono/actions/workflows/ci.yml"><img alt="Build status" src="https://img.shields.io/github/actions/workflow/status/badlogic/pi-mono/ci.yml?style=flat-square&branch=main" /></a>
-</p>
 <p align="center">
-  <a href="https://pi.dev">pi.dev</a> domain graciously donated by
-  <br /><br />
-  <a href="https://exe.dev"><img src="docs/images/exy.png" alt="Exy mascot" width="48" /><br />exe.dev</a>
+  <a href="https://www.npmjs.com/package/@draht/coding-agent"><img alt="npm" src="https://img.shields.io/npm/v/@draht/coding-agent?style=flat-square" /></a>
+  <a href="https://github.com/draht-dev/draht/actions/workflows/ci.yml"><img alt="Build status" src="https://img.shields.io/github/actions/workflow/status/draht-dev/draht/ci.yml?style=flat-square&branch=main" /></a>
 </p>
 
-Pi is a minimal terminal coding harness. Adapt pi to your workflows, not the other way around, without having to fork and modify pi internals. Extend it with TypeScript [Extensions](#extensions), [Skills](#skills), [Prompt Templates](#prompt-templates), and [Themes](#themes). Put your extensions, skills, prompt templates, and themes in [Pi Packages](#pi-packages) and share them with others via npm or git.
+Draht is a minimal terminal coding harness. Adapt it to your workflows, not the other way around, without having to fork and modify internals. Extend it with TypeScript [Extensions](#extensions), [Skills](#skills), [Prompt Templates](#prompt-templates), and [Themes](#themes). Put your extensions, skills, prompt templates, and themes in [Draht Packages](#draht-packages) and share them with others via npm or git.
 
-Pi ships with powerful defaults but skips features like sub agents and plan mode. Instead, you can ask pi to build what you want or install a third party pi package that matches your workflow.
+Draht ships with powerful defaults but skips features like sub agents and plan mode. Instead, you can ask draht to build what you want or install a third party package that matches your workflow.
 
-Pi runs in four modes: interactive, print or JSON, RPC for process integration, and an SDK for embedding in your own apps. See [openclaw/openclaw](https://github.com/openclaw/openclaw) for a real-world SDK integration.
+Draht runs in four modes: interactive, print or JSON, RPC for process integration, and an SDK for embedding in your own apps.
 
 ## Table of Contents
 
@@ -47,7 +30,7 @@ Pi runs in four modes: interactive, print or JSON, RPC for process integration,
   - [Skills](#skills)
   - [Extensions](#extensions)
   - [Themes](#themes)
-  - [Pi Packages](#pi-packages)
+  - [Draht Packages](#draht-packages)
 - [Programmatic Usage](#programmatic-usage)
 - [Philosophy](#philosophy)
 - [CLI Reference](#cli-reference)
@@ -57,24 +40,24 @@ Pi runs in four modes: interactive, print or JSON, RPC for process integration,
 ## Quick Start
 
 ```bash
-npm install -g @mariozechner/pi-coding-agent
+bun add -g @draht/coding-agent
 ```
 
 Authenticate with an API key:
 
 ```bash
 export ANTHROPIC_API_KEY=sk-ant-...
-pi
+draht
 ```
 
 Or use your existing subscription:
 
 ```bash
-pi
+draht
 /login  # Then select provider
 ```
 
-Then just talk to pi. By default, pi gives the model four tools: `read`, `write`, `edit`, and `bash`. The model uses these to fulfill your requests. Add capabilities via [skills](#skills), [prompt templates](#prompt-templates), [extensions](#extensions), or [pi packages](#pi-packages).
+Then just talk to draht. By default, draht gives the model four tools: `read`, `write`, `edit`, and `bash`. The model uses these to fulfill your requests. Add capabilities via [skills](#skills), [prompt templates](#prompt-templates), [extensions](#extensions), or [draht packages](#draht-packages).
 
 **Platform notes:** [Windows](docs/windows.md) | [Termux (Android)](docs/termux.md) | [Terminal setup](docs/terminal-setup.md) | [Shell aliases](docs/shell-aliases.md)
 
@@ -82,7 +65,7 @@ Then just talk to pi. By default, pi gives the model four tools: `read`, `write`
 
 ## Providers & Models
 
-For each built-in provider, pi maintains a list of tool-capable models, updated with every release. Authenticate via subscription (`/login`) or API key, then select any model from that provider via `/model` (or Ctrl+L).
+For each built-in provider,draht maintains a list of tool-capable models, updated with every release. Authenticate via subscription (`/login`) or API key, then select any model from that provider via `/model` (or Ctrl+L).
 
 **Subscriptions:**
 - Anthropic Claude Pro/Max
@@ -106,13 +89,14 @@ For each built-in provider, pi maintains a list of tool-capable models, updated
 - Vercel AI Gateway
 - ZAI
 - OpenCode Zen
+- OpenCode Go
 - Hugging Face
 - Kimi For Coding
 - MiniMax
 
 See [docs/providers.md](docs/providers.md) for detailed setup instructions.
 
-**Custom providers & models:** Add providers via `~/.pi/agent/models.json` if they speak a supported API (OpenAI, Anthropic, Google). For custom APIs or OAuth, use extensions. See [docs/models.md](docs/models.md) and [docs/custom-provider.md](docs/custom-provider.md).
+**Custom providers & models:** Add providers via `~/.draht/agent/models.json` if they speak a supported API (OpenAI, Anthropic, Google). For custom APIs or OAuth, use extensions. See [docs/models.md](docs/models.md) and [docs/custom-provider.md](docs/custom-provider.md).
 
 ---
 
@@ -164,11 +148,11 @@ Type `/` in the editor to trigger commands. [Extensions](#extensions) can regist
 | `/reload` | Reload extensions, skills, prompts, context files (themes hot-reload automatically) |
 | `/hotkeys` | Show all keyboard shortcuts |
 | `/changelog` | Display version history |
-| `/quit`, `/exit` | Quit pi |
+| `/quit`, `/exit` | Quitdraht |
 
 ### Keyboard Shortcuts
 
-See `/hotkeys` for the full list. Customize via `~/.pi/agent/keybindings.json`. See [docs/keybindings.md](docs/keybindings.md).
+See `/hotkeys` for the full list. Customize via `~/.draht/agent/keybindings.json`. See [docs/keybindings.md](docs/keybindings.md).
 
 **Commonly used:**
 
@@ -203,13 +187,13 @@ Sessions are stored as JSONL files with a tree structure. Each entry has an `id`
 
 ### Management
 
-Sessions auto-save to `~/.pi/agent/sessions/` organized by working directory.
+Sessions auto-save to `~/.draht/agent/sessions/` organized by working directory.
 
 ```bash
-pi -c                  # Continue most recent session
-pi -r                  # Browse and select from past sessions
-pi --no-session        # Ephemeral mode (don't save)
-pi --session <path>    # Use specific session file or ID
+draht -c                  # Continue most recent session
+draht -r                  # Browse and select from past sessions
+draht --no-session        # Ephemeral mode (don't save)
+draht --session <path>    # Use specific session file or ID
 ```
 
 ### Branching
@@ -242,8 +226,8 @@ Use `/settings` to modify common options, or edit JSON files directly:
 
 | Location | Scope |
 |----------|-------|
-| `~/.pi/agent/settings.json` | Global (all projects) |
-| `.pi/settings.json` | Project (overrides global) |
+| `~/.draht/agent/settings.json` | Global (all projects) |
+| `.draht/settings.json` | Project (overrides global) |
 
 See [docs/settings.md](docs/settings.md) for all options.
 
@@ -251,8 +235,8 @@ See [docs/settings.md](docs/settings.md) for all options.
 
 ## Context Files
 
-Pi loads `AGENTS.md` (or `CLAUDE.md`) at startup from:
-- `~/.pi/agent/AGENTS.md` (global)
+Draht loads `AGENTS.md` (or `CLAUDE.md`) at startup from:
+- `~/.draht/agent/AGENTS.md` (global)
 - Parent directories (walking up from cwd)
 - Current directory
 
@@ -260,7 +244,7 @@ Use for project instructions, conventions, common commands. All matching files a
 
 ### System Prompt
 
-Replace the default system prompt with `.pi/SYSTEM.md` (project) or `~/.pi/agent/SYSTEM.md` (global). Append without replacing via `APPEND_SYSTEM.md`.
+Replace the default system prompt with `.draht/SYSTEM.md` (project) or `~/.draht/agent/SYSTEM.md` (global). Append without replacing via `APPEND_SYSTEM.md`.
 
 ---
 
@@ -271,19 +255,19 @@ Replace the default system prompt with `.pi/SYSTEM.md` (project) or `~/.pi/agent
 Reusable prompts as Markdown files. Type `/name` to expand.
 
 ```markdown
-<!-- ~/.pi/agent/prompts/review.md -->
+<!-- ~/.draht/agent/prompts/review.md -->
 Review this code for bugs, security issues, and performance problems.
 Focus on: {{focus}}
 ```
 
-Place in `~/.pi/agent/prompts/`, `.pi/prompts/`, or a [pi package](#pi-packages) to share with others. See [docs/prompt-templates.md](docs/prompt-templates.md).
+Place in `~/.draht/agent/prompts/`, `.draht/prompts/`, or a [pi package](#draht-packages) to share with others. See [docs/prompt-templates.md](docs/prompt-templates.md).
 
 ### Skills
 
 On-demand capability packages following the [Agent Skills standard](https://agentskills.io). Invoke via `/skill:name` or let the agent load them automatically.
 
 ```markdown
-<!-- ~/.pi/agent/skills/my-skill/SKILL.md -->
+<!-- ~/.draht/agent/skills/my-skill/SKILL.md -->
 # My Skill
 Use this skill when the user asks about X.
 
@@ -292,19 +276,19 @@ Use this skill when the user asks about X.
 2. Then that
 ```
 
-Place in `~/.pi/agent/skills/`, `~/.agents/skills/`, `.pi/skills/`, or `.agents/skills/` (from `cwd` up through parent directories) or a [pi package](#pi-packages) to share with others. See [docs/skills.md](docs/skills.md).
+Place in `~/.draht/agent/skills/`, `~/.agents/skills/`, `.draht/skills/`, or `.agents/skills/` (from `cwd` up through parent directories) or a [pi package](#draht-packages) to share with others. See [docs/skills.md](docs/skills.md).
 
 ### Extensions
 
 <p align="center"><img src="docs/images/doom-extension.png" alt="Doom Extension" width="600"></p>
 
-TypeScript modules that extend pi with custom tools, commands, keyboard shortcuts, event handlers, and UI components.
+TypeScript modules that extenddraht with custom tools, commands, keyboard shortcuts, event handlers, and UI components.
 
 ```typescript
-export default function (pi: ExtensionAPI) {
-  pi.registerTool({ name: "deploy", ... });
-  pi.registerCommand("stats", { ... });
-  pi.on("tool_call", async (event, ctx) => { ... });
+export default function (draht: ExtensionAPI) {
+ draht.registerTool({ name: "deploy", ... });
+ draht.registerCommand("stats", { ... });
+ draht.on("tool_call", async (event, ctx) => { ... });
 }
 ```
 
@@ -318,50 +302,50 @@ export default function (pi: ExtensionAPI) {
 - Git checkpointing and auto-commit
 - SSH and sandbox execution
 - MCP server integration
-- Make pi look like Claude Code
+- Makedraht look like Claude Code
 - Games while waiting (yes, Doom runs)
 - ...anything you can dream up
 
-Place in `~/.pi/agent/extensions/`, `.pi/extensions/`, or a [pi package](#pi-packages) to share with others. See [docs/extensions.md](docs/extensions.md) and [examples/extensions/](examples/extensions/).
+Place in `~/.draht/agent/extensions/`, `.draht/extensions/`, or a [pi package](#draht-packages) to share with others. See [docs/extensions.md](docs/extensions.md) and [examples/extensions/](examples/extensions/).
 
 ### Themes
 
-Built-in: `dark`, `light`. Themes hot-reload: modify the active theme file and pi immediately applies changes.
+Built-in: `dark`, `light`. Themes hot-reload: modify the active theme file anddraht immediately applies changes.
 
-Place in `~/.pi/agent/themes/`, `.pi/themes/`, or a [pi package](#pi-packages) to share with others. See [docs/themes.md](docs/themes.md).
+Place in `~/.draht/agent/themes/`, `.draht/themes/`, or a [pi package](#draht-packages) to share with others. See [docs/themes.md](docs/themes.md).
 
-### Pi Packages
+### Draht Packages
 
-Bundle and share extensions, skills, prompts, and themes via npm or git. Find packages on [npmjs.com](https://www.npmjs.com/search?q=keywords%3Api-package) or [Discord](https://discord.com/channels/1456806362351669492/1457744485428629628).
+Bundle and share extensions, skills, prompts, and themes via npm or git. Find packages on [npmjs.com](https://www.npmjs.com/search?q=keywords%3Adraht-package) or [Discord](https://discord.com/channels/1456806362351669492/1457744485428629628).
 
-> **Security:** Pi packages run with full system access. Extensions execute arbitrary code, and skills can instruct the model to perform any action including running executables. Review source code before installing third-party packages.
+> **Security:** Draht packages run with full system access. Extensions execute arbitrary code, and skills can instruct the model to perform any action including running executables. Review source code before installing third-party packages.
 
 ```bash
-pi install npm:@foo/pi-tools
-pi install npm:@foo/pi-tools@1.2.3      # pinned version
-pi install git:github.com/user/repo
-pi install git:github.com/user/repo@v1  # tag or commit
-pi install git:git@github.com:user/repo
-pi install git:git@github.com:user/repo@v1  # tag or commit
-pi install https://github.com/user/repo
-pi install https://github.com/user/repo@v1      # tag or commit
-pi install ssh://git@github.com/user/repo
-pi install ssh://git@github.com/user/repo@v1    # tag or commit
-pi remove npm:@foo/pi-tools
-pi list
-pi update                               # skips pinned packages
-pi config                               # enable/disable extensions, skills, prompts, themes
+draht install npm:@foo/draht-tools
+draht install npm:@foo/draht-tools@1.2.3      # pinned version
+draht install git:github.com/user/repo
+draht install git:github.com/user/repo@v1  # tag or commit
+draht install git:git@github.com:user/repo
+draht install git:git@github.com:user/repo@v1  # tag or commit
+draht install https://github.com/user/repo
+draht install https://github.com/user/repo@v1      # tag or commit
+draht install ssh://git@github.com/user/repo
+draht install ssh://git@github.com/user/repo@v1    # tag or commit
+draht remove npm:@foo/draht-tools
+draht list
+draht update                               # skips pinned packages
+draht config                               # enable/disable extensions, skills, prompts, themes
 ```
 
-Packages install to `~/.pi/agent/git/` (git) or global npm. Use `-l` for project-local installs (`.pi/git/`, `.pi/npm/`).
+Packages install to `~/.draht/agent/git/` (git) or global npm. Use `-l` for project-local installs (`.draht/git/`, `.draht/npm/`).
 
-Create a package by adding a `pi` key to `package.json`:
+Create a package by adding a `draht` key to `package.json`:
 
 ```json
 {
-  "name": "my-pi-package",
-  "keywords": ["pi-package"],
-  "pi": {
+  "name": "my-draht-package",
+  "keywords": ["draht-package"],
+  "draht": {
     "extensions": ["./extensions"],
     "skills": ["./skills"],
     "prompts": ["./prompts"],
@@ -370,7 +354,7 @@ Create a package by adding a `pi` key to `package.json`:
 }
 ```
 
-Without a `pi` manifest, pi auto-discovers from conventional directories (`extensions/`, `skills/`, `prompts/`, `themes/`).
+Without a `draht` manifest,draht auto-discovers from conventional directories (`extensions/`, `skills/`, `prompts/`, `themes/`).
 
 See [docs/packages.md](docs/packages.md).
 
@@ -381,7 +365,7 @@ See [docs/packages.md](docs/packages.md).
 ### SDK
 
 ```typescript
-import { AuthStorage, createAgentSession, ModelRegistry, SessionManager } from "@mariozechner/pi-coding-agent";
+import { AuthStorage, createAgentSession, ModelRegistry, SessionManager } from "@draht/coding-agent";
 
 const { session } = await createAgentSession({
   sessionManager: SessionManager.inMemory(),
@@ -399,7 +383,7 @@ See [docs/sdk.md](docs/sdk.md) and [examples/sdk/](examples/sdk/).
 For non-Node.js integrations, use RPC mode over stdin/stdout:
 
 ```bash
-pi --mode rpc
+draht --mode rpc
 ```
 
 See [docs/rpc.md](docs/rpc.md) for the protocol.
@@ -408,11 +392,11 @@ See [docs/rpc.md](docs/rpc.md) for the protocol.
 
 ## Philosophy
 
-Pi is aggressively extensible so it doesn't have to dictate your workflow. Features that other tools bake in can be built with [extensions](#extensions), [skills](#skills), or installed from third-party [pi packages](#pi-packages). This keeps the core minimal while letting you shape pi to fit how you work.
+Draht is aggressively extensible so it doesn't have to dictate your workflow. Features that other tools bake in can be built with [extensions](#extensions), [skills](#skills), or installed from third-party [pi packages](#draht-packages). This keeps the core minimal while letting you shapedraht to fit how you work.
 
 **No MCP.** Build CLI tools with READMEs (see [Skills](#skills)), or build an extension that adds MCP support. [Why?](https://mariozechner.at/posts/2025-11-02-what-if-you-dont-need-mcp/)
 
-**No sub-agents.** There's many ways to do this. Spawn pi instances via tmux, or build your own with [extensions](#extensions), or install a package that does it your way.
+**No sub-agents.** There's many ways to do this. Spawndraht instances via tmux, or build your own with [extensions](#extensions), or install a package that does it your way.
 
 **No permission popups.** Run in a container, or build your own confirmation flow with [extensions](#extensions) inline with your environment and security requirements.
 
@@ -429,17 +413,17 @@ Read the [blog post](https://mariozechner.at/posts/2025-11-30-pi-coding-agent/)
 ## CLI Reference
 
 ```bash
-pi [options] [@files...] [messages...]
+draht [options] [@files...] [messages...]
 ```
 
 ### Package Commands
 
 ```bash
-pi install <source> [-l]    # Install package, -l for project-local
-pi remove <source> [-l]     # Remove package
-pi update [source]          # Update packages (skips pinned)
-pi list                     # List installed packages
-pi config                   # Enable/disable package resources
+draht install <source> [-l]    # Install package, -l for project-local
+draht remove <source> [-l]     # Remove package
+draht update [source]          # Update packages (skips pinned)
+draht list                     # List installed packages
+draht config                   # Enable/disable package resources
 ```
 
 ### Modes
@@ -512,47 +496,47 @@ Combine `--no-*` with explicit flags to load exactly what you need, ignoring set
 Prefix files with `@` to include in the message:
 
 ```bash
-pi @prompt.md "Answer this"
-pi -p @screenshot.png "What's in this image?"
-pi @code.ts @test.ts "Review these files"
+draht @prompt.md "Answer this"
+draht -p @screenshot.png "What's in this image?"
+draht @code.ts @test.ts "Review these files"
 ```
 
 ### Examples
 
 ```bash
 # Interactive with initial prompt
-pi "List all .ts files in src/"
+draht "List all .ts files in src/"
 
 # Non-interactive
-pi -p "Summarize this codebase"
+draht -p "Summarize this codebase"
 
 # Different model
-pi --provider openai --model gpt-4o "Help me refactor"
+draht --provider openai --model gpt-4o "Help me refactor"
 
 # Model with provider prefix (no --provider needed)
-pi --model openai/gpt-4o "Help me refactor"
+draht --model openai/gpt-4o "Help me refactor"
 
 # Model with thinking level shorthand
-pi --model sonnet:high "Solve this complex problem"
+draht --model sonnet:high "Solve this complex problem"
 
 # Limit model cycling
-pi --models "claude-*,gpt-4o"
+draht --models "claude-*,gpt-4o"
 
 # Read-only mode
-pi --tools read,grep,find,ls -p "Review the code"
+draht --tools read,grep,find,ls -p "Review the code"
 
 # High thinking level
-pi --thinking high "Solve this complex problem"
+draht --thinking high "Solve this complex problem"
 ```
 
 ### Environment Variables
 
 | Variable | Description |
 |----------|-------------|
-| `PI_CODING_AGENT_DIR` | Override config directory (default: `~/.pi/agent`) |
-| `PI_PACKAGE_DIR` | Override package directory (useful for Nix/Guix where store paths tokenize poorly) |
-| `PI_SKIP_VERSION_CHECK` | Skip version check at startup |
-| `PI_CACHE_RETENTION` | Set to `long` for extended prompt cache (Anthropic: 1h, OpenAI: 24h) |
+| `DRAHT_CODING_AGENT_DIR` | Override config directory (default: `~/.draht/agent`) |
+| `DRAHT_PACKAGE_DIR` | Override package directory (useful for Nix/Guix where store paths tokenize poorly) |
+| `DRAHT_SKIP_VERSION_CHECK` | Skip version check at startup |
+| `DRAHT_CACHE_RETENTION` | Set to `long` for extended prompt cache (Anthropic: 1h, OpenAI: 24h) |
 | `VISUAL`, `EDITOR` | External editor for Ctrl+G |
 
 ---
@@ -569,6 +553,6 @@ MIT
 
 ## See Also
 
-- [@mariozechner/pi-ai](https://www.npmjs.com/package/@mariozechner/pi-ai): Core LLM toolkit
-- [@mariozechner/pi-agent](https://www.npmjs.com/package/@mariozechner/pi-agent): Agent framework
-- [@mariozechner/pi-tui](https://www.npmjs.com/package/@mariozechner/pi-tui): Terminal UI components
+- [@draht/ai](https://www.npmjs.com/package/@draht/ai): Core LLM toolkit
+- [@draht/agent-core](https://www.npmjs.com/package/@draht/agent-core): Agent framework
+- [@draht/tui](https://www.npmjs.com/package/@draht/tui): Terminal UI components

package/agents/architect.md

@@ -0,0 +1,45 @@
+---
+name: architect
+description: Reads codebase, analyzes requirements, and produces structured implementation plans with file lists, dependencies, and phased task breakdowns.
+tools: read,bash,grep,find,ls
+---
+
+You are the Architect agent. Your job is to analyze requirements and produce clear, actionable implementation plans.
+
+## Process
+
+1. **Understand the request** — read the task carefully, identify what is being asked
+2. **Read the codebase** — use tools to explore relevant files, understand the current architecture, conventions, and patterns
+3. **Identify constraints** — note existing patterns, dependencies, type systems, and conventions that must be followed
+4. **Produce a plan** — output a structured implementation plan
+
+## Output Format
+
+Your plan MUST include:
+
+### Goal
+One sentence describing the outcome (not the activity).
+
+### Context
+What you learned from reading the codebase that informs the plan.
+
+### Tasks
+Numbered list of concrete tasks. For each task:
+- What to do (specific, not vague)
+- Which files to create or modify
+- Key implementation details
+- Dependencies on other tasks
+
+### Risk Assessment
+- What could go wrong
+- What assumptions you are making
+- What needs clarification from the user
+
+## Rules
+
+- DO read actual code before planning — never guess at APIs, types, or file structure
+- DO follow existing conventions you find in the codebase
+- DO keep plans minimal — smallest change that achieves the goal
+- DO NOT produce code — only plans
+- DO NOT make assumptions about APIs without reading the source
+- DO NOT suggest removing existing functionality unless explicitly asked

package/agents/debugger.md

@@ -0,0 +1,57 @@
+---
+name: debugger
+description: Diagnoses bugs, analyzes errors and stack traces, reproduces issues, and identifies root causes.
+tools: read,bash,edit,write,grep,find,ls
+---
+
+You are the Debugger agent. Your job is to find and fix bugs.
+
+## Process
+
+1. **Understand the problem** — read the error message, stack trace, or bug description
+2. **Reproduce** — if possible, run the failing command or test to see the error firsthand
+3. **Trace the cause** — follow the stack trace or logic path to find the root cause
+4. **Read surrounding code** — understand the broader context and intent of the code
+5. **Fix** — make the minimal change that fixes the root cause (not just the symptom)
+6. **Verify** — run the failing command/test again to confirm the fix works
+
+## Debugging Strategies
+
+### Stack Traces
+- Start from the bottom (root cause) not the top (symptom)
+- Read each file in the trace to understand the call chain
+- Look for incorrect assumptions about types, null values, or state
+
+### Test Failures
+- Read the test to understand what it expects
+- Read the implementation to understand what it does
+- Identify the gap between expected and actual behavior
+
+### Type Errors
+- Read the type definitions involved
+- Check if types changed upstream without updating downstream consumers
+- Look for implicit `any` or incorrect type assertions
+
+### Runtime Errors
+- Check for null/undefined access patterns
+- Look for async race conditions
+- Verify environment assumptions (env vars, file paths, dependencies)
+
+## Output Format
+
+### Root Cause
+Clear explanation of why the bug occurs.
+
+### Fix
+What was changed and why. Reference specific files and lines.
+
+### Verification
+Show that the fix works (test output, command output).
+
+## Rules
+
+- ALWAYS reproduce the bug before attempting to fix it
+- Fix the root cause, not the symptom
+- Keep fixes minimal — do not refactor unrelated code
+- If the fix is non-obvious, add a comment explaining why
+- Run verification after fixing to confirm the issue is resolved

package/agents/git-committer.md

@@ -0,0 +1,46 @@
+---
+name: git-committer
+description: Stages and commits changes with conventional commit messages. Reviews diffs before committing.
+tools: bash,read,grep,find,ls
+---
+
+You are the Git Committer agent. Your job is to create clean, well-described git commits.
+
+## Process
+
+1. **Check status** — run `git status` and `git diff --stat` to see what changed
+2. **Review changes** — read the diffs to understand what was done
+3. **Determine scope** — identify which package(s) or area(s) were affected
+4. **Write commit message** — follow the conventional commit format
+5. **Stage and commit** — stage only the relevant files, then commit
+
+## Commit Message Format
+
+```
+type(scope): concise description
+
+Optional body with more detail if the change is complex.
+```
+
+### Types
+- `feat` — new feature
+- `fix` — bug fix
+- `refactor` — code restructuring without behavior change
+- `docs` — documentation only
+- `test` — test changes
+- `chore` — build, CI, dependencies
+- `perf` — performance improvement
+
+### Scopes
+Use the package directory name (e.g., `ai`, `tui`, `agent`, `coding-agent`).
+
+## Rules
+
+- NEVER use `git add -A` or `git add .` — always stage specific files
+- NEVER use `git commit --no-verify`
+- NEVER force push
+- Review the diff before committing to ensure nothing unexpected is included
+- One commit per logical change — split unrelated changes into separate commits
+- Keep the first line under 72 characters
+- No emojis in commit messages
+- If there is a related issue, include `fixes #<number>` or `closes #<number>`

package/agents/implementer.md

@@ -0,0 +1,25 @@
+---
+name: implementer
+description: Implements code changes based on a plan or task description. Reads existing code, writes new code, and edits files.
+tools: read,bash,edit,write,grep,find,ls
+---
+
+You are the Implementer agent. Your job is to write code that fulfills the given task.
+
+## Process
+
+1. **Understand the task** — read the task description or plan carefully
+2. **Read existing code** — understand the codebase patterns, types, and conventions before writing
+3. **Implement** — write or edit files to complete the task
+4. **Verify** — run type checks or linting if applicable to catch errors early
+
+## Rules
+
+- ALWAYS read relevant existing code before writing — understand the patterns and conventions
+- ALWAYS match the existing code style (naming, formatting, structure)
+- NEVER use `any` types unless absolutely necessary
+- NEVER use inline imports — always use standard top-level imports
+- NEVER remove existing functionality unless the task explicitly requires it
+- Keep changes minimal — do only what the task asks for
+- If a task is ambiguous, implement the most conservative interpretation
+- Run `npm run check` or equivalent after changes if the project has one

package/agents/reviewer.md

@@ -0,0 +1,52 @@
+---
+name: reviewer
+description: Reviews code changes for correctness, type safety, conventions, and potential issues.
+tools: read,bash,grep,find,ls
+---
+
+You are the Reviewer agent. Your job is to review code changes and identify issues.
+
+## Process
+
+1. **Identify changes** — use `git diff` or read the provided context to understand what changed
+2. **Read surrounding code** — understand the broader context of the changes
+3. **Check for issues** — evaluate against the criteria below
+4. **Report findings** — produce a clear, prioritized list of issues
+
+## Review Criteria
+
+### Correctness
+- Does the code do what it claims to do?
+- Are there edge cases not handled?
+- Are error cases handled properly?
+
+### Type Safety
+- Are types correct and specific (no unnecessary `any`)?
+- Are type imports used where needed?
+- Do function signatures match their usage?
+
+### Conventions
+- Does the code follow the project's existing patterns?
+- Are naming conventions consistent?
+- Is the code style consistent with surrounding code?
+
+### Maintainability
+- Is the code readable and self-documenting?
+- Are there unnecessary abstractions or missing ones?
+- Is there duplicated logic that should be extracted?
+
+## Output Format
+
+List findings by severity:
+1. **Must fix** — bugs, type errors, logic errors
+2. **Should fix** — convention violations, missing error handling
+3. **Consider** — style suggestions, possible improvements
+
+If no issues found, state that explicitly.
+
+## Rules
+
+- Be specific — reference exact file paths and line numbers
+- Be actionable — say what to change, not just what is wrong
+- Do not nitpick formatting if the project has a formatter
+- Focus on substance over style