GitHub Copilot X

The “X” represents a placeholder for where we intend GitHub Copilot to become available, and what we expect it to be capable of doing (e.g. “Copilot “, “Copilot “). It is extending the product from one experience, code completion, to X experiences across the developer’s workflow. GitHub Copilot will always need to be so much more tomorrow than what it currently is today.

Additionally, The “X”, indicates the magnitude of impact we intend to have on developer achievement. Therefore, it’s a statement of intent, and a commitment to developers, as we collectively enter the age of AI. We want the industry to be confident in GitHub Copilot, and for engineering teams to view it as the neXus of their future growth.

While we are unable to guarantee access to each feature, you can submit your interest by joining the waitlist to preview the features that you are interested in. Joining one waitlist does not confirm your interest in more than one feature, so you must join each separately. Please note we currently don’t have guaranteed timelines for access.

Once you get access to preview a feature, please keep in mind that what you are getting access to is considered beta or a technical preview, meaning the feature may still have some kinks to work out.

We’ve been committed to innovating responsibly with GitHub Copilot from the start and will continue to invest in the AI-powered developer experience of the future. And as a Microsoft company, we are committed to making sure AI systems are developed responsibly and in ways that warrant people’s trust. Here are just some of the principles we are committed to with GitHub Copilot:

• Keeping it professional. We apply sentiment analysis to suggestions to keep slang, slurs, and hate speech out of GitHub Copilot responses.

• Improving code quality. We don’t just pass-through any suggestion produced by the model. We also subject every suggestion to filters that evaluate code quality. While we can’t guarantee that every suggestion is perfect, our filters are getting better all the time and nudging developers toward better quality code.

• Protecting user data. We know that user edit actions, source code snippets, and URLs of repositories and file paths are sensitive data. Consequently, several measures of protection are applied, including data encryption both in transit and at rest as well as strict requirements for GitHub personnel to access data.