wave-agent-sdk 0.11.0 → 0.11.1

package/dist/prompts/index.js

@@ -2,7 +2,7 @@ import * as os from "node:os";
 import { isGitRepository } from "../utils/gitUtils.js";
 import { buildAutoMemoryPrompt } from "./autoMemory.js";
 import { EXPLORE_SUBAGENT_TYPE, PLAN_SUBAGENT_TYPE, } 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";
+import { ASK_USER_QUESTION_TOOL_NAME, EDIT_TOOL_NAME, WRITE_TOOL_NAME, EXIT_PLAN_MODE_TOOL_NAME, AGENT_TOOL_NAME, } from "../constants/tools.js";
 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
@@ -102,141 +102,6 @@ This is critical - your turn should only end with either using the ${ASK_USER_QU
 NOTE: At any point in time through this workflow you should feel free to ask the user questions or clarifications using the ${ASK_USER_QUESTION_TOOL_NAME} tool. Don't make large assumptions about user intent. The goal is to present a well researched plan to the user, and tie any loose ends before implementation begins.`;
 }
 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/dist/utils/configPaths.d.ts

@@ -13,6 +13,10 @@
  * Get the builtin skills directory path
  */
 export declare function getBuiltinSkillsDir(): string;
+/**
+ * Get the builtin subagents directory path
+ */
+export declare function getBuiltinSubagentsDir(): string;
 /**
  * Get the user-specific configuration file path (legacy function)
  * @deprecated Use getUserConfigPaths() for better priority support

package/dist/utils/configPaths.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"configPaths.d.ts","sourceRoot":"","sources":["../../src/utils/configPaths.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;GAUG;AAUH;;GAEG;AACH,wBAAgB,mBAAmB,IAAI,MAAM,CAW5C;AAED;;;GAGG;AACH,wBAAgB,iBAAiB,IAAI,MAAM,CAE1C;AAED;;;GAGG;AACH,wBAAgB,oBAAoB,CAAC,OAAO,EAAE,MAAM,GAAG,MAAM,CAE5D;AAED;;;GAGG;AACH,wBAAgB,kBAAkB,IAAI,MAAM,EAAE,CAG7C;AAED;;GAEG;AACH,wBAAgB,aAAa,IAAI,MAAM,CAEtC;AAED;;;GAGG;AACH,wBAAgB,qBAAqB,CAAC,OAAO,EAAE,MAAM,GAAG,MAAM,EAAE,CAG/D;AAED;;;GAGG;AACH,wBAAgB,iBAAiB,CAAC,OAAO,EAAE,MAAM,GAAG;IAClD,SAAS,EAAE,MAAM,EAAE,CAAC;IACpB,YAAY,EAAE,MAAM,EAAE,CAAC;IACvB,YAAY,EAAE,MAAM,EAAE,CAAC;IACvB,QAAQ,EAAE,MAAM,EAAE,CAAC;CACpB,CAWA;AAED;;;GAGG;AACH,wBAAgB,sBAAsB,CAAC,OAAO,EAAE,MAAM,GAAG;IACvD,SAAS,EAAE,MAAM,EAAE,CAAC;IACpB,YAAY,EAAE,MAAM,EAAE,CAAC;IACvB,YAAY,EAAE,MAAM,EAAE,CAAC;IACvB,aAAa,EAAE,MAAM,EAAE,CAAC;CACzB,CAcA;AAED;;;;GAIG;AACH,wBAAgB,oBAAoB,CAAC,KAAK,EAAE,MAAM,EAAE,GAAG,MAAM,GAAG,SAAS,CAExE;AAED;;;GAGG;AACH,wBAAgB,uBAAuB,CAAC,OAAO,EAAE,MAAM,GAAG;IACxD,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB,WAAW,CAAC,EAAE,MAAM,CAAC;IACrB,aAAa,CAAC,EAAE,MAAM,CAAC;CACxB,CAeA;AAED;;GAEG;AACH,wBAAgB,YAAY,CAAC,OAAO,EAAE,MAAM,GAAG,OAAO,CAGrD;AAED;;GAEG;AACH,wBAAgB,oBAAoB,CAAC,OAAO,EAAE,MAAM,GAAG;IACrD,OAAO,EAAE,OAAO,CAAC;IACjB,UAAU,EAAE,OAAO,CAAC;IACpB,KAAK,EAAE,MAAM,EAAE,CAAC;IAChB,SAAS,EAAE,MAAM,EAAE,CAAC;IACpB,YAAY,EAAE,MAAM,EAAE,CAAC;IACvB,aAAa,EAAE,MAAM,EAAE,CAAC;IACxB,cAAc,EAAE;QACd,QAAQ,CAAC,EAAE,MAAM,CAAC;QAClB,WAAW,CAAC,EAAE,MAAM,CAAC;QACrB,aAAa,CAAC,EAAE,MAAM,CAAC;KACxB,CAAC;CACH,CAcA"}
+{"version":3,"file":"configPaths.d.ts","sourceRoot":"","sources":["../../src/utils/configPaths.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;GAUG;AAUH;;GAEG;AACH,wBAAgB,mBAAmB,IAAI,MAAM,CAI5C;AAED;;GAEG;AACH,wBAAgB,sBAAsB,IAAI,MAAM,CAI/C;AAED;;;GAGG;AACH,wBAAgB,iBAAiB,IAAI,MAAM,CAE1C;AAED;;;GAGG;AACH,wBAAgB,oBAAoB,CAAC,OAAO,EAAE,MAAM,GAAG,MAAM,CAE5D;AAED;;;GAGG;AACH,wBAAgB,kBAAkB,IAAI,MAAM,EAAE,CAG7C;AAED;;GAEG;AACH,wBAAgB,aAAa,IAAI,MAAM,CAEtC;AAED;;;GAGG;AACH,wBAAgB,qBAAqB,CAAC,OAAO,EAAE,MAAM,GAAG,MAAM,EAAE,CAG/D;AAED;;;GAGG;AACH,wBAAgB,iBAAiB,CAAC,OAAO,EAAE,MAAM,GAAG;IAClD,SAAS,EAAE,MAAM,EAAE,CAAC;IACpB,YAAY,EAAE,MAAM,EAAE,CAAC;IACvB,YAAY,EAAE,MAAM,EAAE,CAAC;IACvB,QAAQ,EAAE,MAAM,EAAE,CAAC;CACpB,CAWA;AAED;;;GAGG;AACH,wBAAgB,sBAAsB,CAAC,OAAO,EAAE,MAAM,GAAG;IACvD,SAAS,EAAE,MAAM,EAAE,CAAC;IACpB,YAAY,EAAE,MAAM,EAAE,CAAC;IACvB,YAAY,EAAE,MAAM,EAAE,CAAC;IACvB,aAAa,EAAE,MAAM,EAAE,CAAC;CACzB,CAcA;AAED;;;;GAIG;AACH,wBAAgB,oBAAoB,CAAC,KAAK,EAAE,MAAM,EAAE,GAAG,MAAM,GAAG,SAAS,CAExE;AAED;;;GAGG;AACH,wBAAgB,uBAAuB,CAAC,OAAO,EAAE,MAAM,GAAG;IACxD,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB,WAAW,CAAC,EAAE,MAAM,CAAC;IACrB,aAAa,CAAC,EAAE,MAAM,CAAC;CACxB,CAeA;AAED;;GAEG;AACH,wBAAgB,YAAY,CAAC,OAAO,EAAE,MAAM,GAAG,OAAO,CAGrD;AAED;;GAEG;AACH,wBAAgB,oBAAoB,CAAC,OAAO,EAAE,MAAM,GAAG;IACrD,OAAO,EAAE,OAAO,CAAC;IACjB,UAAU,EAAE,OAAO,CAAC;IACpB,KAAK,EAAE,MAAM,EAAE,CAAC;IAChB,SAAS,EAAE,MAAM,EAAE,CAAC;IACpB,YAAY,EAAE,MAAM,EAAE,CAAC;IACvB,aAAa,EAAE,MAAM,EAAE,CAAC;IACxB,cAAc,EAAE;QACd,QAAQ,CAAC,EAAE,MAAM,CAAC;QAClB,WAAW,CAAC,EAAE,MAAM,CAAC;QACrB,aAAa,CAAC,EAAE,MAAM,CAAC;KACxB,CAAC;CACH,CAcA"}

package/dist/utils/configPaths.js

@@ -19,15 +19,17 @@ const __dirname = dirname(__filename);
  * Get the builtin skills directory path
  */
 export function getBuiltinSkillsDir() {
-    // 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() {
+    // 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");
 }
 /**
  * Get the user-specific configuration file path (legacy function)

package/dist/utils/fileSearch.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"fileSearch.d.ts","sourceRoot":"","sources":["../../src/utils/fileSearch.ts"],"names":[],"mappings":"AAGA,OAAO,KAAK,EAAE,QAAQ,EAAE,MAAM,wBAAwB,CAAC;AAiEvD;;GAEG;AACH,eAAO,MAAM,WAAW,GACtB,OAAO,MAAM,EACb,UAAU;IACR,UAAU,CAAC,EAAE,MAAM,CAAC;IACpB,gBAAgB,CAAC,EAAE,MAAM,CAAC;CAC3B,KACA,OAAO,CAAC,QAAQ,EAAE,CA+DpB,CAAC"}
+{"version":3,"file":"fileSearch.d.ts","sourceRoot":"","sources":["../../src/utils/fileSearch.ts"],"names":[],"mappings":"AAGA,OAAO,KAAK,EAAE,QAAQ,EAAE,MAAM,wBAAwB,CAAC;AAuEvD;;GAEG;AACH,eAAO,MAAM,WAAW,GACtB,OAAO,MAAM,EACb,UAAU;IACR,UAAU,CAAC,EAAE,MAAM,CAAC;IACpB,gBAAgB,CAAC,EAAE,MAAM,CAAC;CAC3B,KACA,OAAO,CAAC,QAAQ,EAAE,CA+DpB,CAAC"}

package/dist/utils/fileSearch.js

@@ -2,6 +2,7 @@ import { spawn } from "child_process";
 import { rgPath } from "./ripgrep.js";
 import fuzzysort from "fuzzysort";
 import { logger } from "./globalLogger.js";
+const EXCLUDED_FILES = [".git", ".DS_Store"];
 /**
  * Execute ripgrep to get all file paths
  */
@@ -31,7 +32,12 @@ async function getAllFiles(workingDirectory) {
             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/dist/utils/subagentParser.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"subagentParser.d.ts","sourceRoot":"","sources":["../../src/utils/subagentParser.ts"],"names":[],"mappings":"AAIA,MAAM,WAAW,qBAAqB;IACpC,IAAI,EAAE,MAAM,CAAC;IACb,WAAW,EAAE,MAAM,CAAC;IACpB,KAAK,CAAC,EAAE,MAAM,EAAE,CAAC;IACjB,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,YAAY,EAAE,MAAM,CAAC;IACrB,QAAQ,EAAE,MAAM,CAAC;IACjB,KAAK,EAAE,SAAS,GAAG,MAAM,GAAG,SAAS,CAAC;IACtC,QAAQ,EAAE,MAAM,CAAC;CAClB;AA+KD;;GAEG;AACH,wBAAsB,0BAA0B,CAC9C,OAAO,EAAE,MAAM,GACd,OAAO,CAAC,qBAAqB,EAAE,CAAC,CAsBlC;AAED;;GAEG;AACH,wBAAsB,kBAAkB,CACtC,IAAI,EAAE,MAAM,EACZ,OAAO,EAAE,MAAM,GACd,OAAO,CAAC,qBAAqB,GAAG,IAAI,CAAC,CAGvC"}
+{"version":3,"file":"subagentParser.d.ts","sourceRoot":"","sources":["../../src/utils/subagentParser.ts"],"names":[],"mappings":"AAKA,MAAM,WAAW,qBAAqB;IACpC,IAAI,EAAE,MAAM,CAAC;IACb,WAAW,EAAE,MAAM,CAAC;IACpB,KAAK,CAAC,EAAE,MAAM,EAAE,CAAC;IACjB,KAAK,CAAC,EAAE,MAAM,CAAC;IACf,YAAY,EAAE,MAAM,CAAC;IACrB,QAAQ,EAAE,MAAM,CAAC;IACjB,KAAK,EAAE,SAAS,GAAG,MAAM,GAAG,SAAS,CAAC;IACtC,QAAQ,EAAE,MAAM,CAAC;CAClB;AAwLD;;GAEG;AACH,wBAAsB,0BAA0B,CAC9C,OAAO,EAAE,MAAM,GACd,OAAO,CAAC,qBAAqB,EAAE,CAAC,CAsBlC;AAED;;GAEG;AACH,wBAAsB,kBAAkB,CACtC,IAAI,EAAE,MAAM,EACZ,OAAO,EAAE,MAAM,GACd,OAAO,CAAC,qBAAqB,GAAG,IAAI,CAAC,CAGvC"}

package/dist/utils/subagentParser.js

@@ -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";
 /**
  * Parse YAML frontmatter from markdown file content
  */
@@ -85,10 +86,19 @@ function parseSubagentFile(filePath, scope) {
     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,
@@ -97,7 +107,7 @@ function parseSubagentFile(filePath, scope) {
             systemPrompt: body,
             filePath,
             scope,
-            priority: scope === "project" ? 1 : 2,
+            priority,
         };
     }
     catch (error) {
@@ -137,9 +147,9 @@ function scanSubagentDirectory(dirPath, scope) {
 export async function loadSubagentConfigurations(workdir) {
     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");
     // Merge configurations, with project configs taking highest precedence

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wave-agent-sdk",
-  "version": "0.11.0",
+  "version": "0.11.1",
   "description": "SDK for building AI-powered development tools and agents",
   "keywords": [
     "ai",
@@ -24,6 +24,7 @@
     "bin",
     "vendor",
     "scripts",
+    "builtin",
     "README.md"
   ],
   "dependencies": {
@@ -48,7 +49,7 @@
   "license": "MIT",
   "scripts": {
     "postinstall": "node scripts/postinstall.js",
-    "build": "rimraf dist && tsc -p tsconfig.build.json && tsc-alias -p tsconfig.build.json && cp -r src/builtin-skills dist/builtin-skills",
+    "build": "rimraf dist && tsc -p tsconfig.build.json && tsc-alias -p tsconfig.build.json",
     "type-check": "tsc --noEmit --incremental",
     "watch": "tsc -p tsconfig.build.json --watch & tsc-alias -p tsconfig.build.json --watch",
     "test": "vitest run --reporter=dot",

package/src/managers/slashCommandManager.ts

@@ -16,7 +16,6 @@ import {
   replaceBashCommandsWithOutput,
   executeBashCommands,
 } from "../utils/markdownParser.js";
-import { INIT_PROMPT } from "../prompts/index.js";
 import type { SkillManager } from "./skillManager.js";
 import type { SkillMetadata } from "../types/skills.js";
 
@@ -73,24 +72,6 @@ export class SlashCommandManager {
   }
 
   private initializeBuiltinCommands(): void {
-    // Register built-in init command
-    this.registerCommand({
-      id: "init",
-      name: "init",
-      description:
-        "Initialize repository for AI agents by generating AGENTS.md",
-      handler: async () => {
-        // Add custom command message to show the command being executed
-        this.messageManager.addUserMessage({
-          content: "/init",
-          customCommandContent: INIT_PROMPT,
-        });
-
-        // Execute the AI conversation with the init prompt
-        await this.aiManager.sendAIMessage();
-      },
-    });
-
     // Register built-in clear command
     this.registerCommand({
       id: "clear",

package/src/prompts/index.ts

@@ -9,11 +9,7 @@ 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,
@@ -128,146 +124,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/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");