@easbot/agent 0.2.6 → 0.2.7

package/dist/assets/txt/tool/grep.txt

@@ -1,8 +1,8 @@
-- Fast content search tool that works with any codebase size
-- Searches file contents using regular expressions
-- Supports full regex syntax (eg. "log.*Error", "function\s+\w+", etc.)
-- Filter files by pattern with the include parameter (eg. "*.js", "*.{ts,tsx}")
-- Returns file paths and line numbers with at least one match sorted by modification time
-- Use this tool when you need to find files containing specific patterns
-- If you need to identify/count the number of matches within files, use the Bash tool with `rg` (ripgrep) directly. Do NOT use `grep`.
-- When you are doing an open-ended search that may require multiple rounds of globbing and grepping, use the Task tool instead
+- Fast content search tool that works with any codebase size
+- Searches file contents using regular expressions
+- Supports full regex syntax (eg. "log.*Error", "function\s+\w+", etc.)
+- Filter files by pattern with the include parameter (eg. "*.js", "*.{ts,tsx}")
+- Returns file paths and line numbers with at least one match sorted by modification time
+- Use this tool when you need to find files containing specific patterns
+- If you need to identify/count the number of matches within files, use the Bash tool with `rg` (ripgrep) directly. Do NOT use `grep`.
+- When you are doing an open-ended search that may require multiple rounds of globbing and grepping, use the Task tool instead

package/dist/assets/txt/tool/ls.txt

@@ -1,6 +1,6 @@
-- Lists all files and directories in a given path
-- Supports tree-style output showing directory hierarchy
-- Automatically ignores common directories like node_modules, .git, dist, build, and more
-- Supports custom ignore patterns via the ignore parameter
-- Returns file count and truncation status when limit is reached
-- When you need to find files by name patterns, prefer the Glob tool
+- Lists all files and directories in a given path
+- Supports tree-style output showing directory hierarchy
+- Automatically ignores common directories like node_modules, .git, dist, build, and more
+- Supports custom ignore patterns via the ignore parameter
+- Returns file count and truncation status when limit is reached
+- When you need to find files by name patterns, prefer the Glob tool

package/dist/assets/txt/tool/lsp.txt

@@ -1,19 +1,19 @@
-Interact with Language Server Protocol (LSP) servers to get code intelligence features.
-
-Supported operations:
-- goToDefinition: Find where a symbol is defined
-- findReferences: Find all references to a symbol
-- hover: Get hover information (documentation, type info) for a symbol
-- documentSymbol: Get all symbols (functions, classes, variables) in a document
-- workspaceSymbol: Search for symbols across the entire workspace
-- goToImplementation: Find implementations of an interface or abstract method
-- prepareCallHierarchy: Get call hierarchy item at a position (functions/methods)
-- incomingCalls: Find all functions/methods that call the function at a position
-- outgoingCalls: Find all functions/methods called by the function at a position
-
-All operations require:
-- filePath: The file to operate on
-- line: The line number (1-based, as shown in editors)
-- character: The character offset (1-based, as shown in editors)
-
-Note: LSP servers must be configured for the file type. If no server is available, an error will be returned.
+Interact with Language Server Protocol (LSP) servers to get code intelligence features.
+
+Supported operations:
+- goToDefinition: Find where a symbol is defined
+- findReferences: Find all references to a symbol
+- hover: Get hover information (documentation, type info) for a symbol
+- documentSymbol: Get all symbols (functions, classes, variables) in a document
+- workspaceSymbol: Search for symbols across the entire workspace
+- goToImplementation: Find implementations of an interface or abstract method
+- prepareCallHierarchy: Get call hierarchy item at a position (functions/methods)
+- incomingCalls: Find all functions/methods that call the function at a position
+- outgoingCalls: Find all functions/methods called by the function at a position
+
+All operations require:
+- filePath: The file to operate on
+- line: The line number (1-based, as shown in editors)
+- character: The character offset (1-based, as shown in editors)
+
+Note: LSP servers must be configured for the file type. If no server is available, an error will be returned.

package/dist/assets/txt/tool/multiedit.txt

@@ -1,43 +1,43 @@
-This is a tool for making multiple edits to one or more files in a single operation. It is built on top of the Edit tool and allows you to perform multiple find-and-replace operations efficiently across multiple files.
-
-Before using this tool:
-
-1. Use the Read tool to understand the file's contents and context
-2. Verify the directory paths are correct
-
-To make multiple file edits, provide the following:
-1. edits: An array of edit operations to perform, where each edit contains:
-   - filePath: The absolute path to the file to modify (must be absolute, not relative)
-   - oldString: The text to replace (must match the file contents exactly, including all whitespace and indentation)
-   - newString: The edited text to replace the oldString
-   - replaceAll: (Optional) Replace all occurrences of oldString. Defaults to false.
-2. continueOnError: (Optional) Whether to continue processing remaining edits if one fails. Defaults to false.
-
-IMPORTANT:
-- You can edit multiple files in a single operation by providing different filePaths in the edits array
-- For edits to the same file, they are applied in sequence, in the order they are provided
-- Each edit operates on the result of the previous edit (for the same file)
-- By default, if any edit fails, the entire operation stops. Set continueOnError to true to continue processing remaining edits.
-- This tool is ideal when you need to make several changes across multiple files or different parts of the same file
-
-CRITICAL REQUIREMENTS:
-1. All edits follow the same requirements as the single Edit tool
-2. Plan your edits carefully to avoid conflicts between sequential operations on the same file
-3. Each edit must have its own filePath specified
-
-WARNING:
-- The tool will fail if edits.oldString doesn't match the file contents exactly (including whitespace)
-- The tool will fail if edits.oldString and edits.newString are the same
-- For edits to the same file, ensure that earlier edits don't affect the text that later edits are trying to find
-
-When making edits:
-- Ensure all edits result in idiomatic, correct code
-- Do not leave the code in a broken state
-- Always use absolute file paths (starting with /)
-- Only use emojis if the user explicitly requests it. Avoid adding emojis to files unless asked.
-- Use replaceAll for replacing and renaming strings across the file. This parameter is useful if you want to rename a variable for instance.
-
-If you want to create a new file, use:
-- A new file path, including dir name if needed
-- First edit: empty oldString and the new file's contents as newString
-- Subsequent edits: normal edit operations on the created content
+This is a tool for making multiple edits to one or more files in a single operation. It is built on top of the Edit tool and allows you to perform multiple find-and-replace operations efficiently across multiple files.
+
+Before using this tool:
+
+1. Use the Read tool to understand the file's contents and context
+2. Verify the directory paths are correct
+
+To make multiple file edits, provide the following:
+1. edits: An array of edit operations to perform, where each edit contains:
+   - filePath: The absolute path to the file to modify (must be absolute, not relative)
+   - oldString: The text to replace (must match the file contents exactly, including all whitespace and indentation)
+   - newString: The edited text to replace the oldString
+   - replaceAll: (Optional) Replace all occurrences of oldString. Defaults to false.
+2. continueOnError: (Optional) Whether to continue processing remaining edits if one fails. Defaults to false.
+
+IMPORTANT:
+- You can edit multiple files in a single operation by providing different filePaths in the edits array
+- For edits to the same file, they are applied in sequence, in the order they are provided
+- Each edit operates on the result of the previous edit (for the same file)
+- By default, if any edit fails, the entire operation stops. Set continueOnError to true to continue processing remaining edits.
+- This tool is ideal when you need to make several changes across multiple files or different parts of the same file
+
+CRITICAL REQUIREMENTS:
+1. All edits follow the same requirements as the single Edit tool
+2. Plan your edits carefully to avoid conflicts between sequential operations on the same file
+3. Each edit must have its own filePath specified
+
+WARNING:
+- The tool will fail if edits.oldString doesn't match the file contents exactly (including whitespace)
+- The tool will fail if edits.oldString and edits.newString are the same
+- For edits to the same file, ensure that earlier edits don't affect the text that later edits are trying to find
+
+When making edits:
+- Ensure all edits result in idiomatic, correct code
+- Do not leave the code in a broken state
+- Always use absolute file paths (starting with /)
+- Only use emojis if the user explicitly requests it. Avoid adding emojis to files unless asked.
+- Use replaceAll for replacing and renaming strings across the file. This parameter is useful if you want to rename a variable for instance.
+
+If you want to create a new file, use:
+- A new file path, including dir name if needed
+- First edit: empty oldString and the new file's contents as newString
+- Subsequent edits: normal edit operations on the created content

package/dist/assets/txt/tool/pty_manage.txt

@@ -1,60 +1,60 @@
-Manage existing PTY sessions including listing, inspecting, controlling, and terminating active terminal sessions. Provides comprehensive session lifecycle management capabilities.
-
-**!! ESSENTIAL TOOL FOR PROPER SESSION MANAGEMENT !!**
-
-**THIS TOOL IS MANDATORY FOR PROPER SESSION MANAGEMENT**
-
-Supported actions:
-- list: Show all active PTY sessions
-- get: Get detailed information about a specific session
-- resize: Change terminal dimensions for a session
-- write: Send input/data to an active session
-- close: Terminate a session gracefully
-
-Key capabilities:
-- Session inventory and monitoring
-- Real-time session inspection
-- Dynamic terminal resizing
-- Interactive session control
-- Resource cleanup and management
-
-Usage patterns:
-- Monitor running sessions: pty_manage { "action": "list" }
-- Inspect specific session: pty_manage { "action": "get", "sessionId": "session-id" }
-- Adjust terminal size: pty_manage { "action": "resize", "sessionId": "id", "cols": 120, "rows": 40 }
-- Send commands to session: pty_manage { "action": "write", "sessionId": "id", "data": "ls -la\n" }
-- Clean up sessions: pty_manage { "action": "close", "sessionId": "id" }
-
-Parameters:
-- action (required): Management operation to perform (list, get, resize, write, close)
-- sessionId (required for get/resize/write/close): Target session identifier
-- cols/rows (required for resize): New terminal dimensions
-- data (required for write): Data/input to send to session
-
-**!! CRITICAL RESOURCE CLEANUP REQUIREMENTS !!**
-
-**WARNING**: PTY sessions PERSIST in background and consume system resources!
-
-**IMPERATIVE ACTIONS**:
-1. **ALWAYS** use this tool to properly terminate UNUSED sessions
-2. **SESSIONS persist in background** and consume CPU, memory, file descriptors
-3. **REGULAR session cleanup prevents SYSTEM RESOURCE EXHAUSTION**
-4. **USE "list" action FREQUENTLY** to monitor active sessions
-5. **USE "close" action IMMEDIATELY** to properly terminate sessions when done
-6. **NEVER leave sessions running unnecessarily** - they do not auto-terminate
-
-**CONSEQUENCES OF POOR RESOURCE MANAGEMENT**:
-- System performance degradation
-- Resource exhaustion leading to crashes
-- Security vulnerabilities from persistent access
-- Inability to start new processes
-- File descriptor leaks
-- System instability
-
-**BEST PRACTICES**:
-- Check active sessions before creating new ones
-- Close sessions immediately after use
-- Monitor session list regularly
-- Clean up orphaned sessions promptly
-
-Security: Requires authorization for all management operations.
+Manage existing PTY sessions including listing, inspecting, controlling, and terminating active terminal sessions. Provides comprehensive session lifecycle management capabilities.
+
+**!! ESSENTIAL TOOL FOR PROPER SESSION MANAGEMENT !!**
+
+**THIS TOOL IS MANDATORY FOR PROPER SESSION MANAGEMENT**
+
+Supported actions:
+- list: Show all active PTY sessions
+- get: Get detailed information about a specific session
+- resize: Change terminal dimensions for a session
+- write: Send input/data to an active session
+- close: Terminate a session gracefully
+
+Key capabilities:
+- Session inventory and monitoring
+- Real-time session inspection
+- Dynamic terminal resizing
+- Interactive session control
+- Resource cleanup and management
+
+Usage patterns:
+- Monitor running sessions: pty_manage { "action": "list" }
+- Inspect specific session: pty_manage { "action": "get", "sessionId": "session-id" }
+- Adjust terminal size: pty_manage { "action": "resize", "sessionId": "id", "cols": 120, "rows": 40 }
+- Send commands to session: pty_manage { "action": "write", "sessionId": "id", "data": "ls -la\n" }
+- Clean up sessions: pty_manage { "action": "close", "sessionId": "id" }
+
+Parameters:
+- action (required): Management operation to perform (list, get, resize, write, close)
+- sessionId (required for get/resize/write/close): Target session identifier
+- cols/rows (required for resize): New terminal dimensions
+- data (required for write): Data/input to send to session
+
+**!! CRITICAL RESOURCE CLEANUP REQUIREMENTS !!**
+
+**WARNING**: PTY sessions PERSIST in background and consume system resources!
+
+**IMPERATIVE ACTIONS**:
+1. **ALWAYS** use this tool to properly terminate UNUSED sessions
+2. **SESSIONS persist in background** and consume CPU, memory, file descriptors
+3. **REGULAR session cleanup prevents SYSTEM RESOURCE EXHAUSTION**
+4. **USE "list" action FREQUENTLY** to monitor active sessions
+5. **USE "close" action IMMEDIATELY** to properly terminate sessions when done
+6. **NEVER leave sessions running unnecessarily** - they do not auto-terminate
+
+**CONSEQUENCES OF POOR RESOURCE MANAGEMENT**:
+- System performance degradation
+- Resource exhaustion leading to crashes
+- Security vulnerabilities from persistent access
+- Inability to start new processes
+- File descriptor leaks
+- System instability
+
+**BEST PRACTICES**:
+- Check active sessions before creating new ones
+- Close sessions immediately after use
+- Monitor session list regularly
+- Clean up orphaned sessions promptly
+
+Security: Requires authorization for all management operations.

package/dist/assets/txt/tool/question.txt

@@ -1,33 +1,33 @@
-Use this tool when you need to ask the user questions during execution. This allows you to:
-1. Gather user preferences or requirements
-2. Clarify ambiguous instructions
-3. Get decisions on implementation choices as you work
-4. Offer choices to the user about what direction to take.
-
-Parameters:
-- `question`: Complete question text to display
-- `header`: Very short label (max 30 chars) that summarizes the question
-- `options`: Array of available choices, each with:
-  - `label`: Display text (1-5 words, concise)
-  - `description`: Explanation of the choice
-- `multiple`: (optional) Allow selecting multiple choices (default: false)
-- `custom`: (optional) Allow typing a custom answer (default: true)
-
-Custom input behavior:
-- When `custom` is true (default): User can either select from options OR type their own answer
-  - System will show: "Hint: Enter option number or custom text"
-  - User can input any text as a custom answer
-  - IMPORTANT: Do NOT add a "[0] Custom input" option - the system handles this automatically via the hint message
-- When `custom` is false: User MUST select from the provided options only
-  - System will show: "Hint: Only valid option numbers allowed"
-  - Custom text input will be rejected as invalid
-  - Use this when you need strict validation (e.g., yes/no questions, predefined choices)
-
-Best practices:
-- Set `custom: false` when you need strict validation and want to ensure users only select from predefined options
-- Set `custom: true` (or omit it) when you want to allow flexibility for users to provide their own answers
-- Keep option labels concise (1-5 words)
-- Provide clear descriptions for each option to help users understand the implications
-- If you recommend a specific option, make that the first option in the list and add "(Recommended)" at the end of the label
-- For yes/no questions, provide explicit "Yes" and "No" options and consider setting `custom: false` for strict validation
-- NEVER add a "Custom input" or "Other" option when custom is true - the system automatically allows custom input through the hint message
+Use this tool when you need to ask the user questions during execution. This allows you to:
+1. Gather user preferences or requirements
+2. Clarify ambiguous instructions
+3. Get decisions on implementation choices as you work
+4. Offer choices to the user about what direction to take.
+
+Parameters:
+- `question`: Complete question text to display
+- `header`: Very short label (max 30 chars) that summarizes the question
+- `options`: Array of available choices, each with:
+  - `label`: Display text (1-5 words, concise)
+  - `description`: Explanation of the choice
+- `multiple`: (optional) Allow selecting multiple choices (default: false)
+- `custom`: (optional) Allow typing a custom answer (default: true)
+
+Custom input behavior:
+- When `custom` is true (default): User can either select from options OR type their own answer
+  - System will show: "Hint: Enter option number or custom text"
+  - User can input any text as a custom answer
+  - IMPORTANT: Do NOT add a "[0] Custom input" option - the system handles this automatically via the hint message
+- When `custom` is false: User MUST select from the provided options only
+  - System will show: "Hint: Only valid option numbers allowed"
+  - Custom text input will be rejected as invalid
+  - Use this when you need strict validation (e.g., yes/no questions, predefined choices)
+
+Best practices:
+- Set `custom: false` when you need strict validation and want to ensure users only select from predefined options
+- Set `custom: true` (or omit it) when you want to allow flexibility for users to provide their own answers
+- Keep option labels concise (1-5 words)
+- Provide clear descriptions for each option to help users understand the implications
+- If you recommend a specific option, make that the first option in the list and add "(Recommended)" at the end of the label
+- For yes/no questions, provide explicit "Yes" and "No" options and consider setting `custom: false` for strict validation
+- NEVER add a "Custom input" or "Other" option when custom is true - the system automatically allows custom input through the hint message

package/dist/assets/txt/tool/read.txt

@@ -1,14 +1,14 @@
-Read a file or directory from the local filesystem. If the path does not exist, an error is returned.
-
-Usage:
-- The filePath parameter should be an absolute path.
-- By default, this tool returns up to 2000 lines from the start of the file.
-- The offset parameter is the line number to start from (1-indexed).
-- To read later sections, call this tool again with a larger offset.
-- Use the grep tool to find specific content in large files or files with long lines.
-- If you are unsure of the correct file path, use the glob tool to look up filenames by glob pattern.
-- Contents are returned with each line prefixed by its line number as `<line>: <content>`. For example, if a file has contents "foo\n", you will receive "1: foo\n". For directories, entries are returned one per line (without line numbers) with a trailing `/` for subdirectories.
-- Any line longer than 2000 characters is truncated.
-- Call this tool in parallel when you know there are multiple files you want to read.
-- Avoid tiny repeated slices (30 line chunks). If you need more context, read a larger window.
-- This tool can read image files and PDFs and return them as file attachments.
+Read a file or directory from the local filesystem. If the path does not exist, an error is returned.
+
+Usage:
+- The filePath parameter should be an absolute path.
+- By default, this tool returns up to 2000 lines from the start of the file.
+- The offset parameter is the line number to start from (1-indexed).
+- To read later sections, call this tool again with a larger offset.
+- Use the grep tool to find specific content in large files or files with long lines.
+- If you are unsure of the correct file path, use the glob tool to look up filenames by glob pattern.
+- Contents are returned with each line prefixed by its line number as `<line>: <content>`. For example, if a file has contents "foo\n", you will receive "1: foo\n". For directories, entries are returned one per line (without line numbers) with a trailing `/` for subdirectories.
+- Any line longer than 2000 characters is truncated.
+- Call this tool in parallel when you know there are multiple files you want to read.
+- Avoid tiny repeated slices (30 line chunks). If you need more context, read a larger window.
+- This tool can read image files and PDFs and return them as file attachments.

package/dist/assets/txt/tool/todo.txt

@@ -1,124 +1,124 @@
-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.
-
-## Operations
-
-This tool supports two operations:
-
-### 1. write - Write/Update TODO list
-Use this operation to create, update, or replace the entire TODO list.
-
-**Parameters:**
-- `operation`: "write" (required)
-- `todos`: Complete TODO list with all task items (required). Can be either an array JSON string.
-
-**When to Use:**
-- Complex multistep tasks - When a task requires 3 or more distinct steps or actions
-- Non-trivial and complex tasks - Tasks that require careful planning or multiple operations
-- User explicitly requests todo list - When the user directly asks you to use the todo list
-- User provides multiple tasks - When users provide a list of things to be done (numbered or comma-separated)
-- After receiving new instructions - Immediately capture user requirements as todos
-- After completing a task - Mark it complete and add any new follow-up tasks
-- When starting a new task - Mark it as in_progress
-
-### 2. read - Read TODO list
-Use this operation to read the current TODO list for the session.
-
-**Parameters:**
-- `operation`: "read" (required)
-
-**When to Use:**
-- At the beginning of conversations to see what's pending
-- Before starting new tasks to prioritize work
-- When the user asks about previous tasks or plans
-- Whenever you're uncertain about what to do next
-- After completing tasks to update your understanding of remaining work
-- After every few messages to ensure you're on track
-
-## 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: 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
-
-### Example 1: write operation
-```
-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.
-*Calls todo tool with operation="write" and todos=[
-  { id: "1", content: "Create dark mode toggle component in Settings page", status: "in_progress", priority: "high" },
-  { id: "2", content: "Add dark mode state management (context/store)", status: "pending", priority: "high" },
-  { id: "3", content: "Implement CSS-in-JS styles for dark theme", status: "pending", priority: "medium" },
-  { id: "4", content: "Update existing components to support theme switching", status: "pending", priority: "medium" },
-  { id: "5", content: "Run tests and build process", status: "pending", priority: "high" }
-]*
-Begins working on the first task
-```
-
-### Example 2: read operation
-```
-User: What tasks do I have pending?
-Assistant: Let me check your TODO list.
-*Calls todo tool with operation="read"*
-Based on your TODO list, you have the following tasks pending:
-1. Create dark mode toggle component in Settings page (in_progress)
-2. Add dark mode state management (pending)
-3. Implement CSS-in-JS styles for dark theme (pending)
-...
-```
-
-### Example 3: write operation with JSON string format
-```
-User: I need to add some tasks to my todo list
-Assistant: I'll add those tasks to your todo list.
-*Calls todo tool with operation="write" and todos='[{"id":"1","content":"New task 1","status":"pending","priority":"high"},{"id":"2","content":"New task 2","status":"pending","priority":"medium"}]'*
-Tasks have been added to your todo list.
-```
-
-### Example 4: write operation with array format
-```
-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.
-*Calls todo tool with operation="write" and todos=[
-  { id: "1", content: "Rename getCwd to getCurrentWorkingDirectory in src/utils.ts", status: "in_progress", priority: "high" },
-  { id: "2", content: "Rename getCwd to getCurrentWorkingDirectory in src/cli.ts", status: "pending", priority: "high" },
-  ...
-]*
-```
-
-## Task States and Management
-
-**Task States:**
-- `pending`: Task not yet started
-- `in_progress`: Currently working on (limit to ONE task at a time)
-- `completed`: Task finished successfully
-- `cancelled`: Task no longer needed
-
-**Task Management:**
-- Update task status in real-time as you work
-- Mark tasks complete IMMEDIATELY after finishing (don't batch completions)
-- Only have ONE task in_progress at any time
-- Complete current tasks before starting new ones
-- Cancel tasks that become irrelevant
-
-**Task Breakdown:**
-- Create specific, actionable items
-- Break complex tasks into smaller, manageable steps
-- Use clear, descriptive task names
-
-## Task Item Structure
-
-Each task item should have:
-- `id`: Unique identifier (string or number)
-- `content`: Description of the task (string)
-- `status`: Current state ("pending", "in_progress", "completed", "cancelled")
-- `priority`: Priority level (optional, "high", "medium", "low")
-
-When in doubt, use this tool. Being proactive with task management demonstrates attentiveness and ensures you complete all requirements successfully.
+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.
+
+## Operations
+
+This tool supports two operations:
+
+### 1. write - Write/Update TODO list
+Use this operation to create, update, or replace the entire TODO list.
+
+**Parameters:**
+- `operation`: "write" (required)
+- `todos`: Complete TODO list with all task items (required). Can be either an array JSON string.
+
+**When to Use:**
+- Complex multistep tasks - When a task requires 3 or more distinct steps or actions
+- Non-trivial and complex tasks - Tasks that require careful planning or multiple operations
+- User explicitly requests todo list - When the user directly asks you to use the todo list
+- User provides multiple tasks - When users provide a list of things to be done (numbered or comma-separated)
+- After receiving new instructions - Immediately capture user requirements as todos
+- After completing a task - Mark it complete and add any new follow-up tasks
+- When starting a new task - Mark it as in_progress
+
+### 2. read - Read TODO list
+Use this operation to read the current TODO list for the session.
+
+**Parameters:**
+- `operation`: "read" (required)
+
+**When to Use:**
+- At the beginning of conversations to see what's pending
+- Before starting new tasks to prioritize work
+- When the user asks about previous tasks or plans
+- Whenever you're uncertain about what to do next
+- After completing tasks to update your understanding of remaining work
+- After every few messages to ensure you're on track
+
+## 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: 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
+
+### Example 1: write operation
+```
+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.
+*Calls todo tool with operation="write" and todos=[
+  { id: "1", content: "Create dark mode toggle component in Settings page", status: "in_progress", priority: "high" },
+  { id: "2", content: "Add dark mode state management (context/store)", status: "pending", priority: "high" },
+  { id: "3", content: "Implement CSS-in-JS styles for dark theme", status: "pending", priority: "medium" },
+  { id: "4", content: "Update existing components to support theme switching", status: "pending", priority: "medium" },
+  { id: "5", content: "Run tests and build process", status: "pending", priority: "high" }
+]*
+Begins working on the first task
+```
+
+### Example 2: read operation
+```
+User: What tasks do I have pending?
+Assistant: Let me check your TODO list.
+*Calls todo tool with operation="read"*
+Based on your TODO list, you have the following tasks pending:
+1. Create dark mode toggle component in Settings page (in_progress)
+2. Add dark mode state management (pending)
+3. Implement CSS-in-JS styles for dark theme (pending)
+...
+```
+
+### Example 3: write operation with JSON string format
+```
+User: I need to add some tasks to my todo list
+Assistant: I'll add those tasks to your todo list.
+*Calls todo tool with operation="write" and todos='[{"id":"1","content":"New task 1","status":"pending","priority":"high"},{"id":"2","content":"New task 2","status":"pending","priority":"medium"}]'*
+Tasks have been added to your todo list.
+```
+
+### Example 4: write operation with array format
+```
+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.
+*Calls todo tool with operation="write" and todos=[
+  { id: "1", content: "Rename getCwd to getCurrentWorkingDirectory in src/utils.ts", status: "in_progress", priority: "high" },
+  { id: "2", content: "Rename getCwd to getCurrentWorkingDirectory in src/cli.ts", status: "pending", priority: "high" },
+  ...
+]*
+```
+
+## Task States and Management
+
+**Task States:**
+- `pending`: Task not yet started
+- `in_progress`: Currently working on (limit to ONE task at a time)
+- `completed`: Task finished successfully
+- `cancelled`: Task no longer needed
+
+**Task Management:**
+- Update task status in real-time as you work
+- Mark tasks complete IMMEDIATELY after finishing (don't batch completions)
+- Only have ONE task in_progress at any time
+- Complete current tasks before starting new ones
+- Cancel tasks that become irrelevant
+
+**Task Breakdown:**
+- Create specific, actionable items
+- Break complex tasks into smaller, manageable steps
+- Use clear, descriptive task names
+
+## Task Item Structure
+
+Each task item should have:
+- `id`: Unique identifier (string or number)
+- `content`: Description of the task (string)
+- `status`: Current state ("pending", "in_progress", "completed", "cancelled")
+- `priority`: Priority level (optional, "high", "medium", "low")
+
+When in doubt, use this tool. Being proactive with task management demonstrates attentiveness and ensures you complete all requirements successfully.