@draht/coding-agent 2026.3.3 → 2026.3.5

package/dist/prompts/commands/atomic-commit.md

@@ -4,19 +4,13 @@ description: "Analyze changes and create atomic commits"
 
 # Git Atomic Commit Analysis
 
-First, check the current status:
+First, gather the current state:
 
-*! git status*
+1. Run `git status` to see what changed
+2. Run `git diff` to see unstaged changes
+3. Run `git diff --cached` to see staged changes
 
-Now get the full diff of all changes:
-
-*! git diff*
-
-And staged changes:
-
-*! git diff --cached*
-
-Based on the changes shown above, analyze and group them into logical, ATOMIC commits. Each commit should:
+Based on the changes, analyze and group them into logical, ATOMIC commits. Each commit should:
 
 1. Contain ONE logical change only
 2. Be self-contained and complete
@@ -27,13 +21,11 @@ For each group of changes you identify:
 - Generate a clear, descriptive commit message following conventional commits format
 - Explain WHY these changes belong in one commit
 
-Then provide the exact `git add` and `git commit` commands to execute for each atomic commit in the order they should be applied.
+Then execute the `git add` and `git commit` commands for each atomic commit in the order they should be applied.
 
 Format each commit message as:
+```
 type(scope): brief description
-- Detailed explanation of what changed
-- Why the change was necessary
-
+```
 
 Common types: feat, fix, refactor, docs, test, chore, style, perf
-

package/dist/prompts/commands/discuss-phase.md

@@ -1,3 +1,7 @@
+---
+description: "Capture implementation decisions before planning a phase"
+---
+
 # /discuss-phase
 
 Capture implementation decisions before planning a phase.
@@ -7,13 +11,15 @@ Capture implementation decisions before planning a phase.
 /discuss-phase [N]
 ```
 
+Phase: $1
+
 ## Steps
-1. Run `draht-tools phase-info N` to load phase context
+1. Run `draht-tools phase-info $1` to load phase context
 2. Identify gray areas based on what's being built
 3. Present 1-2 questions at a time about preferences
 4. If `.planning/DOMAIN.md` exists, load it and validate discovered terms against the glossary. Add any new domain terms found during discussion.
-5. Record decisions with `draht-tools save-context N`
-6. Commit: `draht-tools commit-docs "capture phase N context"`
+5. Record decisions with `draht-tools save-context $1`
+6. Commit: `draht-tools commit-docs "capture phase $1 context"`
 
 ## Gray Area Categories
 - **Visual features** → Layout, density, interactions, empty states

package/dist/prompts/commands/execute-phase.md

@@ -1,3 +1,7 @@
+---
+description: "Execute all plans in a phase with atomic commits"
+---
+
 # /execute-phase
 
 Execute all plans in a phase with atomic commits.
@@ -7,37 +11,40 @@ Execute all plans in a phase with atomic commits.
 /execute-phase [N] [--gaps-only]
 ```
 
+Phase: $1
+Arguments: $ARGUMENTS
+
 ## Steps
-1. Run `draht-tools discover-plans N` to find and order plans
+1. Run `draht-tools discover-plans $1` to find and order plans
 2. For each plan in dependency order:
-   a. Load plan: `draht-tools read-plan N P`
+   a. Load plan: `draht-tools read-plan $1 P`
    b. Execute each task in strict TDD cycle:
 
       **🔴 RED — Write failing tests first**
       - Write the test cases from `<test>`
       - Run tests — confirm they FAIL (if they pass, the test is wrong)
-      - Commit failing tests: `draht-tools commit-task N P T "red: test description"`
+      - Commit failing tests: `draht-tools commit-task $1 P T "red: test description"`
 
       **🟢 GREEN — Minimal implementation**
       - Write the minimum code from `<action>` to make tests pass
       - Use domain language from `<context>` and `<domain>` for all names
       - Run tests — confirm they PASS
-      - Commit: `draht-tools commit-task N P T "green: task name"`
+      - Commit: `draht-tools commit-task $1 P T "green: task name"`
 
       **🔵 REFACTOR — Clean up with safety net**
       - Apply improvements from `<refactor>` (if any)
       - Run tests after each change — must stay green
       - Verify domain language compliance (names match DOMAIN.md)
-      - Commit: `draht-tools commit-task N P T "refactor: description"`
+      - Commit: `draht-tools commit-task $1 P T "refactor: description"`
 
       **✅ VERIFY**
       - Run the `<verify>` step
       - Confirm `<done>` criteria met
 
-   c. Write summary: `draht-tools write-summary N P`
-3. Phase verification: `draht-tools verify-phase N`
+   c. Write summary: `draht-tools write-summary $1 P`
+3. Phase verification: `draht-tools verify-phase $1`
 4. Update state: `draht-tools update-state`
-5. Final commit: `draht-tools commit-docs "complete phase N execution"`
+5. Final commit: `draht-tools commit-docs "complete phase $1 execution"`
 
 ## TDD Rules
 - Never write implementation before a failing test exists

package/dist/prompts/commands/fix.md

@@ -0,0 +1,35 @@
+---
+description: "Diagnose and fix a bug with TDD discipline"
+---
+
+# /fix
+
+Diagnose and fix a specific bug or failing task with TDD discipline.
+
+## Usage
+```
+/fix [description of what's broken]
+```
+
+Issue: $ARGUMENTS
+
+## Steps
+1. **Diagnose**: Read the relevant code and error output to identify the root cause
+   - If a test is failing, run it first to see the actual error
+   - If a runtime bug, reproduce it and capture the error
+2. **Write a reproducing test**: Before touching any implementation:
+   - Write a test that demonstrates the bug (it must fail)
+   - Commit: `draht-tools commit-docs "red: reproduce bug"`
+3. **Minimal fix**: Write the smallest change that makes the test pass
+   - Do not refactor or add features — just fix the bug
+   - Run the full test suite to check for regressions
+   - Commit: `draht-tools commit-docs "green: fix description"`
+4. **Refactor** (if needed): Clean up without changing behavior
+   - Tests must stay green after every change
+   - Commit: `draht-tools commit-docs "refactor: description"`
+5. **Update state**: `draht-tools update-state`
+
+## Rules
+- Always reproduce before fixing — a fix without a test is a guess
+- One bug, one fix, one commit. Do not bundle unrelated changes.
+- If the root cause spans multiple files, explain the chain in the commit message

package/dist/prompts/commands/init-project.md

@@ -0,0 +1,55 @@
+---
+description: "Initialize planning for an existing project"
+---
+
+# /init-project
+
+Initialize planning framework for an existing project: codebase mapping → questioning → domain model → requirements → roadmap.
+
+## Usage
+```
+/init-project [focus area or goal]
+```
+
+Focus: $ARGUMENTS
+
+Use this when you have an existing codebase and want to add structured planning.
+For greenfield projects, use `/new-project` instead.
+
+## Steps
+1. Run `draht-tools init` to check preconditions (git repo, etc.)
+2. Run `draht-tools map-codebase` to build a structural map of the existing code
+3. Analyze the codebase map to understand architecture, tech stack, and conventions
+4. Deep questioning phase (3-7 rounds, 1-2 questions at a time):
+   - What is this project? Who uses it?
+   - What are the current pain points or goals?
+   - What is MVP vs aspirational scope?
+   - What constraints exist (infra, team size, deadlines)?
+5. Run `draht-tools create-project` with gathered info
+6. Run `draht-tools create-domain-model` to define bounded contexts, entities, and ubiquitous language
+7. Create `.planning/DOMAIN.md` with:
+   - `## Bounded Contexts` — each context with name, responsibility, and brief description
+   - `## Ubiquitous Language` — glossary of domain terms agreed with the user (term → definition)
+   - `## Context Map` — how bounded contexts relate to each other (upstream/downstream, shared kernel, ACL)
+   - `## Aggregates` — aggregates and their root entities per context
+   - `## Domain Events` — named events that cross context boundaries
+8. Create `.planning/TEST-STRATEGY.md` with:
+   - `## Test Framework` — chosen framework and rationale
+   - `## Directory Conventions` — where test files live relative to source
+   - `## Coverage Goals` — target coverage percentage and which paths are critical
+   - `## Testing Levels` — what is tested at unit level vs integration vs e2e, with examples
+   - `## Excluded` — what is explicitly not tested and why (config files, generated code, etc.)
+9. Optional research phase via `draht-tools research`
+10. Run `draht-tools create-requirements` with v1/v2/out-of-scope (map requirements to bounded contexts)
+11. Run `draht-tools create-roadmap` with phases
+12. Run `draht-tools init-state`
+13. Git commit via `draht-tools commit-docs "initialize project planning"`
+
+## Rules
+- Ask 1-2 questions at a time, never dump 10 at once
+- Follow threads based on answers
+- Use examples ("Like Stripe Checkout, or custom?")
+- Confirm, don't assume
+- 3-7 follow-up rounds typical
+- Respect what already exists — do not propose rewriting working code
+- Stop when you have: current state, goals, MVP scope, constraints, success criteria

package/dist/prompts/commands/map-codebase.md

@@ -1,3 +1,7 @@
+---
+description: "Analyze existing codebase before planning"
+---
+
 # /map-codebase
 
 Analyze existing codebase before planning.
@@ -7,8 +11,10 @@ Analyze existing codebase before planning.
 /map-codebase [directory]
 ```
 
+Directory: $1
+
 ## Steps
-1. Run `draht-tools map-codebase [dir]`
+1. Run `draht-tools map-codebase $1`
 2. Tool generates: STACK.md, ARCHITECTURE.md, CONVENTIONS.md, CONCERNS.md
 3. Review output, supplement with your own analysis if needed
 4. Identify implicit bounded contexts from directory structure:

package/dist/prompts/commands/new-project.md

@@ -1,12 +1,18 @@
+---
+description: "Initialize a new project with structured planning"
+---
+
 # /new-project
 
-Initialize a new GSD project: questioning → research → requirements → roadmap.
+Initialize a new project: questioning → research → requirements → roadmap.
 
 ## Usage
 ```
 /new-project [description]
 ```
 
+Description: $ARGUMENTS
+
 ## Steps
 1. Run `draht-tools init` to check preconditions
 2. If existing code detected, run `draht-tools map-codebase` first
@@ -29,7 +35,7 @@ Initialize a new GSD project: questioning → research → requirements → road
 9. Run `draht-tools create-requirements` with v1/v2/out-of-scope (map requirements to bounded contexts)
 10. Run `draht-tools create-roadmap` with phases
 11. Run `draht-tools init-state`
-12. Git commit via `draht-tools commit-docs "initialize GSD project"`
+12. Git commit via `draht-tools commit-docs "initialize project planning"`
 
 ## Rules
 - Ask 1-2 questions at a time, never dump 10 at once

package/dist/prompts/commands/next-milestone.md

@@ -0,0 +1,48 @@
+---
+description: "Plan the next milestone after current one completes"
+---
+
+# /next-milestone
+
+Plan the next milestone after the current one is complete.
+
+## Usage
+```
+/next-milestone
+```
+
+## Prerequisites
+- `.planning/ROADMAP.md` must exist
+- Current milestone should be complete or nearly complete
+
+## Steps
+1. Load project context:
+   - Read `.planning/ROADMAP.md` — identify the completed milestone and its phases
+   - Read `.planning/STATE.md` — understand current status
+   - Read `.planning/REQUIREMENTS.md` — check which requirements are satisfied
+   - Read `.planning/DOMAIN.md` (if exists) — review domain model for evolution needs
+2. Review completed work:
+   - Scan `.planning/phases/` for all UAT reports (`*-UAT.md`) and summaries (`*-SUMMARY.md`)
+   - Note what was built, what worked well, what had issues
+3. Assess requirements:
+   - Which v1 requirements are now satisfied?
+   - Which v1 requirements remain?
+   - Should any v2 requirements be promoted based on what we learned?
+   - Are there new requirements discovered during implementation?
+4. Propose next milestone:
+   - Define 3-5 phases, each with a clear goal (outcome, not activity)
+   - Order phases by dependency
+   - Map each phase to specific requirements
+   - Estimate relative complexity
+5. Present the proposed milestone for user approval before writing files
+6. After approval:
+   - Update `ROADMAP.md` with the new milestone and phases
+   - Update `STATE.md` to reflect milestone transition
+   - Update `REQUIREMENTS.md` if requirements changed
+   - Update `DOMAIN.md` if domain model needs evolution
+   - Commit: `draht-tools commit-docs "plan next milestone"`
+
+## Rules
+- Always review what was actually built, not just what was planned
+- Be honest about requirements that slipped or changed scope
+- Each phase goal must be testable — "user can X" not "implement Y"

package/dist/prompts/commands/pause-work.md

@@ -1,3 +1,7 @@
+---
+description: "Create a handoff document for session continuity"
+---
+
 # /pause-work
 
 Create a handoff document for session continuity.

package/dist/prompts/commands/plan-phase.md

@@ -1,3 +1,7 @@
+---
+description: "Create atomic execution plans for a roadmap phase"
+---
+
 # /plan-phase
 
 Create atomic execution plans for a roadmap phase.
@@ -7,18 +11,20 @@ Create atomic execution plans for a roadmap phase.
 /plan-phase [N]
 ```
 
+Phase: $1
+
 ## Steps
-1. Run `draht-tools load-phase-context N` to gather all context
-2. Optional: `draht-tools research-phase N` for domain research
+1. Run `draht-tools load-phase-context $1` to gather all context
+2. Optional: `draht-tools research-phase $1` for domain research
 3. Goal-backward planning:
    a. State the goal (outcome, not activity)
    b. Derive observable truths (3-7 from user perspective)
    c. From each observable truth, derive the test scenarios that would prove it (specific inputs → expected outputs or state changes)
    d. Map to required artifacts (files, endpoints, schemas)
    e. Break into atomic tasks (2-5 per plan)
-4. Write plans: `draht-tools create-plan N P`
-5. Validate: `draht-tools validate-plans N`
-6. Commit: `draht-tools commit-docs "create phase N plans"`
+4. Write plans: `draht-tools create-plan $1 P`
+5. Validate: `draht-tools validate-plans $1`
+6. Commit: `draht-tools commit-docs "create phase $1 plans"`
 
 ## Plan Format
 Plans use XML task format:

package/dist/prompts/commands/progress.md

@@ -1,3 +1,7 @@
+---
+description: "Show current project status"
+---
+
 # /progress
 
 Show current project status.

package/dist/prompts/commands/quick.md

@@ -1,15 +1,21 @@
+---
+description: "Execute a small ad-hoc task with tracking"
+---
+
 # /quick
 
-Execute a small ad-hoc task with GSD tracking.
+Execute a small ad-hoc task with tracking.
 
 ## Usage
 ```
 /quick [description]
 ```
 
+Task: $ARGUMENTS
+
 ## Steps
 1. Run `draht-tools next-quick-number` to get task number
-2. Create quick plan: `draht-tools create-quick-plan NNN "description"`
+2. Create quick plan: `draht-tools create-quick-plan NNN "$ARGUMENTS"`
 3. Execute tasks following the TDD cycle:
    - **🔴 RED** — Write a failing test that describes the desired behaviour
    - **🟢 GREEN** — Write the minimum implementation to make it pass

package/dist/prompts/commands/resume-work.md

@@ -1,3 +1,7 @@
+---
+description: "Resume from last session state"
+---
+
 # /resume-work
 
 Resume from last session state.

package/dist/prompts/commands/review.md

@@ -0,0 +1,32 @@
+---
+description: "Code review and security audit of recent changes"
+---
+
+# /review
+
+Ad-hoc code review and security audit of recent changes or a specific scope.
+
+## Usage
+```
+/review [scope]
+```
+
+Scope: $ARGUMENTS
+
+If no scope given, reviews all recent uncommitted changes.
+
+## Steps
+1. Identify the scope:
+   - If argument given: review those files/directories/description
+   - If no argument: run `git diff --stat` and `git diff --cached --stat` to find changes
+2. For each changed file, examine:
+   - Correctness: logic errors, off-by-one, null handling, error paths
+   - Type safety: any `as` casts, `any` types, missing null checks
+   - Conventions: naming, file organization, import style
+   - Security: injection risks, auth bypasses, secrets in code, unsafe deserialization
+   - Performance: unnecessary allocations, missing indexes, N+1 queries
+3. Produce a prioritized findings report:
+   - **Critical** — must fix before merge (security, data loss, crashes)
+   - **Important** — should fix (bugs, type issues, missing error handling)
+   - **Minor** — style, naming, or optional improvements
+4. For each finding: cite the exact file and line, explain the issue, suggest the fix

package/dist/prompts/commands/verify-work.md

@@ -1,3 +1,7 @@
+---
+description: "Acceptance testing of completed phase work"
+---
+
 # /verify-work
 
 Walk through acceptance testing of completed phase work.
@@ -7,6 +11,8 @@ Walk through acceptance testing of completed phase work.
 /verify-work [N]
 ```
 
+Phase: $1
+
 ## Steps
 1. Run full test suite and capture results:
    - Execute all tests (`bun test` or project-specific runner)
@@ -16,12 +22,12 @@ Walk through acceptance testing of completed phase work.
    - Scan source files for PascalCase identifiers not present in the glossary
    - Flag any bounded context boundary violations (cross-context direct imports)
 3. Run quality gate: `draht-tools quality-gate --strict`
-4. Run `draht-tools extract-deliverables N` to get testable items
+4. Run `draht-tools extract-deliverables $1` to get testable items
 5. Walk user through each deliverable one at a time
 6. Record results (pass/fail/partially/skip)
-7. For failures: diagnose and create fix plans via `draht-tools create-fix-plan N P`
+7. For failures: diagnose and create fix plans via `draht-tools create-fix-plan $1 P`
    - Fix plans MUST include a reproducing test that demonstrates the failure before any implementation
-8. Write UAT report: `draht-tools write-uat N`
+8. Write UAT report: `draht-tools write-uat $1`
    - Report must include: test health summary (pass/fail/coverage), domain model status (any glossary violations), deliverable results
 9. If all passed: mark phase complete
-10. If failures: route to `execute-phase N --gaps-only`
+10. If failures: route to `execute-phase $1 --gaps-only`

package/docs/custom-provider.md

@@ -172,10 +172,17 @@ models: [{
   // ...
   compat: {
     supportsDeveloperRole: false,      // use "system" instead of "developer"
-    supportsReasoningEffort: false,    // disable reasoning_effort param
+    supportsReasoningEffort: true,
+    reasoningEffortMap: {              // map pi-ai levels to provider values
+      minimal: "default",
+      low: "default",
+      medium: "default",
+      high: "default",
+      xhigh: "default"
+    },
     maxTokensField: "max_tokens",      // instead of "max_completion_tokens"
     requiresToolResultName: true,      // tool results need name field
-    requiresMistralToolIds: true       // tool IDs must be 9 alphanumeric chars
+    requiresMistralToolIds: true,
     thinkingFormat: "qwen"             // uses enable_thinking: true
   }
 }]
@@ -568,6 +575,7 @@ interface ProviderModelConfig {
     supportsStore?: boolean;
     supportsDeveloperRole?: boolean;
     supportsReasoningEffort?: boolean;
+    reasoningEffortMap?: Partial<Record<"minimal" | "low" | "medium" | "high" | "xhigh", string>>;
     supportsUsageInStreaming?: boolean;
     maxTokensField?: "max_completion_tokens" | "max_tokens";
     requiresToolResultName?: boolean;

package/docs/extensions.md

@@ -880,6 +880,14 @@ Subscribe to events. See [Events](#events) for event types and return values.
 
 Register a custom tool callable by the LLM. See [Custom Tools](#custom-tools) for full details.
 
+`pi.registerTool()` works both during extension load and after startup. You can call it inside `session_start`, command handlers, or other event handlers. New tools are refreshed immediately in the same session, so they appear in `pi.getAllTools()` and are callable by the LLM without `/reload`.
+
+Use `pi.setActiveTools()` to enable or disable tools (including dynamically added tools) at runtime.
+
+Use `promptSnippet` to customize that tool's one-line entry in `Available tools`, and `promptGuidelines` to append tool-specific bullets to the default `Guidelines` section when the tool is active.
+
+See [dynamic-tools.ts](../examples/extensions/dynamic-tools.ts) for a full example.
+
 ```typescript
 import { Type } from "@sinclair/typebox";
 import { StringEnum } from "@draht/ai";
@@ -888,6 +896,8 @@ pi.registerTool({
   name: "my_tool",
   label: "My Tool",
   description: "What this tool does",
+  promptSnippet: "Summarize or transform text according to action",
+  promptGuidelines: ["Use this tool when the user asks to summarize previously generated text."],
   parameters: Type.Object({
     action: StringEnum(["list", "add"] as const),
     text: Type.Optional(Type.String()),
@@ -1116,7 +1126,7 @@ const result = await pi.exec("git", ["status"], { signal, timeout: 5000 });
 
 ### pi.getActiveTools() / pi.getAllTools() / pi.setActiveTools(names)
 
-Manage active tools.
+Manage active tools. This works for both built-in tools and dynamically registered tools.
 
 ```typescript
 const active = pi.getActiveTools();  // ["read", "bash", "edit", "write"]
@@ -1276,6 +1286,10 @@ export default function (pi: ExtensionAPI) {
 
 Register tools the LLM can call via `pi.registerTool()`. Tools appear in the system prompt and can have custom rendering.
 
+Use `promptSnippet` for a short one-line entry in the `Available tools` section in the default system prompt. If omitted, pi falls back to `description`.
+
+Use `promptGuidelines` to add tool-specific bullets to the default system prompt `Guidelines` section. These bullets are included only while the tool is active (for example, after `pi.setActiveTools([...])`).
+
 Note: Some models are idiots and include the @ prefix in tool path arguments. Built-in tools strip a leading @ before resolving paths. If your custom tool accepts a path, normalize a leading @ as well.
 
 ### Tool Definition
@@ -1289,6 +1303,10 @@ pi.registerTool({
   name: "my_tool",
   label: "My Tool",
   description: "What this tool does (shown to LLM)",
+  promptSnippet: "List or add items in the project todo list",
+  promptGuidelines: [
+    "Use this tool for todo planning instead of direct file edits when the user asks for a task list."
+  ],
   parameters: Type.Object({
     action: StringEnum(["list", "add"] as const),  // Use StringEnum for Google compatibility
     text: Type.Optional(Type.String()),
@@ -1886,6 +1904,7 @@ All examples in [examples/extensions/](../examples/extensions/).
 | `question.ts` | Tool with user interaction | `registerTool`, `ui.select` |
 | `questionnaire.ts` | Multi-step wizard tool | `registerTool`, `ui.custom` |
 | `todo.ts` | Stateful tool with persistence | `registerTool`, `appendEntry`, `renderResult`, session events |
+| `dynamic-tools.ts` | Register tools after startup and during commands | `registerTool`, `session_start`, `registerCommand` |
 | `truncated-tool.ts` | Output truncation example | `registerTool`, `truncateHead` |
 | `tool-override.ts` | Override built-in read tool | `registerTool` (same name as built-in) |
 | **Commands** |||

package/docs/providers.md

@@ -65,6 +65,7 @@ pi
 | Vercel AI Gateway | `AI_GATEWAY_API_KEY` | `vercel-ai-gateway` |
 | ZAI | `ZAI_API_KEY` | `zai` |
 | OpenCode Zen | `OPENCODE_API_KEY` | `opencode` |
+| OpenCode Go | `OPENCODE_API_KEY` | `opencode-go` |
 | Hugging Face | `HF_TOKEN` | `huggingface` |
 | Kimi For Coding | `KIMI_API_KEY` | `kimi-coding` |
 | MiniMax | `MINIMAX_API_KEY` | `minimax` |
@@ -81,7 +82,8 @@ Store credentials in `~/.pi/agent/auth.json`:
   "anthropic": { "type": "api_key", "key": "sk-ant-..." },
   "openai": { "type": "api_key", "key": "sk-..." },
   "google": { "type": "api_key", "key": "..." },
-  "opencode": { "type": "api_key", "key": "..." }
+  "opencode": { "type": "api_key", "key": "..." },
+  "opencode-go": { "type": "api_key", "key": "..." }
 }
 ```
 

package/docs/settings.md

@@ -69,6 +69,7 @@ Edit directly or use `/settings` for common options.
 | Setting | Type | Default | Description |
 |---------|------|---------|-------------|
 | `branchSummary.reserveTokens` | number | `16384` | Tokens reserved for branch summarization |
+| `branchSummary.skipPrompt` | boolean | `false` | Skip "Summarize branch?" prompt on `/tree` navigation (defaults to no summary) |
 
 ### Retry
 

package/examples/extensions/README.md

@@ -33,6 +33,7 @@ cp permission-gate.ts ~/.draht/agent/extensions/
 | `question.ts` | Demonstrates `ctx.ui.select()` for asking the user questions with custom UI |
 | `questionnaire.ts` | Multi-question input with tab bar navigation between questions |
 | `tool-override.ts` | Override built-in tools (e.g., add logging/access control to `read`) |
+| `dynamic-tools.ts` | Register tools after startup (`session_start`) and at runtime via command, with prompt snippets and tool-specific prompt guidelines |
 | `built-in-tool-renderer.ts` | Custom compact rendering for built-in tools (read, bash, edit, write) while keeping original behavior |
 | `minimal-mode.ts` | Override built-in tool rendering for minimal display (only tool calls, no output in collapsed mode) |
 | `truncated-tool.ts` | Wraps ripgrep with proper output truncation (50KB/2000 lines) |

package/examples/extensions/antigravity-image-gen.ts

@@ -49,8 +49,10 @@ type SaveMode = (typeof SAVE_MODES)[number];
 
 const ANTIGRAVITY_ENDPOINT = "https://daily-cloudcode-pa.sandbox.googleapis.com";
 
+const DEFAULT_ANTIGRAVITY_VERSION = "1.18.3";
+
 const ANTIGRAVITY_HEADERS = {
-	"User-Agent": "antigravity/1.15.8 darwin/arm64",
+	"User-Agent": `antigravity/${process.env.PI_AI_ANTIGRAVITY_VERSION || DEFAULT_ANTIGRAVITY_VERSION} darwin/arm64`,
 	"X-Goog-Api-Client": "google-cloud-sdk vscode_cloudshelleditor/0.1",
 	"Client-Metadata": JSON.stringify({
 		ideType: "IDE_UNSPECIFIED",

package/examples/extensions/custom-provider-anthropic/package-lock.json

@@ -1,12 +1,12 @@
 {
   "name": "pi-extension-custom-provider",
-  "version": "1.6.3",
+  "version": "1.7.0",
   "lockfileVersion": 3,
   "requires": true,
   "packages": {
     "": {
       "name": "pi-extension-custom-provider",
-      "version": "1.6.3",
+      "version": "1.7.0",
       "dependencies": {
         "@anthropic-ai/sdk": "^0.52.0"
       }

package/examples/extensions/custom-provider-anthropic/package.json

@@ -1,7 +1,7 @@
 {
   "name": "pi-extension-custom-provider-anthropic",
   "private": true,
-  "version": "1.6.3",
+  "version": "1.7.0",
   "type": "module",
   "scripts": {
     "clean": "echo 'nothing to clean'",

package/examples/extensions/custom-provider-gitlab-duo/package.json

@@ -1,7 +1,7 @@
 {
   "name": "pi-extension-custom-provider-gitlab-duo",
   "private": true,
-  "version": "1.6.3",
+  "version": "1.7.0",
   "type": "module",
   "scripts": {
     "clean": "echo 'nothing to clean'",

package/examples/extensions/custom-provider-qwen-cli/package.json

@@ -1,7 +1,7 @@
 {
   "name": "pi-extension-custom-provider-qwen-cli",
   "private": true,
-  "version": "1.5.3",
+  "version": "1.6.0",
   "type": "module",
   "scripts": {
     "clean": "echo 'nothing to clean'",