cx-viewer 1.0.2 → 1.0.4

package/concepts/en/Tool-Bash.md

@@ -1,167 +0,0 @@
-# Bash
-
-## Definition
-
-Executes shell commands with optional timeout settings. The working directory persists between commands, but shell state (environment variables, etc.) does not persist.
-
-## Parameters
-
-| Parameter | Type | Required | Description |
-|-----------|------|----------|-------------|
-| `command` | string | Yes | The bash command to execute |
-| `description` | string | No | A short description of the command |
-| `timeout` | number | No | Timeout in milliseconds, max 600000, default 120000 |
-| `run_in_background` | boolean | No | Whether to run in the background |
-
-## Use Cases
-
-**Good for:**
-- git operations (commit, push, branch, etc.)
-- npm/yarn and other package management commands
-- docker operations
-- Compilation and build commands
-- Listing directory contents (`ls`)
-- Other system commands that require shell execution
-
-**Not good for:**
-- Reading files — use Read instead
-- Searching for filenames — use Glob instead
-- Searching file contents — use Grep instead
-- Editing files — use Edit instead
-- Writing files — use Write instead
-- Outputting information to the user — output directly in the response text
-- Long-running processes (dev server, watch mode) — recommend the user run them manually
-
-## Notes
-
-- Paths containing spaces must be wrapped in double quotes
-- Output exceeding 30000 characters will be truncated
-- Background commands retrieve results via TaskOutput
-- Use absolute paths whenever possible, avoid `cd`
-- Independent commands can invoke multiple Bash calls in parallel
-- Dependent commands should be chained with `&&`
-- The shell environment is initialized from the user's profile (bash or zsh)
-
-## Original Text
-
-<textarea readonly>Executes a given bash command and returns its output.
-
-The working directory persists between commands, but shell state does not. The shell environment is initialized from the user's profile (bash or zsh).
-
-IMPORTANT: Avoid using this tool to run `find`, `grep`, `cat`, `head`, `tail`, `sed`, `awk`, or `echo` commands, unless explicitly instructed or after you have verified that a dedicated tool cannot accomplish your task. Instead, use the appropriate dedicated tool as this will provide a much better experience for the user:
-
- - File search: Use Glob (NOT find or ls)
- - Content search: Use Grep (NOT grep or rg)
- - Read files: Use Read (NOT cat/head/tail)
- - Edit files: Use Edit (NOT sed/awk)
- - Write files: Use Write (NOT echo >/cat <<EOF)
- - Communication: Output text directly (NOT echo/printf)
-While the Bash tool can do similar things, it’s better to use the built-in tools as they provide a better user experience and make it easier to review tool calls and give permission.
-
-# Instructions
- - If your command will create new directories or files, first use this tool to run `ls` to verify the parent directory exists and is the correct location.
- - Always quote file paths that contain spaces with double quotes in your command (e.g., cd "path with spaces/file.txt")
- - Try to maintain your current working directory throughout the session by using absolute paths and avoiding usage of `cd`. You may use `cd` if the User explicitly requests it.
- - You may specify an optional timeout in milliseconds (up to 600000ms / 10 minutes). By default, your command will timeout after 120000ms (2 minutes).
- - You can use the `run_in_background` parameter to run the command in the background. Only use this if you don't need the result immediately and are OK being notified when the command completes later. You do not need to check the output right away - you'll be notified when it finishes. You do not need to use '&' at the end of the command when using this parameter.
- - Write a clear, concise description of what your command does. For simple commands, keep it brief (5-10 words). For complex commands (piped commands, obscure flags, or anything hard to understand at a glance), include enough context so that the user can understand what your command will do.
- - When issuing multiple commands:
-  - If the commands are independent and can run in parallel, make multiple Bash tool calls in a single message. Example: if you need to run "git status" and "git diff", send a single message with two Bash tool calls in parallel.
-  - If the commands depend on each other and must run sequentially, use a single Bash call with '&&' to chain them together.
-  - Use ';' only when you need to run commands sequentially but don't care if earlier commands fail.
-  - DO NOT use newlines to separate commands (newlines are ok in quoted strings).
- - For git commands:
-  - Prefer to create a new commit rather than amending an existing commit.
-  - Before running destructive operations (e.g., git reset --hard, git push --force, git checkout --), consider whether there is a safer alternative that achieves the same goal. Only use destructive operations when they are truly the best approach.
-  - Never skip hooks (--no-verify) or bypass signing (--no-gpg-sign, -c commit.gpgsign=false) unless the user has explicitly asked for it. If a hook fails, investigate and fix the underlying issue.
- - Avoid unnecessary `sleep` commands:
-  - Do not sleep between commands that can run immediately — just run them.
-  - If your command is long running and you would like to be notified when it finishes – simply run your command using `run_in_background`. There is no need to sleep in this case.
-  - Do not retry failing commands in a sleep loop — diagnose the root cause or consider an alternative approach.
-  - If waiting for a background task you started with `run_in_background`, you will be notified when it completes — do not poll.
-  - If you must poll an external process, use a check command (e.g. `gh run view`) rather than sleeping first.
-  - If you must sleep, keep the duration short (1-5 seconds) to avoid blocking the user.
-
-# Committing changes with git
-
-Only create commits when requested by the user. If unclear, ask first. When the user asks you to create a new git commit, follow these steps carefully:
-
-Git Safety Protocol:
-- NEVER update the git config
-- NEVER run destructive git commands (push --force, reset --hard, checkout ., restore ., clean -f, branch -D) unless the user explicitly requests these actions. Taking unauthorized destructive actions is unhelpful and can result in lost work, so it's best to ONLY run these commands when given direct instructions 
-- NEVER skip hooks (--no-verify, --no-gpg-sign, etc) unless the user explicitly requests it
-- NEVER run force push to main/master, warn the user if they request it
-- CRITICAL: Always create NEW commits rather than amending, unless the user explicitly requests a git amend. When a pre-commit hook fails, the commit did NOT happen — so --amend would modify the PREVIOUS commit, which may result in destroying work or losing previous changes. Instead, after hook failure, fix the issue, re-stage, and create a NEW commit
-- When staging files, prefer adding specific files by name rather than using "git add -A" or "git add .", which can accidentally include sensitive files (.env, credentials) or large binaries
-- NEVER commit changes unless the user explicitly asks you to. It is VERY IMPORTANT to only commit when explicitly asked, otherwise the user will feel that you are being too proactive
-
-1. You can call multiple tools in a single response. When multiple independent pieces of information are requested and all commands are likely to succeed, run multiple tool calls in parallel for optimal performance. run the following bash commands in parallel, each using the Bash tool:
-  - Run a git status command to see all untracked files. IMPORTANT: Never use the -uall flag as it can cause memory issues on large repos.
-  - Run a git diff command to see both staged and unstaged changes that will be committed.
-  - Run a git log command to see recent commit messages, so that you can follow this repository's commit message style.
-2. Analyze all staged changes (both previously staged and newly added) and draft a commit message:
-  - Summarize the nature of the changes (eg. new feature, enhancement to an existing feature, bug fix, refactoring, test, docs, etc.). Ensure the message accurately reflects the changes and their purpose (i.e. "add" means a wholly new feature, "update" means an enhancement to an existing feature, "fix" means a bug fix, etc.).
-  - Do not commit files that likely contain secrets (.env, credentials.json, etc). Warn the user if they specifically request to commit those files
-  - Draft a concise (1-2 sentences) commit message that focuses on the "why" rather than the "what"
-  - Ensure it accurately reflects the changes and their purpose
-3. You can call multiple tools in a single response. When multiple independent pieces of information are requested and all commands are likely to succeed, run multiple tool calls in parallel for optimal performance. run the following commands:
-   - Add relevant untracked files to the staging area.
-   - Create the commit with a message ending with:
-   Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
-   - Run git status after the commit completes to verify success.
-   Note: git status depends on the commit completing, so run it sequentially after the commit.
-4. If the commit fails due to pre-commit hook: fix the issue and create a NEW commit
-
-Important notes:
-- NEVER run additional commands to read or explore code, besides git bash commands
-- NEVER use the TodoWrite or Agent tools
-- DO NOT push to the remote repository unless the user explicitly asks you to do so
-- IMPORTANT: Never use git commands with the -i flag (like git rebase -i or git add -i) since they require interactive input which is not supported.
-- IMPORTANT: Do not use --no-edit with git rebase commands, as the --no-edit flag is not a valid option for git rebase.
-- If there are no changes to commit (i.e., no untracked files and no modifications), do not create an empty commit
-- In order to ensure good formatting, ALWAYS pass the commit message via a HEREDOC, a la this example:
-<example>
-git commit -m "$(cat <<'EOF'
-   Commit message here.
-
-   Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
-   EOF
-   )"
-</example>
-
-# Creating pull requests
-Use the gh command via the Bash tool for ALL GitHub-related tasks including working with issues, pull requests, checks, and releases. If given a Github URL use the gh command to get the information needed.
-
-IMPORTANT: When the user asks you to create a pull request, follow these steps carefully:
-
-1. You can call multiple tools in a single response. When multiple independent pieces of information are requested and all commands are likely to succeed, run multiple tool calls in parallel for optimal performance. run the following bash commands in parallel using the Bash tool, in order to understand the current state of the branch since it diverged from the main branch:
-   - Run a git status command to see all untracked files (never use -uall flag)
-   - Run a git diff command to see both staged and unstaged changes that will be committed
-   - Check if the current branch tracks a remote branch and is up to date with the remote, so you know if you need to push to the remote
-   - Run a git log command and `git diff [base-branch]...HEAD` to understand the full commit history for the current branch (from the time it diverged from the base branch)
-2. Analyze all changes that will be included in the pull request, making sure to look at all relevant commits (NOT just the latest commit, but ALL commits that will be included in the pull request!!!), and draft a pull request title and summary:
-   - Keep the PR title short (under 70 characters)
-   - Use the description/body for details, not the title
-3. You can call multiple tools in a single response. When multiple independent pieces of information are requested and all commands are likely to succeed, run multiple tool calls in parallel for optimal performance. run the following commands in parallel:
-   - Create new branch if needed
-   - Push to remote with -u flag if needed
-   - Create PR using gh pr create with the format below. Use a HEREDOC to pass the body to ensure correct formatting.
-<example>
-gh pr create --title "the pr title" --body "$(cat <<'EOF'
-## Summary
-<1-3 bullet points>
-
-## Test plan
-[Bulleted markdown checklist of TODOs for testing the pull request...]
-
-🤖 Generated with [Claude Code](https://claude.com/claude-code)
-EOF
-)"
-</example>
-
-Important:
-- DO NOT use the TodoWrite or Agent tools
-- Return the PR URL when you're done, so the user can see it
-
-# Other common operations
-- View comments on a Github PR: gh api repos/foo/bar/pulls/123/comments</textarea>

package/concepts/en/Tool-Edit.md

@@ -1,46 +0,0 @@
-# Edit
-
-## Definition
-
-Edits files via exact string replacement. Replaces `old_string` with `new_string` in the file.
-
-## Parameters
-
-| Parameter | Type | Required | Description |
-|-----------|------|----------|-------------|
-| `file_path` | string | Yes | Absolute path of the file to modify |
-| `old_string` | string | Yes | The original text to replace |
-| `new_string` | string | Yes | The new replacement text (must differ from old_string) |
-| `replace_all` | boolean | No | Whether to replace all matches, default `false` |
-
-## Use Cases
-
-**Good for:**
-- Modifying specific code sections in existing files
-- Fixing bugs, updating logic
-- Renaming variables (with `replace_all: true`)
-- Any scenario requiring precise file content modification
-
-**Not good for:**
-- Creating new files — use Write instead
-- Large-scale rewrites — may need Write to overwrite the entire file
-
-## Notes
-
-- You must first read the file via Read before using this tool, otherwise it will error
-- `old_string` must be unique in the file, otherwise the edit fails. If not unique, provide more context to make it unique, or use `replace_all`
-- When editing text, preserve the original indentation (tabs/spaces); do not include the line number prefix from Read output
-- Prefer editing existing files over creating new ones
-- `new_string` must differ from `old_string`
-
-## Original Text
-
-<textarea readonly>Performs exact string replacements in files.
-
-Usage:
-- You must use your `Read` tool at least once in the conversation before editing. This tool will error if you attempt an edit without reading the file. 
-- When editing text from Read tool output, ensure you preserve the exact indentation (tabs/spaces) as it appears AFTER the line number prefix. The line number prefix format is: spaces + line number + tab. Everything after that tab is the actual file content to match. Never include any part of the line number prefix in the old_string or new_string.
-- ALWAYS prefer editing existing files in the codebase. NEVER write new files unless explicitly required.
-- Only use emojis if the user explicitly requests it. Avoid adding emojis to files unless asked.
-- The edit will FAIL if `old_string` is not unique in the file. Either provide a larger string with more surrounding context to make it unique or use `replace_all` to change every instance of `old_string`.
-- Use `replace_all` for replacing and renaming strings across the file. This parameter is useful if you want to rename a variable for instance.</textarea>

package/concepts/en/Tool-EnterPlanMode.md

@@ -1,128 +0,0 @@
-# EnterPlanMode
-
-## Definition
-
-Switches Claude Code into plan mode for exploring the codebase and designing an implementation plan before execution.
-
-## Parameters
-
-No parameters.
-
-## Use Cases
-
-**Good for:**
-- New feature implementation — requires architectural decisions
-- Multiple viable approaches exist — requires user selection
-- Code changes affect existing behavior or structure
-- Multi-file changes — potentially involving 2-3 or more files
-- Requirements are unclear — need to explore first to understand scope
-- User preferences matter — implementation can go in multiple reasonable directions
-
-**Not good for:**
-- Single-line or few-line fixes (typos, obvious bugs)
-- The user has given very specific instructions
-- Pure research/exploration tasks — use Task (Explore type) instead
-
-## Behavior in Plan Mode
-
-After entering plan mode, Claude Code will:
-1. Use Glob, Grep, and Read tools to deeply explore the codebase
-2. Understand existing patterns and architecture
-3. Design an implementation plan
-4. Submit the plan for user approval
-5. Use AskUserQuestion if clarification is needed
-6. Exit via ExitPlanMode when the plan is ready
-
-## Notes
-
-- This tool requires user consent to enter plan mode
-- When unsure whether planning is needed, lean toward planning — aligning upfront is better than rework
-
-## Original Text
-
-<textarea readonly>Use this tool proactively when you're about to start a non-trivial implementation task. Getting user sign-off on your approach before writing code prevents wasted effort and ensures alignment. This tool transitions you into plan mode where you can explore the codebase and design an implementation approach for user approval.
-
-## When to Use This Tool
-
-**Prefer using EnterPlanMode** for implementation tasks unless they're simple. Use it when ANY of these conditions apply:
-
-1. **New Feature Implementation**: Adding meaningful new functionality
-   - Example: "Add a logout button" - where should it go? What should happen on click?
-   - Example: "Add form validation" - what rules? What error messages?
-
-2. **Multiple Valid Approaches**: The task can be solved in several different ways
-   - Example: "Add caching to the API" - could use Redis, in-memory, file-based, etc.
-   - Example: "Improve performance" - many optimization strategies possible
-
-3. **Code Modifications**: Changes that affect existing behavior or structure
-   - Example: "Update the login flow" - what exactly should change?
-   - Example: "Refactor this component" - what's the target architecture?
-
-4. **Architectural Decisions**: The task requires choosing between patterns or technologies
-   - Example: "Add real-time updates" - WebSockets vs SSE vs polling
-   - Example: "Implement state management" - Redux vs Context vs custom solution
-
-5. **Multi-File Changes**: The task will likely touch more than 2-3 files
-   - Example: "Refactor the authentication system"
-   - Example: "Add a new API endpoint with tests"
-
-6. **Unclear Requirements**: You need to explore before understanding the full scope
-   - Example: "Make the app faster" - need to profile and identify bottlenecks
-   - Example: "Fix the bug in checkout" - need to investigate root cause
-
-7. **User Preferences Matter**: The implementation could reasonably go multiple ways
-   - If you would use AskUserQuestion to clarify the approach, use EnterPlanMode instead
-   - Plan mode lets you explore first, then present options with context
-
-## When NOT to Use This Tool
-
-Only skip EnterPlanMode for simple tasks:
-- Single-line or few-line fixes (typos, obvious bugs, small tweaks)
-- Adding a single function with clear requirements
-- Tasks where the user has given very specific, detailed instructions
-- Pure research/exploration tasks (use the Agent tool with explore agent instead)
-
-## What Happens in Plan Mode
-
-In plan mode, you'll:
-1. Thoroughly explore the codebase using Glob, Grep, and Read tools
-2. Understand existing patterns and architecture
-3. Design an implementation approach
-4. Present your plan to the user for approval
-5. Use AskUserQuestion if you need to clarify approaches
-6. Exit plan mode with ExitPlanMode when ready to implement
-
-## Examples
-
-### GOOD - Use EnterPlanMode:
-User: "Add user authentication to the app"
-- Requires architectural decisions (session vs JWT, where to store tokens, middleware structure)
-
-User: "Optimize the database queries"
-- Multiple approaches possible, need to profile first, significant impact
-
-User: "Implement dark mode"
-- Architectural decision on theme system, affects many components
-
-User: "Add a delete button to the user profile"
-- Seems simple but involves: where to place it, confirmation dialog, API call, error handling, state updates
-
-User: "Update the error handling in the API"
-- Affects multiple files, user should approve the approach
-
-### BAD - Don't use EnterPlanMode:
-User: "Fix the typo in the README"
-- Straightforward, no planning needed
-
-User: "Add a console.log to debug this function"
-- Simple, obvious implementation
-
-User: "What files handle routing?"
-- Research task, not implementation planning
-
-## Important Notes
-
-- This tool REQUIRES user approval - they must consent to entering plan mode
-- If unsure whether to use it, err on the side of planning - it's better to get alignment upfront than to redo work
-- Users appreciate being consulted before significant changes are made to their codebase
-</textarea>

package/concepts/en/Tool-EnterWorktree.md

@@ -1,56 +0,0 @@
-# EnterWorktree
-
-## Definition
-
-Creates an isolated git worktree and switches the current session into it. Only used when the user explicitly asks to work in a worktree.
-
-## Parameters
-
-| Name | Type | Required | Description |
-|---|---|---|---|
-| name | string | No | A name for the worktree. If not provided, a random name is generated. |
-
-## Use Cases
-
-**Good for:**
-- The user explicitly says "worktree" (e.g., "start a worktree", "work in a worktree", "create a worktree")
-
-**Not good for:**
-- The user asks to create/switch branches — use git commands instead
-- The user asks to fix a bug or work on a feature — use normal git workflow unless they specifically mention worktrees
-
-## Notes
-
-- Must be in a git repository, or have WorktreeCreate/WorktreeRemove hooks configured
-- Must not already be in a worktree
-
-## Original Text
-
-<textarea readonly>Use this tool ONLY when the user explicitly asks to work in a worktree. This tool creates an isolated git worktree and switches the current session into it.
-
-## When to Use
-
-- The user explicitly says "worktree" (e.g., "start a worktree", "work in a worktree", "create a worktree", "use a worktree")
-
-## When NOT to Use
-
-- The user asks to create a branch, switch branches, or work on a different branch — use git commands instead
-- The user asks to fix a bug or work on a feature — use normal git workflow unless they specifically mention worktrees
-- Never use this tool unless the user explicitly mentions "worktree"
-
-## Requirements
-
-- Must be in a git repository, OR have WorktreeCreate/WorktreeRemove hooks configured in settings.json
-- Must not already be in a worktree
-
-## Behavior
-
-- In a git repository: creates a new git worktree inside `.claude/worktrees/` with a new branch based on HEAD
-- Outside a git repository: delegates to WorktreeCreate/WorktreeRemove hooks for VCS-agnostic isolation
-- Switches the session's working directory to the new worktree
-- On session exit, the user will be prompted to keep or remove the worktree
-
-## Parameters
-
-- `name` (optional): A name for the worktree. If not provided, a random name is generated.
-</textarea>

package/concepts/en/Tool-ExitPlanMode.md

@@ -1,62 +0,0 @@
-# ExitPlanMode
-
-## Definition
-
-Exits plan mode and submits the plan for user approval. The plan content is read from a previously written plan file.
-
-## Parameters
-
-| Parameter | Type | Required | Description |
-|-----------|------|----------|-------------|
-| `allowedPrompts` | array | No | List of permission descriptions required for the implementation plan |
-
-Each element in the `allowedPrompts` array:
-
-| Field | Type | Required | Description |
-|-------|------|----------|-------------|
-| `tool` | enum | Yes | The applicable tool, currently only supports `Bash` |
-| `prompt` | string | Yes | Semantic description of the operation (e.g., "run tests", "install dependencies") |
-
-## Use Cases
-
-**Good for:**
-- The plan is complete in plan mode and ready for user approval
-- Only for implementation tasks that require writing code
-
-**Not good for:**
-- Pure research/exploration tasks — no need to exit plan mode
-- Asking the user "Is the plan okay?" — that is exactly what this tool does, do not use AskUserQuestion for that
-
-## Notes
-
-- This tool does not accept plan content as a parameter — it reads from a previously written plan file
-- The user will see the plan file content for approval
-- Do not use AskUserQuestion to ask "Is the plan okay?" before calling this tool, as that would be redundant
-- Do not mention "the plan" in questions, since the user cannot see the plan content before ExitPlanMode
-
-## Original Text
-
-<textarea readonly>Use this tool when you are in plan mode and have finished writing your plan to the plan file and are ready for user approval.
-
-## How This Tool Works
-- You should have already written your plan to the plan file specified in the plan mode system message
-- This tool does NOT take the plan content as a parameter - it will read the plan from the file you wrote
-- This tool simply signals that you're done planning and ready for the user to review and approve
-- The user will see the contents of your plan file when they review it
-
-## When to Use This Tool
-IMPORTANT: Only use this tool when the task requires planning the implementation steps of a task that requires writing code. For research tasks where you're gathering information, searching files, reading files or in general trying to understand the codebase - do NOT use this tool.
-
-## Before Using This Tool
-Ensure your plan is complete and unambiguous:
-- If you have unresolved questions about requirements or approach, use AskUserQuestion first (in earlier phases)
-- Once your plan is finalized, use THIS tool to request approval
-
-**Important:** Do NOT use AskUserQuestion to ask "Is this plan okay?" or "Should I proceed?" - that's exactly what THIS tool does. ExitPlanMode inherently requests user approval of your plan.
-
-## Examples
-
-1. Initial task: "Search for and understand the implementation of vim mode in the codebase" - Do not use the exit plan mode tool because you are not planning the implementation steps of a task.
-2. Initial task: "Help me implement yank mode for vim" - Use the exit plan mode tool after you have finished planning the implementation steps of the task.
-3. Initial task: "Add a new feature to handle user authentication" - If unsure about auth method (OAuth, JWT, etc.), use AskUserQuestion first, then use exit plan mode tool after clarifying the approach.
-</textarea>

package/concepts/en/Tool-Glob.md

@@ -1,39 +0,0 @@
-# Glob
-
-## Definition
-
-A fast file pattern matching tool that works with any codebase size. Returns matching file paths sorted by modification time.
-
-## Parameters
-
-| Parameter | Type | Required | Description |
-|-----------|------|----------|-------------|
-| `pattern` | string | Yes | Glob pattern (e.g., `**/*.js`, `src/**/*.ts`) |
-| `path` | string | No | Search directory, defaults to the current working directory. Do not pass "undefined" or "null" |
-
-## Use Cases
-
-**Good for:**
-- Finding files by filename pattern
-- Finding all files of a specific type (e.g., all `.tsx` files)
-- Locating files first when searching for a specific class definition (e.g., `class Foo`)
-- Multiple Glob calls can be issued in parallel within a single message
-
-**Not good for:**
-- Searching file contents — use Grep instead
-- Open-ended exploration requiring multiple rounds of searching — use Task (Explore type) instead
-
-## Notes
-
-- Supports standard glob syntax: `*` matches single level, `**` matches multiple levels, `{}` matches alternatives
-- Results are sorted by modification time
-- Preferred over the `find` command in Bash
-
-## Original Text
-
-<textarea readonly>- Fast file pattern matching tool that works with any codebase size
-- Supports glob patterns like "**/*.js" or "src/**/*.ts"
-- Returns matching file paths sorted by modification time
-- Use this tool when you need to find files by name patterns
-- When you are doing an open ended search that may require multiple rounds of globbing and grepping, use the Agent tool instead
-- 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.</textarea>

package/concepts/en/Tool-Grep.md

@@ -1,57 +0,0 @@
-# Grep
-
-## Definition
-
-A powerful content search tool based on ripgrep. Supports regular expressions, file type filtering, and multiple output modes.
-
-## Parameters
-
-| Parameter | Type | Required | Description |
-|-----------|------|----------|-------------|
-| `pattern` | string | Yes | Regular expression search pattern |
-| `path` | string | No | Search path (file or directory), defaults to current working directory |
-| `glob` | string | No | Filename filter (e.g., `*.js`, `*.{ts,tsx}`) |
-| `type` | string | No | File type filter (e.g., `js`, `py`, `rust`), more efficient than glob |
-| `output_mode` | enum | No | Output mode: `files_with_matches` (default), `content`, `count` |
-| `-i` | boolean | No | Case-insensitive search |
-| `-n` | boolean | No | Show line numbers (content mode only), default true |
-| `-A` | number | No | Number of lines to show after a match |
-| `-B` | number | No | Number of lines to show before a match |
-| `-C` / `context` | number | No | Number of lines to show before and after a match |
-| `head_limit` | number | No | Limit the number of output entries, default 0 (unlimited) |
-| `offset` | number | No | Skip the first N results |
-| `multiline` | boolean | No | Enable multiline matching mode, default false |
-
-## Use Cases
-
-**Good for:**
-- Searching for specific strings or patterns in the codebase
-- Finding where functions/variables are used
-- Filtering search results by file type
-- Counting the number of matches
-
-**Not good for:**
-- Finding files by filename — use Glob instead
-- Open-ended exploration requiring multiple rounds of searching — use Task (Explore type) instead
-
-## Notes
-
-- Uses ripgrep syntax (not grep); special characters like braces need escaping
-- `files_with_matches` mode returns only file paths, most efficient
-- `content` mode returns matching line content, supports context lines
-- Multiline matching requires setting `multiline: true`
-- Always prefer the Grep tool over `grep` or `rg` commands in Bash
-
-## Original Text
-
-<textarea readonly>A powerful search tool built on ripgrep
-
-  Usage:
-  - 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.
-  - Supports full regex syntax (e.g., "log.*Error", "function\s+\w+")
-  - Filter files with glob parameter (e.g., "*.js", "**/*.tsx") or type parameter (e.g., "js", "py", "rust")
-  - Output modes: "content" shows matching lines, "files_with_matches" shows only file paths (default), "count" shows match counts
-  - Use Agent tool for open-ended searches requiring multiple rounds
-  - Pattern syntax: Uses ripgrep (not grep) - literal braces need escaping (use `interface\{\}` to find `interface{}` in Go code)
-  - Multiline matching: By default patterns match within single lines only. For cross-line patterns like `struct \{[\s\S]*?field`, use `multiline: true`
-</textarea>

package/concepts/en/Tool-NotebookEdit.md

@@ -1,33 +0,0 @@
-# NotebookEdit
-
-## Definition
-
-Replaces, inserts, or deletes specific cells in a Jupyter notebook (.ipynb file).
-
-## Parameters
-
-| Parameter | Type | Required | Description |
-|-----------|------|----------|-------------|
-| `notebook_path` | string | Yes | Absolute path of the notebook file |
-| `new_source` | string | Yes | New content for the cell |
-| `cell_id` | string | No | ID of the cell to edit. In insert mode, the new cell is inserted after this ID |
-| `cell_type` | enum | No | Cell type: `code` or `markdown`. Required in insert mode |
-| `edit_mode` | enum | No | Edit mode: `replace` (default), `insert`, `delete` |
-
-## Use Cases
-
-**Good for:**
-- Modifying code or markdown cells in a Jupyter notebook
-- Adding new cells to a notebook
-- Deleting cells from a notebook
-
-## Notes
-
-- `cell_number` is 0-indexed
-- `insert` mode inserts a new cell at the specified position
-- `delete` mode deletes the cell at the specified position
-- The path must be an absolute path
-
-## Original Text
-
-<textarea readonly>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.</textarea>

package/concepts/en/Tool-Read.md

@@ -1,56 +0,0 @@
-# Read
-
-## Definition
-
-Reads file contents from the local filesystem. Supports text files, images, PDFs, and Jupyter notebooks.
-
-## Parameters
-
-| Parameter | Type | Required | Description |
-|-----------|------|----------|-------------|
-| `file_path` | string | Yes | Absolute path of the file |
-| `offset` | number | No | Starting line number (for reading large files in segments) |
-| `limit` | number | No | Number of lines to read (for reading large files in segments) |
-| `pages` | string | No | PDF page range (e.g., "1-5", "3", "10-20"), only applicable to PDFs |
-
-## Use Cases
-
-**Good for:**
-- Reading code files, configuration files, and other text files
-- Viewing image files (Claude is a multimodal model)
-- Reading PDF documents
-- Reading Jupyter notebooks (returns all cells with outputs)
-- Reading multiple files in parallel to gather context
-
-**Not good for:**
-- Reading directories — use the `ls` command in Bash instead
-- Open-ended codebase exploration — use Task (Explore type) instead
-
-## Notes
-
-- The path must be an absolute path, not a relative path
-- Reads the first 2000 lines of a file by default
-- Lines exceeding 2000 characters will be truncated
-- Output uses `cat -n` format, with line numbers starting at 1
-- Large PDFs (over 10 pages) must specify the `pages` parameter, max 20 pages per call
-- Reading a non-existent file returns an error (does not crash)
-- Multiple Read calls can be issued in parallel within a single message
-
-## Original Text
-
-<textarea readonly>Reads a file from the local filesystem. You can access any file 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. It is okay to read a file that does not exist; an error will be returned.
-
-Usage:
-- The file_path parameter must be an absolute path, not a relative path
-- By default, it reads up to 2000 lines starting from the beginning of the file
-- You can optionally specify a line offset and limit (especially handy for long files), but it's recommended to read the whole file by not providing these parameters
-- Any lines longer than 2000 characters will be truncated
-- Results are returned using cat -n format, with line numbers starting at 1
-- This tool allows Claude Code to read images (eg PNG, JPG, etc). When reading an image file the contents are presented visually as Claude Code is a multimodal LLM.
-- This tool can read PDF files (.pdf). For large PDFs (more than 10 pages), you MUST provide the pages parameter to read specific page ranges (e.g., pages: "1-5"). Reading a large PDF without the pages parameter will fail. Maximum 20 pages per request.
-- This tool can read Jupyter notebooks (.ipynb files) and returns all cells with their outputs, combining code, text, and visualizations.
-- This tool can only read files, not directories. To read a directory, use an ls command via the Bash tool.
-- 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.</textarea>