feat: make root search more fuzzy, clipboard search more exact

[pablopunk]

What

• Root search now uses scoreFuzzy() with a character-set fallback: after sequential matching fails, it checks if all query characters exist in the text (any order, multiplicity respected). This catches typos like "gmial" → "Gmail" where characters are in the wrong order. Score: 10 (below all other bands).

• Clipboard history search now requires minScore >= 50 (substring match minimum), rejecting the old score-20 fuzzy/sequential matches for more exact results.

• Other extension views and action panel filtering are unchanged.

Score bands (root search)

Score	Match type
100	Exact
80	Starts with
50	Substring
20	Sequential chars
10	Char-set (new — any order)
0	No match

Files

File	Change
src/search-ranking.ts	Added scoreFuzzy() with char-set fallback
src/electron/search-utils.ts	scoreNormalized now uses scoreFuzzy
src/filtering.ts	Added valuesMatchMinScore + minScore option to filters
src/App.tsx	Clipboard history filtering uses minScore: 50
src/search-ranking.test.ts	8 new tests for scoreFuzzy + updated scoreNormalized tests

Validation

• 26/26 search-ranking tests pass
• 68/68 full test suite passes
• TypeScript typecheck clean

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
nvm	Ready	Preview, Comment	Jun 20, 2026 9:19pm

[coderabbitai]

Warning

Review limit reached

@pablopunk, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 43 minutes and 30 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: a836a1d0-6e2a-4292-8ee2-5c801f9ac1c1

📥 Commits

Reviewing files that changed from the base of the PR and between a5c8fe1 and 1766bf0.

📒 Files selected for processing (5)

• src/App.tsx
• src/electron/search-utils.ts
• src/filtering.ts
• src/search-ranking.test.ts
• src/search-ranking.ts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}