[Bug] Slash command autocomplete selection doesn't follow filtered results

Status Fixed / completed
Maintainer reply ✓ Yes — bogini
Activity 4 comments · opened Nov 1, 2025 · closed Nov 3, 2025
💡 Likely answer: A maintainer (bogini, collaborator) responded on this thread — see the highlighted reply below.

Bug Description
The slash command autocomplete now sticks to the first item it selects, even if that item moves down the list as you type more.

For example, I have a command named address-ai-comments and a command named commit-push-pr. If I type /, it selects address-ai-comments because that's at the top. But then when I type /comm, the commit-push-pr command is first in the list as expected, but address-ai-comments remains selected and runs if I press Enter. I have to manually move the selection up to the top to get the command I want.

The selection only changes once I type enough letters that the initial selection address-ai-comments is totally gone from the list.

This just changed recently, not sure if it was in version 2.0.30 or 2.0.31.

Expected Behavior
As I type, the autocomplete should always select the "best" match at the top of the list unless I use arrow keys to select otherwise.

Environment Info

  • Platform: darwin
  • Terminal: WezTerm
  • Version: 2.0.31
  • Feedback ID: 0de7a3e5-6528-4c36-b5cf-a31fbfc08755

Errors

[]

View original on GitHub ↗

4 Comments

nick-durcholz-vectorsolutions · 11 months ago

This issue also occurs on linux using vscode terminal emulator and tilix. Does not appear to be platform or emulator specific.

bogini collaborator · 11 months ago

This should be fixed in 2.0.32.

dimfeld · 11 months ago

Confirmed. Thank you!

github-actions[bot] · 11 months ago

This issue has been automatically locked since it was closed and has not had any activity for 7 days. If you're experiencing a similar issue, please file a new issue and reference this one if it's relevant.