wave-agent-sdk 0.15.3 → 0.15.4

package/src/types/configuration.ts

@@ -104,8 +104,6 @@ export interface ConfigurationPaths {
   userPaths: string[];
   /** Project-specific configuration file paths in priority order */
   projectPaths: string[];
-  /** Builtin configuration file paths */
-  builtinPaths: string[];
   /** All configuration paths combined */
   allPaths: string[];
   /** Only the paths that actually exist on the filesystem */

package/src/utils/builtinSkills.ts

@@ -0,0 +1,158 @@
+/**
+ * Builtin skill configurations hardcoded as TypeScript objects.
+ * Replaces the former builtin/skills directory of markdown files.
+ */
+
+import type { Skill } from "../types/index.js";
+
+const LOOP_CONTENT = [
+  "---",
+  "name: loop",
+  "description: Run a prompt or slash command on a recurring interval (e.g. /loop 5m /foo, defaults to 10m)",
+  "allowed-tools: CronCreate, Skill",
+  "user-invocable: true",
+  "---",
+  "",
+  "# /loop — schedule a recurring prompt",
+  "",
+  "Parse the input below into `[interval] <prompt…>` and schedule it with CronCreate.",
+  "",
+  "## Usage",
+  "",
+  "```",
+  "/loop [interval] <prompt>",
+  "",
+  "Run a prompt or slash command on a recurring interval.",
+  "",
+  "Intervals: Ns, Nm, Nh, Nd (e.g. 5m, 30m, 2h, 1d). Minimum granularity is 1 minute.",
+  "If no interval is specified, defaults to 10m.",
+  "",
+  "Examples:",
+  "  /loop 5m /babysit-prs",
+  "  /loop 30m check the deploy",
+  "  /loop 1h /standup 1",
+  "  /loop check the deploy          (defaults to 10m)",
+  "  /loop check the deploy every 20m",
+  "```",
+  "",
+  "## Parsing (in priority order)",
+  "",
+  "1. **Leading token**: if the first whitespace-delimited token matches `^\\d+[smhd]$` (e.g. `5m`, `2h`), that's the interval; the rest is the prompt.",
+  '2. **Trailing "every" clause**: otherwise, if the input ends with `every <N><unit>` or `every <N> <unit-word>` (e.g. `every 20m`, `every 5 minutes`, `every 2 hours`), extract that as the interval and strip it from the prompt. Only match when what follows "every" is a time expression — `check every PR` has no interval.',
+  "3. **Default**: otherwise, interval is `10m` and the entire input is the prompt.",
+  "",
+  "If the resulting prompt is empty, show usage `/loop [interval] <prompt>` and stop — do not call CronCreate.",
+  "",
+  "Examples:",
+  "- `5m /babysit-prs` → interval `5m`, prompt `/babysit-prs` (rule 1)",
+  "- `check the deploy every 20m` → interval `20m`, prompt `check the deploy` (rule 2)",
+  "- `run tests every 5 minutes` → interval `5m`, prompt `run tests` (rule 2)",
+  "- `check the deploy` → interval `10m`, prompt `check the deploy` (rule 3)",
+  '- `check every PR` → interval `10m`, prompt `check every PR` (rule 3 — "every" not followed by time)',
+  "- `5m` → empty prompt → show usage",
+  "",
+  "## Interval → cron",
+  "",
+  "Supported suffixes: `s` (seconds, rounded up to nearest minute, min 1), `m` (minutes), `h` (hours), `d` (days). Convert:",
+  "",
+  "| Interval pattern      | Cron expression     | Notes                                    |",
+  "|-----------------------|---------------------|------------------------------------------|",
+  "| `Nm` where N ≤ 59   | `*/N * * * *`     | every N minutes                          |",
+  "| `Nm` where N ≥ 60   | `0 */H * * *`     | round to hours (H = N/60, must divide 24)|",
+  "| `Nh` where N ≤ 23   | `0 */N * * *`     | every N hours                            |",
+  "| `Nd`                | `0 0 */N * *`     | every N days at midnight local           |",
+  "| `Ns`                | treat as `ceil(N/60)m` | cron minimum granularity is 1 minute  |",
+  "",
+  "**If the interval doesn't cleanly divide its unit** (e.g. `7m` → `*/7 * * * *` gives uneven gaps at :56→:00; `90m` → 1.5h which cron can't express), pick the nearest clean interval and tell the user what you rounded to before scheduling.",
+  "",
+  "## Avoid the :00 and :30 minute marks",
+  "",
+  "When the user's request is approximate, pick a minute that is NOT 0 or 30:",
+  '- "every morning around 9" → `57 8 * * *` or `3 9 * * *` (not `0 9 * * *`)',
+  '- "hourly" → `7 * * * *` (not `0 * * * *`)',
+  "",
+  'Only use minute 0 or 30 when the user names that exact time and clearly means it ("at 9:00 sharp", "at half past").',
+  "",
+  "## Action",
+  "",
+  "1. Call CronCreate with:",
+  "   - `cron`: the expression from the table above",
+  "   - `prompt`: the parsed prompt from above, verbatim (slash commands are passed through unchanged)",
+  "   - `recurring`: `true`",
+  "2. Briefly confirm: what's scheduled, the cron expression, the human-readable cadence, that recurring tasks auto-expire after 7 days, and that they can cancel sooner with CronDelete (include the job ID).",
+  "3. **Then immediately execute the parsed prompt now** — don't wait for the first cron fire. If it's a slash command, run it directly; otherwise act on it directly.",
+  "",
+  "## Input",
+  "",
+  "$ARGUMENTS",
+].join("\n");
+
+const INIT_CONTENT = [
+  "---",
+  "name: init",
+  "description: Analyze the codebase and create an AGENTS.md file to guide future agents.",
+  "disable-model-invocation: true",
+  "---",
+  "",
+  "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.",
+  "```",
+].join("\n");
+
+export const BUILTIN_SKILLS: Skill[] = [
+  {
+    name: "loop",
+    description:
+      "Run a prompt or slash command on a recurring interval (e.g. /loop 5m /foo, defaults to 10m)",
+    type: "builtin",
+    skillPath: "<builtin:loop>",
+    allowedTools: ["CronCreate", "Skill"],
+    userInvocable: true,
+    content: LOOP_CONTENT,
+    frontmatter: {
+      name: "loop",
+      description:
+        "Run a prompt or slash command on a recurring interval (e.g. /loop 5m /foo, defaults to 10m)",
+      "allowed-tools": ["CronCreate", "Skill"],
+      "user-invocable": true,
+    },
+    isValid: true,
+    errors: [],
+  },
+  {
+    name: "init",
+    description:
+      "Analyze the codebase and create an AGENTS.md file to guide future agents.",
+    type: "builtin",
+    skillPath: "<builtin:init>",
+    disableModelInvocation: true,
+    content: INIT_CONTENT,
+    frontmatter: {
+      name: "init",
+      description:
+        "Analyze the codebase and create an AGENTS.md file to guide future agents.",
+      "disable-model-invocation": true,
+    },
+    isValid: true,
+    errors: [],
+  },
+];

package/src/utils/configPaths.ts

@@ -10,31 +10,9 @@
  * - Project configs override user configs (existing behavior)
  */
 
-import { join, dirname } from "path";
+import { join } from "path";
 import { homedir } from "os";
 import { existsSync } from "fs";
-import { fileURLToPath } from "url";
-
-const __filename = fileURLToPath(import.meta.url);
-const __dirname = dirname(__filename);
-
-/**
- * Get the builtin skills directory path
- */
-export function getBuiltinSkillsDir(): string {
-  // 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");
-}
 
 /**
  * Get the user-specific configuration file path (legacy function)
@@ -84,18 +62,15 @@ export function getProjectConfigPaths(workdir: string): string[] {
 export function getAllConfigPaths(workdir: string): {
   userPaths: string[];
   projectPaths: string[];
-  builtinPaths: string[];
   allPaths: string[];
 } {
   const userPaths = getUserConfigPaths();
   const projectPaths = getProjectConfigPaths(workdir);
-  const builtinPaths = [join(getBuiltinSkillsDir(), "settings", "SKILL.md")];
 
   return {
     userPaths,
     projectPaths,
-    builtinPaths,
-    allPaths: [...userPaths, ...projectPaths, ...builtinPaths],
+    allPaths: [...userPaths, ...projectPaths],
   };
 }
 
@@ -106,20 +81,17 @@ export function getAllConfigPaths(workdir: string): {
 export function getExistingConfigPaths(workdir: string): {
   userPaths: string[];
   projectPaths: string[];
-  builtinPaths: string[];
   existingPaths: string[];
 } {
   const allPaths = getAllConfigPaths(workdir);
 
   const existingUserPaths = allPaths.userPaths.filter(existsSync);
   const existingProjectPaths = allPaths.projectPaths.filter(existsSync);
-  const existingBuiltinPaths = allPaths.builtinPaths.filter(existsSync);
   const allExistingPaths = allPaths.allPaths.filter(existsSync);
 
   return {
     userPaths: existingUserPaths,
     projectPaths: existingProjectPaths,
-    builtinPaths: existingBuiltinPaths,
     existingPaths: allExistingPaths,
   };
 }

package/src/utils/subagentParser.ts

@@ -1,7 +1,6 @@
 import { readFileSync, readdirSync, statSync } from "fs";
 import { join, extname, basename } from "path";
 import { logger } from "./globalLogger.js";
-import { getBuiltinSubagentsDir } from "./configPaths.js";
 
 export interface SubagentConfiguration {
   name: string;
@@ -16,6 +15,164 @@ export interface SubagentConfiguration {
   pluginRoot?: string;
 }
 
+/**
+ * Builtin subagent configurations hardcoded as TypeScript objects.
+ * Replaces the former builtin/subagents directory of markdown files.
+ */
+export const BUILTIN_SUBAGENTS: SubagentConfiguration[] = [
+  {
+    name: "Explore",
+    description:
+      'Fast agent specialized for exploring codebases. Use this when you need to quickly find files by patterns (eg. "src/components/**/*.tsx"), search code for keywords (eg. "API endpoints"), or answer questions about the codebase (eg. "how do API endpoints work?"). When calling this agent, specify the desired thoroughness level: "quick" for basic searches, "medium" for moderate exploration, or "very thorough" for comprehensive analysis across multiple locations and naming conventions.',
+    tools: ["Glob", "Grep", "Read", "Bash", "LSP"],
+    model: "fastModel",
+    systemPrompt: `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 for broad file pattern matching
+- Use Grep for searching file contents with regex
+- Use Read 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 ONLY for read-only operations (ls, git status, git log, git diff, find, cat, head, tail)
+- NEVER use Bash 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.`,
+    filePath: "<builtin:Explore>",
+    scope: "builtin",
+    priority: 3,
+  },
+  {
+    name: "Bash",
+    description:
+      "Command execution specialist for running bash commands. Use this for git operations, command execution, and other terminal tasks.",
+    tools: ["Bash"],
+    model: "inherit",
+    systemPrompt: `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.`,
+    filePath: "<builtin:Bash>",
+    scope: "builtin",
+    priority: 3,
+  },
+  {
+    name: "Plan",
+    description:
+      "Software architect agent for designing implementation plans. Use this when you need to plan the implementation strategy for a task. Returns step-by-step plans, identifies critical files, and considers architectural trade-offs.",
+    tools: ["Glob", "Grep", "Read", "Bash", "LSP"],
+    model: "inherit",
+    systemPrompt: `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, Grep, and Read
+   - Understand the current architecture
+   - Identify similar features as reference
+   - Trace through relevant code paths
+   - Use Bash ONLY for read-only operations (ls, git status, git log, git diff, find, cat, head, tail)
+   - NEVER use Bash 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.`,
+    filePath: "<builtin:Plan>",
+    scope: "builtin",
+    priority: 3,
+  },
+  {
+    name: "general-purpose",
+    description:
+      "General-purpose agent for researching complex questions, searching for code, and executing multi-step tasks. When you are searching for a keyword or file and are not confident that you will find the right match in the first few tries use this agent to perform the search for you.",
+    systemPrompt: `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 or Glob when you need to search broadly. Use Read 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.`,
+    filePath: "<builtin:general-purpose>",
+    scope: "builtin",
+    priority: 3,
+  },
+];
+
 interface SubagentFrontmatter {
   name?: string;
   description?: string;
@@ -231,10 +388,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 builtinConfigs = scanSubagentDirectory(builtinDir, "builtin");
+  // Builtin subagents are hardcoded in TS, not scanned from a directory
+  const builtinConfigs = [...BUILTIN_SUBAGENTS];
   const projectConfigs = scanSubagentDirectory(projectDir, "project");
   const userConfigs = scanSubagentDirectory(userDir, "user");
 

package/builtin/skills/init/SKILL.md

@@ -1,28 +0,0 @@
----
-name: init
-description: Analyze the codebase and create an AGENTS.md file to guide future agents.
-disable-model-invocation: true
----
-
-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.
-```

package/builtin/skills/loop/SKILL.md

@@ -1,79 +0,0 @@
----
-name: loop
-description: Run a prompt or slash command on a recurring interval (e.g. /loop 5m /foo, defaults to 10m)
-allowed-tools: CronCreate, Skill
-user-invocable: true
----
-
-# /loop — schedule a recurring prompt
-
-Parse the input below into `[interval] <prompt…>` and schedule it with CronCreate.
-
-## Usage
-
-```
-/loop [interval] <prompt>
-
-Run a prompt or slash command on a recurring interval.
-
-Intervals: Ns, Nm, Nh, Nd (e.g. 5m, 30m, 2h, 1d). Minimum granularity is 1 minute.
-If no interval is specified, defaults to 10m.
-
-Examples:
-  /loop 5m /babysit-prs
-  /loop 30m check the deploy
-  /loop 1h /standup 1
-  /loop check the deploy          (defaults to 10m)
-  /loop check the deploy every 20m
-```
-
-## Parsing (in priority order)
-
-1. **Leading token**: if the first whitespace-delimited token matches `^\d+[smhd]$` (e.g. `5m`, `2h`), that's the interval; the rest is the prompt.
-2. **Trailing "every" clause**: otherwise, if the input ends with `every <N><unit>` or `every <N> <unit-word>` (e.g. `every 20m`, `every 5 minutes`, `every 2 hours`), extract that as the interval and strip it from the prompt. Only match when what follows "every" is a time expression — `check every PR` has no interval.
-3. **Default**: otherwise, interval is `10m` and the entire input is the prompt.
-
-If the resulting prompt is empty, show usage `/loop [interval] <prompt>` and stop — do not call CronCreate.
-
-Examples:
-- `5m /babysit-prs` → interval `5m`, prompt `/babysit-prs` (rule 1)
-- `check the deploy every 20m` → interval `20m`, prompt `check the deploy` (rule 2)
-- `run tests every 5 minutes` → interval `5m`, prompt `run tests` (rule 2)
-- `check the deploy` → interval `10m`, prompt `check the deploy` (rule 3)
-- `check every PR` → interval `10m`, prompt `check every PR` (rule 3 — "every" not followed by time)
-- `5m` → empty prompt → show usage
-
-## Interval → cron
-
-Supported suffixes: `s` (seconds, rounded up to nearest minute, min 1), `m` (minutes), `h` (hours), `d` (days). Convert:
-
-| Interval pattern      | Cron expression     | Notes                                    |
-|-----------------------|---------------------|------------------------------------------|
-| `Nm` where N ≤ 59   | `*/N * * * *`     | every N minutes                          |
-| `Nm` where N ≥ 60   | `0 */H * * *`     | round to hours (H = N/60, must divide 24)|
-| `Nh` where N ≤ 23   | `0 */N * * *`     | every N hours                            |
-| `Nd`                | `0 0 */N * *`     | every N days at midnight local           |
-| `Ns`                | treat as `ceil(N/60)m` | cron minimum granularity is 1 minute  |
-
-**If the interval doesn't cleanly divide its unit** (e.g. `7m` → `*/7 * * * *` gives uneven gaps at :56→:00; `90m` → 1.5h which cron can't express), pick the nearest clean interval and tell the user what you rounded to before scheduling.
-
-## Avoid the :00 and :30 minute marks
-
-When the user's request is approximate, pick a minute that is NOT 0 or 30:
-- "every morning around 9" → `57 8 * * *` or `3 9 * * *` (not `0 9 * * *`)
-- "hourly" → `7 * * * *` (not `0 * * * *`)
-
-Only use minute 0 or 30 when the user names that exact time and clearly means it ("at 9:00 sharp", "at half past").
-
-## Action
-
-1. Call CronCreate with:
-   - `cron`: the expression from the table above
-   - `prompt`: the parsed prompt from above, verbatim (slash commands are passed through unchanged)
-   - `recurring`: `true`
-2. Briefly confirm: what's scheduled, the cron expression, the human-readable cadence, that recurring tasks auto-expire after 7 days, and that they can cancel sooner with CronDelete (include the job ID).
-3. **Then immediately execute the parsed prompt now** — don't wait for the first cron fire. If it's a slash command, run it directly; otherwise act on it directly.
-
-## Input
-
-$ARGUMENTS

package/builtin/skills/settings/ENV.md

@@ -1,69 +0,0 @@
-# Wave Environment Variables Configuration
-
-Environment variables allow you to customize Wave's behavior, configure AI models, and provide context to hooks and tools. This document provides detailed guidance on how to configure environment variables in `settings.json`.
-
-## The `env` Field
-
-Environment variables are configured in the `env` field of `settings.json`. It is a simple key-value pair of strings.
-
-```json
-{
-  "env": {
-    "WAVE_MODEL": "gemini-3-flash",
-    "MY_CUSTOM_VAR": "some-value"
-  }
-}
-```
-
-## Supported `WAVE_*` Environment Variables
-
-Wave uses several environment variables to control its core functionality.
-
-| Variable | Description | Default |
-| :--- | :--- | :--- |
-| `WAVE_API_KEY` | API key for the AI gateway. | - |
-| `WAVE_BASE_URL` | Base URL for the AI gateway. | - |
-| `WAVE_CUSTOM_HEADERS` | Custom HTTP headers for the AI gateway (JSON string). | - |
-| `WAVE_MODEL` | The primary AI model to use for the agent. | `gemini-3-flash` |
-| `WAVE_FAST_MODEL` | The fast AI model to use for quick tasks. | `gemini-2.5-flash` |
-| `WAVE_MAX_INPUT_TOKENS` | Maximum number of input tokens allowed. | `96000` |
-| `WAVE_MAX_OUTPUT_TOKENS` | Maximum number of output tokens allowed. | `8192` |
-| `WAVE_DISABLE_AUTO_MEMORY` | Set to `1` or `true` to disable the auto-memory feature. | `false` |
-| `WAVE_TASK_LIST_ID` | Explicitly set the task list ID for the session. | (Session ID) |
-| `WAVE_PROMPT_CACHE_REGEX` | Regex pattern to match model names that support prompt caching. Models matching this pattern will have cache control markers applied. | `claude` |
-
-## Configuration Scopes
-
-Environment variables can be set in different scopes, with the following precedence (highest to lowest):
-
-1.  **Local Scope**: `.wave/settings.local.json` (Local overrides, ignored by git)
-2.  **Project Scope**: `.wave/settings.json` (Project-specific settings, shared via git)
-3.  **User Scope**: `~/.wave/settings.json` (Global settings for all projects)
-4.  **System Environment**: Variables set in your shell (e.g., `export WAVE_API_KEY=...`)
-
-## Custom Environment Variables
-
-You can also define custom environment variables in the `env` field. These variables will be available to:
-
-- **Hooks**: Any shell command executed as a hook will have these variables in its environment.
-- **Tools**: Tools like `Bash` will have access to these variables.
-
-Example:
-```json
-{
-  "env": {
-    "PROJECT_NAME": "my-awesome-project",
-    "DEPLOY_TARGET": "staging"
-  }
-}
-```
-
-## Live Reload
-
-Environment variables configured in `settings.json` support **live reload**. When you modify the `env` field in any `settings.json` file (user, project, or local scope), the changes take effect immediately without requiring a Wave session restart.
-
-## Best Practices
-
-- **Use Local Overrides for Secrets**: Never commit sensitive information like `WAVE_API_KEY` to `settings.json`. Use `settings.local.json` instead.
-- **Standard Naming**: Use uppercase and underscores for environment variable names (e.g., `MY_VARIABLE`).
-- **Avoid Overriding System Variables**: Be careful not to override standard system variables like `PATH` or `HOME` unless you have a specific reason to do so.