Autocomplete Should Prioritize Real Options

Feedback
1

Hey there!

I love the cursor auto-complete, but I often find that it suggests completions for functions that don’t exist. Take this screenshot as an example:

image
image1716×258 44.7 KB

It is suggesting that I use the function get_user_with_uuid when that function doesn’t exist. Not only does it not exist, the function I actually want is get_user_with_property.

Notice that the function I want is currently highlighted in the VS Code suggestion, and the cursor auto-complete is suggesting something wrong. When I press tab, the cursor auto-complete is prioritized over the real option, and it types: get_user_with_uuid(uuid).

I often catch myself needing to click on a VS Code suggestion instead of pressing tab because cursor is suggesting something wrong, and it has higher priority for tab.

Maybe there’s a way to add the existing options to the auto-complete context with higher weight? Maybe there’s a way to prioritize the existing options on tab? I don’t know what the solution is, but it’s annoying to press tab when the correct option is highlighted, only to have something different written.

4 Likes
2

Has your codebase been indexed?

3

Yep! It was fully indexed, but just in case I just deleted it and re-indexed.
I’ll post back in a few days about whether re-indexing helped the situation.

4

I have the same problem and it’s incredibly frustrating.

VSCode suggests REAL options, I hit tab, and suddenly I’ve picked a hallucinated option from Cursor by mistake.

This leads me to turning Cursor autocomplete off for hours at a time.

5

Came here, created a user and replied just for this. Really hope someone can come up with a good solution to this soon.

I’m contemplating adding a shortcut to toggle AI autocomplete on/off (somethig like this: Fully disable tab autocomplete / suggestions by toggle)

But then the same shortcut should also toggle the default VSCode keybindings - and that’s beyond my json-settings-expertice-level :person_shrugging: :weary:

6

Hey, while maybe not a perfect fix, in 0.46 you can now rebind the Tab key, so you can separate the normal auto-complete from Tab!

1 Like
7

It would be super nice to have guidance on this, I tried it and its not really reasonable to modify this when one wants to still use tab but have it behave correctly with the intellisense suggestions. Same goes for the escape key, it doesnt quite work 100% of the time and its hard to understand why for someone who isn’t deep in modifying keybindings.