---
updatedAt: 2026-08-17T08:11:10.000Z
agentTools:
  siteIndex: https://docs.jfrog.com/llms.txt
  projectIndex: https://docs.jfrog.com/security/llms.txt
---

# How to Curate VS Code Remote Repositories

**Use Case**

JFrog Curation now supports curating **VS Code remote repositories** created using the **Artifactory AI Editor Extensions**.<br />This capability allows organizations to apply all standard curation controls, such as policies, conditions, and repository connections, to VS Code extensions fetched through supported remote repositories.

Workflow Steps

1. **Create a VS Code Remote Repository**<br />Before you can curate VS Code repositories, create a remote repository for AI Editor Extensions.<br />Follow the setup instructions in the [AI Editor Extension Repositories](https://jfrog.com/help/r/jfrog-artifactory-documentation/ai-editor-extension-repositories) documentation.<br />**When you create the repository, you must change the default URL to** [**https://open-vsx.org/vscode/gallery**](https://open-vsx.org/vscode/gallery)**.**
2. **Verify Environment Compatibility**<br />Ensure your environment meets the following requirements:
   * **Artifactory Version:** 7.125.6 or later
   * **Xray Version:** 3.131.15 or later
3. **Connect the Remote Repository in Curation**<br />In the JFrog Platform, go to **Administration > Curation > Remote Repositories**, and connect your newly created VS Code repository.<br />Once connected, it behaves like any other supported package type in Curation.
4. **Apply Curation Policies and Conditions**
   * Create curation policies and add conditions as needed.
   * The AIEditorExtensions package type supports **all condition types** available in Curation.
   * Apply the relevant actions (e.g., Block, Allow, Notify) per policy.
5. **Monitor Audit Events**<br />After applying policies, audit events for VS Code packages will appear under **Application > Curation > Audit Events**.

<Callout icon="📘" theme="info">
  Because the IDE plugin retries downloads multiple times, you may see several repeated block entries in the audit logs. This is expected behavior and not a system issue.
</Callout>

<br />