Skip to content

feat(cmdk): Add search keywords to reduce no-result queries#119056

Draft
cursor[bot] wants to merge 2 commits into
masterfrom
cursor/command-palette-no-result-queries-5865
Draft

feat(cmdk): Add search keywords to reduce no-result queries#119056
cursor[bot] wants to merge 2 commits into
masterfrom
cursor/command-palette-no-result-queries-5865

Conversation

@cursor

@cursor cursor Bot commented Jul 6, 2026

Copy link
Copy Markdown
Contributor

Summary

Adds keyword synonyms to command-palette (cmd+k) actions to eliminate two clusters of no-result searches surfaced by the Amplitude dashboard ci7qhhad (chart Cmd+K: Top No-Result Queries, last 30 days).

Each query below was verified against the scoreNode fzf logic in commandPalette.tsx: fzf runs case-insensitively against each candidate string ([label, details, ...keywords]) independently, so a query only matches if it is a subsequence within a single string. I confirmed each targeted query did not match any existing candidate before, and now does, without adding redundant keywords (e.g. auth tokens, api key, SENTRY_AUTH_TOKEN, DSN, Client Keys were already reachable and left untouched).

Counts are anonymized aggregates over the last 30 days (summed across the reporting interval).

Changes

Action Keywords Added Top Queries Covered (count)
Organization Tokens & Personal Tokens (userOrgNavigationConfiguration) create token, create new token, create auth token, new token create new tok (26), create tok (10), Create New Token (8)
Client Keys (DSN) (project navigationConfiguration) sdk setup, sdk, setup, install, installation sdk setu (17), SDK Setup (13), setup (11), sdk (7)

Why these targets:

  • Token creation — users searching to make a new auth/API token had no match: the token pages are labeled Organization Tokens / Personal Tokens and none of their keywords contained create. These pages are where tokens are created, so they're the right destination.
  • SDK setupSDK Setup is only a settings section name (not a searchable item), so sdk/setup matched nothing. Client Keys (DSN) is the primary SDK-setup page (the DSN is the core of SDK install), so it's the natural landing spot.

Not addressed (and why)

  • Queries already reachable on master (auth tokens, api key, SENTRY_AUTH_TOKEN, DSN, Client Keys, Alerts — the latter matches alert rules on Create Alert).
  • project slug, SENTRY_ORG, SENTRY_PROJECT, insights — already handled by the still-open PR feat(cmdk): Add search keywords to reduce no-result queries #118642, so intentionally not duplicated here.
  • Non-Latin / single-char / punctuation gibberish, one-off short-IDs and project slugs, typos, billing terms (getsentry, not this repo), and gated features (web vitals / Frontend).

Testing

  • Added recall cases to the existing commandPaletteGlobalActions.spec.tsx search recall suite for create new token, create token, and sdk setup. All 24 tests pass — they render the real palette and assert the actions surface.
  • pnpm run lint:js <changed files> and pnpm run typecheck are green.
  • Separately verified each targeted query is a subsequence of a newly-added keyword and was not a subsequence of any pre-existing candidate.

No customer information is included; all Amplitude values are anonymized aggregate counts.

Open in Web View Automation 

cursoragent and others added 2 commits July 6, 2026 13:07
Co-authored-by: Nicholas Meisenheimer <souredoutlook@users.noreply.github.com>
Drop project slug / SENTRY_ORG / SENTRY_PROJECT keywords that overlap with
open PR #118642, keeping this change focused on the net-new token-creation
and SDK-setup query clusters.

Co-authored-by: Nicholas Meisenheimer <souredoutlook@users.noreply.github.com>
@github-actions github-actions Bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Jul 6, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant