npm - clew-code - Versions diffs - 0.2.21 → 0.2.23 - Mend

clew-code 0.2.21 → 0.2.23

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (67) hide show

package/README.md +45 -45
package/dist/main.js +2906 -2722
package/docs/architecture.html +91 -148
package/docs/assets/clew-agent-loop.png +0 -0
package/docs/assets/clew-general-architecture.png +0 -0
package/docs/assets/clew-mcp-architecture.png +0 -0
package/docs/assets/clew-p2p-swarm.png +0 -0
package/docs/changelog.html +150 -0
package/docs/cli-reference.html +90 -0
package/docs/commands.html +133 -241
package/docs/configuration.html +85 -147
package/docs/contributing.html +91 -0
package/docs/css/styles.css +272 -152
package/docs/daemon.html +62 -129
package/docs/features/bridge-mode.html +61 -66
package/docs/features/evals.html +57 -149
package/docs/features/searxng-search.html +58 -118
package/docs/features/sentry-setup.html +61 -124
package/docs/index.html +185 -148
package/docs/installation.html +77 -105
package/docs/internals/growthbook-ab-testing.html +69 -91
package/docs/internals/hidden-features.html +81 -143
package/docs/js/main.js +29 -0
package/docs/loop.html +69 -181
package/docs/mcp.html +99 -247
package/docs/models.html +63 -92
package/docs/permission-model.html +86 -102
package/docs/plugins.html +84 -102
package/docs/providers.html +87 -127
package/docs/quick-start.html +81 -93
package/docs/research-memory.html +71 -102
package/docs/security.html +71 -0
package/docs/skills.html +67 -117
package/docs/swarm.html +78 -236
package/docs/tools.html +183 -171
package/docs/troubleshooting.html +86 -106
package/docs/voice-mode.html +79 -0
package/package.json +1 -1
package/docs/architecture.th.html +0 -79
package/docs/clew-code-architecture.html +0 -1126
package/docs/commands.th.html +0 -269
package/docs/configuration.th.html +0 -108
package/docs/daemon.th.html +0 -73
package/docs/features/bridge-mode.th.html +0 -62
package/docs/features/evals.th.html +0 -62
package/docs/features/searxng-search.th.html +0 -67
package/docs/features/sentry-setup.th.html +0 -69
package/docs/features/swarm.html +0 -156
package/docs/generated/providers.html +0 -625
package/docs/generated/tools.html +0 -558
package/docs/index.th.html +0 -292
package/docs/installation.th.html +0 -105
package/docs/internals/growthbook-ab-testing.th.html +0 -60
package/docs/internals/hidden-features.th.html +0 -107
package/docs/loop.th.html +0 -227
package/docs/mcp.th.html +0 -207
package/docs/models.th.html +0 -61
package/docs/permission-model.th.html +0 -67
package/docs/plugins.th.html +0 -79
package/docs/prompts-and-features.html +0 -806
package/docs/providers.th.html +0 -81
package/docs/quick-start.th.html +0 -89
package/docs/research-memory.th.html +0 -72
package/docs/skills.th.html +0 -90
package/docs/swarm.th.html +0 -280
package/docs/tools.th.html +0 -84
package/docs/troubleshooting.th.html +0 -85

package/docs/generated/tools.html DELETED Viewed

@@ -1,558 +0,0 @@
-<!DOCTYPE html>
-<html lang="en">
-<head>
-  <meta charset="UTF-8">
-  <meta name="viewport" content="width=device-width, initial-scale=1.0">
-  <title>Tools & Prompts (Auto-generated) — Clew</title>
-  <meta name="description" content="Auto-generated tool reference with 57 system prompts for Clew Code.">
-  <link rel="preconnect" href="https://fonts.googleapis.com">
-  <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin>
-  <link href="https://fonts.googleapis.com/css2?family=DM+Sans:wght@400;500;600;700&family=JetBrains+Mono:wght@400;500;600;700&display=swap" rel="stylesheet">
-  <link rel="stylesheet" href="../css/styles.css">
-  <link rel="icon" type="image/svg+xml" href="../assets/clew.svg">
-</head>
-<body>
-<header class="header">
-  <div class="header-inner">
-    <a href="../index.html" class="logo"><span class="logo-mark">C</span><span>Clew Code</span></a>
-    <nav class="header-nav">
-      <a href="../index.html">Home</a>
-      <a href="../commands.html">Commands</a>
-      <a href="../tools.html">Tools</a>
-      <a href="../providers.html">Providers</a>
-      <a href="../prompts-and-features.html">Reference</a>
-      <a href="../quick-start.html">Docs</a>
-    </nav>
-  </div>
-</header>
-<div class="app">
-  <aside class="sidebar" id="sidebar">
-    <div class="sidebar-section">
-      <div class="sidebar-label">Generated Docs</div>
-      <a href="providers.html" class="sidebar-link"><span class="link-icon"></span>Providers</a>
-      <a href="tools.html" class="sidebar-link"><span class="link-icon"></span>Tools</a>
-    </div>
-    <div class="sidebar-section">
-      <div class="sidebar-label">Static Docs</div>
-      <a href="../commands.html" class="sidebar-link"><span class="link-icon"></span>Commands</a>
-      <a href="../tools.html" class="sidebar-link"><span class="link-icon"></span>Tools</a>
-      <a href="../providers.html" class="sidebar-link"><span class="link-icon"></span>Providers</a>
-    </div>
-  </aside>
-  <div class="sidebar-overlay"></div>
-  <div class="content-wrap"><main class="content">
-    <div class="breadcrumbs"><a href="../index.html">Home</a><span class="sep">/</span><span>Tools & Prompts (Auto-generated)</span></div>
-    <h1>Tools & Prompts (Auto-generated)</h1>
-    <p class="section-subtitle"><em>Auto-generated from source code. Last updated: 2026-06-14.</em></p>
-    <h2>All Tools with Prompts</h2>
-    <p>Clew provides <strong>57 tools</strong> with system prompts. These prompts are injected into the AI model's context at session start to define the tool interface.</p>
-    <div class="table-wrap"><table>
-      <tr><th>Tool</th><th>Description</th></tr>
-      <tr><td><code>Agent</code></td><td>Built-in tool &quot;Agent&quot;. See system prompt for details.</td></tr>
-<tr><td><code>AskUserQuestion</code></td><td>Asks the user multiple choice questions to gather information, clarify ambiguity, understand preferences, make decisions or offer them choices.</td></tr>
-<tr><td><code>Bash</code></td><td>Built-in tool &quot;Bash&quot;. See system prompt for details.</td></tr>
-<tr><td><code>Brief</code></td><td>Send a message to the user</td></tr>
-<tr><td><code>Config</code></td><td>Get or set Clew Code configuration settings.</td></tr>
-<tr><td><code>EnterPlanMode</code></td><td>Built-in tool &quot;EnterPlanMode&quot;. See system prompt for details.</td></tr>
-<tr><td><code>EnterWorktree</code></td><td>Built-in tool &quot;EnterWorktree&quot;. See system prompt for details.</td></tr>
-<tr><td><code>ExitPlanMode</code></td><td>Built-in tool &quot;ExitPlanMode&quot;. See system prompt for details.</td></tr>
-<tr><td><code>ExitWorktree</code></td><td>Built-in tool &quot;ExitWorktree&quot;. See system prompt for details.</td></tr>
-<tr><td><code>FileEdit</code></td><td>Built-in tool &quot;FileEdit&quot;. See system prompt for details.</td></tr>
-<tr><td><code>FileRead</code></td><td>Read a file or multiple files from the local filesystem. Supports batch reading multiple files in parallel for better performance.</td></tr>
-<tr><td><code>FileWrite</code></td><td>Write a file to the local filesystem.</td></tr>
-<tr><td><code>Glob</code></td><td>- Fast file pattern matching tool that works with any codebase size
-- Supports glob patterns like &quot;**/*.js&quot; or &quot;src/**/*.ts&quot;
-- Returns matching file paths sorted by modification time
-- Use this tool when you need to find files by name patterns
-- When you are doing an open ended search that may require multiple rounds of globbing and grepping, use the Agent tool instead</td></tr>
-<tr><td><code>Grep</code></td><td>Built-in tool &quot;Grep&quot;. See system prompt for details.</td></tr>
-<tr><td><code>JsonPath</code></td><td>Query, validate, format, and minify JSON data</td></tr>
-<tr><td><code>ListMcpResources</code></td><td>
-Lists available resources from configured MCP servers.
-Each resource object includes a 'server' field indicating which server it's from.
-Usage examples:
-- List all resources from all servers: \</td></tr>
-<tr><td><code>LSP</code></td><td>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.</td></tr>
-<tr><td><code>MCP</code></td><td>';
-export const DESCRIPTION =</td></tr>
-<tr><td><code>MeshBroadcast</code></td><td>Broadcast a task to ALL currently connected peers at once. </td></tr>
-<tr><td><code>MeshDisconnect</code></td><td>Disconnect and remove a mesh node from the connection list. </td></tr>
-<tr><td><code>MeshDiscover</code></td><td>Discover Clew Code workers on the local network. </td></tr>
-<tr><td><code>MeshHelp</code></td><td>Complete guide to agent-to-agent tools. </td></tr>
-<tr><td><code>MeshInfo</code></td><td>Get detailed information about a specific peer/worker by hostname or ID. </td></tr>
-<tr><td><code>MeshJoin</code></td><td>Connect to a mesh node by host and port. Fetches the mesh node info (hostname, name, role, shell, cwd) </td></tr>
-<tr><td><code>MeshListMessages</code></td><td>List chat messages received from peers. </td></tr>
-<tr><td><code>MeshListRoles</code></td><td>List all discovered mesh nodes with their display names and roles. </td></tr>
-<tr><td><code>MeshPing</code></td><td>Check if a specific peer is still online and reachable. </td></tr>
-<tr><td><code>MeshRun</code></td><td>Run a shell command on a remote mesh node and get the output back. </td></tr>
-<tr><td><code>MeshSendMessage</code></td><td>Send a chat message to a mesh node Clew Code instance on the LAN. </td></tr>
-<tr><td><code>MeshSetName</code></td><td>Set a custom display name for a mesh node. This name is shown in the mesh list </td></tr>
-<tr><td><code>MeshSetRole</code></td><td>Assign a role to a mesh node (e.g., &quot;builder&quot;, &quot;tester&quot;, &quot;deployer&quot;). </td></tr>
-<tr><td><code>MeshShare</code></td><td>Start or stop advertising this Clew Code instance as a worker. </td></tr>
-<tr><td><code>MeshSpawn</code></td><td>Spawn a new peer terminal window on the local machine with optional custom settings </td></tr>
-<tr><td><code>NotebookEdit</code></td><td>Replace the contents of a specific cell in a Jupyter notebook.</td></tr>
-<tr><td><code>PowerShell</code></td><td>Built-in tool &quot;PowerShell&quot;. See system prompt for details.</td></tr>
-<tr><td><code>PR</code></td><td>Manage GitHub pull requests — create, list, view, review, merge, and check CI status.</td></tr>
-<tr><td><code>ProcessMesh</code></td><td>Delegate a task to a local process-backed worker (e.g. Codex CLI) and return its output. </td></tr>
-<tr><td><code>PrSubscription</code></td><td>Built-in tool &quot;PrSubscription&quot;. See system prompt for details.</td></tr>
-<tr><td><code>ReadMcpResource</code></td><td>
-Reads a specific resource from an MCP server.
-- server: The name of the MCP server to read from
-- uri: The URI of the resource to read
-Usage examples:
-- Read a resource from a server: \</td></tr>
-<tr><td><code>RemoteTrigger</code></td><td>Manage scheduled remote Clew Code agents (triggers) via the claude.ai CCR API. Auth is handled in-process — the token never reaches the shell.</td></tr>
-<tr><td><code>RequestShutdown</code></td><td>Built-in tool &quot;RequestShutdown&quot;. See system prompt for details.</td></tr>
-<tr><td><code>ScheduleCron</code></td><td>Built-in tool &quot;ScheduleCron&quot;. See system prompt for details.</td></tr>
-<tr><td><code>SendMessage</code></td><td>Send a message to another agent</td></tr>
-<tr><td><code>SessionSearch</code></td><td>Built-in tool &quot;SessionSearch&quot;. See system prompt for details.</td></tr>
-<tr><td><code>Skill</code></td><td>Built-in tool &quot;Skill&quot;. See system prompt for details.</td></tr>
-<tr><td><code>Sleep</code></td><td>Wait for a specified duration</td></tr>
-<tr><td><code>TaskCreate</code></td><td>Create a new task in the task list</td></tr>
-<tr><td><code>TaskGet</code></td><td>Get a task by ID from the task list</td></tr>
-<tr><td><code>TaskList</code></td><td>List all tasks in the task list</td></tr>
-<tr><td><code>TaskStop</code></td><td>
-- Stops a running background task by its ID
-- Takes a task_id parameter identifying the task to stop
-- Returns a success or failure status
-- Use this tool when you need to terminate a long-running task
-</td></tr>
-<tr><td><code>TaskUpdate</code></td><td>Update a task in the task list</td></tr>
-<tr><td><code>TeamCreate</code></td><td>Built-in tool &quot;TeamCreate&quot;. See system prompt for details.</td></tr>
-<tr><td><code>TeamDelete</code></td><td>Built-in tool &quot;TeamDelete&quot;. See system prompt for details.</td></tr>
-<tr><td><code>TodoWrite</code></td><td>Update the todo list for the current session. To be used proactively and often to track progress and pending tasks. Make sure that at least one task is in_progress at all times. Always provide both content (imperative) and activeForm (present continuous) for each task.</td></tr>
-<tr><td><code>ToolSearch</code></td><td>Built-in tool &quot;ToolSearch&quot;. See system prompt for details.</td></tr>
-<tr><td><code>WebFetch</code></td><td>
-- Fetches content from a specified URL and processes it using an AI model
-- Takes a URL and a prompt as input
-- Fetches the URL content, converts HTML to markdown
-- Processes the content with the prompt using a small, fast model
-- Returns the model's response about the content
-- Use this tool when you need to retrieve and analyze web content
-Usage notes:
-  - IMPORTANT: If an MCP-provided web fetch tool is available, prefer using that tool instead of this one, as it may have fewer restrictions.
-  - The URL must be a fully-formed valid URL
-  - HTTP URLs will be automatically upgraded to HTTPS
-  - The prompt should describe what information you want to extract from the page
-  - This tool is read-only and does not modify any files
-  - Results may be summarized if the content is very large
-  - Includes a self-cleaning 15-minute cache for faster responses when repeatedly accessing the same URL
-  - When a URL redirects to a different host, the tool will inform you and provide the redirect URL in a special format. You should then make a new WebFetch request with the redirect URL to fetch the content.
-  - For GitHub URLs, prefer using the gh CLI via Bash instead (e.g., gh pr view, gh issue view, gh api).
-</td></tr>
-<tr><td><code>WebSearch</code></td><td>Built-in tool &quot;WebSearch&quot;. See system prompt for details.</td></tr>
-    </table></div>
-    <h2>Tool Prompts</h2>
-    <p>Each tool's system prompt, as seen by the AI model:</p>
-    <div class="tool-prompts"><details>
-        <summary><code>JsonPath</code> — System Prompt</summary>
-        <div class="prompt-box">A tool for querying, validating, formatting, and minifying JSON data. Use this tool when you need to extract specific values from JSON, validate JSON structure, or transform JSON for storage/transmission.
-## When to Use This Tool
-1. **Query JSON** - Extract specific values, keys, or paths from JSON data using JSONPath expressions
-2. **Validate JSON** - Check if JSON data matches an expected schema or structure
-3. **Format JSON** - Pretty-print JSON with configurable indentation
-4. **Minify JSON** - Compact JSON to remove unnecessary whitespace
-5. **Convert to/from JSON** - Parse stringified JSON or stringify objects
-## Features
-- **query**: Extract data using JSONPath or key paths (e.g., &quot;user.address.city&quot;, &quot;items[0].name&quot;)
-- **validate**: Validate JSON structure and optionally check against expected shape
-- **format**: Pretty-print with custom indent (2, 4, or tab)
-- **minify**: Remove all whitespace for compact storage
-- **stringify**: Convert JavaScript object to JSON string
-- **parse**: Convert JSON string to object (with optional validation)
-## Examples
-&lt;example&gt;
-User: What's the email address in this JSON?
-Assistant: *Uses json_path with query to extract the email*
-\</div>
-      </details>
-<details>
-        <summary><code>ListMcpResources</code> — System Prompt</summary>
-        <div class="prompt-box">List available resources from configured MCP servers.
-Each returned resource will include all standard MCP resource fields plus a 'server' field
-indicating which server the resource belongs to.
-Parameters:
-- server (optional): The name of a specific MCP server to get resources from. If not provided,
-  resources from all servers will be returned.</div>
-      </details>
-<details>
-        <summary><code>MCP</code> — System Prompt</summary>
-        <div class="prompt-box">';
-export const DESCRIPTION =</div>
-      </details>
-<details>
-        <summary><code>MeshBroadcast</code> — System Prompt</summary>
-        <div class="prompt-box">This tool sends the same task to every connected peer simultaneously.</div>
-      </details>
-<details>
-        <summary><code>MeshDisconnect</code> — System Prompt</summary>
-        <div class="prompt-box">This tool removes a mesh node from the local connection list.</div>
-      </details>
-<details>
-        <summary><code>MeshDiscover</code> — System Prompt</summary>
-        <div class="prompt-box">This tool scans the local network for other Clew Code instances that are</div>
-      </details>
-<details>
-        <summary><code>MeshInfo</code> — System Prompt</summary>
-        <div class="prompt-box">Fetches detailed information about a mesh node from the local peer store,</div>
-      </details>
-<details>
-        <summary><code>MeshJoin</code> — System Prompt</summary>
-        <div class="prompt-box">Connects to a remote peer by making an HTTP request to their peer-info endpoint.</div>
-      </details>
-<details>
-        <summary><code>MeshListMessages</code> — System Prompt</summary>
-        <div class="prompt-box">This tool lists peer chat messages in the local store.</div>
-      </details>
-<details>
-        <summary><code>MeshListRoles</code> — System Prompt</summary>
-        <div class="prompt-box">Lists all discovered mesh nodes and their assigned metadata (display name, role).</div>
-      </details>
-<details>
-        <summary><code>MeshPing</code> — System Prompt</summary>
-        <div class="prompt-box">This tool pings a mesh node to check if they are online.</div>
-      </details>
-<details>
-        <summary><code>MeshRun</code> — System Prompt</summary>
-        <div class="prompt-box">Executes a shell command on a remote mesh node via its HTTP API.</div>
-      </details>
-<details>
-        <summary><code>MeshSendMessage</code> — System Prompt</summary>
-        <div class="prompt-box">This tool sends a chat message to a mesh node Clew Code instance on the LAN.</div>
-      </details>
-<details>
-        <summary><code>MeshSetName</code> — System Prompt</summary>
-        <div class="prompt-box">Assigns a human-readable display name to a mesh node. The name is stored locally and</div>
-      </details>
-<details>
-        <summary><code>MeshSetRole</code> — System Prompt</summary>
-        <div class="prompt-box">Assigns a functional role to a mesh node. The role is displayed in the mesh list and</div>
-      </details>
-<details>
-        <summary><code>MeshShare</code> — System Prompt</summary>
-        <div class="prompt-box">Controls whether this Clew Code instance advertises itself as a worker on the LAN.</div>
-      </details>
-<details>
-        <summary><code>MeshSpawn</code> — System Prompt</summary>
-        <div class="prompt-box">Spawns a new local peer terminal window running Clew Code. The spawned peer will share automatically.</div>
-      </details>
-<details>
-        <summary><code>NotebookEdit</code> — System Prompt</summary>
-        <div class="prompt-box">Completely replaces the contents of a specific cell in a Jupyter notebook (.ipynb file) with new source. Jupyter notebooks are interactive documents that combine code, text, and visualizations, commonly used for data analysis and scientific computing. The notebook_path parameter must be an absolute path, not a relative path. The cell_number is 0-indexed. Use edit_mode=insert to add a new cell at the index specified by cell_number. Use edit_mode=delete to delete the cell at the index specified by cell_number.</div>
-      </details>
-<details>
-        <summary><code>ProcessMesh</code> — System Prompt</summary>
-        <div class="prompt-box">Runs a local process-backed AI worker for one task and returns stdout/stderr.</div>
-      </details>
-<details>
-        <summary><code>ReadMcpResource</code> — System Prompt</summary>
-        <div class="prompt-box">Reads a specific resource from an MCP server, identified by server name and resource URI.
-Parameters:
-- server (required): The name of the MCP server from which to read the resource
-- uri (required): The URI of the resource to read</div>
-      </details>
-<details>
-        <summary><code>RemoteTrigger</code> — System Prompt</summary>
-        <div class="prompt-box">Call the claude.ai remote-trigger API. Use this instead of curl — the OAuth token is added automatically in-process and never exposed.
-Actions:
-- list: GET /v1/code/triggers
-- get: GET /v1/code/triggers/{trigger_id}
-- create: POST /v1/code/triggers (requires body)
-- update: POST /v1/code/triggers/{trigger_id} (requires body, partial update)
-- run: POST /v1/code/triggers/{trigger_id}/run
-The response is the raw JSON from the API.</div>
-      </details>
-<details>
-        <summary><code>TaskGet</code> — System Prompt</summary>
-        <div class="prompt-box">Use this tool to retrieve a task by its ID from the task list.
-## When to Use This Tool
-- When you need the full description and context before starting work on a task
-- To understand task dependencies (what it blocks, what blocks it)
-- After being assigned a task, to get complete requirements
-## Output
-Returns full task details:
-- **subject**: Task title
-- **description**: Detailed requirements and context
-- **status**: 'pending', 'in_progress', or 'completed'
-- **blocks**: Tasks waiting on this one to complete
-- **blockedBy**: Tasks that must complete before this one can start
-## Tips
-- After fetching a task, verify its blockedBy list is empty before beginning work.
-- Use TaskList to see all tasks in summary form.</div>
-      </details>
-<details>
-        <summary><code>TaskUpdate</code> — System Prompt</summary>
-        <div class="prompt-box">Use this tool to update a task in the task list.
-## When to Use This Tool
-**Mark tasks as resolved:**
-- When you have completed the work described in a task
-- When a task is no longer needed or has been superseded
-- IMPORTANT: Always mark your assigned tasks as resolved when you finish them
-- After resolving, call TaskList to find your next task
-- 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
-**Delete tasks:**
-- When a task is no longer relevant or was created in error
-- Setting status to \</div>
-      </details>
-<details>
-        <summary><code>TodoWrite</code> — System Prompt</summary>
-        <div class="prompt-box">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
-&lt;example&gt;
-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: *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*
-&lt;reasoning&gt;
-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 &quot;Ensure tests and build succeed&quot; as the final task
-&lt;/reasoning&gt;
-&lt;/example&gt;
-&lt;example&gt;
-User: Help me rename the function getCwd to getCurrentWorkingDirectory across my project
-Assistant: *Uses grep or search tools to locate all instances of getCwd in the codebase*
-I've found 15 instances of 'getCwd' across 8 different files.
-*Creates todo list with specific items for each file that needs updating*
-&lt;reasoning&gt;
-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
-&lt;/reasoning&gt;
-&lt;/example&gt;
-&lt;example&gt;
-User: I need to implement these features for my e-commerce site: user registration, product catalog, shopping cart, and checkout flow.
-Assistant: *Creates a todo list breaking down each feature into specific tasks based on the project architecture*
-Let's start with user registration. This will involve creating database models, API endpoints, and frontend forms that integrate with your existing authentication system.
-&lt;reasoning&gt;
-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
-&lt;/reasoning&gt;
-&lt;/example&gt;
-&lt;example&gt;
-User: Can you help optimize my React application? It's rendering slowly and has performance issues.
-Assistant: *Reviews component structure, render patterns, state management, and data fetching*
-After analyzing your codebase, I've identified several performance issues.
-*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.
-&lt;reasoning&gt;
-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
-&lt;/reasoning&gt;
-&lt;/example&gt;
-## Examples of When NOT to Use the Todo List
-&lt;example&gt;
-User: How do I print 'Hello World' in Python?
-Assistant: In Python, you can print &quot;Hello World&quot; with this simple code:
-python
-print(&quot;Hello World&quot;)
-This will output the text &quot;Hello World&quot; to the console when executed.
-&lt;reasoning&gt;
-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.
-&lt;/reasoning&gt;
-&lt;/example&gt;
-&lt;example&gt;
-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.
-&lt;reasoning&gt;
-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.
-&lt;/reasoning&gt;
-&lt;/example&gt;
-&lt;example&gt;
-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 ${FILE_EDIT_TOOL_NAME} tool to add a comment to the calculateTotal function *
-&lt;reasoning&gt;
-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.
-&lt;/reasoning&gt;
-&lt;/example&gt;
-&lt;example&gt;
-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.
-&lt;reasoning&gt;
-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.
-&lt;/reasoning&gt;
-&lt;/example&gt;
-## 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., &quot;Run tests&quot;, &quot;Build the project&quot;)
-   - activeForm: The present continuous form shown during execution (e.g., &quot;Running tests&quot;, &quot;Building the project&quot;)
-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: &quot;Fix authentication bug&quot;
-     - activeForm: &quot;Fixing authentication bug&quot;
-When in doubt, use this tool. Being proactive with task management demonstrates attentiveness and ensures you complete all requirements successfully.</div>
-      </details>
-</div>
-    <style>
-      .tool-prompts details {
-        background: var(--bg-card);
-        border: 1px solid var(--border-subtle);
-        border-radius: 8px;
-        margin: 0.5rem 0;
-        padding: 0.75rem 1rem;
-      }
-      .tool-prompts summary { cursor: pointer; font-weight: 600; font-size: var(--text-sm); }
-      .prompt-box {
-        background: var(--code-bg);
-        border: 1px solid var(--code-border);
-        border-radius: 6px;
-        padding: 1rem;
-        margin: 0.75rem 0;
-        font-family: var(--font-mono);
-        font-size: var(--text-xs);
-        line-height: 1.6;
-        color: var(--code-text);
-        white-space: pre-wrap;
-        overflow-x: auto;
-      }
-    </style>
-  </main></div>
-</div>
-</body>
-</html>