wave-agent-sdk 0.5.0 → 0.6.2

package/dist/managers/subagentManager.js

@@ -8,7 +8,7 @@ export class SubagentManager {
         this.cachedConfigurations = null;
         this.workdir = options.workdir;
         this.parentToolManager = options.parentToolManager;
-        this.parentMessageManager = options.parentMessageManager;
+        this.taskManager = options.taskManager;
         this.callbacks = options.callbacks; // Store SubagentManagerCallbacks
         this.logger = options.logger;
         this.getGatewayConfig = options.getGatewayConfig;
@@ -55,7 +55,7 @@ export class SubagentManager {
     /**
      * Create a new subagent instance with isolated managers
      */
-    async createInstance(configuration, parameters, runInBackground) {
+    async createInstance(configuration, parameters, runInBackground, onUpdate) {
         if (!this.parentToolManager) {
             throw new Error("SubagentManager not properly initialized - call initialize() first");
         }
@@ -76,6 +76,7 @@ export class SubagentManager {
         const aiManager = new AIManager({
             messageManager,
             toolManager,
+            taskManager: this.taskManager,
             logger: this.logger,
             workdir: this.workdir,
             systemPrompt: configuration.systemPrompt,
@@ -118,11 +119,11 @@ export class SubagentManager {
             toolManager,
             status: "initializing",
             messages: [],
+            lastTools: [], // Initialize lastTools
             subagentType: parameters.subagent_type, // Store the subagent type
+            onUpdate,
         };
         this.instances.set(subagentId, instance);
-        // Create subagent block in parent message manager
-        this.parentMessageManager.addSubagentBlock(subagentId, configuration.name, messageManager.getSessionId(), configuration, "active", parameters, runInBackground);
         return instance;
     }
     /**
@@ -139,9 +140,6 @@ export class SubagentManager {
             }
             // Set status to active and update parent
             this.updateInstanceStatus(instance.subagentId, "active");
-            this.parentMessageManager.updateSubagentBlock(instance.subagentId, {
-                status: "active",
-            });
             if (runInBackground && this.backgroundTaskManager) {
                 const taskId = this.backgroundTaskManager.generateId();
                 const startTime = Date.now();
@@ -153,6 +151,11 @@ export class SubagentManager {
                     description: instance.configuration.description,
                     stdout: "",
                     stderr: "",
+                    subagentId: instance.subagentId,
+                    onStop: () => {
+                        instance.aiManager.abortAIMessage();
+                        this.cleanupInstance(instance.subagentId);
+                    },
                 });
                 instance.backgroundTaskId = taskId;
                 // Execute in background
@@ -184,9 +187,6 @@ export class SubagentManager {
         }
         catch (error) {
             this.updateInstanceStatus(instance.subagentId, "error");
-            this.parentMessageManager.updateSubagentBlock(instance.subagentId, {
-                status: "error",
-            });
             throw error;
         }
     }
@@ -208,35 +208,30 @@ export class SubagentManager {
             description: instance.configuration.description,
             stdout: "",
             stderr: "",
+            subagentId: instance.subagentId,
+            onStop: () => {
+                instance.aiManager.abortAIMessage();
+                this.cleanupInstance(instance.subagentId);
+            },
         });
         instance.backgroundTaskId = taskId;
-        // Update parent message manager to reflect background status
-        this.parentMessageManager.updateSubagentBlock(subagentId, {
-            runInBackground: true,
-        });
         return taskId;
     }
     async internalExecute(instance, prompt, abortSignal) {
         // Set up consolidated abort handler to prevent listener accumulation
         let abortCleanup;
-        if (abortSignal) {
+        // Only link to parent abort signal if NOT running in background
+        if (abortSignal && !instance.backgroundTaskId) {
             abortCleanup = addConsolidatedAbortListener(abortSignal, [
                 () => {
                     // Update status to aborted
-                    // Only update status if it's NOT a background task
-                    if (!instance.backgroundTaskId) {
-                        this.updateInstanceStatus(instance.subagentId, "aborted");
-                        this.parentMessageManager.updateSubagentBlock(instance.subagentId, {
-                            status: "aborted",
-                        });
-                    }
+                    this.updateInstanceStatus(instance.subagentId, "aborted");
+                    // Cleanup instance immediately on abort
+                    this.cleanupInstance(instance.subagentId);
                 },
                 () => {
                     // Abort the AI execution
-                    // Only abort if it's NOT a background task
-                    if (!instance.backgroundTaskId) {
-                        instance.aiManager.abortAIMessage();
-                    }
+                    instance.aiManager.abortAIMessage();
                 },
             ]);
         }
@@ -276,8 +271,6 @@ export class SubagentManager {
                 model: resolvedModel,
             });
             // If we have an abort signal, race against it using utilities to prevent listener accumulation
-            // BUT: If this is a background task, we DON'T want to race against the abort signal
-            // because the abort signal (Esc) should only stop the tool watching the task, not the task itself.
             if (abortSignal && !instance.backgroundTaskId) {
                 await Promise.race([
                     executeAI,
@@ -300,9 +293,6 @@ export class SubagentManager {
             const response = textBlocks.map((block) => block.content).join("\n");
             // Update status to completed and update parent
             this.updateInstanceStatus(instance.subagentId, "completed");
-            this.parentMessageManager.updateSubagentBlock(instance.subagentId, {
-                status: "completed",
-            });
             // If this was transitioned to background, update the background task
             if (instance.backgroundTaskId && this.backgroundTaskManager) {
                 const task = this.backgroundTaskManager.getTask(instance.backgroundTaskId);
@@ -387,82 +377,6 @@ export class SubagentManager {
     cleanup() {
         this.instances.clear();
     }
-    /**
-     * Restore subagent instances from saved session data
-     * This method is called during agent initialization to restore previous subagent states
-     */
-    async restoreSubagentSessions(subagentSessions) {
-        for (const { sessionData, subagentId, configuration } of subagentSessions) {
-            try {
-                // Use the configuration from the SubagentBlock
-                // Create the subagent instance without executing - just restore the state
-                // Create MessageManager for the restored subagent
-                const subagentCallbacks = this.createSubagentCallbacks(subagentId);
-                const messageManager = new MessageManager({
-                    callbacks: subagentCallbacks,
-                    workdir: this.workdir,
-                    logger: this.logger,
-                    sessionType: "subagent",
-                    subagentType: configuration.name, // Use configuration name for restored sessions
-                    memoryRuleManager: this.memoryRuleManager,
-                });
-                // Use the parent tool manager
-                const toolManager = this.parentToolManager;
-                // Determine model to use
-                let modelToUse;
-                const parentModelConfig = this.getModelConfig();
-                if (!configuration.model || configuration.model === "inherit") {
-                    modelToUse = parentModelConfig.agentModel;
-                }
-                else if (configuration.model === "fastModel") {
-                    modelToUse = parentModelConfig.fastModel;
-                }
-                else {
-                    modelToUse = configuration.model;
-                }
-                // Create AIManager for the restored subagent
-                const aiManager = new AIManager({
-                    messageManager,
-                    toolManager,
-                    logger: this.logger,
-                    workdir: this.workdir,
-                    systemPrompt: configuration.systemPrompt,
-                    subagentType: configuration.name, // Use configuration name as subagent type for restored instances
-                    hookManager: this.hookManager,
-                    permissionManager: this.parentToolManager.getPermissionManager(),
-                    getGatewayConfig: this.getGatewayConfig,
-                    getModelConfig: () => ({
-                        ...parentModelConfig,
-                        agentModel: modelToUse,
-                    }),
-                    getMaxInputTokens: this.getMaxInputTokens,
-                    getLanguage: this.getLanguage,
-                    callbacks: {
-                        onUsageAdded: this.onUsageAdded,
-                    },
-                });
-                // Create restored instance
-                const instance = {
-                    subagentId,
-                    configuration,
-                    aiManager,
-                    messageManager,
-                    toolManager,
-                    status: "completed", // Restored sessions are considered completed
-                    messages: sessionData.messages,
-                    subagentType: configuration.name, // Use configuration name as subagent type for restored instances
-                };
-                // IMPORTANT: Store instance in map BEFORE calling setMessages
-                // This ensures the callback can find the instance
-                this.instances.set(subagentId, instance);
-                messageManager.initializeFromSession(sessionData);
-            }
-            catch (error) {
-                this.logger?.warn(`Failed to restore subagent session ${subagentId}:`, error);
-                // Continue with other sessions even if one fails
-            }
-        }
-    }
     /**
      * Create subagent callbacks for a specific subagent ID
      * Extracted to reuse in both create and restore flows
@@ -494,6 +408,19 @@ export class SubagentManager {
                 }
             },
             onToolBlockUpdated: (params) => {
+                // Track last two tool names when a tool starts running
+                if (params.stage === "running" && params.name) {
+                    const instance = this.instances.get(subagentId);
+                    if (instance) {
+                        // Add to lastTools if it's different from the last one or we want to show duplicates
+                        // Based on "ToolA, ToolB" requirement, we'll just keep the last two
+                        instance.lastTools.push(params.name);
+                        if (instance.lastTools.length > 2) {
+                            instance.lastTools.shift();
+                        }
+                        instance.onUpdate?.();
+                    }
+                }
                 // Forward tool block updates to parent via SubagentManager callbacks
                 if (this.callbacks?.onSubagentToolBlockUpdated) {
                     this.callbacks.onSubagentToolBlockUpdated(subagentId, params);
@@ -504,17 +431,24 @@ export class SubagentManager {
                 const instance = this.instances.get(subagentId);
                 if (instance) {
                     instance.messages = messages;
+                    // Trigger the onUpdate callback if provided
+                    instance.onUpdate?.();
                     // Forward subagent message changes to parent via callbacks
                     if (this.callbacks?.onSubagentMessagesChange) {
                         this.callbacks.onSubagentMessagesChange(subagentId, messages);
                     }
                 }
             },
-            onSessionIdChange: (newSessionId) => {
-                // Update the subagent block with the new session ID
-                this.parentMessageManager.updateSubagentBlock(subagentId, {
-                    sessionId: newSessionId,
-                });
+            onLatestTotalTokensChange: (tokens) => {
+                const instance = this.instances.get(subagentId);
+                if (instance) {
+                    // Trigger the onUpdate callback if provided
+                    instance.onUpdate?.();
+                }
+                // Forward latest total tokens to parent via SubagentManager callbacks
+                if (this.callbacks?.onSubagentLatestTotalTokensChange) {
+                    this.callbacks.onSubagentLatestTotalTokensChange(subagentId, tokens);
+                }
             },
         };
     }

package/dist/managers/toolManager.d.ts

@@ -14,6 +14,8 @@ export interface ToolManagerOptions {
     permissionManager?: PermissionManager;
     /** Foreground task manager for backgrounding tasks */
     foregroundTaskManager?: import("../types/processes.js").IForegroundTaskManager;
+    /** Task manager for task management */
+    taskManager?: import("../services/taskManager.js").TaskManager;
     /** Reversion manager for file snapshots */
     reversionManager?: ReversionManager;
     /** Background task manager for background execution */
@@ -37,6 +39,7 @@ declare class ToolManager {
     private permissionManager?;
     private foregroundTaskManager?;
     private reversionManager?;
+    private taskManager?;
     private backgroundTaskManager?;
     private permissionMode?;
     private canUseToolCallback?;
@@ -88,6 +91,10 @@ declare class ToolManager {
     execute(name: string, args: Record<string, unknown>, context: ToolContext): Promise<ToolResult>;
     list(): ToolPlugin[];
     getToolsConfig(): ChatCompletionFunctionTool[];
+    /**
+     * Get the list of registered tool plugins
+     */
+    getTools(): ToolPlugin[];
     /**
      * Get the current permission mode
      */
@@ -101,6 +108,10 @@ declare class ToolManager {
      * Get the permission manager
      */
     getPermissionManager(): PermissionManager | undefined;
+    /**
+     * Get the task manager
+     */
+    getTaskManager(): import("../services/taskManager.js").TaskManager | undefined;
 }
 export { ToolManager };
 //# sourceMappingURL=toolManager.d.ts.map

package/dist/managers/toolManager.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"toolManager.d.ts","sourceRoot":"","sources":["../../src/managers/toolManager.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,WAAW,EAAE,UAAU,EAAE,UAAU,EAAE,MAAM,mBAAmB,CAAC;AAmB7E,OAAO,EAAE,UAAU,EAAE,MAAM,iBAAiB,CAAC;AAC7C,OAAO,EAAE,iBAAiB,EAAE,MAAM,wBAAwB,CAAC;AAC3D,OAAO,EAAE,0BAA0B,EAAE,MAAM,qBAAqB,CAAC;AACjE,OAAO,KAAK,EACV,MAAM,EACN,cAAc,EACd,kBAAkB,EAClB,WAAW,EACZ,MAAM,mBAAmB,CAAC;AAC3B,OAAO,KAAK,EAAE,eAAe,EAAE,MAAM,sBAAsB,CAAC;AAC5D,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,mBAAmB,CAAC;AAEtD,OAAO,EAAE,gBAAgB,EAAE,MAAM,uBAAuB,CAAC;AAEzD,MAAM,WAAW,kBAAkB;IACjC,UAAU,EAAE,UAAU,CAAC;IACvB,UAAU,CAAC,EAAE,WAAW,CAAC;IACzB,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,6DAA6D;IAC7D,iBAAiB,CAAC,EAAE,iBAAiB,CAAC;IACtC,sDAAsD;IACtD,qBAAqB,CAAC,EAAE,OAAO,uBAAuB,EAAE,sBAAsB,CAAC;IAC/E,2CAA2C;IAC3C,gBAAgB,CAAC,EAAE,gBAAgB,CAAC;IACpC,uDAAuD;IACvD,qBAAqB,CAAC,EAAE,OAAO,4BAA4B,EAAE,qBAAqB,CAAC;IACnF,iEAAiE;IACjE,cAAc,CAAC,EAAE,cAAc,CAAC;IAChC,gDAAgD;IAChD,kBAAkB,CAAC,EAAE,kBAAkB,CAAC;CACzC;AAED;;;;;GAKG;AACH,cAAM,WAAW;IACf,OAAO,CAAC,KAAK,CAAiC;IAC9C,OAAO,CAAC,UAAU,CAAa;IAC/B,OAAO,CAAC,UAAU,CAAC,CAAc;IACjC,OAAO,CAAC,MAAM,CAAC,CAAS;IACxB,OAAO,CAAC,iBAAiB,CAAC,CAAoB;IAC9C,OAAO,CAAC,qBAAqB,CAAC,CAAyD;IACvF,OAAO,CAAC,gBAAgB,CAAC,CAAmB;IAC5C,OAAO,CAAC,qBAAqB,CAAC,CAA6D;IAC3F,OAAO,CAAC,cAAc,CAAC,CAAiB;IACxC,OAAO,CAAC,kBAAkB,CAAC,CAAqB;gBAEpC,OAAO,EAAE,kBAAkB;IAavC;;OAEG;IACI,QAAQ,CAAC,IAAI,EAAE,UAAU,GAAG,IAAI;IAIvC;;;;;;;;;;;;;;;;;;;;;;OAsBG;IACI,sBAAsB,CAAC,IAAI,CAAC,EAAE;QACnC,eAAe,CAAC,EAAE,eAAe,CAAC;QAClC,YAAY,CAAC,EAAE,YAAY,CAAC;KAC7B,GAAG,IAAI;IAmCR;;;;;;;;;;;;OAYG;IACG,OAAO,CACX,IAAI,EAAE,MAAM,EACZ,IAAI,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,EAC7B,OAAO,EAAE,WAAW,GACnB,OAAO,CAAC,UAAU,CAAC;IA8DtB,IAAI,IAAI,UAAU,EAAE;IAMpB,cAAc,IAAI,0BAA0B,EAAE;IAmB9C;;OAEG;IACI,iBAAiB,IAAI,cAAc;IAS1C;;;OAGG;IACI,iBAAiB,CAAC,IAAI,EAAE,cAAc,GAAG,IAAI;IAIpD;;OAEG;IACI,oBAAoB,IAAI,iBAAiB,GAAG,SAAS;CAG7D;AAGD,OAAO,EAAE,WAAW,EAAE,CAAC"}
+{"version":3,"file":"toolManager.d.ts","sourceRoot":"","sources":["../../src/managers/toolManager.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,WAAW,EAAE,UAAU,EAAE,UAAU,EAAE,MAAM,mBAAmB,CAAC;AAwB7E,OAAO,EAAE,UAAU,EAAE,MAAM,iBAAiB,CAAC;AAC7C,OAAO,EAAE,iBAAiB,EAAE,MAAM,wBAAwB,CAAC;AAC3D,OAAO,EAAE,0BAA0B,EAAE,MAAM,qBAAqB,CAAC;AACjE,OAAO,KAAK,EACV,MAAM,EACN,cAAc,EACd,kBAAkB,EAClB,WAAW,EACZ,MAAM,mBAAmB,CAAC;AAC3B,OAAO,KAAK,EAAE,eAAe,EAAE,MAAM,sBAAsB,CAAC;AAC5D,OAAO,KAAK,EAAE,YAAY,EAAE,MAAM,mBAAmB,CAAC;AAEtD,OAAO,EAAE,gBAAgB,EAAE,MAAM,uBAAuB,CAAC;AAEzD,MAAM,WAAW,kBAAkB;IACjC,UAAU,EAAE,UAAU,CAAC;IACvB,UAAU,CAAC,EAAE,WAAW,CAAC;IACzB,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,6DAA6D;IAC7D,iBAAiB,CAAC,EAAE,iBAAiB,CAAC;IACtC,sDAAsD;IACtD,qBAAqB,CAAC,EAAE,OAAO,uBAAuB,EAAE,sBAAsB,CAAC;IAC/E,uCAAuC;IACvC,WAAW,CAAC,EAAE,OAAO,4BAA4B,EAAE,WAAW,CAAC;IAC/D,2CAA2C;IAC3C,gBAAgB,CAAC,EAAE,gBAAgB,CAAC;IACpC,uDAAuD;IACvD,qBAAqB,CAAC,EAAE,OAAO,4BAA4B,EAAE,qBAAqB,CAAC;IACnF,iEAAiE;IACjE,cAAc,CAAC,EAAE,cAAc,CAAC;IAChC,gDAAgD;IAChD,kBAAkB,CAAC,EAAE,kBAAkB,CAAC;CACzC;AAED;;;;;GAKG;AACH,cAAM,WAAW;IACf,OAAO,CAAC,KAAK,CAAiC;IAC9C,OAAO,CAAC,UAAU,CAAa;IAC/B,OAAO,CAAC,UAAU,CAAC,CAAc;IACjC,OAAO,CAAC,MAAM,CAAC,CAAS;IACxB,OAAO,CAAC,iBAAiB,CAAC,CAAoB;IAC9C,OAAO,CAAC,qBAAqB,CAAC,CAAyD;IACvF,OAAO,CAAC,gBAAgB,CAAC,CAAmB;IAC5C,OAAO,CAAC,WAAW,CAAC,CAAmD;IACvE,OAAO,CAAC,qBAAqB,CAAC,CAA6D;IAC3F,OAAO,CAAC,cAAc,CAAC,CAAiB;IACxC,OAAO,CAAC,kBAAkB,CAAC,CAAqB;gBAEpC,OAAO,EAAE,kBAAkB;IAcvC;;OAEG;IACI,QAAQ,CAAC,IAAI,EAAE,UAAU,GAAG,IAAI;IAIvC;;;;;;;;;;;;;;;;;;;;;;OAsBG;IACI,sBAAsB,CAAC,IAAI,CAAC,EAAE;QACnC,eAAe,CAAC,EAAE,eAAe,CAAC;QAClC,YAAY,CAAC,EAAE,YAAY,CAAC;KAC7B,GAAG,IAAI;IAsCR;;;;;;;;;;;;OAYG;IACG,OAAO,CACX,IAAI,EAAE,MAAM,EACZ,IAAI,EAAE,MAAM,CAAC,MAAM,EAAE,OAAO,CAAC,EAC7B,OAAO,EAAE,WAAW,GACnB,OAAO,CAAC,UAAU,CAAC;IAgEtB,IAAI,IAAI,UAAU,EAAE;IAMpB,cAAc,IAAI,0BAA0B,EAAE;IAmB9C;;OAEG;IACI,QAAQ,IAAI,UAAU,EAAE;IAI/B;;OAEG;IACI,iBAAiB,IAAI,cAAc;IAS1C;;;OAGG;IACI,iBAAiB,CAAC,IAAI,EAAE,cAAc,GAAG,IAAI;IAIpD;;OAEG;IACI,oBAAoB,IAAI,iBAAiB,GAAG,SAAS;IAI5D;;OAEG;IACI,cAAc,IACjB,OAAO,4BAA4B,EAAE,WAAW,GAChD,SAAS;CAGd;AAGD,OAAO,EAAE,WAAW,EAAE,CAAC"}

package/dist/managers/toolManager.js

@@ -12,10 +12,10 @@ import { globTool } from "../tools/globTool.js";
 import { grepTool } from "../tools/grepTool.js";
 import { lsTool } from "../tools/lsTool.js";
 import { readTool } from "../tools/readTool.js";
-import { todoWriteTool } from "../tools/todoWriteTool.js";
 import { lspTool } from "../tools/lspTool.js";
 import { createTaskTool } from "../tools/taskTool.js";
 import { createSkillTool } from "../tools/skillTool.js";
+import { taskCreateTool, taskGetTool, taskUpdateTool, taskListTool, } from "../tools/taskManagementTools.js";
 /**
  * Tool Manager
  *
@@ -29,6 +29,7 @@ class ToolManager {
         this.lspManager = options.lspManager;
         this.logger = options.logger;
         this.permissionManager = options.permissionManager;
+        this.taskManager = options.taskManager;
         this.foregroundTaskManager = options.foregroundTaskManager;
         this.reversionManager = options.reversionManager;
         this.backgroundTaskManager = options.backgroundTaskManager;
@@ -80,8 +81,11 @@ class ToolManager {
             grepTool,
             lsTool,
             readTool,
-            todoWriteTool,
             lspTool,
+            taskCreateTool,
+            taskGetTool,
+            taskUpdateTool,
+            taskListTool,
         ];
         for (const tool of builtInTools) {
             this.tools.set(tool.name, tool);
@@ -120,11 +124,13 @@ class ToolManager {
             permissionMode: effectivePermissionMode,
             canUseToolCallback: this.canUseToolCallback,
             permissionManager: this.permissionManager,
+            taskManager: this.taskManager,
             reversionManager: this.reversionManager,
             backgroundTaskManager: this.backgroundTaskManager,
             foregroundTaskManager: this.foregroundTaskManager,
             mcpManager: this.mcpManager,
             lspManager: this.lspManager,
+            sessionId: context.sessionId,
         };
         this.logger?.debug("Executing tool with enhanced context", {
             toolName: name,
@@ -185,6 +191,12 @@ class ToolManager {
         const mcpToolsConfig = this.mcpManager.getMcpToolsConfig();
         return [...builtInToolsConfig, ...mcpToolsConfig];
     }
+    /**
+     * Get the list of registered tool plugins
+     */
+    getTools() {
+        return Array.from(this.tools.values());
+    }
     /**
      * Get the current permission mode
      */
@@ -207,6 +219,12 @@ class ToolManager {
     getPermissionManager() {
         return this.permissionManager;
     }
+    /**
+     * Get the task manager
+     */
+    getTaskManager() {
+        return this.taskManager;
+    }
 }
 // Export tool registry class and types
 export { ToolManager };

package/dist/{constants/prompts.d.ts → prompts/index.d.ts}

@@ -1,20 +1,22 @@
+import { ToolPlugin } from "../tools/types.js";
 export declare 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.\n\n# Doing tasks\nThe 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:\n- 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.\n- 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.\n- Avoid over-engineering. Only make changes that are directly requested or clearly necessary. Keep solutions simple and focused.\n  - 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.\n  - 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.\n  - 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\u2014three similar lines of code is better than a premature abstraction.\n- 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.\n\n# Tool usage policy\n- 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.\n- 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.\n- 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 declare const TASK_MANAGEMENT_POLICY = "\n# Task Management\nYou have access to the TodoWrite 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.\nThese 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.\nIt 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 declare const ASK_USER_POLICY = "\n# Asking questions as you work\nYou have access to the AskUserQuestion 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 declare const SUBAGENT_POLICY = "\n- When doing file search, prefer to use the Task tool in order to reduce context usage.\n- You should proactively use the Task tool with specialized agents when the task at hand matches the agent's description.\n- 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 with subagent_type=Explore instead of running search commands directly.";
-export declare 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 declare const READ_FILE_POLICY = " Read for reading files instead of cat/head/tail";
-export declare const EDIT_FILE_POLICY = " Edit/MultiEdit for editing instead of sed/awk";
-export declare const WRITE_FILE_POLICY = " Write for creating files instead of cat with heredoc or echo redirection";
-export declare const SEARCH_FILE_POLICY = " LS/Glob/Grep for searching and listing files instead of find/ls/grep";
-export declare const BASH_POLICY = "\n- 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.\n- 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 declare const TASK_MANAGEMENT_POLICY = "\n# Task Management\nYou have access to the TaskCreate, TaskGet, TaskUpdate, and TaskList 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.\nThese 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.\nIt is critical that you mark tasks as completed as soon as you are done with a task. Do not batch up multiple tasks before marking them as completed.";
+export declare function buildPlanModePrompt(planFilePath: string, planExists: boolean, isSubagent?: boolean): string;
 export declare const DEFAULT_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.\n\n# Doing tasks\nThe 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:\n- 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.\n- 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.\n- Avoid over-engineering. Only make changes that are directly requested or clearly necessary. Keep solutions simple and focused.\n  - 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.\n  - 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.\n  - 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\u2014three similar lines of code is better than a premature abstraction.\n- 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.\n\n# Tool usage policy\n- 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.\n- 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.\n- 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 declare const BASH_SUBAGENT_SYSTEM_PROMPT = "You are a command execution specialist. Your role is to execute bash commands efficiently and safely.\n\nGuidelines:\n- Execute commands precisely as instructed\n- For git operations, follow git safety protocols\n- Report command output clearly and concisely\n- If a command fails, explain the error and suggest solutions\n- Use command chaining (&&) for dependent operations\n- Quote paths with spaces properly\n- For clear communication, avoid using emojis\n\nComplete the requested operations efficiently.";
 export declare 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.\n\nYour strengths:\n- Searching for code, configurations, and patterns across large codebases\n- Analyzing multiple files to understand system architecture\n- Investigating complex questions that require exploring many files\n- Performing multi-step research tasks\n\nGuidelines:\n- For file searches: Use Grep or Glob when you need to search broadly. Use Read when you know the specific file path.\n- For analysis: Start broad and narrow down. Use multiple search strategies if the first doesn't yield results.\n- Be thorough: Check multiple locations, consider different naming conventions, look for related files.\n- NEVER create files unless they're absolutely necessary for achieving your goal. ALWAYS prefer editing an existing file to creating a new one.\n- NEVER proactively create documentation files (*.md) or README files. Only create documentation files if explicitly requested.\n- 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.\n- For clear communication, avoid using emojis.";
+export declare const EXPLORE_SUBAGENT_SYSTEM_PROMPT = "You are a file search specialist. You excel at thoroughly navigating and exploring codebases.\n\t\n\t=== CRITICAL: READ-ONLY MODE - NO FILE MODIFICATIONS ===\n\tThis is a READ-ONLY exploration task. You are STRICTLY PROHIBITED from:\n\t- Creating new files (no Write, touch, or file creation of any kind)\n\t- Modifying existing files (no Edit operations)\n\t- Deleting files (no rm or deletion)\n\t- Moving or copying files (no mv or cp)\n\t- Creating temporary files anywhere, including /tmp\n\t- Using redirect operators (>, >>, |) or heredocs to write to files\n\t- Running ANY commands that change system state\n\t\n\tYour role is EXCLUSIVELY to search and analyze existing code. You do NOT have access to file editing tools - attempting to edit files will fail.\n\t\n\tYour strengths:\n\t- Rapidly finding files using glob patterns\n\t- Searching code and text with powerful regex patterns\n\t- Reading and analyzing file contents\n\t- Using Language Server Protocol (LSP) for deep code intelligence (definitions, references, etc.)\n\t\n\tGuidelines:\n\t- Use Glob for broad file pattern matching\n\t- Use Grep for searching file contents with regex\n\t- Use Read when you know the specific file path you need to read\n\t- Use LSP for code intelligence features like finding definitions, references, implementations, and symbols. This is especially useful for understanding complex code relationships.\n\t- Use Bash ONLY for read-only operations (ls, git status, git log, git diff, find, cat, head, tail)\n\t- NEVER use Bash for: mkdir, touch, rm, cp, mv, git add, git commit, npm install, pip install, or any file creation/modification\n\t- Adapt your search approach based on the thoroughness level specified by the caller\n\t- Return file paths as absolute paths in your final response\n\t- For clear communication, avoid using emojis\n\t- Communicate your final report directly as a regular message - do NOT attempt to create files\n\t\n\tNOTE: You are meant to be a fast agent that returns output as quickly as possible. In order to achieve this you must:\n\t- Make efficient use of the tools that you have at your disposal: be smart about how you search for files and implementations\n\t- Wherever possible you should try to spawn multiple parallel tool calls for grepping and reading files\n\t\n\tComplete the user's search request efficiently and report your findings clearly.";
+export declare const PLAN_SUBAGENT_SYSTEM_PROMPT = "You are a software architect and planning specialist. Your role is to explore the codebase and design implementation plans.\n\n=== CRITICAL: READ-ONLY MODE - NO FILE MODIFICATIONS ===\nThis is a READ-ONLY planning task. You are STRICTLY PROHIBITED from:\n- Creating new files (no Write, touch, or file creation of any kind)\n- Modifying existing files (no Edit operations)\n- Deleting files (no rm or deletion)\n- Moving or copying files (no mv or cp)\n- Creating temporary files anywhere, including /tmp\n- Using redirect operators (>, >>, |) or heredocs to write to files\n- Running ANY commands that change system state\n\nYour 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.\n\nYou will be provided with a set of requirements and optionally a perspective on how to approach the design process.\n\n## Your Process\n\n1. **Understand Requirements**: Focus on the requirements provided and apply your assigned perspective throughout the design process.\n\n2. **Explore Thoroughly**:\n   - Read any files provided to you in the initial prompt\n   - Find existing patterns and conventions using Glob, Grep, and Read\n   - Understand the current architecture\n   - Identify similar features as reference\n   - Trace through relevant code paths\n   - Use Bash ONLY for read-only operations (ls, git status, git log, git diff, find, cat, head, tail)\n   - NEVER use Bash for: mkdir, touch, rm, cp, mv, git add, git commit, npm install, pip install, or any file creation/modification\n\n3. **Design Solution**:\n   - Create implementation approach based on your assigned perspective\n   - Consider trade-offs and architectural decisions\n   - Follow existing patterns where appropriate\n\n4. **Detail the Plan**:\n   - Provide step-by-step implementation strategy\n   - Identify dependencies and sequencing\n   - Anticipate potential challenges\n\n## Required Output\n\nEnd your response with:\n\n### Critical Files for Implementation\nList 3-5 files most critical for implementing this plan:\n- path/to/file1.ts - [Brief reason: e.g., \"Core logic to modify\"]\n- path/to/file2.ts - [Brief reason: e.g., \"Interfaces to implement\"]\n- path/to/file3.ts - [Brief reason: e.g., \"Pattern to follow\"]\n\nREMEMBER: 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 declare 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.\n\nWhat to add:\n1. 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.\n2. 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.\n\nUsage notes:\n- If there's already a AGENTS.md, suggest improvements to it.\n- 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\".\n- Avoid listing every component or file structure that can be easily discovered.\n- Don't include generic development practices.\n- 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.\n- If there is a README.md, make sure to include the important parts.\n- 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.\n- Be sure to prefix the file with the following text:\n\n```\n# AGENTS.md\n\nThis file provides guidance to Agent when working with code in this repository.\n```";
-export declare function buildSystemPrompt(basePrompt: string, tools: {
-    name?: string;
-    function?: {
-        name: string;
+export declare 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:\n1. Task Overview\nThe user's core request and success criteria\nAny clarifications or constraints they specified\n2. Current State\nWhat has been completed so far\nFiles created, modified, or analyzed (with paths if relevant)\nKey outputs or artifacts produced\n3. Important Discoveries\nTechnical constraints or requirements uncovered\nDecisions made and their rationale\nErrors encountered and how they were resolved\nWhat approaches were tried that didn't work (and why)\n4. Next Steps\nSpecific actions needed to complete the task\nAny blockers or open questions to resolve\nPriority order if multiple steps remain\n5. Context to Preserve\nUser preferences or style requirements\nDomain-specific details that aren't obvious\nAny promises made to the user\nBe concise but complete\u2014err on the side of including information that would prevent duplicate work or repeated mistakes. Write in a way that enables immediate resumption of the task.\nWrap your summary in <summary></summary> tags.";
+export declare function buildSystemPrompt(basePrompt: string | undefined, tools: ToolPlugin[], options?: {
+    workdir?: string;
+    memory?: string;
+    language?: string;
+    isSubagent?: boolean;
+    planMode?: {
+        planFilePath: string;
+        planExists: boolean;
     };
-}[]): string;
-//# sourceMappingURL=prompts.d.ts.map
+}): string;
+//# sourceMappingURL=index.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../src/prompts/index.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,UAAU,EAAE,MAAM,mBAAmB,CAAC;AAqB/C,eAAO,MAAM,kBAAkB,ksFAe8G,CAAC;AAE9I,eAAO,MAAM,sBAAsB,moBAImH,CAAC;AAEvJ,wBAAgB,mBAAmB,CACjC,YAAY,EAAE,MAAM,EACpB,UAAU,EAAE,OAAO,EACnB,UAAU,GAAE,OAAe,GAC1B,MAAM,CAmFR;AAED,eAAO,MAAM,qBAAqB,ksFAAqB,CAAC;AAExD,eAAO,MAAM,2BAA2B,igBAWO,CAAC;AAEhD,eAAO,MAAM,6BAA6B,izCAeK,CAAC;AAEhD,eAAO,MAAM,8BAA8B,21EAoCuC,CAAC;AAEnF,eAAO,MAAM,2BAA2B,25EAiDyG,CAAC;AAElJ,eAAO,MAAM,WAAW,kkDAoBjB,CAAC;AAER,eAAO,MAAM,+BAA+B,20CAsBG,CAAC;AAEhD,wBAAgB,iBAAiB,CAC/B,UAAU,EAAE,MAAM,GAAG,SAAS,EAC9B,KAAK,EAAE,UAAU,EAAE,EACnB,OAAO,GAAE;IACP,OAAO,CAAC,EAAE,MAAM,CAAC;IACjB,MAAM,CAAC,EAAE,MAAM,CAAC;IAChB,QAAQ,CAAC,EAAE,MAAM,CAAC;IAClB,UAAU,CAAC,EAAE,OAAO,CAAC;IACrB,QAAQ,CAAC,EAAE;QACT,YAAY,EAAE,MAAM,CAAC;QACrB,UAAU,EAAE,OAAO,CAAC;KACrB,CAAC;CACE,GACL,MAAM,CAmDR"}