pybao-cli 1.5.47 → 1.5.50

package/dist/{chunk-J3TM7T3W.js → chunk-KKNO6B2K.js}

@@ -2,17 +2,17 @@ import { createRequire as __pybCreateRequire } from "node:module";
 const require = __pybCreateRequire(import.meta.url);
 import {
   loadPybAgentSessionMessages
-} from "./chunk-TLMCXAET.js";
+} from "./chunk-NSFU6Y4R.js";
 import {
   appendSessionCustomTitleRecord,
   appendSessionJsonlFromMessage,
   appendSessionTagRecord,
   listPybAgentSessions
-} from "./chunk-T6S6TXIY.js";
+} from "./chunk-IXFDCJ25.js";
 import {
   formatValidationResult,
   validatePluginOrMarketplacePath
-} from "./chunk-IAIXAB4N.js";
+} from "./chunk-K3QEELFX.js";
 import {
   ConversationTracker,
   appendFinishState,
@@ -20,10 +20,10 @@ import {
   getConversationTrackerForContext,
   isFinishComplete,
   mapFinishReason
-} from "./chunk-ITD4GQ6O.js";
+} from "./chunk-L4CGYTJQ.js";
 import {
   FileSystemConversationPersistence
-} from "./chunk-V6W537PO.js";
+} from "./chunk-J6HKEIL2.js";
 import {
   beginReplSessionScope
 } from "./chunk-F4AXICO7.js";
@@ -38,7 +38,7 @@ import {
   runStopHooks,
   runUserPromptSubmitHooks,
   updateHookTranscriptForMessages
-} from "./chunk-6JVCLWCU.js";
+} from "./chunk-DBMDQEQO.js";
 import {
   DEFAULT_OUTPUT_STYLE,
   getAvailableOutputStyles,
@@ -47,11 +47,11 @@ import {
   getOutputStyleSystemPromptAdditions,
   resolveOutputStyleName,
   setCurrentOutputStyle
-} from "./chunk-57BVHCH3.js";
+} from "./chunk-BQCQ3DEN.js";
 import {
   fetchCustomModels,
   getModelFeatures
-} from "./chunk-Q4WANADY.js";
+} from "./chunk-5P4A6TN2.js";
 import {
   getCurrentSessionId,
   getSessionState
@@ -60,13 +60,30 @@ import {
   queryLLM,
   queryQuick,
   verifyApiKey
-} from "./chunk-ZLNJ6XFU.js";
+} from "./chunk-ZDDVFBS4.js";
 import {
   DEFAULT_TIMEOUT_MS,
+  DESCRIPTION,
+  DESCRIPTION2,
+  DESCRIPTION3,
+  DESCRIPTION4,
+  DESCRIPTION5,
+  DESCRIPTION6,
   FallbackToolUseRejectedMessage,
   MAX_OUTPUT_LENGTH,
   MCPTool,
   OutputLine,
+  PROMPT,
+  PROMPT2,
+  PROMPT3,
+  TOOL_NAME,
+  TOOL_NAME2,
+  TOOL_NAME3,
+  TOOL_NAME4,
+  TOOL_NAME5,
+  TOOL_NAME6,
+  TOOL_NAME7,
+  TOOL_NAME8,
   getBashToolPrompt,
   getClients,
   getMCPCommands,
@@ -75,7 +92,7 @@ import {
   listMCPServers,
   loadMergedSettings,
   normalizeSandboxRuntimeConfigFromSettings
-} from "./chunk-SD3VNTAR.js";
+} from "./chunk-FNDIHEBT.js";
 import {
   addMarketplace,
   disableSkillPlugin,
@@ -88,11 +105,11 @@ import {
   refreshMarketplaceAsync,
   removeMarketplace,
   uninstallSkillPlugin
-} from "./chunk-GHNPBDR6.js";
+} from "./chunk-CHH6TEXB.js";
 import {
   loadToolPermissionContextFromDisk,
   persistToolPermissionUpdateToDisk
-} from "./chunk-Q2FTNJHH.js";
+} from "./chunk-Y7I4XTJJ.js";
 import {
   applyToolPermissionContextUpdate,
   applyToolPermissionContextUpdates,
@@ -103,14 +120,14 @@ import {
   generateSystemReminders,
   resetReminderSession,
   systemReminderService
-} from "./chunk-RRLBQ3XD.js";
+} from "./chunk-NRORTICH.js";
 import {
   clearAgentCache,
   getActiveAgents,
   getAgentByType,
   getAllAgents,
   getAvailableAgentTypes
-} from "./chunk-A5O2MBVW.js";
+} from "./chunk-YFVKGHW2.js";
 import {
   API_ERROR_MESSAGE_PREFIX,
   CANCEL_MESSAGE,
@@ -145,7 +162,7 @@ import {
   reorderMessages,
   resetAutoCompactTelemetry,
   stripSystemMessages
-} from "./chunk-UUTMXSER.js";
+} from "./chunk-PXRUNRK7.js";
 import {
   getRequestStatus,
   setRequestStatus,
@@ -177,7 +194,7 @@ import {
   normalizeFilePath,
   readTextContent,
   writeTextContent
-} from "./chunk-US6EALFL.js";
+} from "./chunk-NBDDIZNJ.js";
 import {
   parseBlockEdits
 } from "./chunk-QWIBSCDN.js";
@@ -191,7 +208,7 @@ import {
   formatDiagnosticsPretty,
   initParser,
   loadLanguage
-} from "./chunk-VDLMXEHU.js";
+} from "./chunk-NQGIALRP.js";
 import {
   emitTelemetryEvent,
   registerTelemetryListener
@@ -200,13 +217,13 @@ import {
   getSettingsFileCandidates,
   loadSettingsWithLegacyFallback,
   readSettingsFile
-} from "./chunk-7WPBMV6W.js";
+} from "./chunk-CNBKKQSV.js";
 import {
   getCustomCommandDirectories,
   hasCustomCommands,
   loadCustomCommands,
   reloadCustomCommands
-} from "./chunk-XIAHHC4E.js";
+} from "./chunk-7MR3XX5X.js";
 import {
   getSessionPlugins
 } from "./chunk-BJSWTHRM.js";
@@ -215,7 +232,7 @@ import {
   buildModelProfileKey,
   getModelManager,
   isDefaultSlowAndCapableModel
-} from "./chunk-K3AQYDRJ.js";
+} from "./chunk-VAZ4VRTA.js";
 import {
   getCodeStyle,
   getContext,
@@ -223,16 +240,16 @@ import {
   getIsGit,
   getProjectDocs,
   getProjectStructureStatisticsBlock
-} from "./chunk-OPEQBEHZ.js";
+} from "./chunk-LE5VGGP6.js";
 import {
   getRipgrepPath,
   getRipgrepPolicyMode,
   resolveRipgrepPolicy,
   ripGrep
-} from "./chunk-7UF7PBUR.js";
+} from "./chunk-ZKW5V7MR.js";
 import {
   getTheme
-} from "./chunk-N2W52I56.js";
+} from "./chunk-EY3ZOE75.js";
 import {
   DEFAULT_GLOBAL_CONFIG,
   enableConfigs,
@@ -245,7 +262,7 @@ import {
   saveGlobalConfig,
   setAllPointersToModel,
   setModelPointer
-} from "./chunk-2AU4PKSQ.js";
+} from "./chunk-CNW45NOZ.js";
 import {
   AbortError
 } from "./chunk-RQVLBMP7.js";
@@ -254,7 +271,7 @@ import {
   getCurrentRequest,
   logUserFriendly,
   markPhase
-} from "./chunk-MWL7Q5HG.js";
+} from "./chunk-A45A3UUU.js";
 import {
   ASCII_LOGO,
   BunShell,
@@ -298,10 +315,10 @@ import {
   setCwd,
   shouldApplyToolOutputTruncation,
   truncateToolOutput
-} from "./chunk-CN443EB5.js";
+} from "./chunk-UJRT7VK2.js";
 import {
   MACRO
-} from "./chunk-5OJHTSFR.js";
+} from "./chunk-5ITEAEJC.js";
 import {
   __export
 } from "./chunk-I3J4JYES.js";
@@ -482,7 +499,7 @@ var getCommandSubcommandPrefix = memoize(
 var getCommandPrefix = memoize(
   async (command4, abortSignal) => {
     const { systemPrompt, userPrompt } = buildBashCommandPrefixDetectionPrompt(command4);
-    const { API_ERROR_MESSAGE_PREFIX: API_ERROR_MESSAGE_PREFIX2, queryQuick: queryQuick2 } = await import("./llm-QPAHJ643.js");
+    const { API_ERROR_MESSAGE_PREFIX: API_ERROR_MESSAGE_PREFIX2, queryQuick: queryQuick2 } = await import("./llm-KXF74SNS.js");
     const response = await queryQuick2({
       systemPrompt,
       userPrompt,
@@ -4284,7 +4301,7 @@ function formatParseError(error) {
   return error instanceof Error ? error.message : String(error);
 }
 async function defaultGateQuery(args) {
-  const { API_ERROR_MESSAGE_PREFIX: API_ERROR_MESSAGE_PREFIX2, queryLLM: queryLLM2 } = await import("./llm-QPAHJ643.js");
+  const { API_ERROR_MESSAGE_PREFIX: API_ERROR_MESSAGE_PREFIX2, queryLLM: queryLLM2 } = await import("./llm-KXF74SNS.js");
   const queryLLMFn = args.queryLLMOverride ?? queryLLM2;
   const messages = [
     {
@@ -4678,8 +4695,8 @@ function Cost({ costUSD, durationMs, debug: debug2 }) {
 }
 
 // src/tools/network/WebFetchTool/prompt.ts
-var TOOL_NAME_FOR_PROMPT = "WebFetch";
-var PROMPT = `
+var TOOL_NAME9 = "WebFetch";
+var PROMPT4 = `
 - Fetches content from a specified URL
 - Takes a URL and optional prompt/format as input
 - Fetches the URL content, converts HTML to the requested format
@@ -5098,7 +5115,7 @@ async function fetchWithRedirectDetection(url2, signal, connectTimeoutMs) {
   }
 }
 var WebFetchTool = {
-  name: TOOL_NAME_FOR_PROMPT,
+  name: TOOL_NAME9,
   async description(input) {
     const url2 = input?.url;
     try {
@@ -5118,7 +5135,7 @@ var WebFetchTool = {
     return true;
   },
   async prompt() {
-    return PROMPT;
+    return PROMPT4;
   },
   async validateInput({ url: url2 }) {
     if (url2.length > MAX_URL_LENGTH) {
@@ -6120,8 +6137,9 @@ function HighlightedCode({ code, language }) {
 }
 
 // src/tools/filesystem/NotebookEditTool/prompt.ts
-var DESCRIPTION = "Replace the contents of a specific cell in a Jupyter notebook.";
-var PROMPT2 = `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.
+var TOOL_NAME10 = "NotebookEdit";
+var DESCRIPTION7 = "Replace the contents of a specific cell in a Jupyter notebook.";
+var PROMPT5 = `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.
 `.trim();
 
 // src/utils/permissions/filesystem.ts
@@ -6233,12 +6251,12 @@ var inputSchema2 = z2.strictObject({
   )
 });
 var NotebookEditTool = {
-  name: "NotebookEdit",
+  name: TOOL_NAME10,
   async description() {
-    return DESCRIPTION;
+    return DESCRIPTION7;
   },
   async prompt() {
-    return PROMPT2;
+    return PROMPT5;
   },
   inputSchema: inputSchema2,
   userFacingName() {
@@ -6455,71 +6473,6 @@ var NotebookEditTool = {
   }
 };
 
-// src/tools/filesystem/FileEditTool/prompt.ts
-var DESCRIPTION2 = `Performs smart string replacements in files using SEARCH/REPLACE blocks.
-
-Usage:
-1. **Read First**: You must use your \`Read\` tool at least once before editing.
-2. **Block Format**: Provide changes as one or more SEARCH/REPLACE blocks.
-   \`\`\`
-   <<<<<<< SEARCH
-   [original code to replace]
-   =======
-   [new code to insert]
-   >>>>>>> REPLACE
-   \`\`\`
-3. **Multiple Edits**: You can provide multiple blocks in a single turn to perform batch edits.
-4. **Context**: Include enough surrounding lines in the SEARCH block to ensure uniqueness.
-5. **Indentation**: Preserve the exact indentation (tabs/spaces) of the original file in your SEARCH block.
-6. **Smart Matching**: The tool uses a fuzzy matching engine. It can locate code even if there are minor differences in whitespace or indentation.
-7. **Conditional Edit**: Use \`if_not_contains\` to skip the edit if the file already contains a specific string.
-8. **Thinking**: You can include "thinking" text between blocks; the tool will ignore it.
-
-## LSP-Integrated Behavior
-- **Semantic Anchor Assist**: Before fuzzy replacement, Edit tries LSP anchor matching to narrow replacement to the most relevant symbol range.
-- **When It Helps**: Especially useful when the same snippet appears multiple times and plain text matching may hit the wrong block.
-- **Fallback**: If LSP anchor is unavailable, Edit falls back to normal SEARCH/REPLACE matching.
-- **Post-Edit Verification**: Set \`verify: true\` to run LSP diagnostics after applying edits.
-- **Verification Guardrail**: If syntax/type diagnostics contain errors after edit, Edit reverts changes and returns a verification failure.
-- **When LSP Is Unavailable**: You may receive verification unavailable; retry with \`verify: false\` only when you have high confidence in edit safety.
-
-Notes:
-- The edit will FAIL if the SEARCH block matches multiple locations(ambiguous). Provide more context.
-- To delete code, leave the REPLACE section empty.
-- To create a new file, use an empty SEARCH block with the desired content in REPLACE.
-- ALWAYS prefer editing existing files. NEVER write new files unless explicitly required.
-- For Jupyter Notebooks (.ipynb), use the NotebookEditTool instead.
-
-## Typical Usage Examples
-### Example 1: Ambiguous Duplicate Snippet with LSP Anchor
-<example>
-user: Update the constructor guard in UserService, not the test helper copy
-assistant: [uses Read on UserService file to confirm target block]
-[uses Edit with SEARCH/REPLACE block and verify=true]
-[relies on LSP anchor assist to prefer semantic symbol region when duplicate text exists]
-<reasoning>
-The assistant enabled semantic-safe editing because:
-1. Duplicate snippets can cause ambiguous fuzzy matches
-2. LSP anchor narrows replacement to the intended symbol scope
-3. verify=true adds post-edit diagnostics guardrail and auto-revert on syntax errors
-</reasoning>
-</example>
-
-### Example 2: Verification-Unavailable Recovery
-<example>
-user: Apply this quick rename in a generated file
-assistant: [uses Read to confirm exact path and block]
-[uses Edit with verify=true]
-[if response says verification unavailable, retries with verify=false and tighter SEARCH context]
-<reasoning>
-The assistant keeps verification first, then degrades safely because:
-1. LSP verification is preferred for correctness
-2. Generated or unsupported files may not have active LSP diagnostics
-3. Retrying with verify=false is acceptable only after narrowing context
-</reasoning>
-</example>
-`.trim();
-
 // src/utils/terminal/paste.ts
 function normalizeLineEndings(text) {
   return text.replace(/\r\n/g, "\n").replace(/\r/g, "\n");
@@ -6724,7 +6677,7 @@ var inputSchema3 = z3.strictObject({
   )
 });
 var FileEditTool = {
-  name: "Edit",
+  name: TOOL_NAME2,
   async description() {
     return "A tool for editing files using SEARCH/REPLACE blocks";
   },
@@ -6847,7 +6800,7 @@ var FileEditTool = {
     const originalFileContent = currentFileContent;
     let totalPatch = [];
     const { SmartEdit } = await import("./smart-edit-AWHJDSU6.js");
-    const { findLspAnchor } = await import("./lspAnchor-YI3SOGER.js");
+    const { findLspAnchor } = await import("./lspAnchor-7Z5YNXX3.js");
     for (const op of editOperations) {
       const normalizedSearch = normalizeLineEndings(op.search);
       const normalizedReplace = normalizeLineEndings(op.replace);
@@ -6972,102 +6925,6 @@ import { extname as extname4, relative as relative6 } from "node:path";
 import * as React13 from "react";
 import { z as z4 } from "zod";
 
-// src/tools/filesystem/FileReadTool/prompt.ts
-var MAX_LINES_TO_READ = 2e3;
-var MAX_LINE_LENGTH = 2e3;
-var DESCRIPTION3 = "Read a file or directory from the local filesystem.";
-var PROMPT3 = `Reads a file or directory from the local filesystem. You can access any file or directory directly by using this tool.Assume this tool is able to read all files on the machine. If the User provides a path to a file assume that path is valid; otherwise, Ensure the path is confirmed by Glob/Grep before reading.
-
-## Best Practice
-- **Read vs Analyze**: Use this tool when you need to inspect full implementation details.
-- **Workflow**: Locate file (Glob/Grep) -> Read file (FileRead) -> Edit file.
-- **Avoid**: Do not use this to 'search' for code strings; use 'Grep' or 'Glob' for that.
-
-## When NOT to Use Read Tool
-- **Unverified Paths**: Do NOT read a file if the path was inferred or guessed from context. Always verify the path exists using Glob/Grep first.
-- **Exploration Phase**: When exploring unfamiliar code, do NOT assume file locations. Use Glob/Grep to discover actual paths before reading.
-- It is okay to read a file that does not exist; an error will be returned. 
-
-## Usage Details
-- The file_path parameter must be an absolute path, not a relative path
-- This tool supports both file mode and directory mode
-- In directory mode, offset/limit are 1-based entry pagination and offset>=1 is required
-- In file mode, offset/limit are 1-based line pagination; offset=1 starts from the first line shown in cat -n output
-- By default, file mode reads up to ${MAX_LINES_TO_READ} lines starting from the beginning of the file
-- You can optionally specify a line offset and limit (especially handy for long files). **Smart Truncation is active** only in file mode when \`limit\` is provided and \`symbol_name\` is not provided: if your limit cuts a function or class in the middle, the tool will automatically extend the read range to include the full semantic block (up to 500 extra lines).
-- Smart Truncation is a best-effort semantic boundary repair (Tree-sitter). If semantic parsing fails, Read falls back to the original offset/limit window.
-- symbol_name enables LSP-assisted symbol read: provide an exact symbol name to resolve the symbol range and read that block directly
-- When \`symbol_name\` is provided, Read resolves symbol range via LSP and reads that block directly (offset/limit are ignored for range selection).
-- Use symbol_name only after file path is confirmed and when you need a specific class/function definition; if symbol is missing, unresolved, or LSP is unavailable, fallback to offset/limit or use LspTool for semantic discovery first.
-- Directory mode returns a one-level tree structure using \u251C\u2500\u2500/\u2514\u2500\u2500 and supports pagination continuation hints
-- For large files, iterate in chunks: offset=1 limit=200, then offset=201 limit=200, and so on until the needed region is covered
-- File text truncation is capped at 50KB per result and 2000 lines; 50KB is file text truncation and not a directory access gate
-- Any lines longer than ${MAX_LINE_LENGTH} characters will be truncated
-- Results are returned using cat -n format, with line numbers starting at 1
-- This tool allows reading images (eg PNG, JPG, etc). When reading an image file the contents are presented visually.
-- This tool can read PDF files and return them as document blocks for analysis.
-- This tool can read Jupyter notebooks (.ipynb files) and returns all cells with their outputs, combining code, text, and visualizations.
-- For wide repository exploration, still prefer Glob first, then use Read for focused file/directory inspection.
-- You can call multiple tools in a single response. It is always better to speculatively read multiple potentially useful files in parallel.
-- You will regularly be asked to read screenshots. If the user provides a path to a screenshot, ALWAYS use this tool to view the file at the path. This tool will work with all temporary file paths.
-- If you read a file that exists but has empty contents you will receive a system reminder warning in place of file contents.
-
-## Typical Usage Examples
-### Example 1: Exploring Unfamiliar Codebase
- <example>
-  user: How does authentication work in this project?
-  assistant: [uses Grep tool with pattern="auth|login" to find relevant files]
-  [uses Glob tool with pattern="**/auth*.{ts,js}" to locate auth modules]
-  [reads the matched files after confirming their paths]
- </example>
-
-### Example 2: User Mentions a Concept Without Path
- <example>
-  user: Check the database configuration
-  assistant: [uses Glob tool with pattern="**/config*.{ts,js,json}"]
-  [uses Grep tool with pattern="database|db_" to find config files with db settings]
-  [reads the confirmed config file]
- </example>
-
-### Example 3: Read Directory Structure Then Read File
- <example>
-  user: Check the API module layout and read router implementation
-  assistant: [uses Glob tool with pattern="**/api*"]
-  [reads the confirmed api directory path to get one-level tree structure with Read]
-  [reads the router file path found in that directory tree]
- </example>
-
-### Example 4: LSP-Assisted Symbol Read
- <example>
-  user: I only need the function that actually executes file reading, not the whole file
-  assistant: [uses Glob/Grep to confirm FileReadTool file path]
-  [uses Read with file_path="<absolute path>/FileReadTool.tsx" symbol_name="call"]
-  [if symbol is missing or unresolved, uses LspTool documentSymbol to discover exact symbol names, then retries]
-  [if LSP is unavailable, falls back to offset/limit chunked reads around likely implementation area]
-  <reasoning>
-  The assistant used symbol_name-based Read because:
-  1. User intent is a specific implementation block, not whole-file browsing
-  2. symbol_name gives precise semantic range selection and avoids noisy context
-  3. LspTool is used only for symbol discovery fallback, while Read remains the code retrieval tool
-  </reasoning>
- </example>
-
-### Example 5: Smart Truncation on Partial Window
- <example>
-  user: Please read this file section for me; I do not know where the function ends
-  assistant: [uses Read with file_path="<absolute path>/service.ts" offset=120 limit=30]
-  [relies on Smart Truncation to auto-extend when the requested window cuts a function/class boundary]
-  [checks returned startLine/numLines and continues with adjacent chunks if more context is needed]
-  [if semantic parsing fails, falls back to original offset/limit and continues chunked reading]
-  <reasoning>
-  The assistant used offset/limit Read with Smart Truncation because:
-  1. User asked for a local section without symbol-level knowledge
-  2. Pagination windows can split semantic containers, causing misleading partial code
-  3. Smart Truncation repairs semantic boundaries while preserving pagination workflow
-  </reasoning>
- </example>
-`.trim();
-
 // src/utils/fs/secureFile.ts
 import {
   existsSync as existsSync4,
@@ -7702,7 +7559,7 @@ function toSmartTruncationFallbackEvent(input) {
 
 // src/tools/filesystem/FileReadTool/FileReadTool.tsx
 var MAX_LINES_TO_RENDER = 0;
-var MAX_LINE_LENGTH2 = 2e3;
+var MAX_LINE_LENGTH = 2e3;
 var MAX_TEXT_OUTPUT_BYTES = 50 * 1024;
 var MAX_TEXT_OUTPUT_LINES = 2e3;
 var DIRECTORY_DEFAULT_LIMIT = 200;
@@ -7824,12 +7681,12 @@ var inputSchema4 = z4.strictObject({
   )
 });
 var FileReadTool = {
-  name: "Read",
+  name: TOOL_NAME,
   async description() {
-    return DESCRIPTION3;
+    return DESCRIPTION;
   },
   async prompt() {
-    return PROMPT3;
+    return PROMPT;
   },
   inputSchema: inputSchema4,
   isReadOnly() {
@@ -8113,7 +7970,7 @@ var FileReadTool = {
       finalLimit
     );
     const truncatedLines = content.split(/\r?\n/).map(
-      (line) => line.length > MAX_LINE_LENGTH2 ? line.slice(0, MAX_LINE_LENGTH2) : line
+      (line) => line.length > MAX_LINE_LENGTH ? line.slice(0, MAX_LINE_LENGTH) : line
     ).join("\n");
     const textPage = capTextOutput(truncatedLines, {
       startLine,
@@ -8462,19 +8319,6 @@ import { EOL } from "os";
 import { dirname as dirname4, extname as extname5, isAbsolute as isAbsolute5, relative as relative7, resolve as resolve5 } from "path";
 import * as React14 from "react";
 import { z as z5 } from "zod";
-
-// src/tools/filesystem/FileWriteTool/prompt.ts
-var PROMPT4 = `Writes a file to the local filesystem.
-
-Usage:
-- This tool will overwrite the existing file if there is one at the provided path.
-- If this is an existing file, you MUST use the ${FileReadTool.name} tool first to read the file's contents. This tool will fail if you did not read the file first.
-- ALWAYS prefer editing existing files in the codebase. NEVER write new files unless explicitly required.
-- NEVER proactively create documentation files (*.md) or README files. Only create documentation files if explicitly requested by the User.
-- Only use emojis if the user explicitly requests it. Avoid writing emojis to files unless asked.
-`.trim();
-
-// src/tools/filesystem/FileWriteTool/FileWriteTool.tsx
 var MAX_LINES_TO_RENDER2 = 5;
 var MAX_LINES_TO_RENDER_FOR_ASSISTANT = 16e3;
 var TRUNCATED_MESSAGE = "<response clipped><NOTE>To save on context only part of this file has been shown to you. You should retry this tool after you have searched inside the file with Grep in order to find the line numbers of what you are looking for.</NOTE>";
@@ -8485,13 +8329,13 @@ var inputSchema5 = z5.strictObject({
   content: z5.string().describe("The content to write to the file")
 });
 var FileWriteTool = {
-  name: "Write",
+  name: TOOL_NAME3,
   async description() {
-    return "Write a file to the local filesystem.";
+    return DESCRIPTION3;
   },
   userFacingName: () => "Write",
   async prompt() {
-    return PROMPT4;
+    return PROMPT2;
   },
   inputSchema: inputSchema5,
   async isEnabled() {
@@ -8664,116 +8508,6 @@ ${addLineNumbers({
 import { Box as Box14, Text as Text15 } from "ink";
 import React15 from "react";
 import { z as z6 } from "zod";
-
-// src/tools/filesystem/GlobTool/prompt.ts
-var TOOL_NAME_FOR_PROMPT2 = "Glob";
-var DESCRIPTION4 = `Fast file pattern matching tool that works with any codebase size
-
-  ## WhenToUse & Best Practice
-  - If you have keywords or fuzzy paths, use Glob first to narrow candidates.
-  - When you are doing an open ended search that may require multiple rounds of globbing and grepping, use the Agent tool instead
-  - You can call multiple tools in a single response. It is always better to speculatively perform multiple searches in parallel if they are potentially useful.
-  - This tool is for FINDING files.
-
-  ## Directory Structure Guidance
-  - For one-level directory structure, use Read directly on the directory path (offset>=1, optional limit)
-  - Use Glob for file-path discovery and candidate narrowing, not as the primary one-level directory listing workflow
-
-  ## Search Strategy
-  - **Broad-to-Narrow Pattern**: Start with a broad pattern, then narrow based on results.
-    - Step 1: Use broad patterns like \`**/*.ts\` or \`src/**/*\` to get an overview
-    - Step 2: Analyze results and refine with more specific patterns
-    - Example: "\`**/*.test.ts\`" \u2192 too many results \u2192 "src/**/auth*.test.ts"
-  - **Pattern Selection Guide**:
-    - Unknown structure? Start with \`**/*.{ext}\` to discover layout, then use Read on specific directory paths for one-level structure
-    - Looking for specific type? Use descriptive names: \`**/test*\`, \`**/config*\`
-    - In a specific area? Combine path + pattern: \`src/auth/**/*.ts\`
-  - **Discovery Workflow**: For unfamiliar codebases, run these in parallel:
-    - \`**/package.json\`, \`**/*.{ts,js,tsx,jsx}\`, \`**/README*\`, \`**/*config*.{ts,js,json}\`
-    - Analyze structure \u2192 refine search \u2192 read key files
-  - **Tool Collaboration**:
-    - Read \`directory_path\` \u2192 Get one-level directory tree structure
-    - Grep \u2192 After Glob finds files, use Grep to search content
-    - Read \u2192 Read the found file contents
-
-  ## Usage Details
-  - Supports glob patterns like "**/*.js" or "src/**/*.ts"
-  - Returns absolute file paths sorted by modification time (most recent first)
-  - Use this tool when you need to find files by name patterns
-  - Powered by ripgrep with \`--files\` mode for fast pattern matching
-  - \`path\` parameter: Specify the directory to search in. If omitted, uses the current working directory. IMPORTANT: Omit this field to use the default directory. DO NOT enter "undefined" or "null" - simply omit it for the default behavior. Supports both relative and absolute paths.
-  - Results are limited to 100 files by default. If truncated, use a more specific path or pattern to narrow results.
-  - Search ignores .gitignore rules and includes hidden files by default.
-  - **Empty Results**: When no files are found, try broader patterns (e.g., src/**/*) or verify path exists.
-  - **Error Handling**: Returns error if \`path\` does not exist or is not a valid directory.
-  - **LSP Semantic Mode**: \`semantic: true\` enables workspace symbol fallback when file globbing returns empty.
-  - **Semantic search is opt-in**: Only set \`semantic: true\` when you intentionally want LSP-assisted fallback.
-  - Semantic output may include:
-    - \`semanticNotice\`: human-readable semantic fallback note
-    - \`semanticReason\`: structured reason code (e.g., \`SYMBOLS_ADDED\`, \`NO_SYMBOL_MATCH\`, \`LSP_UNAVAILABLE\`)
-    - \`semanticSuggestion\`: suggested next action aligned to reason code
-  - **Truncated Results**: When results are truncated (limited to 100 files), narrow down using:
-    1. Add a more specific path: \`src/core/**/*.ts\` instead of \`**/*.ts\`
-    2. Use file extension filter: \`src/**/*.test.ts\` instead of \`src/**/*.ts\`
-    3. Use Read on a specific directory path to confirm one-level structure, then target specific directories with Glob
-
-  ## Typical Usage Examples
-
-  ### Example 1: Project Structure Discovery (Unknown Codebase)
-  <example>
-  user: I'm new to this project, what's the structure?       
-  assistant: [uses Glob tool with pattern="**/package.json" to find project roots]
-  [reads the confirmed source directory path to inspect one-level tree structure]
-  [uses Glob tool with pattern="**/*.{ts,tsx,js,jsx}" to locate major source areas]
-  </example>
-
-  ### Example 2: Find Files by Type in Specific Area
-  <example>
-  user: Find all test files in the auth module
-  assistant: [uses Glob tool with pattern="src/auth/**/*.test.ts"]
-  [uses Read tool to examine specific test files]
-  </example>
-
-  ### Example 3: Config File Location (Deterministic)        
-  <example>
-  user: Where is the webpack configuration?
-  assistant: [uses Glob tool with pattern="**/webpack*.{js,ts,json}"]
-  [uses Read tool on the matched config file]
-  </example>
-
-  ### Example 4: Parallel Discovery for Entry Points
-  <example>
-  user: What are the main entry points of this application?
-  assistant: [uses Glob tool with pattern="**/index.{ts,js}"]
-  [uses Glob tool with pattern="**/main.{ts,js}"]
-  [uses Glob tool with pattern="**/app.{ts,js}"]
-  [uses Read tool to examine the entry point files]
-  </example>
-
-  ### Example 5: Narrow Down After Broad Results
-  <example>
-  user: Find all TypeScript files in the project
-  assistant: [uses Glob tool with pattern="**/*.ts" - returns 500+ files, truncated]
-  [uses Glob tool with pattern="src/**/*.ts" to focus on source code]
-  [uses Glob tool with pattern="src/core/**/*.ts" to narrow further if needed]
-  </example>
-
-  ### Example 6: Semantic Fallback for Unknown File Path
-  <example>
-  user: Find where AuthService is implemented, I do not know the file name
-  assistant: [uses Glob tool with pattern="**/*AuthService*" semantic=false first]
-  [if no files found, retries with semantic=true]
-  [reads semanticReason and semanticSuggestion to decide next step]
-  <reasoning>
-  The assistant switches to semantic mode because:
-  1. Filename-based glob failed and user intent is symbol-oriented
-  2. semantic=true allows LSP workspace symbols to recover likely file paths
-  3. semanticReason + semanticSuggestion provide explicit fallback diagnostics
-  </reasoning>
-  </example>
-`.trim();
-
-// src/tools/filesystem/GlobTool/GlobTool.tsx
 import { existsSync as existsSync6, statSync as statSync9 } from "fs";
 import { isAbsolute as isAbsolute6, join as join5, relative as relative8, resolve as resolve6 } from "path";
 import { fileURLToPath as fileURLToPath2 } from "url";
@@ -8821,7 +8555,7 @@ var inputSchema6 = z6.strictObject({
 });
 var DEFAULT_LIMIT = 100;
 var GlobTool = {
-  name: TOOL_NAME_FOR_PROMPT2,
+  name: TOOL_NAME4,
   async description() {
     return DESCRIPTION4;
   },
@@ -8975,130 +8709,6 @@ import React16 from "react";
 import { existsSync as existsSync7 } from "fs";
 import { stat as statAsync } from "fs/promises";
 import { z as z7 } from "zod";
-
-// src/tools/search/GrepTool/prompt.ts
-var TOOL_NAME_FOR_PROMPT3 = "Grep";
-var DESCRIPTION5 = `A powerful fast content search tool that works with any codebase size
-
-  ## Best Practice
-  - Use Grep as a "Scout" to *find* entry points based on text patterns.
-    - STEP 1: Search for a unique string (e.g., error message, URL route, specific variable name).
-    - STEP 2: Once you get a match (File + Line Number), STOP grepping.
-    - STEP 3: Use Read to get the exact line + character, then call LspTool for definition or references.
-    - AVOID: Do not use Grep to trace execution flow (e.g., searching for "functionName" manually). Use LSP for that.
-  - Hotspot strategy: narrow the path scope first, then paginate or refine the search; after truncation, focus on high-signal directories to avoid full-repo scans.
-
-  ## Search Strategy
-  - **Pattern Refinement Workflow**:
-    - Start broad: simple keyword first, observe results
-    - Narrow down: add constraints (type, glob, path) if too many matches
-    - Switch mode: \`files_with_matches\` for discovery, \`content\` for details
-  - **From Vague Intent to Precise Pattern**:
-    - "How does auth work?" \u2192 Start with Grep("auth", type="ts") \u2192 Analyze results \u2192 Refine pattern
-    - "Find the API endpoints" \u2192 Grep("router|route|endpoint", type="ts") \u2192 Read key files
-    - "Where is this error from?" \u2192 Grep(exact error message) \u2192 Trace back to source
-  - **Iterative Narrowing**:
-    - Too many results? Add \`glob\`, \`type\`, or narrower \`path\`
-    - No results? Broaden pattern, try case-insensitive (\`-i\`), or try alternative keywords
-    - Wrong results? Adjust pattern, check regex syntax, try alternative keywords
-  - **Tool Collaboration**:
-    - Read "directory_path" \u2192 Confirm one-level directory structure for search scope
-    - Glob "file_path" \u2192 Confirm file path existence
-    - Read \u2192 Read specific content of matched files
-    - LspTool \u2192 Trace definitions and references (replace manual Grep tracing)
-
-  ## Usage Details
-  - ALWAYS use Grep for search tasks. NEVER invoke \`grep\` or \`rg\` as a Bash command. The Grep tool has been optimized for correct permissions and access.
-  - Powered by ripgrep for fast text search with full regex support (e.g., "log.*Error", "function\\s+\\w+")
-  - Pattern syntax: Uses ripgrep - literal braces need escaping (use \`interface\\{\\}\` to find \`interface{}\` in Go code)
-  - Excludes version control directories (.git, .svn, .hg, .bzr) automatically
-  - Includes hidden files by default
-
-  **Path & Scope**:
-  - \`path\` parameter: File or directory to search in. Defaults to current working directory.
-  - \`glob\` parameter: Filter files by glob pattern (e.g., "*.js", "*.{ts,tsx}") - maps to rg --glob
-  - \`type\` parameter: Filter by file type (e.g., "js", "py", "rust", "go", "java") - more efficient than glob for standard types
-  - Path guidance: If user provides a path, use it directly. If uncertain, confirm with Glob first.
-
-  **Output Modes**:
-  - \`files_with_matches\` (default): Returns file paths sorted by modification time
-  - \`content\`: Shows matching lines with line numbers (supports -A/-B/-C context)
-  - \`count\`: Shows match counts per file
-
-  **Context & Pagination**:
-  - \`-B\`, \`-A\`, \`-C\`: Context lines before/after/around matches (requires output_mode: "content")
-  - \`-n\`: Show line numbers (default: true, requires output_mode: "content")
-  - \`head_limit\`: Limit output to first N entries (works across all modes)
-  - \`offset\`: Skip first N entries before applying head_limit
-  - \`multiline\`: Enable multiline mode where . matches newlines (default: false)
-
-  **Case Sensitivity**:
-  - \`-i\`: Enable case-insensitive search
-
-  **Result Handling**:
-  - Results are truncated at 20,000 characters if too large
-  - Use Task tool for open-ended searches requiring multiple rounds
-  - **Semantic Fallback** (\`semantic: true\`): when text grep has no hit (or \`symbol_type\` is provided), Grep can query LSP workspace symbols.
-  - Semantic-enhanced outputs may include:
-    - \`semanticNotice\`: fallback summary
-    - \`semanticReason\`: structured reason code (e.g., \`SYMBOLS_ADDED\`, \`NO_SYMBOL_MATCH\`, \`LSP_UNAVAILABLE\`)
-    - \`semanticSuggestion\`: suggested next action by reason code
-  - Keep deterministic workflow: text search first, semantic fallback second.
-
-  **Typical Usage Examples**:
-
-  Example 1: Exact Error Message Tracing (Deterministic)
-  <example>
-  user: Where does the error "Connection timeout after 30s" come from?
-  assistant: [uses Grep tool with pattern="Connection timeout after 30s"output_mode="content"]
-  [uses Read tool to examine the error source and surrounding context]
-  </example>
-
-  Example 2: Precise Function Definition Lookup (Deterministic)
-  <example>
-  user: Find the implementation of \`calculateCompoundInterest\` function
-  assistant: [uses Grep tool with pattern="calculateCompoundInterest" type="ts"output_mode="content"]
-  [uses Read tool on the matched file to read the full implementation]
-  </example>
-  
-  Example 3: Iterative Narrowing for Broad Patterns
-  <example>
-  user: Find all API route definitions
-  assistant: [uses Grep tool with pattern="router\\.(get|post|put|delete)" type="ts"]       
-  [if too many results: adds path="src/routes" to narrow scope]
-  [uses Read tool to inspect specific route handlers]
-  </example>
-
-  Example 4: Handoff to LSP After Entry Point Found
-  <example>
-  user: Find all usages of the \`PaymentService\` class
-  assistant: [uses Grep tool with pattern="class PaymentService" type="ts"output_mode="content"]
-  [uses LSP findReferences at the class definition location to get all references]
-  </example>
-
-  Example 5: Case-Insensitive Search for Config Values
-  <example>
-  user: Where is the database host configured?
-  assistant: [uses Grep tool with pattern="database.*host|db_host|DB_HOST" -i: true]        
-  [uses Read tool to examine configuration files]
-  </example>
-
-  Example 6: Semantic Fallback with Structured Reason
-  <example>
-  user: Find usages of PaymentSrvce (name might be misspelled)
-  assistant: [uses Grep tool with pattern="PaymentSrvce" output_mode="files_with_matches"]
-  [if no hit, retries with semantic=true]
-  [uses semanticReason and semanticSuggestion to decide whether to broaden query or switch to LspTool]
-  <reasoning>
-  The assistant uses semantic fallback because:
-  1. Text grep may miss typo-tolerant symbol matches
-  2. LSP workspace symbols can recover intended semantic targets
-  3. Structured reason fields make fallback outcomes explicit and actionable
-  </reasoning>
-  </example>
-  `.trim();
-
-// src/tools/search/GrepTool/GrepTool.tsx
 import { isAbsolute as isAbsolute7, relative as relative9, resolve as resolve7 } from "path";
 import { fileURLToPath as fileURLToPath3 } from "url";
 var inputSchema7 = z7.strictObject({
@@ -9188,7 +8798,7 @@ function parseGlobString(glob) {
   return expanded;
 }
 var GrepTool = {
-  name: TOOL_NAME_FOR_PROMPT3,
+  name: TOOL_NAME5,
   async description() {
     return DESCRIPTION5;
   },
@@ -9637,7 +9247,7 @@ var TASK_FORK_CONTEXT_POLICY = [
 ].join("\n");
 
 // src/tools/network/WebSearchTool/prompt.ts
-var TOOL_NAME_FOR_PROMPT4 = "WebSearch";
+var TOOL_NAME11 = "WebSearch";
 function todayISO() {
   const now = /* @__PURE__ */ new Date();
   const year = now.getFullYear();
@@ -9645,7 +9255,7 @@ function todayISO() {
   const day = String(now.getDate()).padStart(2, "0");
   return `${year}-${month}-${day}`;
 }
-var PROMPT5 = `
+var PROMPT6 = `
 - Allows the assistant to search the web and use the results to inform responses
 - Provides up-to-date information for current events and recent data
 - Returns search result information formatted as search result blocks, including links as markdown hyperlinks
@@ -9800,7 +9410,7 @@ function resolveWebSearchProvider() {
   };
 }
 var WebSearchTool = {
-  name: TOOL_NAME_FOR_PROMPT4,
+  name: TOOL_NAME11,
   async description(input) {
     const query2 = input?.query ?? "";
     return `Requesting web search for: ${query2}`;
@@ -9816,7 +9426,7 @@ var WebSearchTool = {
     return true;
   },
   async prompt() {
-    return PROMPT5;
+    return PROMPT6;
   },
   renderToolUseMessage({ query: query2, allowed_domains, blocked_domains }, { verbose }) {
     let summary = `"${query2}"`;
@@ -12792,7 +12402,7 @@ async function createAndStoreApiKey(accessToken) {
       }
       saveGlobalConfig(config2);
       try {
-        const { resetAnthropicClient } = await import("./llm-QPAHJ643.js");
+        const { resetAnthropicClient } = await import("./llm-KXF74SNS.js");
         resetAnthropicClient();
       } catch {
       }
@@ -17216,7 +16826,7 @@ async function refreshPluginRuntimeFromInstalls() {
   const existingRoots = getSessionPlugins().map((p) => p.rootDir);
   const dirs = Array.from(/* @__PURE__ */ new Set([...existingRoots, ...installedRoots]));
   if (dirs.length === 0) return [];
-  const { configureSessionPlugins } = await import("./pluginRuntime-TLFHDTDH.js");
+  const { configureSessionPlugins } = await import("./pluginRuntime-3XWIAPQ7.js");
   const { errors } = await configureSessionPlugins({ pluginDirs: dirs });
   return errors;
 }
@@ -17891,7 +17501,7 @@ async function call(onDone, context) {
     ModelConfig,
     {
       onClose: () => {
-        import("./model-JFUZ777G.js").then(({ reloadModelManager: reloadModelManager2 }) => {
+        import("./model-7WMFC6F7.js").then(({ reloadModelManager: reloadModelManager2 }) => {
           reloadModelManager2();
           triggerModelConfigChange();
           onDone();
@@ -27233,25 +26843,10 @@ function getListNumber(listDepth, orderedListNumber) {
   }
 }
 
-// src/tools/ai/AskExpertModelTool/AskExpertModelTool.tsx
-var inputSchema9 = z11.strictObject({
-  question: z11.string().describe(
-    "COMPLETE SELF-CONTAINED QUESTION: Must include full background context, relevant details, and a clear independent question. The expert model will receive ONLY this content with no access to previous conversation or external context. Structure as: 1) Background/Context 2) Specific situation/problem 3) Clear question. Ensure the expert can fully understand and respond without needing additional information."
-  ),
-  expert_model: z11.string().describe(
-    "The expert model to use (e.g., gpt-5, claude-3-5-sonnet-20241022)"
-  ),
-  chat_session_id: z11.string().describe(
-    'Chat session ID: use "new" for new session or existing session ID'
-  )
-});
-var AskExpertModelTool = {
-  name: "AskExpertModel",
-  async description() {
-    return "Consult external AI models for expert opinions and analysis";
-  },
-  async prompt() {
-    return `Ask a question to a specific external AI model for expert analysis.
+// src/tools/ai/AskExpertModelTool/prompt.ts
+var TOOL_NAME12 = "AskExpertModel";
+var DESCRIPTION8 = "Consult external AI models for expert opinions and analysis";
+var PROMPT7 = `Ask a question to a specific external AI model for expert analysis.
 
 This tool allows you to consult different AI models for their unique perspectives and expertise.
 
@@ -27262,7 +26857,7 @@ The question MUST be completely self-contained and include:
 3. INDEPENDENT QUESTION - What exactly you want the expert to analyze/answer
 
 The expert model receives ONLY your question content with NO access to:
-- Previous conversation history (unless using existing session)  
+- Previous conversation history (unless using existing session)
 - Current codebase or file context
 - User's current task or project details
 
@@ -27273,7 +26868,7 @@ IMPORTANT: This tool is for asking questions to models, not for task execution.
 
 The expert_model parameter accepts:
 - OpenAI: gpt-4, gpt-5, o1-preview
-- Messages API: claude-3-5-sonnet, claude-3-opus  
+- Messages API: claude-3-5-sonnet, claude-3-opus
 - Others: kimi, gemini-pro, mixtral
 
 Example of well-structured question:
@@ -27282,6 +26877,26 @@ Example of well-structured question:
 Current situation: Users report 3-5 second delays when scrolling through the list. The component re-renders the entire list on every state change.
 
 Question: What are the most effective React optimization techniques for handling large lists, and how should I prioritize implementing virtualization vs memoization vs other approaches?"`;
+
+// src/tools/ai/AskExpertModelTool/AskExpertModelTool.tsx
+var inputSchema9 = z11.strictObject({
+  question: z11.string().describe(
+    "COMPLETE SELF-CONTAINED QUESTION: Must include full background context, relevant details, and a clear independent question. The expert model will receive ONLY this content with no access to previous conversation or external context. Structure as: 1) Background/Context 2) Specific situation/problem 3) Clear question. Ensure the expert can fully understand and respond without needing additional information."
+  ),
+  expert_model: z11.string().describe(
+    "The expert model to use (e.g., gpt-5, claude-3-5-sonnet-20241022)"
+  ),
+  chat_session_id: z11.string().describe(
+    'Chat session ID: use "new" for new session or existing session ID'
+  )
+});
+var AskExpertModelTool = {
+  name: TOOL_NAME12,
+  async description() {
+    return DESCRIPTION8;
+  },
+  async prompt() {
+    return PROMPT7;
   },
   isReadOnly() {
     return true;
@@ -27629,9 +27244,9 @@ import { z as z12 } from "zod";
 var BLACK_CIRCLE = env.platform === "macos" ? "\u23FA" : "\u25CF";
 
 // src/tools/interaction/AskUserQuestionTool/prompt.ts
-var TOOL_NAME_FOR_PROMPT5 = "AskUserQuestion";
-var DESCRIPTION6 = "Asks the user multiple choice questions to gather information, clarify ambiguity, understand preferences, make decisions or offer them choices.";
-var PROMPT6 = `Use this tool when you need to ask the user questions during execution. This allows you to:
+var TOOL_NAME13 = "AskUserQuestion";
+var DESCRIPTION9 = "Asks the user multiple choice questions to gather information, clarify ambiguity, understand preferences, make decisions or offer them choices.";
+var PROMPT8 = `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
@@ -27671,9 +27286,9 @@ var inputSchema10 = z12.strictObject({
   }
 );
 var AskUserQuestionTool = {
-  name: TOOL_NAME_FOR_PROMPT5,
+  name: TOOL_NAME13,
   async description() {
-    return DESCRIPTION6;
+    return DESCRIPTION9;
   },
   userFacingName() {
     return "";
@@ -27695,7 +27310,7 @@ var AskUserQuestionTool = {
     return true;
   },
   async prompt() {
-    return PROMPT6;
+    return PROMPT8;
   },
   renderToolUseMessage() {
     return null;
@@ -27840,9 +27455,9 @@ function maybeTruncateVerboseToolOutput(text, options) {
 }
 
 // src/tools/system/TaskOutputTool/prompt.ts
-var TOOL_NAME_FOR_PROMPT6 = "TaskOutput";
-var DESCRIPTION7 = "Retrieves output from a running or completed task";
-var PROMPT7 = `- Retrieves output from a running or completed task (background shell, agent, or remote session)
+var TOOL_NAME14 = "TaskOutput";
+var DESCRIPTION10 = "Retrieves output from a running or completed task";
+var PROMPT9 = `- Retrieves output from a running or completed task (background shell, agent, or remote session)
 - Takes a task_id parameter identifying the task
 - Returns the task output along with status information
 - Use block=true (default) to wait for task completion
@@ -27968,7 +27583,7 @@ async function analyzeOutputWithLsp(output, exitCode) {
   if (exitCode !== 0 || errorCount > 0 || warningCount > 0) {
     try {
       const { isAbsolute: isAbsolute11, resolve: resolve16 } = await import("path");
-      const { getSessionRoot: getSessionRoot2 } = await import("./state-MDP57623.js");
+      const { getSessionRoot: getSessionRoot2 } = await import("./state-NZVNNCHH.js");
       const lines = output.split("\n");
       const uniqueFiles = /* @__PURE__ */ new Set();
       const lspSuggestions = [];
@@ -28055,9 +27670,9 @@ async function waitForBashTaskCompletion(args) {
   return buildTaskSummary(taskId);
 }
 var TaskOutputTool = {
-  name: TOOL_NAME_FOR_PROMPT6,
+  name: TOOL_NAME14,
   async description() {
-    return DESCRIPTION7;
+    return DESCRIPTION10;
   },
   userFacingName() {
     return "Task Output";
@@ -28076,7 +27691,7 @@ var TaskOutputTool = {
     return false;
   },
   async prompt() {
-    return PROMPT7;
+    return PROMPT9;
   },
   renderToolUseMessage(input) {
     const normalized = normalizeTaskOutputInput(input);
@@ -28243,7 +27858,8 @@ import { z as z14 } from "zod";
 import { isAbsolute as isAbsolute9, relative as relative11, resolve as resolve10 } from "path";
 
 // src/tools/filesystem/DeleteTool/prompt.ts
-var PROMPT8 = `You can use this tool to delete files (regular file or directory), you can delete multi files in one toolcall, and you MUST make sure the files is exist before deleting.
+var TOOL_NAME15 = "Delete";
+var PROMPT10 = `You can use this tool to delete files (regular file or directory), you can delete multi files in one toolcall, and you MUST make sure the files is exist before deleting.
 When you need to delete file, you MUST use this tool to delete file instead of using shell.
 
 Usage:
@@ -28314,13 +27930,13 @@ var inputSchema12 = z14.strictObject({
   )
 });
 var DeleteTool = {
-  name: "Delete",
+  name: TOOL_NAME15,
   async description() {
     return "Use this tool to delete files or directories. ALWAYS use this tool instead of running shell commands (like 'rm', 'del') to ensure cross-platform compatibility and safety. Supports deleting multiple paths at once.";
   },
   userFacingName: () => "Delete",
   async prompt() {
-    return PROMPT8;
+    return PROMPT10;
   },
   inputSchema: inputSchema12,
   async isEnabled() {
@@ -28369,7 +27985,7 @@ var DeleteTool = {
         }
         if (!force) {
           try {
-            const { LspFacade: LspFacade2 } = await import("./lsp-WIEWEHYU.js");
+            const { LspFacade: LspFacade2 } = await import("./lsp-OKPL75YW.js");
             const referenceDetail = await LspFacade2.checkFileReferences(fullPath);
             if (referenceDetail) {
               failedItems.push(
@@ -28432,9 +28048,9 @@ import React51 from "react";
 import { z as z15 } from "zod";
 
 // src/tools/system/KillShellTool/prompt.ts
-var TOOL_NAME_FOR_PROMPT7 = "KillShell";
-var DESCRIPTION8 = "Kill a background bash shell by ID";
-var PROMPT9 = `
+var TOOL_NAME16 = "KillShell";
+var DESCRIPTION11 = "Kill a background bash shell by ID";
+var PROMPT11 = `
 - Kills a running background bash shell by its ID
 - Takes a shell_id parameter identifying the shell to kill
 - Returns a success or failure status 
@@ -28447,9 +28063,9 @@ var inputSchema13 = z15.strictObject({
   shell_id: z15.string().describe("The ID of the background shell to kill")
 });
 var KillShellTool = {
-  name: TOOL_NAME_FOR_PROMPT7,
+  name: TOOL_NAME16,
   async description() {
-    return DESCRIPTION8;
+    return DESCRIPTION11;
   },
   userFacingName() {
     return "Kill Shell";
@@ -28468,7 +28084,7 @@ var KillShellTool = {
     return false;
   },
   async prompt() {
-    return PROMPT9;
+    return PROMPT11;
   },
   renderToolUseMessage({ shell_id }) {
     return `Kill shell: ${shell_id}`;
@@ -28524,14 +28140,14 @@ import { z as z16 } from "zod";
 import { ListResourcesResultSchema } from "@modelcontextprotocol/sdk/types.js";
 
 // src/tools/mcp/ListMcpResourcesTool/prompt.ts
-var TOOL_NAME = "ListMcpResourcesTool";
-var DESCRIPTION9 = `Lists available resources from configured MCP servers.
+var TOOL_NAME17 = "ListMcpResourcesTool";
+var DESCRIPTION12 = `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: \`listMcpResources\`
 - List resources from a specific server: \`listMcpResources({ server: "myserver" })\``;
-var PROMPT10 = `List available resources from configured MCP servers.
+var PROMPT12 = `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.
 
@@ -28544,12 +28160,12 @@ var inputSchema14 = z16.strictObject({
   server: z16.string().optional().describe("Optional server name to filter resources by")
 });
 var ListMcpResourcesTool = {
-  name: TOOL_NAME,
+  name: TOOL_NAME17,
   async description() {
-    return DESCRIPTION9;
+    return DESCRIPTION12;
   },
   async prompt() {
-    return PROMPT10;
+    return PROMPT12;
   },
   inputSchema: inputSchema14,
   userFacingName() {
@@ -28641,138 +28257,6 @@ import { Box as Box42, Text as Text46 } from "ink";
 import { relative as relative12, resolve as resolve11 } from "path";
 import React53 from "react";
 import { z as z17 } from "zod";
-
-// src/tools/search/LspTool/prompt.ts
-var TOOL_NAME_FOR_PROMPT8 = "LSP";
-var PROMPT11 = `Interact with Language Server Protocol (LSP) servers to get code intelligence features.Supports all languages.
-
-## Capabilities & Scenarios
-This tool acts as your "Code Analyst". Use it to understand the codebase semantically, rather than just matching text.
-
-### 1. Tracing Logic (Where does this go?)
-- **Scenario**: You see a function call \`calculateTax(amount)\` and need to know its formula.
-- **Action**: Use \`goToDefinition\` on the function name.
-- **Why**: It jumps directly to the implementation, even if it's imported from another file.
-
-### 2. Impact Analysis (What uses this?)
-- **Scenario**: You are planning to rename or modify the \`User\` class.
-- **Action**: Use \`findReferences\` at the symbol position (line + character) in the file where \`User\` is declared or used.
-- **Why**: It lists every file and line where \`User\` is referenced, ensuring you don't break dependents.
-
-### 3. Exploring New Files (What's in here?)
-- **Scenario**: You just opened a large file \`utils.ts\` and want a quick overview.
-- **Action**: Use \`documentSymbol\`.
-- **Why**: It returns a structured outline (Classes, Functions, Variables) using LspFacade policy: LSP-first for accuracy, Tree-Sitter fallback for speed when needed.
-
-### 4. Interface Implementation (Who implements this?)
-- **Scenario**: You see an interface \`IStorage\` and want to find the concrete class (e.g., \`S3Storage\`).
-- **Action**: Use \`goToImplementation\`.
-- **Why**: Grep might just find the import; LSP finds the actual code that implements the interface.
-
-### 5. Scope Analysis (What is visible here?)
-- **Scenario**: You are debugging a closure or nested function and want to know which variables are captured or locally defined.
-- **Action**: Use \`getScope\`.
-- **Why**: It returns the local variables and closure captures at the current position. Essential for debugging Python closures or JavaScript lexical scopes.
-
-### 6. Real-time Diagnostics (Is this correct?)
-- **Scenario**: You just edited a file and want to verify if you introduced any syntax errors.
-- **Action**: Use \`diagnostics\` with \`waitForDiagnostics: true\`.
-- **Why**: It waits for the language server to re-analyze the file and returns fresh errors/warnings. This is your "Self-Correction" mechanism.
-
-### 7. Workspace Symbol Search (Where is this symbol?)
-- **Scenario**: You need to find a class or function across the entire project.
-- **Action**: Use \`workspaceSymbol\` with a query string and a scoped filePath (module or directory).
-- **Why**: It searches across all files in the scope. **Important**: Must provide a scoped path to avoid unbounded full-repo queries.
-
-## Supported Operations
-
-### Location-Based Operations (require line + character)
-These 8 operations require precise symbol position:
-- \`goToDefinition\`: Find where a symbol is defined
-- \`findReferences\`: Find all references to a symbol
-- \`hover\`: Get hover information (documentation, type info) for a symbol
-- \`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
-- \`getScope\`: Get local variables and closure captures at a position
-
-### Document-Level Operations (no position required)
-- \`documentSymbol\`: Get all symbols (functions, classes, variables) in a document
-- \`diagnostics\`: Get validation errors and warnings for a file (supports waiting for fresh results)
-
-### Workspace-Level Operations
-- \`workspaceSymbol\`: Search for symbols across the entire workspace (requires query + scoped filePath)
-
-## Parameters
-
-All operations require:
-- \`filePath\`: The file or directory to operate on
-
-Location-based operations require:
-- \`line\`: The line number (1-based, as shown in editors)
-- \`character\`: The character offset (1-based, as shown in editors)
-
-\`workspaceSymbol\` requires:
-- \`query\`: The symbol name or keyword to search for
-
-Optional:
-- \`waitForDiagnostics\`: If true, wait for fresh diagnostics (used with "diagnostics" operation)
-- \`timeout\`: Timeout in milliseconds for waiting operations (default: 5000)
-
-## Intelligent Position Handling
-
-**Do not pass a symbol name.** LSPTool works on positions, not names. Use Read to locate the symbol and derive line + character first.
-
-### Auto-Adjustment Mechanism
-If the specified position is not on a valid symbol, the tool automatically searches for the nearest valid token:
-- **Search scope**: Current line, then previous line, then next line
-- **Priority**: Current line tokens are preferred (lower score)
-- **Skipped tokens**: Keywords (function, class, if, for, return, etc.) and operators (=, =>, +, -, &&, ||, etc.) are automatically skipped
-- **If no valid token found**: Returns an error message
-
-### Best Practice for Position
-1. Use Read to open the file and locate the symbol
-2. Provide accurate 1-based line and character offset
-3. Position should be on the symbol name itself, not on keywords/operators
-4. If unsure, position at the start of the symbol name
-
-## Workflow & Scope Guidelines
-- **Priority order**: documentSymbol \u2192 hotspot detection \u2192 Read \u2192 LSP (ensure line + character)
-- **workspaceSymbol**: Must provide scoped filePath (module or directory), avoid unbounded full-repo queries
-- **documentSymbol**: Uses LspFacade policy (LSP-first for accuracy, Tree-Sitter fallback for speed)
-
-## Typical Usage Examples
-### Example 1: Find Symbol Then Read Precise Block
-<example>
-user: Locate JWT validation implementation quickly
-assistant: [uses LSP workspaceSymbol with query="jwt validate" and scoped filePath]
-[uses Read on the discovered file and then LSP documentSymbol/definition as needed]
-<reasoning>
-The assistant starts semantically because:
-1. User asks for implementation location, not broad text grep
-2. workspaceSymbol narrows candidate files efficiently
-3. Read is then used for exact code extraction once target is known
-</reasoning>
-</example>
-
-### Example 2: Diagnostics-First Debugging
-<example>
-user: Build failed in api package, tell me real code errors
-assistant: [uses LSP diagnostics with waitForDiagnostics=true on scoped filePath]
-[uses goToDefinition/findReferences for follow-up impact tracing]
-<reasoning>
-The assistant prioritizes diagnostics because:
-1. Diagnostics provide direct semantic errors from language tooling
-2. Scoped path avoids unbounded workspace queries
-3. Follow-up LSP ops can trace root-cause dependencies
-</reasoning>
-</example>
-
-Note: LSP servers are automatically managed and installed for most languages. For system-level languages (like C++, Java), ensure the corresponding tools (clangd, jdtls) are in your PATH.`;
-var DESCRIPTION10 = PROMPT11;
-
-// src/tools/search/LspTool/LspTool.tsx
 var inputSchema15 = z17.strictObject({
   operation: z17.enum([
     "goToDefinition",
@@ -29021,12 +28505,12 @@ function summarizeToolResult(operation, resultCount, fileCount) {
   return /* @__PURE__ */ React53.createElement(Text46, null, "Found ", /* @__PURE__ */ React53.createElement(Text46, { bold: true }, resultCount), " ", noun, fileCount > 1 ? /* @__PURE__ */ React53.createElement(React53.Fragment, null, " ", "across ", /* @__PURE__ */ React53.createElement(Text46, { bold: true }, fileCount), " files") : null);
 }
 var LspTool = {
-  name: TOOL_NAME_FOR_PROMPT8,
+  name: TOOL_NAME6,
   async description() {
-    return DESCRIPTION10;
+    return DESCRIPTION6;
   },
   async prompt() {
-    return PROMPT11;
+    return PROMPT3;
   },
   inputSchema: inputSchema15,
   userFacingName() {
@@ -29238,14 +28722,14 @@ import { z as z18 } from "zod";
 import { ReadResourceResultSchema } from "@modelcontextprotocol/sdk/types.js";
 
 // src/tools/mcp/ReadMcpResourceTool/prompt.ts
-var TOOL_NAME2 = "ReadMcpResourceTool";
-var DESCRIPTION11 = `Reads a specific resource from an MCP server.
+var TOOL_NAME18 = "ReadMcpResourceTool";
+var DESCRIPTION13 = `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: \`readMcpResource({ server: "myserver", uri: "my-resource-uri" })\``;
-var PROMPT12 = `Reads a specific resource from an MCP server, identified by server name and resource URI.
+var PROMPT13 = `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
@@ -29257,12 +28741,12 @@ var inputSchema16 = z18.strictObject({
   uri: z18.string().describe("The resource URI to read")
 });
 var ReadMcpResourceTool = {
-  name: TOOL_NAME2,
+  name: TOOL_NAME18,
   async description() {
-    return DESCRIPTION11;
+    return DESCRIPTION13;
   },
   async prompt() {
-    return PROMPT12;
+    return PROMPT13;
   },
   inputSchema: inputSchema16,
   userFacingName() {
@@ -29367,7 +28851,7 @@ import { z as z19 } from "zod";
 import * as React55 from "react";
 
 // src/tools/ai/SkillTool/prompt.ts
-var TOOL_NAME_FOR_PROMPT9 = "Skill";
+var TOOL_NAME19 = "Skill";
 
 // src/tools/ai/SkillTool/SkillTool.tsx
 var inputSchema17 = z19.strictObject({
@@ -29386,7 +28870,7 @@ function normalizeCommandModelName(model) {
   return trimmed;
 }
 var SkillTool = {
-  name: TOOL_NAME_FOR_PROMPT9,
+  name: TOOL_NAME19,
   async description({ skill }) {
     return `Execute skill: ${skill}`;
   },
@@ -29488,7 +28972,7 @@ ${availableSkills}${truncatedNotice}
     if (cmd.disableModelInvocation) {
       return {
         result: false,
-        message: `Skill ${skillName} cannot be used with ${TOOL_NAME_FOR_PROMPT9} tool due to disable-model-invocation`,
+        message: `Skill ${skillName} cannot be used with ${TOOL_NAME19} tool due to disable-model-invocation`,
         errorCode: 4
       };
     }
@@ -29511,7 +28995,7 @@ ${availableSkills}${truncatedNotice}
     }
     if (cmd.disableModelInvocation) {
       throw new Error(
-        `Skill ${skillName} cannot be used with ${TOOL_NAME_FOR_PROMPT9} tool due to disable-model-invocation`
+        `Skill ${skillName} cannot be used with ${TOOL_NAME19} tool due to disable-model-invocation`
       );
     }
     if (cmd.type !== "prompt") {
@@ -29758,9 +29242,6 @@ assistant: "I'm going to use the Task tool to launch the with the greeting-respo
 </example>`;
 }
 
-// src/tools/agent/TaskTool/constants.ts
-var TOOL_NAME3 = "Task";
-
 // src/tools/agent/TaskTool/TaskTool.tsx
 var inputSchema18 = z20.object({
   description: z20.string().describe("A short (3-5 word) description of the task"),
@@ -29921,7 +29402,7 @@ function buildForkContextForAgent(options) {
   };
 }
 var TaskTool = {
-  name: TOOL_NAME3,
+  name: TOOL_NAME7,
   inputSchema: inputSchema18,
   async description() {
     return "Delegate complex, multi-step work to specialized agents";
@@ -30387,8 +29868,9 @@ function createTaskToolError(params) {
 }
 
 // src/tools/interaction/TaskCreateTool/prompt.ts
-var DESCRIPTION12 = "Plan and create tasks for complex multi-step work";
-var PROMPT13 = `Use this tool to create a new task in the current task list. It is the entry point for planning multi-step work.
+var TOOL_NAME20 = "TaskCreate";
+var DESCRIPTION14 = "Plan and create tasks for complex multi-step work";
+var PROMPT14 = `Use this tool to create a new task in the current task list. It is the entry point for planning multi-step work.
 
 ## When to Use This Tool
 
@@ -30749,13 +30231,13 @@ var inputSchema19 = z22.strictObject({
   metadata: metadataSchema.optional()
 });
 var TaskCreateTool = {
-  name: "TaskCreate",
-  cachedDescription: DESCRIPTION12,
+  name: TOOL_NAME20,
+  cachedDescription: DESCRIPTION14,
   async description() {
-    return DESCRIPTION12;
+    return DESCRIPTION14;
   },
   async prompt() {
-    return PROMPT13;
+    return PROMPT14;
   },
   inputSchema: inputSchema19,
   userFacingName() {
@@ -30825,8 +30307,9 @@ var TaskCreateTool = {
 import { z as z23 } from "zod";
 
 // src/tools/interaction/TaskGetTool/prompt.ts
-var DESCRIPTION13 = "Review planned task details";
-var PROMPT14 = `Use this tool to fetch a single task by id.
+var TOOL_NAME21 = "TaskGet";
+var DESCRIPTION15 = "Review planned task details";
+var PROMPT15 = `Use this tool to fetch a single task by id.
 
 ## When to Use This Tool
 Use this tool proactively in these scenarios:
@@ -30862,13 +30345,13 @@ var inputSchema20 = z23.strictObject({
   taskId: z23.string().min(1)
 });
 var TaskGetTool = {
-  name: "TaskGet",
-  cachedDescription: DESCRIPTION13,
+  name: TOOL_NAME21,
+  cachedDescription: DESCRIPTION15,
   async description() {
-    return DESCRIPTION13;
+    return DESCRIPTION15;
   },
   async prompt() {
-    return PROMPT14;
+    return PROMPT15;
   },
   inputSchema: inputSchema20,
   userFacingName() {
@@ -30924,8 +30407,9 @@ var TaskGetTool = {
 import { z as z24 } from "zod";
 
 // src/tools/interaction/TaskListTool/prompt.ts
-var DESCRIPTION14 = "Review planned tasks, readiness, and blockers";
-var PROMPT15 = `Use this tool to list tasks and understand readiness. It returns ready and blocked groupings to help prioritize work. TaskList only returns id/subject/status/blockedBy for summaries; use TaskGet for details.
+var TOOL_NAME22 = "TaskList";
+var DESCRIPTION16 = "Review planned tasks, readiness, and blockers";
+var PROMPT16 = `Use this tool to list tasks and understand readiness. It returns ready and blocked groupings to help prioritize work. TaskList only returns id/subject/status/blockedBy for summaries; use TaskGet for details.
 
 ## When to Use This Tool
 Use this tool proactively in these scenarios:
@@ -31005,13 +30489,13 @@ var getActiveBlockers = (task, tasksById) => {
   return active2;
 };
 var TaskListTool = {
-  name: "TaskList",
-  cachedDescription: DESCRIPTION14,
+  name: TOOL_NAME22,
+  cachedDescription: DESCRIPTION16,
   async description() {
-    return DESCRIPTION14;
+    return DESCRIPTION16;
   },
   async prompt() {
-    return PROMPT15;
+    return PROMPT16;
   },
   inputSchema: inputSchema21,
   userFacingName() {
@@ -31077,8 +30561,9 @@ var TaskListTool = {
 import { z as z25 } from "zod";
 
 // src/tools/interaction/TaskUpdateTool/prompt.ts
-var DESCRIPTION15 = "Manage task progress, status, and dependencies";
-var PROMPT16 = `Use this tool to update an existing task. It is the primary way to track progress and adjust task details.
+var TOOL_NAME23 = "TaskUpdate";
+var DESCRIPTION17 = "Manage task progress, status, and dependencies";
+var PROMPT17 = `Use this tool to update an existing task. It is the primary way to track progress and adjust task details.
 
 ## When to Use This Tool
 Use this tool proactively in these scenarios:
@@ -31529,13 +31014,13 @@ var inputSchema22 = z25.strictObject({
   addBlocks: z25.array(z25.string()).optional()
 });
 var TaskUpdateTool = {
-  name: "TaskUpdate",
-  cachedDescription: DESCRIPTION15,
+  name: TOOL_NAME23,
+  cachedDescription: DESCRIPTION17,
   async description() {
-    return DESCRIPTION15;
+    return DESCRIPTION17;
   },
   async prompt() {
-    return PROMPT16;
+    return PROMPT17;
   },
   inputSchema: inputSchema22,
   userFacingName() {
@@ -31804,8 +31289,9 @@ import * as React57 from "react";
 import { z as z26 } from "zod";
 
 // src/tools/memory/MemoryReadTool/prompt.ts
-var DESCRIPTION16 = "Read agent memory files from the local filesystem.";
-var PROMPT17 = `Reads agent memory files from the local filesystem.
+var TOOL_NAME24 = "MemoryRead";
+var DESCRIPTION18 = "Read agent memory files from the local filesystem.";
+var PROMPT18 = `Reads agent memory files from the local filesystem.
 
 Usage:
 - The file_path parameter must be a path relative to the agent's memory directory
@@ -31828,12 +31314,12 @@ var inputSchema23 = z26.strictObject({
   file_path: z26.string().optional().describe("Optional path to a specific memory file to read")
 });
 var MemoryReadTool = {
-  name: "MemoryRead",
+  name: TOOL_NAME24,
   async description() {
-    return DESCRIPTION16;
+    return DESCRIPTION18;
   },
   async prompt() {
-    return PROMPT17;
+    return PROMPT18;
   },
   inputSchema: inputSchema23,
   userFacingName() {
@@ -31981,8 +31467,9 @@ function writeMemoryFile(input, deps) {
 }
 
 // src/tools/memory/MemoryWriteTool/prompt.ts
-var DESCRIPTION17 = "Write agent memory files to the local filesystem.";
-var PROMPT18 = `Write agent memory files to the local filesystem.
+var TOOL_NAME25 = "MemoryWrite";
+var DESCRIPTION19 = "Write agent memory files to the local filesystem.";
+var PROMPT19 = `Write agent memory files to the local filesystem.
 
 Usage:
 - The file_path parameter is required and specifies the memory file to write
@@ -32015,12 +31502,12 @@ var inputSchema24 = z27.strictObject({
   mode: z27.enum(["append", "replace"]).optional().describe("Write mode: append adds to existing content, replace overwrites")
 });
 var MemoryWriteTool = {
-  name: "MemoryWrite",
+  name: TOOL_NAME25,
   async description() {
-    return DESCRIPTION17;
+    return DESCRIPTION19;
   },
   async prompt() {
-    return PROMPT18;
+    return PROMPT19;
   },
   inputSchema: inputSchema24,
   userFacingName() {
@@ -38810,7 +38297,7 @@ function useStatusLine() {
 // src/ui/components/PromptInput.tsx
 async function interpretHashCommand(input) {
   try {
-    const { queryQuick: queryQuick2 } = await import("./llm-QPAHJ643.js");
+    const { queryQuick: queryQuick2 } = await import("./llm-KXF74SNS.js");
     const systemPrompt = [
       "You're helping the user structure notes that will be added to their PYB.md file.",
       "Format the user's input into a well-structured note that will be useful for later reference.",
@@ -39123,7 +38610,7 @@ function PromptInput({
     if (messages2.length) {
       if (mode === "bash") {
         onQuery(messages2, newAbortController).then(async () => {
-          const { getCwd: getCwd2 } = await import("./state-MDP57623.js");
+          const { getCwd: getCwd2 } = await import("./state-NZVNNCHH.js");
           setCurrentPwd(getCwd2());
         });
       } else {
@@ -40753,7 +40240,7 @@ import { homedir as homedir8 } from "os";
 // src/commands/agents/generation.ts
 import { randomUUID as randomUUID9 } from "crypto";
 async function generateAgentWithClaude(prompt) {
-  const { queryModel } = await import("./llm-QPAHJ643.js");
+  const { queryModel } = await import("./llm-KXF74SNS.js");
   const systemPrompt = `You are an expert at creating AI agent configurations. Based on the user's description, generate a specialized agent configuration.
 
 Return your response as a JSON object with exactly these fields:
@@ -42433,7 +41920,7 @@ function getCommand(commandName, commands) {
 }
 
 // src/tools/interaction/SlashCommandTool/prompt.ts
-var TOOL_NAME_FOR_PROMPT10 = "SlashCommand";
+var TOOL_NAME26 = "SlashCommand";
 
 // src/tools/interaction/SlashCommandTool/SlashCommandTool.tsx
 var inputSchema26 = z28.strictObject({
@@ -42455,7 +41942,7 @@ function getCharBudget() {
   return Number.isFinite(raw) && raw > 0 ? raw : 15e3;
 }
 var SlashCommandTool = {
-  name: TOOL_NAME_FOR_PROMPT10,
+  name: TOOL_NAME26,
   async description({ command: command4 }) {
     return `Execute slash command: ${command4}`;
   },
@@ -42551,14 +42038,14 @@ ${availableLines}${truncatedNotice}
     if (cmd.disableModelInvocation) {
       return {
         result: false,
-        message: `Slash command ${parsed.commandName} cannot be used with ${TOOL_NAME_FOR_PROMPT10} tool due to disable-model-invocation`,
+        message: `Slash command ${parsed.commandName} cannot be used with ${TOOL_NAME26} tool due to disable-model-invocation`,
         errorCode: 4
       };
     }
     if (cmd.disableNonInteractive) {
       return {
         result: false,
-        message: `Slash command ${parsed.commandName} cannot be used with ${TOOL_NAME_FOR_PROMPT10} tool because it is non-interactive`,
+        message: `Slash command ${parsed.commandName} cannot be used with ${TOOL_NAME26} tool because it is non-interactive`,
         errorCode: 6
       };
     }
@@ -42583,12 +42070,12 @@ ${availableLines}${truncatedNotice}
     }
     if (cmd.disableModelInvocation) {
       throw new Error(
-        `Slash command ${parsed.commandName} cannot be used with ${TOOL_NAME_FOR_PROMPT10} tool due to disable-model-invocation`
+        `Slash command ${parsed.commandName} cannot be used with ${TOOL_NAME26} tool due to disable-model-invocation`
       );
     }
     if (cmd.disableNonInteractive) {
       throw new Error(
-        `Slash command ${parsed.commandName} cannot be used with ${TOOL_NAME_FOR_PROMPT10} tool because it is non-interactive`
+        `Slash command ${parsed.commandName} cannot be used with ${TOOL_NAME26} tool because it is non-interactive`
       );
     }
     if (cmd.type !== "prompt") {
@@ -43621,7 +43108,7 @@ Output: Create directory 'foo'`
   )
 });
 var BashTool = {
-  name: "Bash",
+  name: TOOL_NAME8,
   cachedDescription: "Run shell command",
   async description(input) {
     return input?.description || await getBashToolPrompt();
@@ -44273,12 +43760,12 @@ Task records use subject as the single primary name, with activeForm provided by
 It is critical that you mark tasks as completed as soon as you are done with a task. Do not batch up multiple tasks before marking them as completed.
 
 # Cognitive Safety & Sensing
-1. **Modification Check**: Before editing, you MUST verify if the change is already present (e.g. use \`grep\` or \`read\`). Do not rely on memory from previous turns.
+1. **Modification Check**: Before editing, you MUST verify if the change is already present (e.g. use \`Grep\` or \`Read\`). Do not rely on memory from previous turns.
 2. **Precise Targeting**: For code injection, prefer using LSP to find exact function boundaries, or Read the file to get unique context.
-3. **Artifact Verification**: After completing a complex task, verify the artifacts (e.g. check if files exist using \`glob\`).
-4. **LSP Instinct**: Before modifying any code, you MUST first build structure context (structure tree \u2192 hotspot \u2192 Read). Use \`LSP documentSymbol\` or \`LSP goToDefinition\` only when you have a precise position and need to confirm exact range. Do NOT rely on line numbers from \`read_file\` alone as they may be outdated.
+3. **Artifact Verification**: After completing a complex task, verify the artifacts (e.g. check if files exist using \`Glob\`).
+4. **LSP Instinct**: Before modifying any code, you MUST first build structure context (structure tree \u2192 hotspot \u2192 Read). Use \`LSP documentSymbol\` or \`LSP goToDefinition\` only when you have a precise position and need to confirm exact range. Do NOT rely on line numbers from \`Read\` alone as they may be outdated.
 5. **Atomic Verification**: When editing code, especially in critical or complex files, you should strongly consider setting \`verify: true\` in the \`FileEditTool\`. This enables the tool to automatically detect syntax errors and ROLLBACK changes if they are invalid, preventing you from breaking the build.
-6. **Semantic Search**: When searching for code concepts (e.g. "AuthLogic", "UserHandler") rather than exact filenames, prefer using \`GlobTool\` with \`semantic: true\`. This leverages LSP to find files by their content definitions.
+6. **Semantic Search**: When searching for code concepts (e.g. "AuthLogic", "UserHandler") rather than exact filenames, prefer using \`Glob\` with \`semantic: true\`. This leverages LSP to find files by their content definitions.
 7. **Reference Guard**: Be aware that deleting files might be blocked if they are referenced elsewhere. If the \`DeleteTool\` blocks you, check the references it reports. Only use \`force: true\` if you are refactoring and intentionally removing those references.
 
 # Memory