[BUG] VSCode extension 2.1.27 ripgrep path resolves to C:\Users\vendor\ instead of extension directory

Description

The VSCode extension fails to find files when using @-mention because ripgrep path resolution is broken.

Error from logs

[error] Ripgrep search failed A system error occurred (spawn c:\Users\vendor\ripgrep\x64-win32\rg.exe ENOENT)
[warning] Ripgrep search failed, falling back to VSCode findFiles

Root Cause

In extension.js line 147, the ripgrep path is resolved as:

let e = path.resolve(__dirname, "..", "..", "..", "..")
let r = path.resolve(e, "vendor", "ripgrep")
// Windows: path.resolve(r, "x64-win32", "rg.exe")

This goes 4 directories up from __dirname, which from the extension install location:

• C:\Users\Jeremy Spiegel\.vscode\extensions\anthropic.claude-code-2.1.27-win32-x64
• 4 levels up = C:\Users\
• Result: C:\Users\vendor\ripgrep\x64-win32\rg.exe ❌

Ripgrep is also NOT bundled with the extension - only claude.exe is in resources/native-binary/.

Expected Behavior

Ripgrep should either be bundled with the extension or the path should resolve correctly.

Environment

• Extension version: 2.1.27-win32-x64
• OS: Windows 11
• VSCode version:

Version: 1.108.2 (user setup)
Commit: c9d77990917f3102ada88be140d28b038d1dd7c7
Date: 2026-01-21T13:52:09.270Z (1 wk ago)
Electron: 39.2.7
ElectronBuildId: 12953945
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.26200

Workaround

The VSCode findFiles fallback works but is slow (several seconds delay).