Cursor Usage Tracker (Extension)

Showcase
53

Cursor’s lack of documentation on this issue is terrible.

They make no mention of the fact that the “Marketplace” in Cursor is not the official Visual Studio Marketplace, so users (and developers like yourself) are constantly wondering why extensions won’t show up when searching, or why extensions imported from VSC don’t update. :man_shrugging:

Your extension shows up fine in Visual Studio Code:

image
image521×253 16.1 KB

But no one will ever find it in Cursor (and each update has to be manually installed from a .vsix file):
image
image392×251 12.7 KB

Here’s proper documentation on the topic:

Extensions + Marketplace

Being a vscode based editor, **** gets additional features by installing VS Code extensions. Unfortunately, as Microsoft prohibits usages of the Microsoft marketplace by any other products or redistribution of .vsix files from it, in order to use VS Code extensions in non-Microsoft products those need to be installed differently.

By default, the product.json file is set up to use open-vsx.org as extension gallery, which has an adapter to the Marketplace API used by VS Code. Since that is a rather new project, you will likely miss some extensions you know from the VS Code Marketplace. You have the following options to obtain such missing extensions:

  • Ask the extension maintainers to publish to open-vsx.org in addition to the VS Code Marketplace. The publishing process is documented in the Open VSX Wiki.
  • Create a pull request to this repository to have the @open-vsx service account publish the extensions for you.
  • Download and install the vsix files, for example from the release page in their source repository.

How to use the Open VSX Registry

As noted above, the Open VSX Registry is the pre-set extension gallery in ****. Using the extension view in **** will therefore by default use it. See this article for more information on the motivation behind Open VSX…