Copilot Extensions move to public beta
GitHub has made Copilot Extensions available in public beta to all Copilot users, opening the platform for any developer or organization to build and distribute extensions. The move follows a limited public beta that began in May and represents the next step in turning Copilot from a standalone assistant into an extensible platform for AI-assisted development.
Extensions integrate third-party tools directly into the Copilot experience, allowing the AI to interact with external databases, testing frameworks, deployment services, and other development infrastructure through natural language—without leaving the editor. Developers can now build private extensions tailored to their organization's internal APIs, coding standards, and workflows, then share them publicly through the GitHub Marketplace if they choose.
Enterprise customization
For organizations, the value proposition centers on context. A Copilot Extension can encode proprietary tools, frameworks, and practices, so the assistant understands company-specific patterns rather than just generic coding conventions. The goal is to reduce context-switching, documentation lookups, and the cognitive overhead of remembering internal processes—letting developers focus on core business problems while Copilot handles the organizational knowledge.
Early adopters are already exercising this capability. Octopus, for example, built an extension that provides on-demand expertise on the company's systems and processes directly within Copilot Chat.
Generative AI and agentic assistants are creating a new wave of developer tools that are context-aware and can be tailored with company knowledge. Tools such as log analysis, vulnerability monitoring, database migration assistance, and project management become accessible through conversational interactions with Copilot.
Onboarding new members of a DevOps team becomes so much easier with our Copilot Extension. There is no abstraction between written instructions like ‘Deploy the latest release of the 'Frontend WebApp' project to the 'Production' environment’ and that execution of that instruction. People no longer need to learn a new UI or platform to execute the vast majority of their day-to-day tasks.
A distribution channel for tool builders
For third-party developers, the public beta represents access to a large installed base: over 77,000 organizations, 1.8 million paid subscribers, and more than 500,000 students, teachers, and open source maintainers use Copilot. Extensions offer a way to reach that audience, integrated into the coding workflow rather than bolted on as a separate tool. Users can interact with these services via natural language queries inside the editor.
Developers and Ops teams often have to navigate tool and knowledge silos in order to follow the real-time impact of source code on system performance, which delays remediation and slows innovation. The New Relic extension for GitHub Copilot helps teams align on observability best practices by making our 16+ years of expertise directly accessible from Copilot Chat in GitHub.com and the IDE.
At Atlassian, we view Copilot Extensions as a major boost in reducing context switching for developers as they write code. With our new Rovo-powered Atlassian extension for GitHub Copilot, developers can look up all of their requirements, testing plans, issues, and docs from Jira or Confluence directly in Copilot Chat at GitHub.com or their IDE—saving time and frustration.
An official toolkit and resources
To support extension development, GitHub has published the Copilot Extensions Toolkit, centralizing documentation, step-by-step tutorials, a CLI, samples, and SDKs.
GitHub also demonstrated the process by building a Copilot Extension for GitHub Models, showing how to bring external context into Copilot and work with it as part of the assistant's capabilities.
Road ahead
GitHub says it will observe how extensions are used, collect feedback, and refine the platform iteratively. The public beta is a first step toward a larger ecosystem: integrations available in the Marketplace, and the ability for any team to ship its own extensions for internal use or public distribution.
