[BUG] Accidentally leaving the mouse over autocomplete items highlights them

[JosXa]

Problem (one or two sentences)

When the autocompletions for a @ context or / command opens and the mouse cursor happens to be over one of the autocomplete items, it automatically highlights that entry instead of the topmost one - even if the mouse doesn't move.

Context (who is affected and when)

This is quite annoying as you typically click into the "Type a message..." field in order to put the cursor there, meaning the mouse will be in a bad spot and trigger the autocomplete items constantly. When you type out or paste the full name of a file, you expect the Enter key to pick the correct result (the topmost one) - but that gets messed up because the mouse has accidentally preselected a different item in the meantime.

Reproduction steps

qjHEY3WJyQ.mp4

Expected result

Mouse cursor should be ignored when it doesn't move

Actual result

Mouse highlights results immediately

Suggested Fix

Make autocompletion work like in Ctrl+P in VS Code, with a selected item state that can be changed by UpArrow and DownArrow keys, and mere hover highlighting without actually preselecting anything when only hovering over with the mouse:

Code_d8NE2sSWv7.mp4

I think people are much more like to want to use their keyboard for navigating through the selections anyway. Hovering over them with the mouse should not preselect them, causing Enter to potentially select the wrong file when you know you spelled out the full name of a file.

Variations tried (optional)

No response

App Version

v3.28.16

API Provider (optional)

None

Model Used (optional)

No response

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

[roomote]

I'm exploring a potential fix for the autocomplete mouse hover issue and will open a PR to share progress.

[JosXa]

@roomote Edited the post. Explore potential fix now.

[roomote]

I've seen your comment @JosXa and I'm exploring a potential fix now. I'll implement separate hover and selection states for the autocomplete, similar to VS Code's Ctrl+P behavior, to prevent accidental mouse highlighting from interfering with keyboard navigation.

[roomote]

Opened a PR with my attempt at addressing this issue: #8616. Feedback welcome!

The fix adds mouse movement tracking to prevent autocomplete items from being highlighted when the mouse cursor happens to be over them without actually moving. This makes the behavior consistent with VS Code's standard autocomplete.

[roomote]

@JosXa I've implemented a fix for the autocomplete mouse hover issue and opened PR #8617.

The solution adds a smart hover detection system that distinguishes between intentional mouse movement and incidental cursor position. Items will now only show hover state after the mouse has actually moved (more than 5 pixels), preventing the unwanted highlighting when the autocomplete opens with the cursor over an item.

Key improvements:

• Keyboard navigation now works independently with clear visual selection
• Mouse hover only activates after intentional movement
• The topmost item remains the default selection for Enter key
• All existing functionality preserved

The PR has passed initial checks and is ready for review. Feedback welcome!