What are GitHub Copilot Extensions

In this learning pathway module, we’ll cover the most common questions related to GitHub Copilot Extensions; what they are, how you get them, how you build them, and more.

GitHub Copilot Extensions are a way to enhance the capabilities of GitHub Copilot by integrating third-party tools and services directly into the Copilot Chat interface and more. These extensions enable you to interact with external systems, gather insights, and automate tasks without leaving your development environment. GitHub Copilot Extensions can help you streamline workflows, reduce context switching, and boost productivity. Whether it's managing databases, monitoring performance, or interacting with APIs, extensions make Copilot more versatile and powerful for you.

Where do extensions “light up”

Extensions can be used in multiple environments depending upon how you build them. They can support multiple experiences including Visual Studio Code, Visual Studio 2022 on Windows, and directly on GitHub.com. Copilot Extensions can be especially useful in scenarios where you need to integrate external tools with your workflows. For example, in Visual Studio Code, extensions can leverage the Language Model and Chat APIs to provide context-aware assistance, making it easier for developers to query databases, track issues, or manage deployments directly from their editor. You can also have an extension that surfaces information in all of the chat interfaces like the @github extension available with Copilot Enterprise. The seamless integration across these platforms ensures that you can stay in the flow, regardless of where you are working.

Getting Extensions: the GitHub Marketplace

Extensions can be found and installed through the GitHub Marketplace, which serves as a hub for publicly available extensions. You can browse a wide variety of extensions created by individual contributors, organizations, and GitHub Partners. Beyond Copilot Extensions, the Marketplace offers tools that enhance coding practices, integrate with CI/CD pipelines, or provide specialized assistance based on the technologies being used. Installing an extension is straightforward—you can search for the desired extension, review its features, and add it to your development environment with just a few clicks. In addition, administrators can install extensions for your entire organization.

Note that extensions built for a single platform, such as Visual Studio Code, might be published in other locations and installed differently. For example, Visual Studio Code extensions are available via the Visual Studio Marketplace  from which you can install Copilot-enabled extensions.

Who Can Build Copilot Extensions

GitHub Copilot Extensions can be built by anyone. You’ll want to consider who you’re targeting and where you want to surface your extension.Is the extension just for you? Do you want to have broad reach? No matter what you want to do, it’s quick and easy and you can just start coding. For organizations, there’s the added option of creating private extensions tailored to internal workflows, making it possible to extend Copilot’s capabilities in a way that aligns with company-specific needs which will require you coordinate with an organization administrator for access and deployment.

Regardless, you should consider if you want to share your extension with the world via the GitHub Marketplace. You’ll need to be a verified publisher and you might want to consider joining the GitHub Technology Partner Program, which provides additional support to increase your extensions reach and visibility. Developers publishing extensions must adhere to the guidelines set by GitHub, such as ensuring data privacy and security when interacting with external systems.