Look for Cursor where its installer puts it - #808
Merged
Conversation
Only %ProgramFiles%\Cursor\ was searched. Cursor's own installer defaults to a per user install under %LocalAppData%\Programs\cursor\, so an ordinary installation was not found unless the machine happened to also have a system wide one. VS Code's definition already lists both locations for the same reason. Additive: the existing directory is kept and the per user one is searched first, so nothing that resolves today stops resolving. Not verified against an install - I have no Cursor here - so this rests on the documented layout rather than on having watched it resolve. One thing I deliberately did not change on the same evidence: PathCommandName is still Cursor.exe, while Cursor, being a VS Code fork, most likely ships a cursor.cmd shim the way VS Code ships code.cmd. VS Code's definition uses the shim for both names. If that holds for Cursor too then the PATH lookup here is still wrong, and someone with it installed should check.
This was referenced Aug 26, 2026
This was referenced Aug 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Only %ProgramFiles%\Cursor\ was searched. Cursor's own installer defaults to a
per user install under %LocalAppData%\Programs\cursor, so an ordinary
installation was not found unless the machine happened to also have a system
wide one. VS Code's definition already lists both locations for the same reason.
Additive: the existing directory is kept and the per user one is searched first,
so nothing that resolves today stops resolving.
Not verified against an install - I have no Cursor here - so this rests on the
documented layout rather than on having watched it resolve. One thing I
deliberately did not change on the same evidence: PathCommandName is still
Cursor.exe, while Cursor, being a VS Code fork, most likely ships a cursor.cmd
shim the way VS Code ships code.cmd. VS Code's definition uses the shim for both
names. If that holds for Cursor too then the PATH lookup here is still wrong,
and someone with it installed should check.