IntelliJ Styled Search

IntelliJ Styled Search adds an IntelliJ IDEA-like project search panel to VS Code. It opens as a movable overlay, streams workspace results, and shows an editable Monaco preview for the selected match.

Features

• Find in project from a movable IntelliJ-style overlay.
• Search the selected text directly from the editor context menu or keybinding.
• Preview matches in an embedded Monaco editor with hover, completions, and editor-style highlighting when renderer capture is available.
• Narrow large searches with a local trigram index, then verify results with ripgrep.
• Support literal, regex, case-sensitive, whole-word, and multi-line searches.
• Keep results responsive by streaming matches and showing candidate files while ripgrep is still running.

Commands

MCP Usage

This repository includes project MCP config files:

• .mcp.json for Claude Code project-scoped MCP discovery.
• .codex/config.toml for Codex project-scoped MCP configuration when supported by the installed Codex CLI.

The MCP clients spawn a stdio proxy, but the proxy still needs the VS Code extension's localhost endpoint. In trusted workspaces the extension auto-starts that endpoint by default. Each VS Code window binds an OS-assigned free port and writes the actual URL to .codeidx/mcp-server.json, so multiple projects can run at the same time without sharing a fixed port. The extension also writes .codeidx/codeidx-mcp-stdio.js, which lets project MCP configs launch the proxy through node without depending on a global codeidx-mcp binary.

Manual stdio proxy command:

codeidx-mcp stdio --workspace .

From a workspace where the extension has started, use the generated project launcher:

node .codeidx/codeidx-mcp-stdio.js stdio --workspace .

The proxy discovers the VS Code endpoint from .codeidx/mcp-server.json. If you disable intellijStyledSearch.mcpAutoStart, run IntelliJ Search: Start Codeidx MCP Server in that VS Code window before starting Codex or Claude Code. You can also pass the URL explicitly:

codeidx-mcp stdio --url http://127.0.0.1:<port>/mcp

Codex example:

codex mcp add codeidx -- node .codeidx/codeidx-mcp-stdio.js stdio --workspace .

If your Codex CLI does not load project-scoped .codex/config.toml, run the codex mcp add command once to register it in your user config.

Claude Code example:

claude mcp add --transport stdio codeidx -- node .codeidx/codeidx-mcp-stdio.js stdio --workspace .

Claude Code also auto-detects the checked-in .mcp.json after you approve the project-scoped MCP server.

Useful MCP self-check tools:

• mcp_health: verifies the MCP connection and reports endpoint, discovery file, capabilities, and index status.
• mcp_test: compares codeidx_search_code against a bounded grep-like workspace scan and reports result overlap plus estimated token savings.

Native OR search is available through queries; the engine unions per-term index candidates before verification, so this avoids broad regex alternation for simple keyword sets:

{
  "queries": ["AlphaService", "BetaService", "GammaService"],
  "query_kind": "literal",
  "query_operator": "any"
}

By default, codeidx_search_code protects common dependency/generated/sensitive paths such as node_modules/**, out/**, dist/**, graphql-codegen/**, and .env*. To deliberately search a normally excluded path, pass a narrow include plus an exclude policy override:

{
  "query": "SomeGeneratedSymbol",
  "include_globs": ["out/**/*.js"],
  "exclude_policy": "custom_only"
}

Use exclude_policy: "none" only when you intentionally want to ignore both default excludes and exclude_globs. Both override modes bypass intellijStyledSearch.excludeGlobs for that MCP request; keep include_globs narrow when searching dependency or generated trees. For generated/codegen searches, include_generated: true disables generated excludes and uses a bounded full scan with a larger MCP file-size cap so large generated files are not silently missed.

Example prompt for Codex or Claude:

Use the codeidx MCP mcp_health tool, then run mcp_test with query "UserService".

Keybindings

Settings

Runtime Notes

On first activation, the extension attempts to install a platform-specific ripgrep binary into VS Code's extension global storage. If that install fails or the platform is unsupported, it falls back to VS Code's bundled ripgrep when available, and finally to the JavaScript search path.

The editable preview relies on VS Code renderer internals. If the overlay appears but the preview falls back to plain DOM rendering, run IntelliJ Search: Reinject Renderer Patch (Recovery).

Development

npm install
npm run compile
npm test
npm run bench:zoekt -- --files 10000,50000,100000

npm run bench:zoekt saves a timestamped artifact plus latest.json under artifacts/benchmarks/zoekt/. The artifact includes the raw benchmark response, wall-clock runtime, git commit, Rust toolchain versions, and host metadata so repeated runs stay comparable.

Deployment

Deployment and release steps now live in DEPLOY.md.

Short version:

• vsce package builds a lightweight VSIX from the current .vscodeignore.
• That default VSIX does not include target/**, so it relies on first-run Cargo builds for the Rust zoekt runtime.
• A self-contained VSIX requires prebuilding target/release/zoek-rs and target/release/ijss-rebuild, then allowing those artifacts through .vscodeignore before packaging.

Quick local package:

vsce package