Introduction
AI Editor Extension repositories in Artifactory act as a secure caching proxy for IDE extensions such as Cursor, Kiro, Windsurf, and VS Code. By proxying public marketplaces like the Visual Studio Marketplace, Artifactory enables you to control which plugins that developers can use.
1. Creating an AI Editor Extension Remote Repository
To centrally control VS Code extensions, the first step is to create a remote repository that proxies a trusted upstream extension registry.
Steps to Create the Repository
-
Navigate to: Administration → Repositories → Create Repository
-
Click Remote
-
Select the AI Editor Extension package type
-
Provide a repository key, for example: <repo-name>-vscode-remote
Set the remote URL to the curated upstream: https://open-vsx.org
-
Save the configuration
This repository now serves as the enforcement point through which all VS Code extension downloads must pass. Developers continue using VS Code as usual, but every extension request now flows through Artifactory.
2. Configuring VS Code to Use Artifactory
To ensure developers download extensions through Artifactory instead of public markets, VS Code must be configured accordingly.
Steps
-
Open AI Editor Extension Remote Repository SetMeUp instructions for the repository.
-
Update the following files in VS Code installation:
-
-
product.json
-
settings.json
-
Restart VS Code.
3. Download the Extensions
Install the extensions through Extensions sidebar in VS Code.
Install the extensions using the CLI:
code --install-extension <PUBLISHER>.<EXTENSION_NAME>
Example: code --install-extension aws-toolkit-vscode.vsix
Conclusion
AI Editor Extension repositories in Artifactory provide a centralized way to manage IDE extensions. By proxying public marketplaces, it routes all extension requests through Artifactory without changing developer workflows.
This ensures only approved and trusted extensions are installed across the organization.