wave-agent-sdk 0.11.0 → 0.11.2

package/src/prompts/index.ts

@@ -9,16 +9,14 @@ import {
 } from "../constants/subagents.js";
 import {
   ASK_USER_QUESTION_TOOL_NAME,
-  BASH_TOOL_NAME,
   EDIT_TOOL_NAME,
-  GLOB_TOOL_NAME,
-  GREP_TOOL_NAME,
-  READ_TOOL_NAME,
   WRITE_TOOL_NAME,
   EXIT_PLAN_MODE_TOOL_NAME,
   AGENT_TOOL_NAME,
 } from "../constants/tools.js";
 
+export const MAX_PARALLEL_TOOL_CALLS = 3;
+
 export const BASE_SYSTEM_PROMPT = `You are an interactive CLI tool that helps users with software engineering tasks. Use the instructions below and the tools available to you to assist the user.
 
 # Doing tasks
@@ -34,6 +32,7 @@ The user will primarily request you perform software engineering tasks. This inc
 export const TOOL_POLICY = `
 # Tool usage policy
 - You can call multiple tools in a single response. If you intend to call multiple tools and there are no dependencies between them, make all independent tool calls in parallel. Maximize use of parallel tool calls where possible to increase efficiency.
+- **Limit**: You MUST NOT call more than ${MAX_PARALLEL_TOOL_CALLS} tools in parallel in a single response.
 - However, if some tool calls depend on previous calls to inform dependent values, do NOT call these tools in parallel and instead call them sequentially. For instance, if one operation must complete before another starts, run these operations sequentially instead. Never use placeholders or guess missing parameters in tool calls.
 - If the user specifies that they want you to run tools "in parallel", you MUST send a single message with multiple tool use content blocks.`;
 
@@ -128,146 +127,6 @@ NOTE: At any point in time through this workflow you should feel free to ask the
 
 export const DEFAULT_SYSTEM_PROMPT = BASE_SYSTEM_PROMPT;
 
-export const BASH_SUBAGENT_SYSTEM_PROMPT = `You are a command execution specialist. Your role is to execute bash commands efficiently and safely.
-
-Guidelines:
-- Execute commands precisely as instructed
-- For git operations, follow git safety protocols
-- Report command output clearly and concisely
-- If a command fails, explain the error and suggest solutions
-- Use command chaining (&&) for dependent operations
-- Quote paths with spaces properly
-- For clear communication, avoid using emojis
-
-Complete the requested operations efficiently.`;
-
-export const GENERAL_PURPOSE_SYSTEM_PROMPT = `You are an agent. Given the user's message, you should use the tools available to complete the task. Do what has been asked; nothing more, nothing less. When you complete the task simply respond with a detailed writeup.
-
-Your strengths:
-- Searching for code, configurations, and patterns across large codebases
-- Analyzing multiple files to understand system architecture
-- Investigating complex questions that require exploring many files
-- Performing multi-step research tasks
-
-Guidelines:
-- For file searches: Use ${GREP_TOOL_NAME} or ${GLOB_TOOL_NAME} when you need to search broadly. Use ${READ_TOOL_NAME} when you know the specific file path.
-- For analysis: Start broad and narrow down. Use multiple search strategies if the first doesn't yield results.
-- Be thorough: Check multiple locations, consider different naming conventions, look for related files.
-- NEVER create files unless they're absolutely necessary for achieving your goal. ALWAYS prefer editing an existing file to creating a new one.
-- NEVER proactively create documentation files (*.md) or README files. Only create documentation files if explicitly requested.
-- In your final response always share relevant file names and code snippets. Any file paths you return in your response MUST be absolute. Do NOT use relative paths.
-- For clear communication, avoid using emojis.`;
-
-export const EXPLORE_SUBAGENT_SYSTEM_PROMPT = `You are a file search specialist. You excel at thoroughly navigating and exploring codebases.
-	
-	=== CRITICAL: READ-ONLY MODE - NO FILE MODIFICATIONS ===
-	This is a READ-ONLY exploration task. You are STRICTLY PROHIBITED from:
-	- Creating new files (no Write, touch, or file creation of any kind)
-	- Modifying existing files (no Edit operations)
-	- Moving or copying files (no mv or cp)
-	- Creating temporary files anywhere, including /tmp
-	- Using redirect operators (>, >>, |) or heredocs to write to files
-	- Running ANY commands that change system state
-	
-	Your role is EXCLUSIVELY to search and analyze existing code. You do NOT have access to file editing tools - attempting to edit files will fail.
-	
-	Your strengths:
-	- Rapidly finding files using glob patterns
-	- Searching code and text with powerful regex patterns
-	- Reading and analyzing file contents
-	- Using Language Server Protocol (LSP) for deep code intelligence (definitions, references, etc.)
-	
-	Guidelines:
-	- Use ${GLOB_TOOL_NAME} for broad file pattern matching
-	- Use ${GREP_TOOL_NAME} for searching file contents with regex
-	- Use ${READ_TOOL_NAME} when you know the specific file path you need to read
-	- Use LSP for code intelligence features like finding definitions, references, implementations, and symbols. This is especially useful for understanding complex code relationships.
-	- Use ${BASH_TOOL_NAME} ONLY for read-only operations (ls, git status, git log, git diff, find, cat, head, tail)
-	- NEVER use ${BASH_TOOL_NAME} for: mkdir, touch, rm, cp, mv, git add, git commit, npm install, pip install, or any file creation/modification
-	- Adapt your search approach based on the thoroughness level specified by the caller
-	- Return file paths as absolute paths in your final response
-	- For clear communication, avoid using emojis
-	- Communicate your final report directly as a regular message - do NOT attempt to create files
-	
-	NOTE: You are meant to be a fast agent that returns output as quickly as possible. In order to achieve this you must:
-	- Make efficient use of the tools that you have at your disposal: be smart about how you search for files and implementations
-	- Wherever possible you should try to spawn multiple parallel tool calls for grepping and reading files
-	
-	Complete the user's search request efficiently and report your findings clearly.`;
-
-export const PLAN_SUBAGENT_SYSTEM_PROMPT = `You are a software architect and planning specialist. Your role is to explore the codebase and design implementation plans.
-
-=== CRITICAL: READ-ONLY MODE - NO FILE MODIFICATIONS ===
-This is a READ-ONLY planning task. You are STRICTLY PROHIBITED from:
-- Creating new files (no Write, touch, or file creation of any kind)
-- Modifying existing files (no Edit operations)
-- Moving or copying files (no mv or cp)
-- Creating temporary files anywhere, including /tmp
-- Using redirect operators (>, >>, |) or heredocs to write to files
-- Running ANY commands that change system state
-
-Your role is EXCLUSIVELY to explore the codebase and design implementation plans. You do NOT have access to file editing tools - attempting to edit files will fail.
-
-You will be provided with a set of requirements and optionally a perspective on how to approach the design process.
-
-## Your Process
-
-1. **Understand Requirements**: Focus on the requirements provided and apply your assigned perspective throughout the design process.
-
-2. **Explore Thoroughly**:
-   - Read any files provided to you in the initial prompt
-   - Find existing patterns and conventions using ${GLOB_TOOL_NAME}, ${GREP_TOOL_NAME}, and ${READ_TOOL_NAME}
-   - Understand the current architecture
-   - Identify similar features as reference
-   - Trace through relevant code paths
-   - Use ${BASH_TOOL_NAME} ONLY for read-only operations (ls, git status, git log, git diff, find, cat, head, tail)
-   - NEVER use ${BASH_TOOL_NAME} for: mkdir, touch, rm, cp, mv, git add, git commit, npm install, pip install, or any file creation/modification
-
-3. **Design Solution**:
-   - Create implementation approach based on your assigned perspective
-   - Consider trade-offs and architectural decisions
-   - Follow existing patterns where appropriate
-
-4. **Detail the Plan**:
-   - Provide step-by-step implementation strategy
-   - Identify dependencies and sequencing
-   - Anticipate potential challenges
-
-## Required Output
-
-End your response with:
-
-### Critical Files for Implementation
-List 3-5 files most critical for implementing this plan:
-- path/to/file1.ts - [Brief reason: e.g., "Core logic to modify"]
-- path/to/file2.ts - [Brief reason: e.g., "Interfaces to implement"]
-- path/to/file3.ts - [Brief reason: e.g., "Pattern to follow"]
-
-REMEMBER: You can ONLY explore and plan. You CANNOT and MUST NOT write, edit, or modify any files. You do NOT have access to file editing tools.`;
-
-export const INIT_PROMPT = `Please analyze this codebase and create a AGENTS.md file, which will be given to future instances of Agent to operate in this repository.
-
-What to add:
-1. Commands that will be commonly used, such as how to build, lint, and run tests. Include the necessary commands to develop in this codebase, such as how to run a single test.
-2. High-level code architecture and structure so that future instances can be productive more quickly. Focus on the "big picture" architecture that requires reading multiple files to understand.
-
-Usage notes:
-- If there's already a AGENTS.md, suggest improvements to it.
-- When you make the initial AGENTS.md, do not repeat yourself and do not include obvious instructions like "Provide helpful error messages to users", "Write unit tests for all new utilities", "Never include sensitive information (API keys, tokens) in code or commits".
-- Avoid listing every component or file structure that can be easily discovered.
-- Don't include generic development practices.
-- If there are Cursor rules (in .cursor/rules/ or .cursorrules) or Copilot rules (in .github/copilot-instructions.md), make sure to include the important parts.
-- Do NOT include rules from .wave/rules/ as they are automatically loaded by the system.
-- If there is a README.md, make sure to include the important parts.
-- Do not make up information such as "Common Development Tasks", "Tips for Development", "Support and Documentation" unless this is expressly included in other files that you read.
-- Be sure to prefix the file with the following text:
-
-\`\`\`
-# AGENTS.md
-
-This file provides guidance to Agent when working with code in this repository.
-\`\`\``;
-
 export const COMPRESS_MESSAGES_SYSTEM_PROMPT = `You have been working on the task described above but have not yet completed it. Write a continuation summary that will allow you (or another instance of yourself) to resume work efficiently in a future context window where the conversation history will be replaced with this summary. Your summary should be structured, concise, and actionable. Include:
 1. Task Overview
 The user's core request and success criteria

package/src/tools/bashTool.ts

@@ -45,6 +45,20 @@ function processOutput(output: string): string {
   }
 }
 
+/**
+ * Simple throttle function to limit the frequency of updates.
+ */
+function throttle(func: () => void, limit: number) {
+  let inThrottle: boolean;
+  return function () {
+    if (!inThrottle) {
+      func();
+      inThrottle = true;
+      setTimeout(() => (inThrottle = false), limit);
+    }
+  };
+}
+
 /**
  * Bash command execution tool - supports both foreground and background execution
  */
@@ -232,6 +246,35 @@ Usage notes:
       let errorBuffer = "";
       let isAborted = false;
       let isBackgrounded = false;
+      let isFinished = false;
+
+      const updateRealtimeResults = throttle(() => {
+        if (isAborted || isBackgrounded || isFinished) return;
+
+        const combinedOutput =
+          outputBuffer + (errorBuffer ? "\n" + errorBuffer : "");
+
+        // Update shortResult: last 3 lines
+        if (context.onShortResultUpdate) {
+          const tail = combinedOutput.slice(-5000);
+          const lines = tail.trim().split("\n");
+          const shortResult =
+            lines.length <= 3
+              ? lines.join("\n")
+              : `... +${lines.length - 3} lines\n` + lines.slice(-3).join("\n");
+          context.onShortResultUpdate(shortResult);
+        }
+
+        // Update full result
+        if (context.onResultUpdate) {
+          const content =
+            combinedOutput.length <= MAX_OUTPUT_LENGTH
+              ? combinedOutput
+              : combinedOutput.substring(0, MAX_OUTPUT_LENGTH) +
+                "\n\n... (output truncated)";
+          context.onResultUpdate(content);
+        }
+      }, 1000);
 
       const foregroundTaskId = `bash_${Date.now()}_${Math.random().toString(36).substr(2, 9)}`;
 
@@ -346,6 +389,7 @@ Usage notes:
         if (!isAborted && !isBackgrounded && !runInBackground) {
           const chunk = stripAnsiColors(data.toString());
           outputBuffer += chunk;
+          updateRealtimeResults();
         }
       });
 
@@ -353,10 +397,12 @@ Usage notes:
         if (!isAborted && !isBackgrounded && !runInBackground) {
           const chunk = stripAnsiColors(data.toString());
           errorBuffer += chunk;
+          updateRealtimeResults();
         }
       });
 
       child.on("exit", (code) => {
+        isFinished = true;
         if (context.foregroundTaskManager) {
           context.foregroundTaskManager.unregisterForegroundTask(
             foregroundTaskId,
@@ -381,8 +427,7 @@ Usage notes:
           const shortResult =
             lines.length <= 3
               ? lines.join("\n")
-              : lines.slice(0, 3).join("\n") +
-                `\n... +${lines.length - 3} lines`;
+              : `... +${lines.length - 3} lines\n` + lines.slice(-3).join("\n");
 
           resolve({
             success: exitCode === 0,
@@ -397,6 +442,7 @@ Usage notes:
       });
 
       child.on("error", (error) => {
+        isFinished = true;
         if (context.foregroundTaskManager) {
           context.foregroundTaskManager.unregisterForegroundTask(
             foregroundTaskId,

package/src/tools/types.ts

@@ -87,4 +87,6 @@ export interface ToolContext {
   toolCallId?: string;
   /** Callback to update the short result of the current tool block */
   onShortResultUpdate?: (shortResult: string) => void;
+  /** Callback to update the full result of the current tool block */
+  onResultUpdate?: (result: string) => void;
 }

package/src/utils/configPaths.ts

@@ -22,16 +22,18 @@ const __dirname = dirname(__filename);
  * Get the builtin skills directory path
  */
 export function getBuiltinSkillsDir(): string {
-  // In development, it's in src/builtin-skills
-  // In production (dist), it should be in dist/builtin-skills
-  // We'll look for it relative to this file
-  const devPath = join(__dirname, "..", "builtin-skills");
-  const prodPath = join(__dirname, "builtin-skills");
-
-  if (existsSync(devPath)) {
-    return devPath;
-  }
-  return prodPath;
+  // Builtin skills are now in the 'builtin/skills' directory at the root of the package
+  // Relative to this file (src/utils/configPaths.ts), it's ../../builtin/skills
+  return join(__dirname, "..", "..", "builtin", "skills");
+}
+
+/**
+ * Get the builtin subagents directory path
+ */
+export function getBuiltinSubagentsDir(): string {
+  // Builtin subagents are now in the 'builtin/subagents' directory at the root of the package
+  // Relative to this file (src/utils/configPaths.ts), it's ../../builtin/subagents
+  return join(__dirname, "..", "..", "builtin", "subagents");
 }
 
 /**

package/src/utils/fileSearch.ts

@@ -4,6 +4,8 @@ import fuzzysort from "fuzzysort";
 import type { FileItem } from "../types/fileSearch.js";
 import { logger } from "./globalLogger.js";
 
+const EXCLUDED_FILES = [".git", ".DS_Store"];
+
 /**
  * Execute ripgrep to get all file paths
  */
@@ -39,7 +41,11 @@ async function getAllFiles(workingDirectory: string): Promise<string[]> {
       const files = stdout
         .trim()
         .split("\n")
-        .filter((f) => f.length > 0)
+        .filter((f) => {
+          if (f.length === 0) return false;
+          const parts = f.split(/[/\\]/);
+          return !parts.some((part) => EXCLUDED_FILES.includes(part));
+        })
         .map((f) => f.replace(/\\/g, "/")); // Normalize to forward slashes
       resolve(files);
     });

package/src/utils/subagentParser.ts

@@ -1,6 +1,7 @@
 import { readFileSync, readdirSync, statSync } from "fs";
-import { join, extname } from "path";
+import { join, extname, basename } from "path";
 import { logger } from "./globalLogger.js";
+import { getBuiltinSubagentsDir } from "./configPaths.js";
 
 export interface SubagentConfiguration {
   name: string;
@@ -122,18 +123,27 @@ function validateConfiguration(
  */
 function parseSubagentFile(
   filePath: string,
-  scope: "project" | "user",
+  scope: "project" | "user" | "builtin",
 ): SubagentConfiguration {
   try {
     const content = readFileSync(filePath, "utf-8");
     const { frontmatter, body } = parseFrontmatter(content);
 
+    // Use filename as default name if not specified in frontmatter
+    if (!frontmatter.name) {
+      frontmatter.name = basename(filePath, extname(filePath));
+    }
+
     validateConfiguration(frontmatter, filePath);
 
     if (!body.trim()) {
       throw new Error(`Empty system prompt in ${filePath}`);
     }
 
+    let priority = 1;
+    if (scope === "user") priority = 2;
+    if (scope === "builtin") priority = 3;
+
     return {
       name: frontmatter.name!,
       description: frontmatter.description!,
@@ -142,7 +152,7 @@ function parseSubagentFile(
       systemPrompt: body,
       filePath,
       scope,
-      priority: scope === "project" ? 1 : 2,
+      priority,
     };
   } catch (error) {
     throw new Error(
@@ -156,7 +166,7 @@ function parseSubagentFile(
  */
 function scanSubagentDirectory(
   dirPath: string,
-  scope: "project" | "user",
+  scope: "project" | "user" | "builtin",
 ): SubagentConfiguration[] {
   const configurations: SubagentConfiguration[] = [];
 
@@ -194,10 +204,10 @@ export async function loadSubagentConfigurations(
 ): Promise<SubagentConfiguration[]> {
   const projectDir = join(workdir, ".wave", "agents");
   const userDir = join(process.env.HOME || "~", ".wave", "agents");
+  const builtinDir = getBuiltinSubagentsDir();
 
   // Load configurations from all sources
-  const { getBuiltinSubagents } = await import("./builtinSubagents.js");
-  const builtinConfigs = getBuiltinSubagents();
+  const builtinConfigs = scanSubagentDirectory(builtinDir, "builtin");
   const projectConfigs = scanSubagentDirectory(projectDir, "project");
   const userConfigs = scanSubagentDirectory(userDir, "user");
 

package/dist/builtin-skills/builtin-skills/loop/parsing.ts

@@ -1,159 +0,0 @@
-export interface ParsedLoop {
-  interval: string;
-  prompt: string;
-  originalInterval?: string;
-  roundedTo?: string;
-}
-
-export function parseLoopInput(
-  input: string,
-  defaultInterval: string = "10m",
-): ParsedLoop {
-  const trimmedInput = input.trim();
-  if (!trimmedInput) {
-    return { interval: defaultInterval, prompt: "" };
-  }
-
-  // 1. Leading token: ^\d+[smhd]$
-  const tokens = trimmedInput.split(/\s+/);
-  if (tokens[0].match(/^\d+[smhd]$/)) {
-    const interval = tokens[0];
-    const prompt = tokens.slice(1).join(" ");
-    return { interval, prompt };
-  }
-
-  // 2. Trailing "every" clause: every <N><unit> or every <N> <unit-word>
-  // Units: s, m, h, d, second(s), minute(s), hour(s), day(s)
-  const everyRegex =
-    /\s+every\s+(\d+)\s*(s|m|h|d|seconds?|minutes?|hours?|days?)$/i;
-  const match = trimmedInput.match(everyRegex);
-  if (match) {
-    const n = match[1];
-    const unitWord = match[2].toLowerCase();
-    const unit = unitWord[0];
-    const interval = `${n}${unit}`;
-    const prompt = trimmedInput.substring(0, match.index).trim();
-    return { interval, prompt };
-  }
-
-  // 3. Default
-  return { interval: defaultInterval, prompt: trimmedInput };
-}
-
-const CLEAN_MINUTES = [1, 2, 3, 4, 5, 6, 10, 12, 15, 20, 30];
-const CLEAN_HOURS = [1, 2, 3, 4, 6, 8, 12];
-
-function getNearestClean(value: number, cleanValues: number[]): number {
-  let nearest = cleanValues[0];
-  let minDiff = Math.abs(value - nearest);
-  for (const clean of cleanValues) {
-    const diff = Math.abs(value - clean);
-    if (diff < minDiff) {
-      minDiff = diff;
-      nearest = clean;
-    } else if (diff === minDiff) {
-      // If equal diff, prefer the larger one? Or smaller?
-      // Let's prefer the larger one to be less frequent
-      if (clean > nearest) {
-        nearest = clean;
-      }
-    }
-  }
-  return nearest;
-}
-
-export function intervalToCron(interval: string): {
-  cron: string;
-  roundedTo?: string;
-  cadence: string;
-} {
-  const match = interval.match(/^(\d+)([smhd])$/);
-  if (!match) {
-    throw new Error(`Invalid interval format: ${interval}`);
-  }
-
-  let n = parseInt(match[1], 10);
-  const unit = match[2];
-  let roundedTo: string | undefined;
-
-  if (unit === "s") {
-    const minutes = Math.ceil(n / 60);
-    const result = intervalToCron(`${minutes}m`);
-    return {
-      ...result,
-      roundedTo:
-        result.roundedTo || (minutes * 60 !== n ? `${minutes}m` : undefined),
-    };
-  }
-
-  if (unit === "m") {
-    if (n >= 60) {
-      const hours = Math.round(n / 60);
-      const result = intervalToCron(`${hours}h`);
-      return {
-        ...result,
-        roundedTo:
-          result.roundedTo || (hours * 60 !== n ? `${hours}h` : undefined),
-      };
-    }
-
-    if (!CLEAN_MINUTES.includes(n)) {
-      const nearest = getNearestClean(n, CLEAN_MINUTES);
-      roundedTo = `${nearest}m`;
-      n = nearest;
-    }
-
-    // For minutes, we use */N. Thundering herd is less of an issue for high frequency,
-    // but we could still offset it. However, the spec says "random minute for approximate requests like 'hourly'".
-    // So for minutes, we'll stick to */N.
-    return {
-      cron: `*/${n} * * * *`,
-      roundedTo,
-      cadence: `every ${n} minute${n > 1 ? "s" : ""}`,
-    };
-  }
-
-  if (unit === "h") {
-    if (n > 23) {
-      const days = Math.round(n / 24);
-      const result = intervalToCron(`${days}d`);
-      return {
-        ...result,
-        roundedTo:
-          result.roundedTo || (days * 24 !== n ? `${days}d` : undefined),
-      };
-    }
-
-    if (!CLEAN_HOURS.includes(n)) {
-      const nearest = getNearestClean(n, CLEAN_HOURS);
-      roundedTo = `${nearest}h`;
-      n = nearest;
-    }
-
-    // Thundering herd prevention: pick a random minute
-    const randomMinute = Math.floor(Math.random() * 60);
-    return {
-      cron: `${randomMinute} */${n} * * *`,
-      roundedTo,
-      cadence: `every ${n} hour${n > 1 ? "s" : ""}`,
-    };
-  }
-
-  if (unit === "d") {
-    if (![1, 2, 3, 4, 5, 6, 7, 10, 14, 30].includes(n)) {
-      // For days, we don't have a strict "clean" list in spec, but let's use some common ones if needed.
-      // Actually, cron supports any */N for days.
-    }
-
-    // Thundering herd prevention: pick a random minute and hour
-    const randomMinute = Math.floor(Math.random() * 60);
-    const randomHour = Math.floor(Math.random() * 24);
-    return {
-      cron: `${randomMinute} ${randomHour} */${n} * *`,
-      roundedTo,
-      cadence: `every ${n} day${n > 1 ? "s" : ""}`,
-    };
-  }
-
-  throw new Error(`Unsupported unit: ${unit}`);
-}

package/dist/builtin-skills/builtin-skills/settings/HOOKS.md

@@ -1,82 +0,0 @@
-# Wave Hooks Configuration
-
-Hooks allow you to automate tasks when certain events occur in Wave. This document provides detailed guidance on how to configure hooks in `settings.json`.
-
-## Hook Events
-
-Wave supports the following hook events:
-
-- `PreToolUse`: Triggered before a tool is executed.
-- `PostToolUse`: Triggered after a tool has finished executing.
-- `UserPromptSubmit`: Triggered when a user submits a prompt.
-- `PermissionRequest`: Triggered when Wave requests permission to use a tool.
-- `Stop`: Triggered when Wave finishes its response cycle (no more tool calls).
-- `SubagentStop`: Triggered when a subagent finishes its response cycle.
-- `WorktreeCreate`: Triggered when a new worktree is created.
-
-## Hook Configuration Structure
-
-Hooks are configured in the `hooks` field of `settings.json`. Each event can have multiple hook configurations.
-
-```json
-{
-  "hooks": {
-    "PreToolUse": [
-      {
-        "matcher": "Write",
-        "hooks": [
-          {
-            "command": "pnpm lint",
-            "description": "Run lint before writing files"
-          }
-        ]
-      }
-    ],
-    "PermissionRequest": [
-      {
-        "matcher": "Bash",
-        "hooks": [
-          {
-            "command": "echo \"Permission requested for Bash tool\" >> hooks.log",
-            "description": "Log permission requests for Bash"
-          }
-        ]
-      }
-    ]
-  }
-}
-```
-
-## Hook Configuration Fields
-
-- `matcher`: (Optional) A pattern to match against the tool name (e.g., "Write", "Read*", "/^Edit/"). Only applicable for `PreToolUse`, `PostToolUse`, and `PermissionRequest`.
-- `hooks`: An array of hook commands to execute.
-  - `command`: The shell command to execute.
-  - `description`: A brief description of the hook's purpose.
-  - `async`: (Optional) Whether the hook should run in the background without blocking (default: `false`).
-  - `timeout`: (Optional) Maximum execution time in seconds (default: `600`).
-
-## Hook Input JSON
-
-Wave provides detailed context to hook processes via `stdin` as a JSON object. This allows hooks to make informed decisions based on the current state.
-
-### Common Fields
-- `session_id`: The current session ID.
-- `transcript_path`: Path to the session transcript file (JSON).
-- `cwd`: The current working directory.
-- `hook_event_name`: The name of the triggering event.
-
-### Event-Specific Fields
-- `tool_name`: (PreToolUse, PostToolUse, PermissionRequest) The name of the tool.
-- `tool_input`: (PreToolUse, PostToolUse, PermissionRequest) The input parameters passed to the tool.
-- `tool_response`: (PostToolUse) The result of the tool execution.
-- `user_prompt`: (UserPromptSubmit) The text submitted by the user.
-- `subagent_type`: (If executed by a subagent) The type of the subagent.
-- `name`: (WorktreeCreate) The name of the new worktree.
-
-## Best Practices
-
-- **Keep hooks fast**: Long-running hooks can slow down your workflow unless they are `async`.
-- **Use descriptive names**: Help yourself and others understand what each hook does.
-- **Test your hooks**: Run the commands manually first to ensure they work as expected.
-- **Use local overrides**: For machine-specific hooks, use `.wave/settings.local.json`.