Text of code.visualstudio.com › docs › agent-customization › overview as Styx crawled it on Nov 18, 2026. The page may have changed since. Only its words are kept, without pictures or layout, and only the first part of a long page.

Open the live page

Customize agents for your workflow

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. Customize agents for your workflow View as Markdown Ask in VS Code Ask in VS Code Insiders Agent customizations adapt agents to your coding standards, workflows, and development systems.

Start by looking for an existing skill, plugin, or integration in a customization marketplace before creating your own. This guide helps you find, install, and verify customizations in Visual Studio Code, or create project-specific guidance. To understand how customization types differ and work together, see Agent customization concepts . Choose how to customize Start with a recurring task or an observed problem, such as the agent using the wrong test command.

Choose a representative task and define the result you expect. If the agent already meets your needs, don't add a customization. Put one-time requirements in the current request instead. If you want to Start with Adopt an existing workflow or packaged setup Browse customization marketplaces for skills, plugins, and integrations Stop repeating project commands and conventions Create or refine project instructions Reuse a multi-step process specific to your team Create or adapt an agent skill Give a recurring role focused guidance and tools Create a custom agent Connect an external service Use a Copilot connector Copilot connectors is in preview and might change before it becomes generally available. or add an MCP server Run an action at specific events of the agent's workflow Configure a hook To understand what each type contributes, see customization building blocks .

Agent Customizations editor The Agent Customizations editor brings discovery, authoring, and management into one place: Discover reusable skills, plugins, and integrations through the Customization Marketplace (Preview). Inspect customizations by type and source to see what is available. Create and edit instructions, skills, custom agents, and supported configurations using inline editors and forms. Manage availability with the enablement and tool-selection controls supported by the selected harness.

Available actions depend on the customization type, source, and harness. Some entries are read-only. The editor shows customizations for the selected session , not a combined list for all sessions. Switching sessions can change what appears because the harness, workspace, or execution environment differs. You can see the active harness in the editor's title bar. The editor can also list disabled items. A listed customization isn't necessarily used in every request: verify it with a representative task.

To open the Agent Customizations editor: Select a session and harness for which you want to configure customizations. Open the Agent Customizations editor: Agents window : select Customizations in the left sidebar. Chat view : select Open Customizations in the title bar, or run Chat: Open Customizations from the Command Palette ( ⇧⌘P (Windows, Linux Ctrl+Shift+P ) ). Use the tabs in the editor to navigate between different customization types, such as skills, custom agents, hooks, and MCP servers.

The experimental Extensions section also lets you install and manage extensions in the Agents window . For remote hosts and Dev Containers, see Manage customizations for remote sessions . Important If the Agent Customizations editor shows Migrations User customization migration is experimental and might change or be removed. , Copilot cannot use one or more customizations in their current location or format. Select Migrations to review the required work, and follow Migrate Copilot customizations in VS Code for detailed steps.

Reuse customizations across harnesses For new customizations, select the intended session before creating them in the editor. The editor offers locations and configuration fields for that harness. When reusing existing customizations, check more than the file's presence: Location : personal customizations can live in different directories for each harness. Format : skills use a shared format, but custom-agent fields and hook configuration can differ.

Behavior : referenced tools, scripts, and commands must work in the target session's environment. After adapting a customization, verify it in a session using the target harness. Discover and install existing customizations (Preview) Use the customization marketplace to find a workflow or integration you can reuse instead of building it from scratch. The unified Browse page in the Agent Customizations editor brings together available sources, including plugin marketplaces, GitHub Feed, and Copilot connectors Copilot connectors is in preview and might change before it becomes generally available. .

The list of available sources and installation actions depends on the selected harness and organization policy. You can install an individual skill or a plugin that bundles related customizations, such as skills, custom agents, hooks, and MCP servers. For a service integration, find an MCP server or connect a supported service without server setup. To find and install a customization: Open the Agent Customizations editor and select Browse .

Use the source menu to browse all sources or select a specific available source, such as GitHub Feed or an individual plugin marketplace. Search by name or use a type filter, such as @type:skill or @type:mcp . Select an item and review its publisher, source, installation details, and any setup requirements. Select Install and choose a scope when prompted for a destination. For Copilot connectors Copilot connectors is in preview and might change before it becomes generally available. , select Connect and complete authorization instead.

If your team shares plugins through another marketplace, select Configure Marketplaces from the source menu to add or manage plugin marketplaces . Adding a marketplace makes its plugins available to browse. It doesn't install them. After installation, complete any publisher setup and verify the customization with a representative task. For type-specific guidance, see install a skill , install a plugin , or find an MCP server .

Marketplace availability The Browse page appears when a marketplace source is available. Marketplace discovery is enabled by default with chat.customizations.marketplace.enabled Open in VS Code Open in VS Code Insiders . If Browse isn't available, check that the setting is enabled and your organization permits Editor preview features . Disabling that policy forces the unified Browse experience and Copilot connectors off.

See organization and enterprise settings . The experimental GitHub Feed source is enabled by default for harnesses that provide marketplace search. Local sessions don't provide this source, and organization policy can restrict access. Use the chat.customizations.marketplace.sources.publicFeed.enabled Open in VS Code Open in VS Code Insiders setting to show or hide this source. For plugin discovery without the unified Browse page, follow the plugin installation guide .

Create a customization For file-based customizations, use the editor to create a file at user or workspace scope : Select the intended session and confirm its harness, workspace, and execution environment. Open the Agent Customizations editor and select a customization type. Select the + button next to User or Workspace for your chosen scope. Enter a name and choose a storage location when prompted. Edit the customization in the inline editor, which provides syntax highlighting and validation.

Review and save the customization. You can also run the Chat: New <customization-type> command from the Command Palette ( ⇧⌘P (Windows, Linux Ctrl+Shift+P ) ). The command creates the corresponding file in a supported location for that customization type. To add

The rest of this page is on the live site.