GitHub Copilot Extensions can now access local context in your editor and github.com to provide you with richer and more tailored responses.
As a developer, you can benefit from context passing when interacting with extensions. Passing context to extensions will continue to maintain security through permission controls set by your administrators and content exclusion rules.
Available contexts by development environment
Environment | client.file | client.selection | github.repository | github.current-url | Additional contexts |
---|---|---|---|---|---|
Visual Studio Code | ✔️ | ✔️ | ✔️ | X | Repository owner and branch |
Visual Studio | ✔️ | ✔️ | ✔️ | X | Repository owner and branch |
github.com | X | X | ✔️ | ✔️ | Repository information and other GitHub resources |
GitHub Mobile | X | X | X | ✔️ | X |
JetBrains IDEs | X | X | X | X | X |
Local context is not passed to extensions by default.
Requirements for developers
- Access to GitHub Copilot Extensions
- Admin authorization to install on organization-owned repos
Requirements for builders
- Explicit requests to receive editor context, configured in your GitHub app settings
- Update your APIs to handle new reference types and account for certain references only being available in certain contexts
Connect with our community in our Discussion Forum, or relay your feedback here.