Extension registry - Editor - IDE 1.x - Docs - Kiro Loading image... Product * About Kiro * IDE * CLI * Web * Mobile * Crew * Pricing * Downloads For * Enterprise * Startups * Students Community * Overview * Ambassadors * Discord * Events * Powers * Shop * Showcase Resources * Docs * Blog * Changelog * FAQs * Report a bug * Suggest an idea * Billing support Social * * * * * * * English Site Terms License Responsible AI Policy Legal Privacy Policy Cookie Preferences English Loading image... * Apps * CLI * Web * Enterprise * Pricing * Docs * Community * Resources SIGN IN DOWNLOADS Loading image... Get Started Installation Authentication Your first project Models Overview Available models Reasoning effort Features How Kiro works Specs Steering Hooks MCP Permissions Custom agents Agent Skills Powers Cloud sessions Compaction Kiroignore Checkpoints and rewind Built-in tools Configuration scopes IDE 1.x What's new in 1.0 Setup & First Run Editor Interface Keyboard shortcuts Source control Multi-root workspaces Extension registry Chat Experimental Troubleshooting 0.x reference CLI What's new in 3.0 Setup & First Run Terminal UI Chat Voice mode Headless mode ACP Auto complete Experimental 2.x reference Crew Quick start Installation Running 24/7 Chat Agent Capabilities Features Interfaces Apps System & storage Configuration Security Troubleshooting Web Setup & First Run Identity Center Connect your repositories Working with the agent Autonomous mode Automations Memory Configuration Sync Sandbox Mobile - Preview Overview Commands and Reference CLI commands Slash commands Built-in tools Exit codes Settings Billing Overview Managing your subscription Upgrading your plan Downgrading your plan Cancelling your plan Purchasing add-on credits Managing your payments Managing usage notifications Managing your taxes Contacting billing support Deleting your account Related questions Enterprise Concepts Onboarding quickstart Connecting your identity provider Deployment options Subscribe your team Manage subscriptions Governance Monitor and track Settings Managed updates Billing IAM Supported regions Privacy and Security Overview Data protection Code references Compliance validation Infrastructure security IAM permissions Firewalls, proxies, and data perimeters VPC endpoints (AWS PrivateLink) Guides Overview Language support Learn by playing Migration Migrating from Q Developer Migrating from VSCode Upgrading from Q CLI * Docs * * IDE 1.x * * Editor * * Extension registry Copy page View as Markdown Custom extension registry Copy page View as Markdown By default, Kiro uses the IDE extension marketplace at https://open-vsx.org . You can use OS-specific "policies" to configure Kiro to use a different extension registry; for example, a private registry for your organization that contains a limited set of vetted extensions. Windows To specify a custom extension registry for Kiro IDE on Windows devices, create a registry-based policy (.admx/.adml files) to define a new ExtensionGalleryServiceUrl Windows registry entry for Kiro IDE and set its value to your extension registry URL. For more information on Windows registry-based policies, refer to Microsoft's documentation . Below are minimal, sample .admx and .adml files that define a new registry entry for Kiro IDE extensions. First, ensure you have administrative privileges on your test PC . Save the contents of the first XML snippet below into C:\Windows\PolicyDefinitions\Kiro.admx , and the contents of the second into C:\Windows\PolicyDefinitions\en-US\Kiro.adml . Next, open the Local Group Policy Editor by opening the Run dialog (Windows+R), typing gpedit.msc , and hitting Enter. Go to Computer Configuration > Administrative Templates > Kiro > Extensions . Double-click on the "ExtensionGalleryServiceUrl" setting, select "Enabled", and under "Options", set the value of "ExtensionGalleryServiceUrl" to the URL of your private registry. Hit Ok to close the dialog, then close the policy editor. Restart Kiro to confirm it is now using your private extension registry. Once verified, use an MDM solution or AD Group Policy profile to deploy it at scale across all your Windows devices. Kiro.admx sample: xml <?xml version="1.0" encoding="utf-8"?> < policyDefinitions revision = " 1.1 " schemaVersion = " 1.0 " > < policyNamespaces > < target prefix = " Kiro " namespace = " AWS.Policies.Kiro " /> </ policyNamespaces > < resources minRequiredRevision = " 1.0 " /> < supportedOn > < definitions > < definition name = " Supported_0_11_133 " displayName = " $(string.Supported_0_11_133) " /> </ definitions > </ supportedOn > < categories > < category displayName = " $(string.Application) " name = " Application " /> < category displayName = " $(string.Category_extensionsConfigurationTitle) " name = " extensionsConfigurationTitle " > < parentCategory ref = " Application " /> </ category > </ categories > < policies > < policy name = " ExtensionGalleryServiceUrl " class = " Both " displayName = " $(string.ExtensionGalleryServiceUrl) " explainText = " $(string.ExtensionGalleryServiceUrl_extensions_gallery_serviceUrl) " key = " Software\Policies\Microsoft\Kiro " presentation = " $(presentation.ExtensionGalleryServiceUrl) " > < parentCategory ref = " extensionsConfigurationTitle " /> < supportedOn ref = " Supported_0_11_133 " /> < elements > < text id = " ExtensionGalleryServiceUrl " valueName = " ExtensionGalleryServiceUrl " required = " true " /> </ elements > </ policy > </ policies > </ policyDefinitions > Kiro.adml sample: xml <?xml version="1.0" encoding="utf-8"?> < policyDefinitionResources revision = " 1.0 " schemaVersion = " 1.0 " > < displayName /> < description /> < resources > < stringTable > < string id = " Application " > Kiro </ string > < string id = " Supported_0_11_133 " > Kiro &gt; = 0.11.133 </ string > < string id = " Category_extensionsConfigurationTitle " > Extensions </ string > < string id = " ExtensionGalleryServiceUrl " > ExtensionGalleryServiceUrl </ string > < string id = " ExtensionGalleryServiceUrl_extensions_gallery_serviceUrl " > Custom extension marketplace URL </ string > </ stringTable > < presentationTable > < presentation id = " ExtensionGalleryServiceUrl " > < textBox refId = " ExtensionGalleryServiceUrl " > < label > ExtensionGalleryServiceUrl: </ label > </ textBox > </ presentation > </ presentationTable > </ resources > </ policyDefinitionResources > macOS To specify a custom extension registry for Kiro IDE on macOS devices, create a configuration profile (.mobileconfig file) with the ExtensionGalleryServiceUrl property pointing to your registry URL, and then deploy this profile to all your macOS devices via an MDM solution. For more information on macOS configuration profiles, refer to Apple's documentation . Below is a minimal, sample .mobileconfig file that configures Kiro IDE to point to a custom registry. To use this sample, create a file on disk, e.g., kiro.mobileconfig , with these contents, replacing the placeholder UUIDs in both PayloadUUID entries and the second PayloadIdentifier entry with unique UUIDs, and the placeholder URL for ExtensionGalleryServiceUrl with the URL of your private registry. Adjust any other properties as needed. Next, open System Settings , navigate to General > Device Management , and drag-and-drop the kiro.mobileconfig file into that screen to install. Restart Kiro to confirm it is now using your private extension registry. Once verified, use your MDM solution to deploy it at scale across all your macOS devices. kiro.mobileconfig sample: xml <?xml version="1.0" encoding="UTF-8"?> <! DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd" > < plist version = " 1.0 " > < dict > < key > PayloadDisplayName </ key > < string > Kiro Configuration Profile </ string > < key > PayloadType </ key > < string > Configuration </ string > < key > PayloadVersion </ key > < integer > 1 </ integer > < key > PayloadIdentifier </ key > < string > dev.kiro.desktop </ string > < key > PayloadUUID </ key > < string > 12345678-1234-1234-1234-123456789012 </ string > < key > PayloadContent </ key > < array > < dict > < key > PayloadDisplayName </ key > < string > Kiro </ string > < key > PayloadType </ key > < string > dev.kiro.desktop </ string > < key > PayloadVersion </ key > < integer > 1 </ integer > < key > PayloadIdentifier </ key > < string > dev.kiro.desktop.12345678-1234-1234-1234-123456789012 </ string > < key > PayloadUUID </ key > < string > 12345678-1234-1234-1234-123456789012 </ string > < key > ExtensionGalleryServiceUrl </ key > < string > https://registry.example.com/extensions </ string > </ dict > </ array > </ dict > </ plist > Linux To specify a custom extension registry for Kiro IDE on Linux devices, create a policy (policy.json file) with the ExtensionGalleryServiceUrl property pointing to your registry URL, and then deploy this policy to all your Linux devices via an MDM solution. Below is a minimal policy.json file that configures Kiro IDE to point to a custom registry. To use this sample, save the below contents to /etc/kiro/policy.json , replacing the placeholder URL with the URL of your private registry. Restart Kiro to confirm it is now using your private extension registry. Once verified, use your MDM solution to deploy it at scale across all your Linux devices. policy.json sample: json { "ExtensionGalleryServiceUrl" : "https://registry.example.com/extensions" } Page updated: August 4, 2026 Multi-root workspaces Chat