Agent plugins in VS Code
AI agents: See llms.txt for documentation discovery and navigation. Documentation articles are also available as Markdown by appending .md to the article URL. Join VS Code at Microsoft Ignite or catch the sessions online. A year of VS Code, wrapped. Explore the highlights. Agent plugins in VS Code View as Markdown Ask in VS Code Ask in VS Code Insiders Agent plugins package related customizations, such as skills, agents, and tool integrations, so you can install them together.
For example, a testing plugin can include a test-running skill, review agent, and reporting integration that are intended to work together. This article shows you how to discover and install a plugin, verify it with a document-review workflow, and manage the installation. To create or package a plugin, see the agent plugin authoring reference . If you only need a project rule or a single skill, start with an individual customization .
Choose a bundle when its components support a workflow you want to adopt together. Note Enable or disable support for agent plugins with the chat.plugins.enabled Open in VS Code Open in VS Code Insiders setting. What plugins provide Plugins can provide the following customizations. The selected harness and plugin format determine which components are available. Capability Purpose Skills Instructions, scripts, and resources for specialized workflows MCP servers Tools for interacting with external systems Canvases Canvases is in preview and might change before it becomes generally available.
Interactive visual surfaces shared by you and the agent in supported Copilot sessions Custom agents Specialized roles and tool configurations Custom instructions Reusable guidance supplied as plugin rules Hooks Commands that run at specific points in the agent's workflow Automation templates Starting prompts and schedules to review before creating an automation Slash commands Commands you can invoke with / in chat Installed plugin customizations appear alongside your locally defined ones.
For example, skills from a plugin show up in Configure Skills , and MCP servers appear in the MCP server list. Installing an automation template does not start an automation; review and configure it before turning it on. Check the plugin's supported clients and components before installing. See Cross-tool compatibility for how portable and client-specific components differ. Caution Plugins can include hooks and MCP servers that run code on your machine.
Review the plugin contents and publisher before installing, especially for plugins from community marketplaces. Discover and install plugins Use the Agent Customizations editor to browse marketplaces and install plugins. You can also install a plugin directly from a Git repository or local folder. Available plugins and actions depend on the selected agent harness and organization policy. Choose your harness before installing and use the same harness to verify the result.
The walkthrough below uses Copilot . Plugin marketplaces let you reuse workflows published by the community or your organization. If you don't need a bundle, the Customization Marketplace also provides discovery for individual skills and MCP servers from supported sources. Install a plugin from a marketplace Open the Agent Customizations editor by running Chat: Open Customizations from the Command Palette, selecting Open Customizations in the Chat view title bar, or selecting Customizations in the Agents window sidebar.
Browse available plugins from your configured marketplaces . Available sources depend on the selected harness and organization policy. In the unified Customization Marketplace (Preview), select Browse and use the source menu to choose a plugin marketplace, or search across available sources. If the unified Browse page isn't available, select Plugins and then Browse Marketplace to find available plugins. Select a plugin to review its publisher, included customizations, and Plugin README , when provided.
Select Install to install a plugin. The first time you install a plugin from a new marketplace, VS Code shows a trust prompt. Review the marketplace source before confirming. Trusting a marketplace doesn't replace reviewing each plugin's contents, setup requirements, or future updates. Install a plugin from source You can install a plugin directly from a Git repository or local folder without adding a full marketplace first.
For a repository URL, VS Code clones and installs the plugin. In the Agent Customizations editor, select Plugins , then select the add ( + ) button next to User or Workspace , depending on where you want to install the plugin. Enter a Git repository URL (for example, https://github.com/rwoll/markdown-review ) or a local folder path. Alternatively, run Chat: Install Plugin from Source from the Command Palette. Try a document-review workflow The community Markdown Review plugin provides a skill that opens a Markdown file in a browser for comments and returns the feedback to the agent.
Use it to check the full workflow, not just whether a plugin appears in the editor. For this example, open a local project with the Copilot harness. Install Node.js with npx available and use a machine where you can open a local browser. Review the plugin's README and bundled markdown-plan-review-feedback skill before installing. Install the plugin from source using https://github.com/rwoll/markdown-review . Choose User for a personal trial.
Start a fresh Copilot session in your project and enter: Create plugin-review.md with a short documentation plan for this repository. Use the Markdown Review plugin to open it for my review, then summarize the feedback I submit. Do not change application code. Inspect the skill and tool activity. Review any approval request before the publisher's CLI runs. The workflow launches a temporary local web server and opens the review UI in your browser.
Add a comment to the document in the browser, then submit your feedback. Check that the agent receives your comment and accurately summarizes it. Confirm that the Markdown file exists and no application code changed. The workflow succeeds when you can trace your browser comment back to the agent's response. If the browser doesn't open or feedback doesn't return, check the plugin's runtime requirements and command output before repeating the request.
After the trial, close the review tab and remove plugin-review.md if you don't need it. You can uninstall the plugin if you don't want to keep the workflow. Share and install plugins with deep links Plugin providers can create shareable deep links to help users register a marketplace or install a specific named plugin directly in VS Code. Important Agent plugins are distinct from VS Code extensions. To install an extension from the Visual Studio Marketplace, use vscode:extension/<publisher>.<extensionName> as described in URL handling .
Install a specific plugin Use the chat-plugin/install route to add a marketplace (if not already registered) and install a specific named plugin: vscode://chat-plugin/install?source=<url-encoded-source>&plugin=<url-encoded-plugin-name> Parameters: source (required): The remote marketplace source (for example, owner/repo or a Git repository URL). plugin (required): The exact plugin name declared in the plugin manifest ( plugin.json ).
Do not include the @marketplace qualifier used by the CLI. URL-encode parameter values (for example, / as %2F ). Example: vscode://chat-plugin/install?source=owner%2Frepo&plugin=plugin-name When opened, VS Code asks the user to confirm adding the marketplace and installing the plugin. If confirmed, VS Code registers the marketplace, locates the plugin by name, installs it into the Copilot Agent Host session, and opens the Agent Customizations editor filtered to the plugin.
Add a plugin marketplace To register a marketplace without installing any plugins, use the chat-plugin/add-marketplace route: vscode://chat-plugin/add-marketplace?ref=<url-encoded-source> Exa
The rest of this page is on the live site.