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

Resolved 💬 4 comments Opened Nov 1, 2025 by dimfeld Closed Nov 3, 2025

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 ↗

This issue has 4 comments on GitHub. Read the full discussion on GitHub ↗