wave-agent-sdk 0.5.0 → 0.6.2

package/src/utils/gitUtils.ts

@@ -0,0 +1,24 @@
+import * as path from "node:path";
+import * as fsSync from "node:fs";
+
+/**
+ * Check if a directory is a git repository
+ * @param dirPath Directory path
+ * @returns "Yes" if it's a git repository, "No" otherwise
+ */
+export function isGitRepository(dirPath: string): string {
+  try {
+    // Check if .git directory exists in current directory or any parent directory
+    let currentPath = path.resolve(dirPath);
+    while (currentPath !== path.dirname(currentPath)) {
+      const gitPath = path.join(currentPath, ".git");
+      if (fsSync.existsSync(gitPath)) {
+        return "Yes";
+      }
+      currentPath = path.dirname(currentPath);
+    }
+    return "No";
+  } catch {
+    return "No";
+  }
+}

package/src/utils/messageOperations.ts

@@ -1,7 +1,5 @@
 import type { Message, Usage } from "../types/index.js";
 import { MessageSource } from "../types/index.js";
-import { DEFAULT_KEEP_LAST_MESSAGES_COUNT } from "./constants.js";
-import type { SubagentConfiguration } from "./subagentParser.js";
 import { readFileSync } from "fs";
 import { extname } from "path";
 import { ChatCompletionMessageFunctionToolCall } from "openai/resources.js";
@@ -23,7 +21,7 @@ export interface AddUserMessageParams extends UserMessageParams {
 export interface UpdateToolBlockParams {
   messages: Message[];
   id: string;
-  parameters: string;
+  parameters?: string;
   result?: string;
   success?: boolean;
   error?: string;
@@ -40,6 +38,7 @@ export interface UpdateToolBlockParams {
   images?: Array<{ data: string; mediaType?: string }>;
   compactParams?: string;
   parametersChunk?: string; // Incremental parameter updates for streaming
+  isManuallyBackgrounded?: boolean;
 }
 
 // Agent specific interfaces (without messages parameter)
@@ -53,14 +52,6 @@ export interface AddErrorBlockParams {
   error: string;
 }
 
-export interface AddMemoryBlockParams {
-  messages: Message[];
-  content: string;
-  isSuccess: boolean;
-  memoryType?: "project" | "user";
-  storagePath?: string;
-}
-
 export interface AddCommandOutputParams {
   messages: Message[];
   command: string;
@@ -78,26 +69,6 @@ export interface CompleteCommandParams {
   exitCode: number;
 }
 
-/**
- * Extract text content from user messages in the messages array
- * Excludes messages with source HOOK to prevent hook-generated content from entering user history
- */
-export const extractUserInputHistory = (messages: Message[]): string[] => {
-  return messages
-    .filter((message) => message.role === "user")
-    .map((message) => {
-      // Extract text block content, excluding HOOK-sourced blocks
-      const textBlocks = message.blocks.filter(
-        (block) => block.type === "text" && block.source !== MessageSource.HOOK,
-      );
-      return textBlocks
-        .map((block) => (block as { content: string }).content)
-        .join(" ")
-        .trim();
-    })
-    .filter((text) => text.length > 0); // Filter out empty text
-};
-
 /**
  * Convert image file path to base64 format
  * @param imagePath Image file path
@@ -230,6 +201,7 @@ export const updateToolBlockInMessage = ({
   images,
   compactParams,
   parametersChunk,
+  isManuallyBackgrounded,
 }: UpdateToolBlockParams): Message[] => {
   const newMessages = [...messages];
   // Find the last assistant message
@@ -253,6 +225,8 @@ export const updateToolBlockInMessage = ({
             toolBlock.compactParams = compactParams;
           if (parametersChunk !== undefined)
             toolBlock.parametersChunk = parametersChunk;
+          if (isManuallyBackgrounded !== undefined)
+            toolBlock.isManuallyBackgrounded = isManuallyBackgrounded;
         }
       } else {
         // If existing block not found, create new one
@@ -270,6 +244,7 @@ export const updateToolBlockInMessage = ({
           stage: stage ?? "start",
           compactParams: compactParams,
           parametersChunk: parametersChunk,
+          isManuallyBackgrounded: isManuallyBackgrounded,
         });
       }
       break;
@@ -315,113 +290,6 @@ export const addErrorBlockToMessage = ({
   return newMessages;
 };
 
-// Add Memory Block as new assistant message
-export const addMemoryBlockToMessage = ({
-  messages,
-  content,
-  isSuccess,
-  memoryType,
-  storagePath,
-}: AddMemoryBlockParams): Message[] => {
-  const newMessages = [...messages];
-
-  // Create new assistant message containing MemoryBlock
-  const memoryMessage: Message = {
-    role: "assistant",
-    blocks: [
-      {
-        type: "memory",
-        content,
-        isSuccess,
-        memoryType,
-        storagePath,
-      },
-    ],
-  };
-
-  // Add to end of message list
-  newMessages.push(memoryMessage);
-  return newMessages;
-};
-
-/**
- * Count valid blocks from the end
- * Only text, image, and tool type blocks are counted
- * @param messages Message array
- * @param targetCount Number of valid blocks to count
- * @returns { messageIndex: number, blockCount: number } Message index and actual counted block count
- */
-export const countValidBlocksFromEnd = (
-  messages: Message[],
-  targetCount: number,
-): { messageIndex: number; blockCount: number } => {
-  let validBlockCount = 0;
-
-  // Iterate messages from end to beginning
-  for (let i = messages.length - 1; i >= 0; i--) {
-    const message = messages[i];
-
-    // Iterate through all blocks of current message
-    for (const block of message.blocks) {
-      // Only count valid block types
-      if (
-        block.type === "text" ||
-        block.type === "image" ||
-        block.type === "tool"
-      ) {
-        validBlockCount++;
-
-        // If target count reached, return current message index
-        if (validBlockCount >= targetCount) {
-          return { messageIndex: i, blockCount: validBlockCount };
-        }
-      }
-    }
-  }
-
-  // If target count not reached, return index 0
-  return { messageIndex: 0, blockCount: validBlockCount };
-};
-
-/**
- * Get messages to be compressed and insertion position
- * @param messages Message array
- * @param keepLastCount Keep the last few valid blocks uncompressed
- * @returns { messagesToCompress: Message[], insertIndex: number }
- */
-export const getMessagesToCompress = (
-  messages: Message[],
-  keepLastCount: number = DEFAULT_KEEP_LAST_MESSAGES_COUNT,
-): { messagesToCompress: Message[]; insertIndex: number } => {
-  // Calculate message position to keep from end to beginning
-  const { messageIndex } = countValidBlocksFromEnd(messages, keepLastCount);
-
-  // Find the last message containing compression block
-  let lastCompressIndex = -1;
-  for (let i = messages.length - 1; i >= 0; i--) {
-    const hasCompressBlock = messages[i].blocks.some(
-      (block) => block.type === "compress",
-    );
-    if (hasCompressBlock) {
-      lastCompressIndex = i;
-      break;
-    }
-  }
-
-  // Determine compression start position
-  // If compression block exists, start from compression block position (include compression block)
-  // If no compression block, start from beginning
-  const startIndex = lastCompressIndex >= 0 ? lastCompressIndex : 0;
-
-  // Messages to compress are all messages from start position to before calculated position
-  const messagesToCompress = messages.slice(startIndex, messageIndex);
-
-  // Change insertion position to negative number, indicating position from end
-  const insertIndex = messageIndex - messages.length;
-
-  return { messagesToCompress, insertIndex };
-};
-
 // Add command output block to message list
 export const addCommandOutputMessage = ({
   messages,
@@ -496,97 +364,6 @@ export const completeCommandInMessage = ({
   return newMessages;
 };
 
-// Subagent block message operations
-export interface AddSubagentBlockParams {
-  messages: Message[];
-  subagentId: string;
-  subagentName: string;
-  status: "active" | "completed" | "error" | "aborted";
-  sessionId: string;
-  configuration: SubagentConfiguration;
-  runInBackground?: boolean;
-}
-
-export interface UpdateSubagentBlockParams {
-  messages: Message[];
-  subagentId: string;
-  status: "active" | "completed" | "error" | "aborted";
-  sessionId?: string;
-}
-
-export const addSubagentBlockToMessage = ({
-  messages,
-  subagentId,
-  subagentName,
-  status,
-  sessionId,
-  configuration,
-  runInBackground,
-}: AddSubagentBlockParams): Message[] => {
-  const newMessages = [...messages];
-
-  // Find the last assistant message or create one
-  let lastAssistantMessage = newMessages[newMessages.length - 1];
-
-  if (!lastAssistantMessage || lastAssistantMessage.role !== "assistant") {
-    // Create new assistant message if the last message is not from assistant
-    lastAssistantMessage = {
-      id: `msg-${Date.now()}-${Math.random().toString(36).slice(2, 9)}`,
-      role: "assistant",
-      blocks: [],
-    };
-    newMessages.push(lastAssistantMessage);
-  }
-
-  // Add subagent block
-  lastAssistantMessage.blocks.push({
-    type: "subagent",
-    subagentId,
-    subagentName,
-    status,
-    sessionId,
-    configuration,
-    runInBackground,
-  });
-
-  return newMessages;
-};
-
-export const updateSubagentBlockInMessage = (
-  messages: Message[],
-  subagentId: string,
-  updates: Partial<{
-    status: "active" | "completed" | "error" | "aborted";
-    sessionId: string;
-    runInBackground: boolean;
-  }>,
-): Message[] => {
-  const newMessages = [...messages];
-
-  // Find and update the subagent block
-  for (let i = newMessages.length - 1; i >= 0; i--) {
-    const message = newMessages[i];
-    if (message.role === "assistant") {
-      for (const block of message.blocks) {
-        if (block.type === "subagent" && block.subagentId === subagentId) {
-          if (updates.status !== undefined) {
-            block.status = updates.status;
-          }
-          if (updates.sessionId !== undefined) {
-            block.sessionId = updates.sessionId;
-          }
-          if (updates.runInBackground !== undefined) {
-            block.runInBackground = updates.runInBackground;
-          }
-          return newMessages;
-        }
-      }
-    }
-  }
-
-  return newMessages;
-};
-
 /**
  * Removes the last user message from the messages array
  * Used for hook error handling when the user prompt needs to be erased

package/src/utils/nameGenerator.ts

@@ -71,8 +71,25 @@ const nouns = [
 /**
  * Generates a random English name (adjective-noun)
  */
-export function generateRandomName(): string {
-  const adj = adjectives[Math.floor(Math.random() * adjectives.length)];
-  const noun = nouns[Math.floor(Math.random() * nouns.length)];
+export function generateRandomName(seed?: string): string {
+  let adjIndex: number;
+  let nounIndex: number;
+
+  if (seed) {
+    // Simple hash function to derive indices from seed
+    let hash = 0;
+    for (let i = 0; i < seed.length; i++) {
+      hash = (hash << 5) - hash + seed.charCodeAt(i);
+      hash |= 0; // Convert to 32bit integer
+    }
+    adjIndex = Math.abs(hash) % adjectives.length;
+    nounIndex = Math.abs(hash >> 8) % nouns.length;
+  } else {
+    adjIndex = Math.floor(Math.random() * adjectives.length);
+    nounIndex = Math.floor(Math.random() * nouns.length);
+  }
+
+  const adj = adjectives[adjIndex];
+  const noun = nouns[nounIndex];
   return `${adj}-${noun}`;
 }

package/dist/constants/prompts.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"prompts.d.ts","sourceRoot":"","sources":["../../src/constants/prompts.ts"],"names":[],"mappings":"AAcA,eAAO,MAAM,kBAAkB,ksFAe8G,CAAC;AAE9I,eAAO,MAAM,sBAAsB,+lBAImH,CAAC;AAEvJ,eAAO,MAAM,eAAe,mVAEgS,CAAC;AAE7T,eAAO,MAAM,eAAe,meAG0P,CAAC;AAEvR,eAAO,MAAM,uBAAuB,2JAA2J,CAAC;AAChM,eAAO,MAAM,gBAAgB,qDAAkE,CAAC;AAChG,eAAO,MAAM,gBAAgB,mDAA8E,CAAC;AAC5G,eAAO,MAAM,iBAAiB,8EAA2F,CAAC;AAC1H,eAAO,MAAM,kBAAkB,0EAAiH,CAAC;AAEjJ,eAAO,MAAM,WAAW,sjBAE4O,CAAC;AAErQ,eAAO,MAAM,qBAAqB,ksFAAqB,CAAC;AAExD,eAAO,MAAM,6BAA6B,izCAeK,CAAC;AAEhD,eAAO,MAAM,WAAW,kkDAoBjB,CAAC;AAER,wBAAgB,iBAAiB,CAC/B,UAAU,EAAE,MAAM,EAClB,KAAK,EAAE;IAAE,IAAI,CAAC,EAAE,MAAM,CAAC;IAAC,QAAQ,CAAC,EAAE;QAAE,IAAI,EAAE,MAAM,CAAA;KAAE,CAAA;CAAE,EAAE,GACtD,MAAM,CAsDR"}

package/dist/constants/prompts.js

@@ -1,118 +0,0 @@
-import { ASK_USER_QUESTION_TOOL_NAME, BASH_TOOL_NAME, EDIT_TOOL_NAME, GLOB_TOOL_NAME, GREP_TOOL_NAME, LS_TOOL_NAME, MULTI_EDIT_TOOL_NAME, READ_TOOL_NAME, TASK_TOOL_NAME, TODO_WRITE_TOOL_NAME, WRITE_TOOL_NAME, } from "./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
-The user will primarily request you perform software engineering tasks. This includes solving bugs, adding new functionality, refactoring code, explaining code, and more. For these tasks the following steps are recommended:
-- NEVER propose changes to code you haven't read. If a user asks about or wants you to modify a file, read it first. Understand existing code before suggesting modifications.
-- Be careful not to introduce security vulnerabilities such as command injection, XSS, SQL injection, and other OWASP top 10 vulnerabilities. If you notice that you wrote insecure code, immediately fix it.
-- Avoid over-engineering. Only make changes that are directly requested or clearly necessary. Keep solutions simple and focused.
-  - Don't add features, refactor code, or make "improvements" beyond what was asked. A bug fix doesn't need surrounding code cleaned up. A simple feature doesn't need extra configurability. Don't add docstrings, comments, or type annotations to code you didn't change. Only add comments where the logic isn't self-evident.
-  - Don't add error handling, fallbacks, or validation for scenarios that can't happen. Trust internal code and framework guarantees. Only validate at system boundaries (user input, external APIs). Don't use feature flags or backwards-compatibility shims when you can just change the code.
-  - Don't create helpers, utilities, or abstractions for one-time operations. Don't design for hypothetical future requirements. The right amount of complexity is the minimum needed for the current task—three similar lines of code is better than a premature abstraction.
-- Avoid backwards-compatibility hacks like renaming unused \`_vars\`, re-exporting types, adding \`// removed\` comments for removed code, etc. If something is unused, delete it completely.
-
-# 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.
-- 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.`;
-export const TASK_MANAGEMENT_POLICY = `
-# Task Management
-You have access to the ${TODO_WRITE_TOOL_NAME} tools to help you manage and plan tasks. Use these tools VERY frequently to ensure that you are tracking your tasks and giving the user visibility into your progress.
-These tools are also EXTREMELY helpful for planning tasks, and for breaking down larger complex tasks into smaller steps. If you do not use this tool when planning, you may forget to do important tasks - and that is unacceptable.
-It is critical that you mark todos as completed as soon as you are done with a task. Do not batch up multiple tasks before marking them as completed.`;
-export const ASK_USER_POLICY = `
-# Asking questions as you work
-You have access to the ${ASK_USER_QUESTION_TOOL_NAME} tool to ask the user questions when you need clarification, want to validate assumptions, or need to make a decision you're unsure about. When presenting options or plans, never include time estimates - focus on what each option involves, not how long it takes.`;
-export const SUBAGENT_POLICY = `
-- When doing file search, prefer to use the ${TASK_TOOL_NAME} tool in order to reduce context usage.
-- You should proactively use the ${TASK_TOOL_NAME} tool with specialized agents when the task at hand matches the agent's description.
-- VERY IMPORTANT: When exploring the codebase to gather context or to answer a question that is not a needle query for a specific file/class/function, it is CRITICAL that you use the ${TASK_TOOL_NAME} tool with subagent_type=Explore instead of running search commands directly.`;
-export const FILE_TOOL_POLICY_PREFIX = `\n- Use specialized tools instead of bash commands when possible, as this provides a better user experience. For file operations, use dedicated tools:`;
-export const READ_FILE_POLICY = ` ${READ_TOOL_NAME} for reading files instead of cat/head/tail`;
-export const EDIT_FILE_POLICY = ` ${EDIT_TOOL_NAME}/${MULTI_EDIT_TOOL_NAME} for editing instead of sed/awk`;
-export const WRITE_FILE_POLICY = ` ${WRITE_TOOL_NAME} for creating files instead of cat with heredoc or echo redirection`;
-export const SEARCH_FILE_POLICY = ` ${LS_TOOL_NAME}/${GLOB_TOOL_NAME}/${GREP_TOOL_NAME} for searching and listing files instead of find/ls/grep`;
-export const BASH_POLICY = `
-- Reserve bash tools exclusively for actual system commands and terminal operations that require shell execution. NEVER use bash echo or other command-line tools to communicate thoughts, explanations, or instructions to the user. Output all communication directly in your response text instead.
-- When making multiple bash tool calls, you MUST send a single message with multiple tools calls to run the calls in parallel. For example, if you need to run "git status" and "git diff", send a single message with two tool calls to run the calls in parallel.`;
-export const DEFAULT_SYSTEM_PROMPT = BASE_SYSTEM_PROMPT;
-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 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.`;
-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.
-- 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 function buildSystemPrompt(basePrompt, tools) {
-    let prompt = basePrompt;
-    const toolNames = new Set(tools.map((t) => t.function?.name || t.name).filter(Boolean));
-    if (toolNames.has(TODO_WRITE_TOOL_NAME)) {
-        prompt += TASK_MANAGEMENT_POLICY;
-    }
-    if (toolNames.has(ASK_USER_QUESTION_TOOL_NAME)) {
-        prompt += ASK_USER_POLICY;
-    }
-    if (toolNames.has(TASK_TOOL_NAME)) {
-        prompt += SUBAGENT_POLICY;
-    }
-    if (toolNames.has(READ_TOOL_NAME) ||
-        toolNames.has(EDIT_TOOL_NAME) ||
-        toolNames.has(MULTI_EDIT_TOOL_NAME) ||
-        toolNames.has(WRITE_TOOL_NAME) ||
-        toolNames.has(LS_TOOL_NAME) ||
-        toolNames.has(GLOB_TOOL_NAME) ||
-        toolNames.has(GREP_TOOL_NAME)) {
-        const parts = [];
-        if (toolNames.has(READ_TOOL_NAME)) {
-            parts.push(READ_FILE_POLICY);
-        }
-        if (toolNames.has(EDIT_TOOL_NAME) || toolNames.has(MULTI_EDIT_TOOL_NAME)) {
-            parts.push(EDIT_FILE_POLICY);
-        }
-        if (toolNames.has(WRITE_TOOL_NAME)) {
-            parts.push(WRITE_FILE_POLICY);
-        }
-        if (toolNames.has(LS_TOOL_NAME) ||
-            toolNames.has(GLOB_TOOL_NAME) ||
-            toolNames.has(GREP_TOOL_NAME)) {
-            parts.push(SEARCH_FILE_POLICY);
-        }
-        if (parts.length > 0) {
-            prompt += FILE_TOOL_POLICY_PREFIX + parts.join(",") + ".";
-        }
-    }
-    if (toolNames.has(BASH_TOOL_NAME)) {
-        prompt += BASH_POLICY;
-    }
-    return prompt;
-}

package/dist/tools/todoWriteTool.d.ts

@@ -1,6 +0,0 @@
-import type { ToolPlugin } from "./types.js";
-/**
- * TodoWrite tool for creating and managing structured task lists
- */
-export declare const todoWriteTool: ToolPlugin;
-//# sourceMappingURL=todoWriteTool.d.ts.map

package/dist/tools/todoWriteTool.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"todoWriteTool.d.ts","sourceRoot":"","sources":["../../src/tools/todoWriteTool.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,UAAU,EAA2B,MAAM,YAAY,CAAC;AAStE;;GAEG;AACH,eAAO,MAAM,aAAa,EAAE,UAoP3B,CAAC"}