cx-viewer 1.0.3 → 1.0.4

package/concepts/de/Tool-WebSearch.md

@@ -1,58 +0,0 @@
-# WebSearch
-
-## Definition
-
-Führt eine Suchmaschinenabfrage durch und gibt Suchergebnisse zurück, um aktuelle Informationen zu erhalten.
-
-## Parameter
-
-| Parameter | Typ | Erforderlich | Beschreibung |
-|-----------|-----|--------------|--------------|
-| `query` | string | Ja | Suchanfrage (mindestens 2 Zeichen) |
-| `allowed_domains` | string[] | Nein | Nur Ergebnisse von diesen Domains einschließen |
-| `blocked_domains` | string[] | Nein | Ergebnisse von diesen Domains ausschließen |
-
-## Anwendungsfälle
-
-**Geeignet für:**
-- Aktuelle Informationen abrufen, die über den Wissensstand des Modells hinausgehen
-- Aktuelle Ereignisse und neueste Daten finden
-- Neueste technische Dokumentation suchen
-
-## Hinweise
-
-- Suchergebnisse werden im Markdown-Hyperlink-Format zurückgegeben
-- Nach der Verwendung muss am Ende der Antwort ein "Sources:"-Abschnitt mit den relevanten URLs angefügt werden
-- Unterstützt Domain-Filterung (einschließen/ausschließen)
-- In Suchanfragen sollte das aktuelle Jahr verwendet werden
-- Nur in den USA verfügbar
-
-## Originaltext
-
-<textarea readonly>
-- Allows Claude 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
-- Use this tool for accessing information beyond Claude's knowledge cutoff
-- Searches are performed automatically within a single API call
-
-CRITICAL REQUIREMENT - You MUST follow this:
-  - After answering the user's question, you MUST include a "Sources:" section at the end of your response
-  - In the Sources section, list all relevant URLs from the search results as markdown hyperlinks: [Title](URL)
-  - This is MANDATORY - never skip including sources in your response
-  - Example format:
-
-    [Your answer here]
-
-    Sources:
-    - [Source Title 1](https://example.com/1)
-    - [Source Title 2](https://example.com/2)
-
-Usage notes:
-  - Domain filtering is supported to include or block specific websites
-  - Web search is only available in the US
-
-IMPORTANT - Use the correct year in search queries:
-  - The current month is March 2026. You MUST use this year when searching for recent information, documentation, or current events.
-  - Example: If the user asks for "latest React docs", search for "React documentation" with the current year, NOT last year
-</textarea>

package/concepts/de/Tool-Write.md

@@ -1,39 +0,0 @@
-# Write
-
-## Definition
-
-Schreibt Inhalte in das lokale Dateisystem. Überschreibt die Datei, falls sie bereits existiert.
-
-## Parameter
-
-| Parameter | Typ | Erforderlich | Beschreibung |
-|-----------|-----|--------------|--------------|
-| `file_path` | string | Ja | Absoluter Pfad der Datei (muss ein absoluter Pfad sein) |
-| `content` | string | Ja | Der zu schreibende Inhalt |
-
-## Anwendungsfälle
-
-**Geeignet für:**
-- Neue Dateien erstellen
-- Wenn der Dateiinhalt vollständig neu geschrieben werden muss
-
-**Nicht geeignet für:**
-- Teilinhalte einer Datei ändern – dafür Edit verwenden
-- Nicht proaktiv Dokumentationsdateien (*.md) oder READMEs erstellen, es sei denn, der Benutzer fordert es ausdrücklich an
-
-## Hinweise
-
-- Wenn die Zieldatei bereits existiert, muss sie zuerst über Read gelesen werden, sonst schlägt der Vorgang fehl
-- Überschreibt den gesamten Inhalt einer vorhandenen Datei
-- Edit zum Bearbeiten vorhandener Dateien bevorzugen; Write nur für neue Dateien oder vollständige Neuschreibungen verwenden
-
-## Originaltext
-
-<textarea readonly>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 Read tool first to read the file's contents. This tool will fail if you did not read the file first.
-- Prefer the Edit tool for modifying existing files — it only sends the diff. Only use this tool to create new files or for complete rewrites.
-- NEVER create documentation files (*.md) or README files unless explicitly requested by the User.
-- Only use emojis if the user explicitly requests it. Avoid writing emojis to files unless asked.</textarea>

package/concepts/de/Tool-executeCode.md

@@ -1,41 +0,0 @@
-# executeCode (mcp__ide__executeCode)
-
-## Definition
-
-Führt Python-Code im Jupyter-Kernel der aktuellen Notebook-Datei aus.
-
-## Parameter
-
-| Parameter | Typ | Erforderlich | Beschreibung |
-|-----------|-----|--------------|--------------|
-| `code` | string | Ja | Der auszuführende Python-Code |
-
-## Anwendungsfälle
-
-**Geeignet für:**
-- Code in einer Jupyter-Notebook-Umgebung ausführen
-- Code-Snippets testen
-- Datenanalyse und Berechnungen
-
-**Nicht geeignet für:**
-- Codeausführung außerhalb von Jupyter – dafür Bash verwenden
-- Dateien ändern – dafür Edit oder Write verwenden
-
-## Hinweise
-
-- Dies ist ein MCP-Tool (Model Context Protocol), bereitgestellt durch die IDE-Integration
-- Code wird im aktuellen Jupyter-Kernel ausgeführt, der Zustand bleibt zwischen Aufrufen bestehen
-- Sofern der Benutzer es nicht ausdrücklich anfordert, sollte das Deklarieren von Variablen oder Ändern des Kernel-Zustands vermieden werden
-- Nach einem Kernel-Neustart geht der Zustand verloren
-
-## Originaltext
-
-<textarea readonly>Execute python code in the Jupyter kernel for the current notebook file.
-    
-    All code will be executed in the current Jupyter kernel.
-    
-    Avoid declaring variables or modifying the state of the kernel unless the user
-    explicitly asks for it.
-    
-    Any code executed will persist across calls to this tool, unless the kernel
-    has been restarted.</textarea>

package/concepts/de/Tool-getDiagnostics.md

@@ -1,32 +0,0 @@
-# getDiagnostics (mcp__ide__getDiagnostics)
-
-## Definition
-
-Ruft Sprachdiagnoseinformationen von VS Code ab, einschließlich Syntaxfehler, Typfehler, Lint-Warnungen usw.
-
-## Parameter
-
-| Parameter | Typ | Erforderlich | Beschreibung |
-|-----------|-----|--------------|--------------|
-| `uri` | string | Nein | Datei-URI. Wenn nicht angegeben, werden Diagnoseinformationen aller Dateien abgerufen |
-
-## Anwendungsfälle
-
-**Geeignet für:**
-- Syntax-, Typ-, Lint- und andere semantische Probleme im Code prüfen
-- Nach Codebearbeitung überprüfen, ob neue Fehler eingeführt wurden
-- Als Alternative zu Bash-Befehlen zur Codequalitätsprüfung
-
-**Nicht geeignet für:**
-- Tests ausführen – dafür Bash verwenden
-- Laufzeitfehler prüfen – dafür Code über Bash ausführen
-
-## Hinweise
-
-- Dies ist ein MCP-Tool (Model Context Protocol), bereitgestellt durch die IDE-Integration
-- Nur in VS Code / IDE-Umgebungen verfügbar
-- Dieses Tool gegenüber Bash-Befehlen zur Codeprüfung bevorzugen
-
-## Originaltext
-
-<textarea readonly>Get language diagnostics from VS Code</textarea>

package/concepts/de/Tools.md

@@ -1,67 +0,0 @@
-# Claude Code Tool-Übersicht
-
-Claude Code stellt dem Modell über den tool_use-Mechanismus der Anthropic API eine Reihe integrierter Tools zur Verfügung. Das `tools`-Array jeder MainAgent-Anfrage enthält die vollständigen JSON-Schema-Definitionen dieser Tools, und das Modell ruft sie in der Antwort über `tool_use` Content Blocks auf.
-
-Im Folgenden finden Sie den kategorisierten Index aller Tools.
-
-## Agent-System
-
-| Tool | Zweck |
-|------|-------|
-| [Task](Tool-Task.md) | Startet einen Sub-Agent (SubAgent) für komplexe mehrstufige Aufgaben |
-| [TaskOutput](Tool-TaskOutput.md) | Ruft die Ausgabe von Hintergrundaufgaben ab |
-| [TaskStop](Tool-TaskStop.md) | Stoppt eine laufende Hintergrundaufgabe |
-| [TaskCreate](Tool-TaskCreate.md) | Erstellt einen strukturierten Aufgabenlisteneintrag |
-| [TaskGet](Tool-TaskGet.md) | Ruft Aufgabendetails ab |
-| [TaskUpdate](Tool-TaskUpdate.md) | Aktualisiert Aufgabenstatus, Abhängigkeiten usw. |
-| [TaskList](Tool-TaskList.md) | Listet alle Aufgaben auf |
-
-## Dateioperationen
-
-| Tool | Zweck |
-|------|-------|
-| [Read](Tool-Read.md) | Liest Dateiinhalte (unterstützt Text, Bilder, PDF, Jupyter Notebook) |
-| [Edit](Tool-Edit.md) | Bearbeitet Dateien durch exakte Zeichenkettenersetzung |
-| [Write](Tool-Write.md) | Schreibt oder überschreibt Dateien |
-| [NotebookEdit](Tool-NotebookEdit.md) | Bearbeitet Jupyter-Notebook-Zellen |
-
-## Suche
-
-| Tool | Zweck |
-|------|-------|
-| [Glob](Tool-Glob.md) | Sucht Dateien nach Dateinamenmustern |
-| [Grep](Tool-Grep.md) | Dateiinhaltssuche basierend auf ripgrep |
-
-## Terminal
-
-| Tool | Zweck |
-|------|-------|
-| [Bash](Tool-Bash.md) | Führt Shell-Befehle aus |
-
-## Web
-
-| Tool | Zweck |
-|------|-------|
-| [WebFetch](Tool-WebFetch.md) | Ruft Webinhalte ab und verarbeitet sie mit KI |
-| [WebSearch](Tool-WebSearch.md) | Suchmaschinenabfrage |
-
-## Planung und Interaktion
-
-| Tool | Zweck |
-|------|-------|
-| [EnterPlanMode](Tool-EnterPlanMode.md) | Wechselt in den Planungsmodus zur Entwurfsplanung |
-| [ExitPlanMode](Tool-ExitPlanMode.md) | Verlässt den Planungsmodus und reicht den Plan zur Benutzerfreigabe ein |
-| [AskUserQuestion](Tool-AskUserQuestion.md) | Stellt dem Benutzer Fragen zur Klärung oder Entscheidungsfindung |
-
-## Erweiterungen
-
-| Tool | Zweck |
-|------|-------|
-| [Skill](Tool-Skill.md) | Führt einen Skill (Slash Command) aus |
-
-## IDE-Integration
-
-| Tool | Zweck |
-|------|-------|
-| [getDiagnostics](Tool-getDiagnostics.md) | Ruft VS Code Sprachdiagnoseinformationen ab |
-| [executeCode](Tool-executeCode.md) | Führt Code im Jupyter-Kernel aus |

package/concepts/en/CacheRebuild.md

@@ -1,36 +0,0 @@
-# Cache Rebuild
-
-## Background
-
-Anthropic's prompt caching mechanism concatenates system → tools → messages (up to the cache breakpoint) in order to form the cache key. When the cache key matches the previous request exactly, the API returns `cache_read_input_tokens` (cache hit); when the cache key changes, the API recreates the cache and returns a large number of `cache_creation_input_tokens`, i.e., a cache rebuild.
-
-Cache rebuilds mean additional token charges (cache creation is priced higher than cache read), so identifying rebuild causes has direct value for cost optimization.
-
-## Cache Rebuild Reason Categories
-
-cc-viewer compares the bodies of two consecutive MainAgent requests to precisely determine the cause of a cache rebuild:
-
-| reason | Meaning | Detection Method |
-|--------|---------|------------------|
-| `ttl` | Cache expired | More than 5 minutes since the last MainAgent request |
-| `system_change` | System prompt changed | `JSON.stringify(prev.system) !== JSON.stringify(curr.system)` |
-| `tools_change` | Tool definitions changed | `JSON.stringify(prev.tools) !== JSON.stringify(curr.tools)` |
-| `model_change` | Model switched | `prev.model !== curr.model` |
-| `msg_truncated` | Message stack truncated | Current request has fewer messages than the previous one, usually triggered by context window overflow |
-| `msg_modified` | Historical messages modified | Prefix message content is inconsistent (prefix should be identical during normal appending) |
-| `key_change` | Unknown key change | Fallback when none of the above conditions match |
-
-## Detection Priority
-
-1. First check the time interval — if more than 5 minutes, immediately classify as `ttl` without body comparison
-2. Then check model, system, tools, and messages in sequence
-3. A single request may match multiple reasons (e.g., model switch + system prompt change), in which case the `reasons` array contains all matches and the tooltip displays them on separate lines
-
-## Common Scenarios
-
-- **`ttl`**: The user paused for more than 5 minutes before continuing, and the cache naturally expired
-- **`system_change`**: Claude Code updated the system prompt (e.g., loaded new CLAUDE.md, project instructions changed)
-- **`tools_change`**: MCP server connection/disconnection caused changes to the available tool list
-- **`model_change`**: The user switched models via the `/model` command
-- **`msg_truncated`**: A long conversation triggered context window management, and Claude Code truncated earlier messages
-- **`msg_modified`**: Claude Code edited historical messages (e.g., `/compact` replaced original messages with a compressed summary)

package/concepts/en/KVCacheContent.md

@@ -1,49 +0,0 @@
-# KV-Cache Content
-
-## What is Prompt Caching?
-
-When you chat with Claude, each API request sends the full conversation context (system prompt + tool definitions + historical messages). Anthropic's prompt caching mechanism caches previously computed prefix content on the server side. If the prefix of a subsequent request matches, the cached result is reused directly, skipping redundant computation and significantly reducing latency and cost.
-
-In cc-viewer, this mechanism is referred to as "KV-Cache", corresponding to Anthropic's API-level prompt caching — not the key-value cache within the transformer attention layers of the LLM itself.
-
-## How Caching Works
-
-Anthropic's prompt caching concatenates the cache key in a fixed order:
-
-```
-Tools → System Prompt → Messages (up to cache breakpoint)
-```
-
-As long as this prefix exactly matches any request within the TTL window, the API returns a cache hit (`cache_read_input_tokens`) rather than recomputing (`cache_creation_input_tokens`).
-
-> **Claude Code does not strongly depend on the `cache_control` attribute. The server will strip some of these attributes accordingly, yet caching still works well. So not seeing `cache_control` does not mean the content is not cached.**
->
-> For special clients like Claude Code, Anthropic's server does not fully rely on the `cache_control` attribute in requests to determine caching behavior. The server automatically applies caching policies to specific fields (such as system prompt and tool definitions), even when the request does not explicitly include `cache_control` markers. Therefore, when you don't see this attribute in the request body, don't be puzzled — the server has already performed the caching operation behind the scenes, it simply hasn't exposed this information to the client. This is a tacit understanding between Claude Code and the Anthropic API.
-
-## What is "Current KV-Cache Content"?
-
-The "Current KV-Cache Content" displayed in cc-viewer is extracted from the most recent MainAgent request — specifically the content before the cache boundary (cache breakpoint). It includes:
-
-- **System Prompt**: Claude Code's system instructions, including core agent directives, tool usage specifications, CLAUDE.md project instructions, environment information, etc.
-- **Tools**: The current list of available tool definitions (such as Read, Write, Bash, Agent, MCP tools, etc.)
-- **Messages**: The portion of conversation history that is cached (typically earlier messages, up to the last `cache_control` marker)
-
-## Why View Cache Content?
-
-1. **Understand Context**: See what Claude currently "remembers" to help you judge whether its behavior matches expectations
-2. **Cost Optimization**: Cache hits cost far less than recomputation. Viewing cache content helps you understand why certain requests triggered a cache rebuild
-3. **Debug Conversations**: When Claude's responses don't match expectations, checking cache content confirms whether the system prompt and historical messages are correct
-4. **Context Quality Monitoring**: During debugging, configuration changes, or prompt adjustments, KV-Cache-Text provides a centralized view to quickly confirm whether core context has degraded or been unexpectedly polluted — without manually reviewing raw messages
-
-## Multi-Level Caching Strategy
-
-The KV-Cache corresponding to Claude Code is not a single cache. The server generates separate caches for Tools and System Prompt, independent from the Messages cache. The benefit of this design is: when the messages stack becomes corrupted (e.g., context truncation, message modification) and needs rebuilding, it won't invalidate the Tools and System Prompt caches along with it, avoiding a full recomputation.
-
-This is a current server-side optimization strategy — because Tool definitions and the System Prompt remain relatively stable during normal use and rarely change. Caching them separately minimizes unnecessary rebuild overhead. So when you observe the cache, you'll notice that apart from Tools rebuilds which require a full cache refresh, disruptions to the System Prompt and Messages still have inheritable caches available.
-
-## Cache Lifecycle
-
-- **Creation**: On first request or after cache expiration, the API creates a new cache (`cache_creation_input_tokens`)
-- **Hit**: Subsequent requests with matching prefixes reuse the cache (`cache_read_input_tokens`)
-- **Expiration**: Cache has a 5-minute TTL (time-to-live) and automatically expires after timeout
-- **Rebuild**: When system prompt, tool list, model, or message content changes, the cache key no longer matches, triggering a rebuild at the corresponding level

package/concepts/en/Tool-Agent.md

@@ -1,125 +0,0 @@
-# Agent
-
-## Definition
-
-Launches a SubAgent to autonomously handle complex multi-step tasks. SubAgents are independent subprocesses, each with their own dedicated tool set and context. Agent is the renamed version of the Task tool in newer Claude Code releases.
-
-## Parameters
-
-| Parameter | Type | Required | Description |
-|-----------|------|----------|-------------|
-| `prompt` | string | Yes | Description of the task for the SubAgent to execute |
-| `description` | string | Yes | A 3-5 word short summary |
-| `subagent_type` | string | Yes | SubAgent type, determines the available tool set |
-| `model` | enum | No | Specify model (sonnet / opus / haiku), defaults to inheriting from parent |
-| `max_turns` | integer | No | Maximum number of agentic turns |
-| `run_in_background` | boolean | No | Whether to run in the background; background tasks return an output_file path |
-| `resume` | string | No | Agent ID to resume, continues from the last execution. Useful for picking up where a previous SubAgent left off without losing context |
-| `isolation` | enum | No | Isolation mode, `worktree` creates a temporary git worktree |
-
-## SubAgent Types
-
-| Type | Purpose | Available Tools |
-|------|---------|-----------------|
-| `Bash` | Command execution, git operations | Bash |
-| `general-purpose` | General multi-step tasks | All tools |
-| `Explore` | Quick codebase exploration | All tools except Agent/Edit/Write/NotebookEdit/ExitPlanMode |
-| `Plan` | Design implementation plans | All tools except Agent/Edit/Write/NotebookEdit/ExitPlanMode |
-| `claude-code-guide` | Claude Code usage guide Q&A | Glob, Grep, Read, WebFetch, WebSearch |
-| `statusline-setup` | Configure status bar | Read, Edit |
-
-## Use Cases
-
-**Good for:**
-- Complex tasks requiring multi-step autonomous completion
-- Codebase exploration and deep research (using Explore type)
-- Parallel work requiring isolated environments
-- Long-running tasks that need to run in the background
-
-**Not good for:**
-- Reading a specific file path — use Read or Glob directly
-- Searching within 2-3 known files — use Read directly
-- Searching for a specific class definition — use Glob directly
-
-## Notes
-
-- After completion, the SubAgent returns a single message; its results are not visible to the user and need to be relayed by the main agent
-- Multiple Agent calls can be issued in parallel within a single message for efficiency
-- Background tasks are checked for progress via the TaskOutput tool
-- The Explore type is slower than directly calling Glob/Grep; only use it when simple searches are insufficient
-- Use `run_in_background: true` for long-running tasks that don't need immediate results; use foreground (default) when the main agent needs the result before proceeding
-- The `resume` parameter allows continuing a previously started SubAgent session, preserving its accumulated context
-
-## Original Text
-
-<textarea readonly>Launch a new agent to handle complex, multi-step tasks autonomously.
-
-The Agent tool launches specialized agents (subprocesses) that autonomously handle complex tasks. Each agent type has specific capabilities and tools available to it.
-
-Available agent types and the tools they have access to:
-- general-purpose: General-purpose agent for researching complex questions, searching for code, and executing multi-step tasks. When you are searching for a keyword or file and are not confident that you will find the right match in the first few tries use this agent to perform the search for you. (Tools: *)
-- statusline-setup: Use this agent to configure the user's Claude Code status line setting. (Tools: Read, Edit)
-- Explore: Fast agent specialized for exploring codebases. Use this when you need to quickly find files by patterns (eg. "src/components/**/*.tsx"), search code for keywords (eg. "API endpoints"), or answer questions about the codebase (eg. "how do API endpoints work?"). When calling this agent, specify the desired thoroughness level: "quick" for basic searches, "medium" for moderate exploration, or "very thorough" for comprehensive analysis across multiple locations and naming conventions. (Tools: All tools except Agent, ExitPlanMode, Edit, Write, NotebookEdit)
-- Plan: Software architect agent for designing implementation plans. Use this when you need to plan the implementation strategy for a task. Returns step-by-step plans, identifies critical files, and considers architectural trade-offs. (Tools: All tools except Agent, ExitPlanMode, Edit, Write, NotebookEdit)
-- claude-code-guide: Use this agent when the user asks questions ("Can Claude...", "Does Claude...", "How do I...") about: (1) Claude Code (the CLI tool) - features, hooks, slash commands, MCP servers, settings, IDE integrations, keyboard shortcuts; (2) Claude Agent SDK - building custom agents; (3) Claude API (formerly Anthropic API) - API usage, tool use, Anthropic SDK usage. **IMPORTANT:** Before spawning a new agent, check if there is already a running or recently completed claude-code-guide agent that you can resume using the "resume" parameter. (Tools: Glob, Grep, Read, WebFetch, WebSearch)
-
-When using the Agent tool, you must specify a subagent_type parameter to select which agent type to use.
-
-When NOT to use the Agent tool:
-- If you want to read a specific file path, use the Read or Glob tool instead of the Agent tool, to find the match more quickly
-- If you are searching for a specific class definition like "class Foo", use the Glob tool instead, to find the match more quickly
-- If you are searching for code within a specific file or set of 2-3 files, use the Read tool instead of the Agent tool, to find the match more quickly
-- Other tasks that are not related to the agent descriptions above
-
-Usage notes:
-- Always include a short description (3-5 words) summarizing what the agent will do
-- Launch multiple agents concurrently whenever possible, to maximize performance; to do that, use a single message with multiple tool uses
-- When the agent is done, it will return a single message back to you. The result returned by the agent is not visible to the user. To show the user the result, you should send a text message back to the user with a concise summary of the result.
-- You can optionally run agents in the background using the run_in_background parameter. When an agent runs in the background, you will be automatically notified when it completes — do NOT sleep, poll, or proactively check on its progress. Continue with other work or respond to the user instead.
-- **Foreground vs background**: Use foreground (default) when you need the agent's results before you can proceed — e.g., research agents whose findings inform your next steps. Use background when you have genuinely independent work to do in parallel.
-- Agents can be resumed using the `resume` parameter by passing the agent ID from a previous invocation. When resumed, the agent continues with its full previous context preserved. When NOT resuming, each invocation starts fresh and you should provide a detailed task description with all necessary context.
-- When the agent is done, it will return a single message back to you along with its agent ID. You can use this ID to resume the agent later if needed for follow-up work.
-- Provide clear, detailed prompts so the agent can work autonomously and return exactly the information you need.
-- Agents with "access to current context" can see the full conversation history before the tool call. When using these agents, you can write concise prompts that reference earlier context (e.g., "investigate the error discussed above") instead of repeating information. The agent will receive all prior messages and understand the context.
-- The agent's outputs should generally be trusted
-- Clearly tell the agent whether you expect it to write code or just to do research (search, file reads, web fetches, etc.), since it is not aware of the user's intent
-- If the agent description mentions that it should be used proactively, then you should try your best to use it without the user having to ask for it first. Use your judgement.
-- If the user specifies that they want you to run agents "in parallel", you MUST send a single message with multiple Agent tool use content blocks. For example, if you need to launch both a build-validator agent and a test-runner agent in parallel, send a single message with both tool calls.
-- You can optionally set `isolation: "worktree"` to run the agent in a temporary git worktree, giving it an isolated copy of the repository. The worktree is automatically cleaned up if the agent makes no changes; if changes are made, the worktree path and branch are returned in the result.
-
-Example usage:
-
-<example_agent_descriptions>
-"test-runner": use this agent after you are done writing code to run tests
-"greeting-responder": use this agent to respond to user greetings with a friendly joke
-</example_agent_descriptions>
-
-<example>
-user: "Please write a function that checks if a number is prime"
-assistant: Sure let me write a function that checks if a number is prime
-assistant: First let me use the Write tool to write a function that checks if a number is prime
-assistant: I'm going to use the Write tool to write the following code:
-<code>
-function isPrime(n) {
-  if (n <= 1) return false
-  for (let i = 2; i * i <= n; i++) {
-    if (n % i === 0) return false
-  }
-  return true
-}
-</code>
-<commentary>
-Since a significant piece of code was written and the task was completed, now use the test-runner agent to run the tests
-</commentary>
-assistant: Now let me use the test-runner agent to run the tests
-assistant: Uses the Agent tool to launch the test-runner agent
-</example>
-
-<example>
-user: "Hello"
-<commentary>
-Since the user is greeting, use the greeting-responder agent to respond with a friendly joke
-</commentary>
-assistant: "I'm going to use the Agent tool to launch the greeting-responder agent"
-</example>
-</textarea>

package/concepts/en/Tool-AskUserQuestion.md

@@ -1,75 +0,0 @@
-# AskUserQuestion
-
-## Definition
-
-Asks the user a question during execution to obtain clarification, validate assumptions, or request decisions.
-
-## Parameters
-
-| Parameter | Type | Required | Description |
-|-----------|------|----------|-------------|
-| `questions` | array | Yes | List of questions (1-4 questions) |
-| `answers` | object | No | Answers collected from the user |
-| `annotations` | object | No | Annotations for each question (e.g., notes for preview selections) |
-| `metadata` | object | No | Metadata for tracking and analysis |
-
-Each `question` object:
-
-| Field | Type | Required | Description |
-|-------|------|----------|-------------|
-| `question` | string | Yes | Full question text, should end with a question mark |
-| `header` | string | Yes | Short label (max 12 characters), displayed as a tag chip |
-| `options` | array | Yes | 2-4 options |
-| `multiSelect` | boolean | Yes | Whether multiple selections are allowed |
-
-Each `option` object:
-
-| Field | Type | Required | Description |
-|-------|------|----------|-------------|
-| `label` | string | Yes | Option display text (1-5 words) |
-| `description` | string | Yes | Option description |
-| `markdown` | string | No | Preview content (for visual comparison of ASCII layouts, code snippets, etc.) |
-
-## Use Cases
-
-**Good for:**
-- Collecting user preferences or requirements
-- Clarifying ambiguous instructions
-- Getting decisions during implementation
-- Providing directional choices to the user
-
-**Not good for:**
-- Asking "Is the plan okay?" — use ExitPlanMode instead
-
-## Notes
-
-- The user can always choose "Other" to provide custom input
-- Place the recommended option first and append "(Recommended)" to its label
-- `markdown` preview is only supported for single-select questions
-- Options with `markdown` switch to a side-by-side layout
-- In plan mode, used to clarify requirements before finalizing the plan
-
-## Original Text
-
-<textarea readonly>Use this tool when you need to ask the user questions during execution. This allows you to:
-1. Gather user preferences or requirements
-2. Clarify ambiguous instructions
-3. Get decisions on implementation choices as you work
-4. Offer choices to the user about what direction to take.
-
-Usage notes:
-- Users will always be able to select "Other" to provide custom text input
-- Use multiSelect: true to allow multiple answers to be selected for a question
-- If you recommend a specific option, make that the first option in the list and add "(Recommended)" at the end of the label
-
-Plan mode note: In plan mode, use this tool to clarify requirements or choose between approaches BEFORE finalizing your plan. Do NOT use this tool to ask "Is my plan ready?" or "Should I proceed?" - use ExitPlanMode for plan approval. IMPORTANT: Do not reference "the plan" in your questions (e.g., "Do you have feedback about the plan?", "Does the plan look good?") because the user cannot see the plan in the UI until you call ExitPlanMode. If you need plan approval, use ExitPlanMode instead.
-
-Preview feature:
-Use the optional `markdown` field on options when presenting concrete artifacts that users need to visually compare:
-- ASCII mockups of UI layouts or components
-- Code snippets showing different implementations
-- Diagram variations
-- Configuration examples
-
-When any option has a markdown, the UI switches to a side-by-side layout with a vertical option list on the left and preview on the right. Do not use previews for simple preference questions where labels and descriptions suffice. Note: previews are only supported for single-select questions (not multiSelect).
-</textarea>