Slash command autocomplete selects wrong item when filtering with Korean IME

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

When filtering custom slash commands with Korean IME input, the highlighted/selected autocomplete item is not the first matching command. Pressing Enter executes the wrong highlighted command.

Example: typing /주 shows /주석 as the first list item, but /완료검증 (which does not match 주) remains highlighted. Enter runs /완료검증 instead of /주석.

This appears related to Korean IME composition (isComposing) and/or the selection index not resetting when the filtered command list updates.

Steps to Reproduce

  1. Create custom slash commands with Korean names under .cursor/commands/ (e.g. /주석, /완료검증, /쿼리추출).
  2. Open Agent/Chat input in Cursor IDE.
  3. Switch to Korean IME and type /주.
  4. Observe the slash command autocomplete popup: /주석 is first, but a different item (e.g. /완료검증) is highlighted.
  5. Press Enter.

Expected Behavior

Enter should select the best/first matching command (/주석). While Korean IME composition is active, Enter should not confirm a mismatched highlighted item. When the filtered list updates, the highlight should reset to the top match.

Operating System

Windows 10/11

Version Information

Version: 3.15.6
VSCode Version: 1.128.0
Commit: a1f686545fd0ce8917bbd2449f733551a9bce420
OS: Windows_NT x64 10.0.26200 (Windows 11 Pro)
IME: Korean (Hangul)

Additional Information

Workarounds:

  • Click the correct command with the mouse
  • Press Arrow Up to re-select the first item, then Enter
  • Commit IME composition first (e.g. Space), then Enter
  • Use ASCII command names to avoid IME path

Related class of issues: CJK IME Enter handling without checking KeyboardEvent.isComposing.
Screenshot available showing /주 typed, /주석 first in list, but /완료검증 highlighted.

Does this stop you from using Cursor

No - Cursor works, but with this issue

vv
vv333×425 16.6 KB

5

Hey, thanks for the detailed report. The steps, version, and screenshot help a lot. From the screenshot I can see you typed /주, and /주석 is first in the list, but a different item is highlighted, so Enter selects the wrong one.

You got the root cause right. The highlight doesn’t reset to the top match when the filtered list updates, and IME composition plus Enter makes it worse. This is an issue we’re already tracking. I can’t share a timeline yet, but I’ll post in the thread when there’s an update.

For now, the most reliable workarounds are the ones you listed:

  • Confirm composition first with Space, then press Enter
  • Or press ArrowUp to move the highlight to the first item, then press Enter
  • Or click the command with the mouse

If you notice the highlight behaves differently with other keyboard layouts or in other versions, let me know and I’ll add it to our notes.