sema-core 1.0.2

package/dist/tools/Task/prompt.js

@@ -0,0 +1,75 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.TOOL_NAME_FOR_PROMPT = void 0;
+exports.getDescription = getDescription;
+const agentsManager_1 = require("../../services/agents/agentsManager");
+exports.TOOL_NAME_FOR_PROMPT = 'Task';
+/**
+ * 获取 Task 工具的完整描述
+ */
+function getDescription() {
+    const agentTypesDesc = (0, agentsManager_1.getAgentTypesDescription)();
+    return `Launch a new agent to handle complex, multi-step tasks autonomously.
+
+The Task tool launches specialized agents (subprocesses) that autonomously handle complex tasks. Each agent type has specific capabilities and tools available to it.
+
+Available agent types and the tools they have access to:
+${agentTypesDesc}
+
+When using the Task tool, you must specify a subagent_type parameter to select which agent type to use.
+
+When NOT to use the Task tool:
+- If you want to read a specific file path, use the Read or Glob tool instead of the Task tool, to find the match more quickly
+- If you are searching for a specific class definition like "class Foo", use the Glob tool instead, to find the match more quickly
+- If you are searching for code within a specific file or set of 2-3 files, use the Read tool instead of the Task tool, to find the match more quickly
+- Other tasks that are not related to the agent descriptions above
+
+
+Usage notes:
+- Always include a short description (3-5 words) summarizing what the agent will do
+- Call only one agent at a time to maintain clarity and control over task execution.
+- When the agent is done, it will return a single message back to you. The result returned by the agent is not visible to the user. To show the user the result, you should send a text message back to the user with a concise summary of the result.
+- When the agent is done, it will return a single message back to you along with its agent ID. 
+- Provide clear, detailed prompts so the agent can work autonomously and return exactly the information you need.
+- The agent's outputs should generally be trusted
+- Clearly tell the agent whether you expect it to write code or just to do research (search, file reads, web fetches, etc.), since it is not aware of the user's intent
+- If the agent description mentions that it should be used proactively, then you should try your best to use it without the user having to ask for it first. Use your judgement.
+- If the user specifies that they want you to run agents "in parallel", you MUST send a single message with multiple Task tool use content blocks. For example, if you need to launch both a build-validator agent and a test-runner agent in parallel, send a single message with both tool calls.
+
+Example usage:
+
+<example_agent_descriptions>
+"test-runner": use this agent after you are done writing code to run tests
+"greeting-responder": use this agent when to respond to user greetings with a friendly joke
+</example_agent_description>
+
+<example>
+user: "Please write a function that checks if a number is prime"
+assistant: Sure let me write a function that checks if a number is prime
+assistant: First let me use the Write tool to write a function that checks if a number is prime
+assistant: I'm going to use the Write tool to write the following code:
+<code>
+function isPrime(n) {
+  if (n <= 1) return false
+  for (let i = 2; i * i <= n; i++) {
+    if (n % i === 0) return false
+  }
+  return true
+}
+</code>
+<commentary>
+Since a significant piece of code was written and the task was completed, now use the test-runner agent to run the tests
+</commentary>
+assistant: Now let me use the test-runner agent to run the tests
+assistant: Uses the Task tool to launch the test-runner agent
+</example>
+
+<example>
+user: "Hello"
+<commentary>
+Since the user is greeting, use the greeting-responder agent to respond with a friendly joke
+</commentary>
+assistant: "I'm going to use the Task tool to launch the greeting-responder agent"
+</example>`;
+}
+//# sourceMappingURL=prompt.js.map

package/dist/tools/Task/prompt.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"prompt.js","sourceRoot":"","sources":["../../../src/tools/Task/prompt.ts"],"names":[],"mappings":";;;AAOA,wCAkEC;AAzED,uEAA8E;AAEjE,QAAA,oBAAoB,GAAG,MAAM,CAAA;AAE1C;;GAEG;AACH,SAAgB,cAAc;IAC5B,MAAM,cAAc,GAAG,IAAA,wCAAwB,GAAE,CAAA;IAEjD,OAAO;;;;;EAKP,cAAc;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;WAwDL,CAAA;AAEX,CAAC"}

package/dist/tools/TodoWrite/TodoWrite.d.ts

@@ -0,0 +1,92 @@
+import { z } from 'zod';
+import { ValidationResult } from '../base/Tool';
+declare const TodoItemSchema: z.ZodObject<{
+    content: z.ZodString;
+    status: z.ZodEnum<["pending", "in_progress", "completed"]>;
+    activeForm: z.ZodString;
+}, "strict", z.ZodTypeAny, {
+    status: "pending" | "in_progress" | "completed";
+    content: string;
+    activeForm: string;
+}, {
+    status: "pending" | "in_progress" | "completed";
+    content: string;
+    activeForm: string;
+}>;
+declare const inputSchema: z.ZodObject<{
+    todos: z.ZodArray<z.ZodObject<{
+        content: z.ZodString;
+        status: z.ZodEnum<["pending", "in_progress", "completed"]>;
+        activeForm: z.ZodString;
+    }, "strict", z.ZodTypeAny, {
+        status: "pending" | "in_progress" | "completed";
+        content: string;
+        activeForm: string;
+    }, {
+        status: "pending" | "in_progress" | "completed";
+        content: string;
+        activeForm: string;
+    }>, "many">;
+}, "strict", z.ZodTypeAny, {
+    todos: {
+        status: "pending" | "in_progress" | "completed";
+        content: string;
+        activeForm: string;
+    }[];
+}, {
+    todos: {
+        status: "pending" | "in_progress" | "completed";
+        content: string;
+        activeForm: string;
+    }[];
+}>;
+type TodoItem = z.infer<typeof TodoItemSchema>;
+export declare const TodoWriteTool: {
+    name: string;
+    description(): string;
+    inputSchema: z.ZodObject<{
+        todos: z.ZodArray<z.ZodObject<{
+            content: z.ZodString;
+            status: z.ZodEnum<["pending", "in_progress", "completed"]>;
+            activeForm: z.ZodString;
+        }, "strict", z.ZodTypeAny, {
+            status: "pending" | "in_progress" | "completed";
+            content: string;
+            activeForm: string;
+        }, {
+            status: "pending" | "in_progress" | "completed";
+            content: string;
+            activeForm: string;
+        }>, "many">;
+    }, "strict", z.ZodTypeAny, {
+        todos: {
+            status: "pending" | "in_progress" | "completed";
+            content: string;
+            activeForm: string;
+        }[];
+    }, {
+        todos: {
+            status: "pending" | "in_progress" | "completed";
+            content: string;
+            activeForm: string;
+        }[];
+    }>;
+    isReadOnly(): false;
+    genResultForAssistant(result: string | TodoItem[]): string;
+    validateInput({ todos }: z.infer<typeof inputSchema>): Promise<ValidationResult>;
+    call({ todos }: z.infer<typeof inputSchema>, agentContext: any): AsyncGenerator<{
+        type: "result";
+        data: string;
+        resultForAssistant: string;
+    } | {
+        type: "result";
+        data: {
+            status: "pending" | "in_progress" | "completed";
+            content: string;
+            activeForm: string;
+        }[];
+        resultForAssistant: string;
+    }, void, unknown>;
+};
+export {};
+//# sourceMappingURL=TodoWrite.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"TodoWrite.d.ts","sourceRoot":"","sources":["../../../src/tools/TodoWrite/TodoWrite.ts"],"names":[],"mappings":"AACA,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAA;AACvB,OAAO,EAAQ,gBAAgB,EAAE,MAAM,cAAc,CAAA;AAIrD,QAAA,MAAM,cAAc;;;;;;;;;;;;EAKlB,CAAA;AAEF,QAAA,MAAM,WAAW;;;;;;;;;;;;;;;;;;;;;;;;;;EAEf,CAAA;AAEF,KAAK,QAAQ,GAAG,CAAC,CAAC,KAAK,CAAC,OAAO,cAAc,CAAC,CAAA;AAsC9C,eAAO,MAAM,aAAa;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;kCASM,MAAM,GAAG,QAAQ,EAAE;6BAIlB,CAAC,CAAC,KAAK,CAAC,OAAO,WAAW,CAAC;oBAOnC,CAAC,CAAC,KAAK,CAAC,OAAO,WAAW,CAAC,gBAAgB,GAAG;;;;;;;;;;;;;CAkCd,CAAA"}

package/dist/tools/TodoWrite/TodoWrite.js

@@ -0,0 +1,101 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.TodoWriteTool = void 0;
+const zod_1 = require("zod");
+const prompt_1 = require("./prompt");
+const StateManager_1 = require("../../manager/StateManager");
+const TodoItemSchema = zod_1.z.strictObject({
+    content: zod_1.z.string().min(1),
+    status: zod_1.z
+        .enum(['pending', 'in_progress', 'completed']),
+    activeForm: zod_1.z.string().min(1),
+});
+const inputSchema = zod_1.z.strictObject({
+    todos: zod_1.z.array(TodoItemSchema).describe('The updated todo list'),
+});
+function validateTodos(todos) {
+    // Check for multiple in_progress tasks
+    const inProgressTasks = todos.filter(todo => todo.status === 'in_progress');
+    if (inProgressTasks.length > 1) {
+        return {
+            result: false,
+            errorCode: 2,
+            message: 'Only one task can be in_progress at a time',
+            meta: { inProgressTaskCount: inProgressTasks.length },
+        };
+    }
+    // Validate each todo
+    for (let i = 0; i < todos.length; i++) {
+        const todo = todos[i];
+        if (!todo.content?.trim()) {
+            return {
+                result: false,
+                errorCode: 3,
+                message: `Todo at index ${i} has empty content`,
+                meta: { todoIndex: i },
+            };
+        }
+        if (!todo.activeForm?.trim()) {
+            return {
+                result: false,
+                errorCode: 5,
+                message: `Todo at index ${i} has empty activeForm`,
+                meta: { todoIndex: i },
+            };
+        }
+    }
+    return { result: true };
+}
+exports.TodoWriteTool = {
+    name: prompt_1.TOOL_NAME_FOR_PROMPT,
+    description() {
+        return prompt_1.DESCRIPTION;
+    },
+    inputSchema,
+    isReadOnly() {
+        return false;
+    },
+    genResultForAssistant(result) {
+        return 'Todos have been modified successfully. Ensure that you continue to use the todo list to track your progress. Please proceed with the current tasks if applicable';
+    },
+    async validateInput({ todos }) {
+        const validation = validateTodos(todos);
+        if (!validation.result) {
+            return validation;
+        }
+        return { result: true };
+    },
+    async *call({ todos }, agentContext) {
+        try {
+            // Simple validation
+            const validation = validateTodos(todos);
+            if (!validation.result) {
+                yield {
+                    type: 'result',
+                    data: `Error: ${validation.message}`,
+                    resultForAssistant: `Error: ${validation.message}`,
+                };
+                return;
+            }
+            // 通过 agentContext 更新 todos（使用智能更新，包含事件发送）
+            const stateManager = (0, StateManager_1.getStateManager)();
+            const agentState = stateManager.forAgent(agentContext.agentId);
+            agentState.updateTodosIntelligently(todos);
+            yield {
+                type: 'result',
+                data: todos, // Return the todos array for rendering
+                resultForAssistant: 'Todos have been modified successfully. Ensure that you continue to use the todo list to track your progress. Please proceed with the current tasks if applicable',
+            };
+        }
+        catch (error) {
+            const errorMessage = error instanceof Error ? error.message : 'Unknown error occurred';
+            const errorResult = `Error updating todos: ${errorMessage}`;
+            yield {
+                type: 'result',
+                data: errorResult,
+                resultForAssistant: errorResult,
+            };
+        }
+    },
+};
+//# sourceMappingURL=TodoWrite.js.map

package/dist/tools/TodoWrite/TodoWrite.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"TodoWrite.js","sourceRoot":"","sources":["../../../src/tools/TodoWrite/TodoWrite.ts"],"names":[],"mappings":";;;AACA,6BAAuB;AAEvB,qCAA4D;AAC5D,6DAA4D;AAE5D,MAAM,cAAc,GAAG,OAAC,CAAC,YAAY,CAAC;IACpC,OAAO,EAAE,OAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC;IAC1B,MAAM,EAAE,OAAC;SACN,IAAI,CAAC,CAAC,SAAS,EAAE,aAAa,EAAE,WAAW,CAAC,CAAC;IAChD,UAAU,EAAE,OAAC,CAAC,MAAM,EAAE,CAAC,GAAG,CAAC,CAAC,CAAC;CAC9B,CAAC,CAAA;AAEF,MAAM,WAAW,GAAG,OAAC,CAAC,YAAY,CAAC;IACjC,KAAK,EAAE,OAAC,CAAC,KAAK,CAAC,cAAc,CAAC,CAAC,QAAQ,CAAC,uBAAuB,CAAC;CACjE,CAAC,CAAA;AAIF,SAAS,aAAa,CAAC,KAAiB;IACtC,uCAAuC;IACvC,MAAM,eAAe,GAAG,KAAK,CAAC,MAAM,CAAC,IAAI,CAAC,EAAE,CAAC,IAAI,CAAC,MAAM,KAAK,aAAa,CAAC,CAAA;IAC3E,IAAI,eAAe,CAAC,MAAM,GAAG,CAAC,EAAE,CAAC;QAC/B,OAAO;YACL,MAAM,EAAE,KAAK;YACb,SAAS,EAAE,CAAC;YACZ,OAAO,EAAE,4CAA4C;YACrD,IAAI,EAAE,EAAE,mBAAmB,EAAE,eAAe,CAAC,MAAM,EAAE;SACtD,CAAA;IACH,CAAC;IAED,qBAAqB;IACrB,KAAK,IAAI,CAAC,GAAG,CAAC,EAAE,CAAC,GAAG,KAAK,CAAC,MAAM,EAAE,CAAC,EAAE,EAAE,CAAC;QACtC,MAAM,IAAI,GAAG,KAAK,CAAC,CAAC,CAAC,CAAA;QACrB,IAAI,CAAC,IAAI,CAAC,OAAO,EAAE,IAAI,EAAE,EAAE,CAAC;YAC1B,OAAO;gBACL,MAAM,EAAE,KAAK;gBACb,SAAS,EAAE,CAAC;gBACZ,OAAO,EAAE,iBAAiB,CAAC,oBAAoB;gBAC/C,IAAI,EAAE,EAAE,SAAS,EAAE,CAAC,EAAE;aACvB,CAAA;QACH,CAAC;QACD,IAAI,CAAC,IAAI,CAAC,UAAU,EAAE,IAAI,EAAE,EAAE,CAAC;YAC7B,OAAO;gBACL,MAAM,EAAE,KAAK;gBACb,SAAS,EAAE,CAAC;gBACZ,OAAO,EAAE,iBAAiB,CAAC,uBAAuB;gBAClD,IAAI,EAAE,EAAE,SAAS,EAAE,CAAC,EAAE;aACvB,CAAA;QACH,CAAC;IACH,CAAC;IAED,OAAO,EAAE,MAAM,EAAE,IAAI,EAAE,CAAA;AACzB,CAAC;AAEY,QAAA,aAAa,GAAG;IAC3B,IAAI,EAAE,6BAAoB;IAC1B,WAAW;QACT,OAAO,oBAAW,CAAA;IACpB,CAAC;IACD,WAAW;IACX,UAAU;QACR,OAAO,KAAK,CAAA;IACd,CAAC;IACD,qBAAqB,CAAC,MAA2B;QAC/C,OAAO,kKAAkK,CAAA;IAC3K,CAAC;IAED,KAAK,CAAC,aAAa,CAAC,EAAE,KAAK,EAA+B;QACxD,MAAM,UAAU,GAAG,aAAa,CAAC,KAAK,CAAC,CAAA;QACvC,IAAI,CAAC,UAAU,CAAC,MAAM,EAAE,CAAC;YACvB,OAAO,UAAU,CAAA;QACnB,CAAC;QACD,OAAO,EAAE,MAAM,EAAE,IAAI,EAAE,CAAA;IACzB,CAAC;IACD,KAAK,CAAC,CAAC,IAAI,CAAC,EAAE,KAAK,EAA+B,EAAE,YAAiB;QACnE,IAAI,CAAC;YACH,oBAAoB;YACpB,MAAM,UAAU,GAAG,aAAa,CAAC,KAAK,CAAC,CAAA;YACvC,IAAI,CAAC,UAAU,CAAC,MAAM,EAAE,CAAC;gBACvB,MAAM;oBACJ,IAAI,EAAE,QAAQ;oBACd,IAAI,EAAE,UAAU,UAAU,CAAC,OAAO,EAAE;oBACpC,kBAAkB,EAAE,UAAU,UAAU,CAAC,OAAO,EAAE;iBACnD,CAAA;gBACD,OAAM;YACR,CAAC;YAED,0CAA0C;YAC1C,MAAM,YAAY,GAAG,IAAA,8BAAe,GAAE,CAAA;YACtC,MAAM,UAAU,GAAG,YAAY,CAAC,QAAQ,CAAC,YAAY,CAAC,OAAO,CAAC,CAAA;YAC9D,UAAU,CAAC,wBAAwB,CAAC,KAAK,CAAC,CAAA;YAE1C,MAAM;gBACJ,IAAI,EAAE,QAAQ;gBACd,IAAI,EAAE,KAAK,EAAE,uCAAuC;gBACpD,kBAAkB,EAAE,kKAAkK;aACvL,CAAA;QACH,CAAC;QAAC,OAAO,KAAK,EAAE,CAAC;YACf,MAAM,YAAY,GAAG,KAAK,YAAY,KAAK,CAAC,CAAC,CAAC,KAAK,CAAC,OAAO,CAAC,CAAC,CAAC,wBAAwB,CAAA;YACtF,MAAM,WAAW,GAAG,yBAAyB,YAAY,EAAE,CAAA;YAE3D,MAAM;gBACJ,IAAI,EAAE,QAAQ;gBACd,IAAI,EAAE,WAAW;gBACjB,kBAAkB,EAAE,WAAW;aAChC,CAAA;QACH,CAAC;IACH,CAAC;CACsD,CAAA"}

package/dist/tools/TodoWrite/prompt.d.ts

@@ -0,0 +1,3 @@
+export declare const TOOL_NAME_FOR_PROMPT = "TodoWrite";
+export declare const DESCRIPTION = "Use this tool to create and manage a structured task list for your current coding session. This helps you track progress, organize complex tasks, and demonstrate thoroughness to the user.\nIt also helps the user understand the progress of the task and overall progress of their requests.\n\n## When to Use This Tool\nUse this tool proactively in these scenarios:\n\n1. Complex multi-step tasks - When a task requires 3 or more distinct steps or actions\n2. Non-trivial and complex tasks - Tasks that require careful planning or multiple operations\n3. User explicitly requests todo list - When the user directly asks you to use the todo list\n4. User provides multiple tasks - When users provide a list of things to be done (numbered or comma-separated)\n5. After receiving new instructions - Immediately capture user requirements as todos\n6. When you start working on a task - Mark it as in_progress BEFORE beginning work. Ideally you should only have one todo as in_progress at a time\n7. After completing a task - Mark it as completed and add any new follow-up tasks discovered during implementation\n\n## When NOT to Use This Tool\n\nSkip using this tool when:\n1. There is only a single, straightforward task\n2. The task is trivial and tracking it provides no organizational benefit\n3. The task can be completed in less than 3 trivial steps\n4. The task is purely conversational or informational\n\nNOTE that you should not use this tool if there is only one trivial task to do. In this case you are better off just doing the task directly.\n\n## Examples of When to Use the Todo List\n\n<example>\nUser: I want to add a dark mode toggle to the application settings. Make sure you run the tests and build when you're done!\nAssistant: I'll help add a dark mode toggle to your application settings. Let me create a todo list to track this implementation.\n*Creates todo list with the following items:*\n1. Creating dark mode toggle component in Settings page\n2. Adding dark mode state management (context/store)\n3. Implementing CSS-in-JS styles for dark theme\n4. Updating existing components to support theme switching\n5. Running tests and build process, addressing any failures or errors that occur\n*Begins working on the first task*\n\n<reasoning>\nThe assistant used the todo list because:\n1. Adding dark mode is a multi-step feature requiring UI, state management, and styling changes\n2. The user explicitly requested tests and build be run afterward\n3. The assistant inferred that tests and build need to pass by adding \"Ensure tests and build succeed\" as the final task\n</reasoning>\n</example>\n\n<example>\nUser: Help me rename the function getCwd to getCurrentWorkingDirectory across my project\nAssistant: Let me first search through your codebase to find all occurrences of 'getCwd'.\n*Uses grep or search tools to locate all instances of getCwd in the codebase*\nAssistant: I've found 15 instances of 'getCwd' across 8 different files. Let me create a todo list to track these changes.\n*Creates todo list with specific items for each file that needs updating*\n\n<reasoning>\nThe assistant used the todo list because:\n1. First, the assistant searched to understand the scope of the task\n2. Upon finding multiple occurrences across different files, it determined this was a complex task with multiple steps\n3. The todo list helps ensure every instance is tracked and updated systematically\n4. This approach prevents missing any occurrences and maintains code consistency\n</reasoning>\n</example>\n\n\n<example>\nUser: I need to implement these features for my e-commerce site: user registration, product catalog, shopping cart, and checkout flow.\nAssistant: I'll help implement these features. First, let's add all the features to the todo list.\n*Creates a todo list breaking down each feature into specific tasks based on the project architecture*\nAssistant: Let's start with user registration. This will involve creating database models, API endpoints, and frontend forms that integrate with your existing authentication system.\n\n<reasoning>\nThe assistant used the todo list because:\n1. The user provided multiple complex features to implement in a comma separated list\n2. The todo list helps organize these large features into manageable tasks\n3. This approach allows for tracking progress across the entire implementation\n</reasoning>\n</example>\n\n<example>\nUser: Can you help optimize my React application? It's rendering slowly and has performance issues.</user>\nAssistant: I'll help optimize your React application. First, let me examine your codebase to identify potential performance bottlenecks.\n*Reviews component structure, render patterns, state management, and data fetching*\nAssistant: After analyzing your codebase, I've identified several performance issues. Let me create a todo list to track our optimization efforts.\n*Creates todo list with items like: 1) Implementing memoization for expensive calculations in ProductList, 2) Adding virtualization for long lists in Dashboard, 3) Optimizing image loading in Gallery component, 4) Fixing state update loops in ShoppingCart, 5) Reviewing bundle size and implementing code splitting*\nLet's start by implementing memoization for the expensive calculations in your ProductList component.</assistant>\n\n<reasoning>\nThe assistant used the todo list because:\n1. First, the assistant examined the codebase to identify specific performance issues\n2. Based on this analysis, it identified multiple optimization opportunities\n3. Performance optimization is a non-trivial task requiring multiple steps\n4. The todo list helps methodically track improvements across different components\n5. This systematic approach ensures all performance bottlenecks are addressed\n</reasoning>\n</example>\n\n## Examples of When NOT to Use the Todo List\n\n<example>\nUser: How do I print 'Hello World' in Python?\nAssistant: In Python, you can print \"Hello World\" with this simple code:\n\npython\nprint(\"Hello World\")\n\nThis will output the text \"Hello World\" to the console when executed.</assistant>\n\n<reasoning>\nThe assistant did not use the todo list because this is a single, trivial task that can be completed in one step. There's no need to track multiple tasks or steps for such a straightforward request.\n</reasoning>\n</example>\n\n<example>\nUser: What does the git status command do?\nAssistant: The git status command shows the current state of your working directory and staging area. It displays which changes have been staged, which haven't, and which files aren't being tracked by Git. This is a fundamental command for understanding the current state of your repository before making commits.\n\n<reasoning>\nThe assistant did not use the todo list because this is an informational request with no actual coding task to complete. The user is simply asking for an explanation, not for the assistant to perform multiple steps or tasks.\n</reasoning>\n</example>\n\n<example>\nUser: Can you add a comment to the calculateTotal function to explain what it does?\nAssistant: Sure, let me add a comment to the calculateTotal function to explain what it does.\n* Uses the Edit tool to add a comment to the calculateTotal function *\n\n<reasoning>\nThe assistant did not use the todo list because this is a single, straightforward task confined to one location in the code. Adding a comment doesn't require tracking multiple steps or systematic organization.\n</reasoning>\n</example>\n\n<example>\nUser: Run npm install for me and tell me what happens.\nAssistant: I'll run the npm install command for you.\n\n*Executes: npm install*\n\nThe command completed successfully. Here's the output:\n[Output of npm install command]\n\nAll dependencies have been installed according to your package.json file.\n\n<reasoning>\nThe assistant did not use the todo list because this is a single command execution with immediate results. There are no multiple steps to track or organize, making the todo list unnecessary for this straightforward task.\n</reasoning>\n</example>\n\n## Task States and Management\n\n1. **Task States**: Use these states to track progress:\n   - pending: Task not yet started\n   - in_progress: Currently working on (limit to ONE task at a time)\n   - completed: Task finished successfully\n\n   **IMPORTANT**: Task descriptions must have two forms:\n   - content: The imperative form describing what needs to be done (e.g., \"Run tests\", \"Build the project\")\n   - activeForm: The present continuous form shown during execution (e.g., \"Running tests\", \"Building the project\")\n\n2. **Task Management**:\n   - Update task status in real-time as you work\n   - Mark tasks complete IMMEDIATELY after finishing (don't batch completions)\n   - Exactly ONE task must be in_progress at any time (not less, not more)\n   - Complete current tasks before starting new ones\n   - Remove tasks that are no longer relevant from the list entirely\n\n3. **Task Completion Requirements**:\n   - ONLY mark a task as completed when you have FULLY accomplished it\n   - If you encounter errors, blockers, or cannot finish, keep the task as in_progress\n   - When blocked, create a new task describing what needs to be resolved\n   - Never mark a task as completed if:\n     - Tests are failing\n     - Implementation is partial\n     - You encountered unresolved errors\n     - You couldn't find necessary files or dependencies\n\n4. **Task Breakdown**:\n   - Create specific, actionable items\n   - Break complex tasks into smaller, manageable steps\n   - Use clear, descriptive task names\n   - Always provide both forms:\n     - content: \"Fix authentication bug\"\n     - activeForm: \"Fixing authentication bug\"\n\nWhen in doubt, use this tool. Being proactive with task management demonstrates attentiveness and ensures you complete all requirements successfully.";
+//# sourceMappingURL=prompt.d.ts.map

package/dist/tools/TodoWrite/prompt.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"prompt.d.ts","sourceRoot":"","sources":["../../../src/tools/TodoWrite/prompt.ts"],"names":[],"mappings":"AAAA,eAAO,MAAM,oBAAoB,cAAc,CAAA;AAE/C,eAAO,MAAM,WAAW,krTAqL8H,CAAA"}

package/dist/tools/TodoWrite/prompt.js

@@ -0,0 +1,187 @@
+"use strict";
+Object.defineProperty(exports, "__esModule", { value: true });
+exports.DESCRIPTION = exports.TOOL_NAME_FOR_PROMPT = void 0;
+exports.TOOL_NAME_FOR_PROMPT = 'TodoWrite';
+exports.DESCRIPTION = `Use this tool to create and manage a structured task list for your current coding session. This helps you track progress, organize complex tasks, and demonstrate thoroughness to the user.
+It also helps the user understand the progress of the task and overall progress of their requests.
+
+## When to Use This Tool
+Use this tool proactively in these scenarios:
+
+1. Complex multi-step tasks - When a task requires 3 or more distinct steps or actions
+2. Non-trivial and complex tasks - Tasks that require careful planning or multiple operations
+3. User explicitly requests todo list - When the user directly asks you to use the todo list
+4. User provides multiple tasks - When users provide a list of things to be done (numbered or comma-separated)
+5. After receiving new instructions - Immediately capture user requirements as todos
+6. When you start working on a task - Mark it as in_progress BEFORE beginning work. Ideally you should only have one todo as in_progress at a time
+7. After completing a task - Mark it as completed and add any new follow-up tasks discovered during implementation
+
+## When NOT to Use This Tool
+
+Skip using this tool when:
+1. There is only a single, straightforward task
+2. The task is trivial and tracking it provides no organizational benefit
+3. The task can be completed in less than 3 trivial steps
+4. The task is purely conversational or informational
+
+NOTE that you should not use this tool if there is only one trivial task to do. In this case you are better off just doing the task directly.
+
+## Examples of When to Use the Todo List
+
+<example>
+User: I want to add a dark mode toggle to the application settings. Make sure you run the tests and build when you're done!
+Assistant: I'll help add a dark mode toggle to your application settings. Let me create a todo list to track this implementation.
+*Creates todo list with the following items:*
+1. Creating dark mode toggle component in Settings page
+2. Adding dark mode state management (context/store)
+3. Implementing CSS-in-JS styles for dark theme
+4. Updating existing components to support theme switching
+5. Running tests and build process, addressing any failures or errors that occur
+*Begins working on the first task*
+
+<reasoning>
+The assistant used the todo list because:
+1. Adding dark mode is a multi-step feature requiring UI, state management, and styling changes
+2. The user explicitly requested tests and build be run afterward
+3. The assistant inferred that tests and build need to pass by adding "Ensure tests and build succeed" as the final task
+</reasoning>
+</example>
+
+<example>
+User: Help me rename the function getCwd to getCurrentWorkingDirectory across my project
+Assistant: Let me first search through your codebase to find all occurrences of 'getCwd'.
+*Uses grep or search tools to locate all instances of getCwd in the codebase*
+Assistant: I've found 15 instances of 'getCwd' across 8 different files. Let me create a todo list to track these changes.
+*Creates todo list with specific items for each file that needs updating*
+
+<reasoning>
+The assistant used the todo list because:
+1. First, the assistant searched to understand the scope of the task
+2. Upon finding multiple occurrences across different files, it determined this was a complex task with multiple steps
+3. The todo list helps ensure every instance is tracked and updated systematically
+4. This approach prevents missing any occurrences and maintains code consistency
+</reasoning>
+</example>
+
+
+<example>
+User: I need to implement these features for my e-commerce site: user registration, product catalog, shopping cart, and checkout flow.
+Assistant: I'll help implement these features. First, let's add all the features to the todo list.
+*Creates a todo list breaking down each feature into specific tasks based on the project architecture*
+Assistant: Let's start with user registration. This will involve creating database models, API endpoints, and frontend forms that integrate with your existing authentication system.
+
+<reasoning>
+The assistant used the todo list because:
+1. The user provided multiple complex features to implement in a comma separated list
+2. The todo list helps organize these large features into manageable tasks
+3. This approach allows for tracking progress across the entire implementation
+</reasoning>
+</example>
+
+<example>
+User: Can you help optimize my React application? It's rendering slowly and has performance issues.</user>
+Assistant: I'll help optimize your React application. First, let me examine your codebase to identify potential performance bottlenecks.
+*Reviews component structure, render patterns, state management, and data fetching*
+Assistant: After analyzing your codebase, I've identified several performance issues. Let me create a todo list to track our optimization efforts.
+*Creates todo list with items like: 1) Implementing memoization for expensive calculations in ProductList, 2) Adding virtualization for long lists in Dashboard, 3) Optimizing image loading in Gallery component, 4) Fixing state update loops in ShoppingCart, 5) Reviewing bundle size and implementing code splitting*
+Let's start by implementing memoization for the expensive calculations in your ProductList component.</assistant>
+
+<reasoning>
+The assistant used the todo list because:
+1. First, the assistant examined the codebase to identify specific performance issues
+2. Based on this analysis, it identified multiple optimization opportunities
+3. Performance optimization is a non-trivial task requiring multiple steps
+4. The todo list helps methodically track improvements across different components
+5. This systematic approach ensures all performance bottlenecks are addressed
+</reasoning>
+</example>
+
+## Examples of When NOT to Use the Todo List
+
+<example>
+User: How do I print 'Hello World' in Python?
+Assistant: In Python, you can print "Hello World" with this simple code:
+
+python
+print("Hello World")
+
+This will output the text "Hello World" to the console when executed.</assistant>
+
+<reasoning>
+The assistant did not use the todo list because this is a single, trivial task that can be completed in one step. There's no need to track multiple tasks or steps for such a straightforward request.
+</reasoning>
+</example>
+
+<example>
+User: What does the git status command do?
+Assistant: The git status command shows the current state of your working directory and staging area. It displays which changes have been staged, which haven't, and which files aren't being tracked by Git. This is a fundamental command for understanding the current state of your repository before making commits.
+
+<reasoning>
+The assistant did not use the todo list because this is an informational request with no actual coding task to complete. The user is simply asking for an explanation, not for the assistant to perform multiple steps or tasks.
+</reasoning>
+</example>
+
+<example>
+User: Can you add a comment to the calculateTotal function to explain what it does?
+Assistant: Sure, let me add a comment to the calculateTotal function to explain what it does.
+* Uses the Edit tool to add a comment to the calculateTotal function *
+
+<reasoning>
+The assistant did not use the todo list because this is a single, straightforward task confined to one location in the code. Adding a comment doesn't require tracking multiple steps or systematic organization.
+</reasoning>
+</example>
+
+<example>
+User: Run npm install for me and tell me what happens.
+Assistant: I'll run the npm install command for you.
+
+*Executes: npm install*
+
+The command completed successfully. Here's the output:
+[Output of npm install command]
+
+All dependencies have been installed according to your package.json file.
+
+<reasoning>
+The assistant did not use the todo list because this is a single command execution with immediate results. There are no multiple steps to track or organize, making the todo list unnecessary for this straightforward task.
+</reasoning>
+</example>
+
+## Task States and Management
+
+1. **Task States**: Use these states to track progress:
+   - pending: Task not yet started
+   - in_progress: Currently working on (limit to ONE task at a time)
+   - completed: Task finished successfully
+
+   **IMPORTANT**: Task descriptions must have two forms:
+   - content: The imperative form describing what needs to be done (e.g., "Run tests", "Build the project")
+   - activeForm: The present continuous form shown during execution (e.g., "Running tests", "Building the project")
+
+2. **Task Management**:
+   - Update task status in real-time as you work
+   - Mark tasks complete IMMEDIATELY after finishing (don't batch completions)
+   - Exactly ONE task must be in_progress at any time (not less, not more)
+   - Complete current tasks before starting new ones
+   - Remove tasks that are no longer relevant from the list entirely
+
+3. **Task Completion Requirements**:
+   - ONLY mark a task as completed when you have FULLY accomplished it
+   - If you encounter errors, blockers, or cannot finish, keep the task as in_progress
+   - When blocked, create a new task describing what needs to be resolved
+   - Never mark a task as completed if:
+     - Tests are failing
+     - Implementation is partial
+     - You encountered unresolved errors
+     - You couldn't find necessary files or dependencies
+
+4. **Task Breakdown**:
+   - Create specific, actionable items
+   - Break complex tasks into smaller, manageable steps
+   - Use clear, descriptive task names
+   - Always provide both forms:
+     - content: "Fix authentication bug"
+     - activeForm: "Fixing authentication bug"
+
+When in doubt, use this tool. Being proactive with task management demonstrates attentiveness and ensures you complete all requirements successfully.`;
+//# sourceMappingURL=prompt.js.map

package/dist/tools/TodoWrite/prompt.js.map

@@ -0,0 +1 @@
+{"version":3,"file":"prompt.js","sourceRoot":"","sources":["../../../src/tools/TodoWrite/prompt.ts"],"names":[],"mappings":";;;AAAa,QAAA,oBAAoB,GAAG,WAAW,CAAA;AAElC,QAAA,WAAW,GAAG;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;;sJAqL2H,CAAA"}

package/dist/tools/Write/Write.d.ts

@@ -0,0 +1,77 @@
+import { Hunk } from 'diff';
+import { z } from 'zod';
+export declare const FileWriteTool: {
+    name: string;
+    description(): string;
+    inputSchema: z.ZodObject<{
+        file_path: z.ZodString;
+        content: z.ZodString;
+    }, "strict", z.ZodTypeAny, {
+        content: string;
+        file_path: string;
+    }, {
+        content: string;
+        file_path: string;
+    }>;
+    isReadOnly(): false;
+    genToolPermission(input: {
+        content: string;
+        file_path: string;
+    }): {
+        title: string;
+        content: Record<string, any>;
+    };
+    genToolResultMessage({ filePath, content, structuredPatch, type }: {
+        type: "create" | "update";
+        filePath: string;
+        content: string;
+        structuredPatch: Hunk[];
+    }): {
+        title: string;
+        summary: string;
+        content: Record<string, any>;
+    };
+    getDisplayTitle(input: {
+        content: string;
+        file_path: string;
+    } | undefined): string;
+    validateInput({ file_path }: {
+        content: string;
+        file_path: string;
+    }, agentContext: any): Promise<{
+        result: true;
+        message?: undefined;
+    } | {
+        result: false;
+        message: string;
+    }>;
+    call({ file_path, content }: {
+        content: string;
+        file_path: string;
+    }, agentContext: any): AsyncGenerator<{
+        type: "result";
+        data: {
+            type: "update";
+            filePath: string;
+            content: string;
+            structuredPatch: Hunk[];
+        };
+        resultForAssistant: string;
+    } | {
+        type: "result";
+        data: {
+            type: "create";
+            filePath: string;
+            content: string;
+            structuredPatch: never[];
+        };
+        resultForAssistant: string;
+    }, void, unknown>;
+    genResultForAssistant({ filePath, content, type }: {
+        type: "create" | "update";
+        filePath: string;
+        content: string;
+        structuredPatch: Hunk[];
+    }): string;
+};
+//# sourceMappingURL=Write.d.ts.map

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

@@ -0,0 +1 @@
+{"version":3,"file":"Write.d.ts","sourceRoot":"","sources":["../../../src/tools/Write/Write.ts"],"names":[],"mappings":"AAAA,OAAO,EAAE,IAAI,EAAE,MAAM,MAAM,CAAA;AAI3B,OAAO,EAAE,CAAC,EAAE,MAAM,KAAK,CAAA;AAwCvB,eAAO,MAAM,aAAa;;;;;;;;;;;;;;;;;;;;;;cAsLhB,QAAQ,GAAG,QAAQ;kBACf,MAAM;iBACP,MAAM;yBACE,IAAI,EAAE;;;;;;;;;;;;;qBA5GwB,GAAG;;;;;;;;;;qBA+BF,GAAG;;;;;;;;;;;;;;;;;;;;cA0E7C,QAAQ,GAAG,QAAQ;kBACf,MAAM;iBACP,MAAM;yBACE,IAAI,EAAE;;CAE1B,CAAA"}