Cline v3.86.2 リリース — VS Code 1.122以降のファイル検索バグを修正 Cline Releases v3.86.2

Cline released version v3.86.2 on June 1, 2026, a focused patch addressing a regression that broke @ file mentions and workspace file search for users running VS Code 1.122 or later.

The root cause lies in a change to the internal binary layout introduced by the @vscode/ripgrep-universal package in VS Code 1.122. ripgrep, the fast Rust-based line-oriented search tool, has long served as VS Code's file search backend. The ripgrep-universal wrapper simplifies cross-platform distribution by bundling platform-specific binaries, but VS Code 1.122 reorganized where those binaries live on disk. Cline's path resolution logic was still targeting the old locations, causing lookups to fail silently and breaking file mention functionality for affected users.

The fix introduces a two-step resolution strategy: Cline first attempts to locate the binary according to the new per-platform directory structure introduced in 1.122, then falls back to the legacy ripgrep paths if the new location is not found. This approach restores compatibility across both older and newer VS Code installations without requiring users to take any action.

The @ file mention feature is a core part of Cline's workflow, allowing users to inject specific source files as context for the AI assistant. When this breaks, the practical utility of the tool drops considerably, making a fast patch release the right call. It's also a reminder of the recurring challenge extension authors face: VS Code moves quickly, and changes to bundled dependencies or internal binary layouts can cascade into downstream breakage with little warning.

ripgrep itself remains one of the most respected tools in the developer tooling ecosystem. Written in Rust by Andrew Gallant, it outperforms traditional grep and alternatives like The Silver Searcher on most real-world search tasks, which is why it has become the de facto choice for editors and IDEs. The ripgrep-universal packaging layer was designed to ease distribution across Windows, macOS, and Linux, but the tradeoff is that any structural reorganization of that package can silently break tools that assume a fixed binary path.

For Cline users on VS Code 1.122 or later who encountered broken file search or @ mention errors, updating to v3.86.2 should resolve the issue immediately. The patch is narrow in scope and carries minimal risk of introducing new regressions.