[FEATURE] Expose built-in Grep/Glob tools in the VS Code native extension (parity with standalone CLI)

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

In a Claude Code session running inside the VS Code native extension (not the integrated terminal running the CLI, the native extension integration), the tool palette exposed to the model does not include the standalone Grep or Glob tools that exist in the CLI. The exposed tools in my session were: Agent, Artifact, AskUserQuestion, Bash, Edit, Read, ReportFindings, ScheduleWakeup, Skill, ToolSearch, Workflow, Write — plus some deferred MCP/cron tools discoverable via ToolSearch. No Grep/Glob tool was present or discoverable.

I confirmed this is not something controllable via project or user .claude/settings.json: the permissions.allow/deny/ask arrays only gate specific Bash command patterns (e.g. "Bash(git commit *)"), not which top-level built-in tools (Read/Write/Edit/Grep/Glob/Bash) are exposed to the model. There is no "tools"/"disabledTools"/"enabledTools" key documented or present in any settings file that affects this.

This means users of the VS Code native extension lose the dedicated, presumably more efficient ripgrep-based search tool that CLI users get, with no way to restore it from user-level config.

Proposed Solution

Expose the same built-in tool palette in the VS Code native extension that the standalone CLI provides, specifically Grep and Glob, so behavior and performance are consistent across both integrations. If there is a deliberate reason these are omitted in the extension (e.g. an editor-native search API is used internally instead), please document that in the extension's release notes or docs, since today it just silently appears as "the tool doesn't exist" with no explanation or toggle.

Alternative Solutions

Current workaround: use the Bash tool directly with grep/rg (ripgrep), which is available and functionally equivalent, just not exposed as a dedicated first-class tool call. Switching to the standalone CLI restores full tool parity, but that defeats the purpose of using the native VS Code extension.

Priority

Low - Nice to have

Feature Category

File operations

Use Case Example

1. I'm working in a large repo inside VS Code using the native Claude Code extension.
2. I ask Claude to find all call sites of a function across the codebase.
3. Today it falls back to Bash(grep -r ...), which works but isn't the dedicated Grep tool the CLI would use.
4. With native Grep/Glob support, tool-use would be more consistent and predictable across CLI and extension sessions.

Additional Context

Environment: macOS (Darwin), VS Code native Claude Code extension, project uses a git repo with an existing .claude/settings.json (only Bash command allow/deny/ask rules, no tool-level restrictions).