Copilot Extensions FAQ

Find answers to common questions about Extensions GitHub Copilot.

Dans cet article

General

This section answers common questions about Extensions GitHub Copilot.

What is the difference between a Extension GitHub Copilot and a Visual Studio Code chat participant?

Extensions GitHub Copilot and Visual Studio Code chat participants use the same backend platform to route requests to extensions. Both provide similar end-user experiences, integrate with Copilot Chat, and can leverage the Copilot API or other LLMs.

While they share similarities, below are several key differences:

  • Extensions GitHub Copilot and Visual Studio Code chat participants are accessed through different marketplaces.
  • Extensions GitHub Copilot are server-side extensions, requiring server infrastructure to build. These extensions provide a built-in connection to your GitHub workspaces, as set by your organization admin.
  • Visual Studio Code chat participants are client-side extensions that have read and write access to your local files. They do not require server infrastructure.
  • Extensions GitHub Copilot can be used in any editor where extensions are supported, while Visual Studio Code Chat Participants are only available in Visual Studio Code.

For more information, see About building Copilot Extensions.

Is indemnity provided for Extensions Copilot?

No, Extensions Copilot are not covered by GitHub Copilot’s indemnity policy. However, this exclusion applies only to issues that arise within extension chat threads.

Installing and using extensions does not affect indemnity coverage for any issues that occur while using other Copilot features such as code completion and chat.

Data and Permissions

This section explains what data is collected and shared when using Extensions Copilot.

What data is being collected and shared with Extensions Copilot?

The following data is shared when interacting with Extensions Copilot:

  • Data attached to your account and Copilot Chat usage, such as GitHub user ID, and timestamps of messages.
  • Past messages within the chat thread where you are invoking an extension. Only one extension can be used per thread, preventing data sharing across extensions. The data retention period for thread context is 30 days.
  • Any additional organization and repository data that is authorized for the extension by your organization admin. Admins installing extensions must approve access to the required permissions prior to completing installation.
  • For Copilot Chat dans GitHub, if your admin has approved the extension to access repository or organization metadata , that data will be shared as well.

What permissions are required for Extensions Copilot?

Les autorisations varient selon l’extension, en fonction du niveau d’autorisation requis par l’extension afin de rĂ©pondre Ă  votre requĂȘte. Vous pouvez afficher les autorisations requises sur la page d’installation de l’extension, situĂ©e aprĂšs l’étape des informations de facturation et avant l’étape d’installation et d’autorisation.

Pour les dĂ©veloppeurs : au minimum, les autorisations Copilot Chat doivent ĂȘtre dĂ©finies sur « En lecture seule ». Les autorisations supplĂ©mentaires peuvent inclure l’exĂ©cution d’actions d’écriture sur d’autres surfaces et l’autorisation d’accĂšs en lecture aux donnĂ©es au niveau du rĂ©fĂ©rentiel et de l’organisation dans GitHub.

Pour les gĂ©nĂ©rateurs : en plus de ce qui prĂ©cĂšde, vous pouvez Ă©galement demander le contexte local Ă  l’éditeur d’un utilisateur pour personnaliser davantage les rĂ©ponses. Pour ce faire, les autorisations Contexte de l’éditeur Copilot doivent ĂȘtre dĂ©finies sur « En lecture seule ». Les utilisateurs recevront une notification leur demandant de fournir l’autorisation requise.

Pour plus d’informations sur les autorisations GitHub App, consultez Choix des autorisations pour une application GitHub

Who can provide permissions for Extensions Copilot to access organization resources?

Only organization admins can grant permissions for Extensions Copilot to access organization resources. Organization members may encounter cases where an extension cannot access a repository or query context. This typically happens because the organization admin has not yet provided permissions or authorized the extension. See Granting permissions to access organization resources.

Can a user use Extensions Copilot that the organization has not provided permissions for?

Yes, any user can install and use Extensions Copilot. However, to query organization resources and repositories, an extension must be installed and authorized by an organization admin. See Granting permissions to access organization resources.

Users should contact their organization admin to request installation and authorization. Company context cannot be accessed without admin permissions.

Policies

This section covers administrative policies for Extensions Copilot

How do I control which Extensions Copilot can be used in my enterprise?

Enterprise admins can disable Extensions Copilot across their enterprise by setting the Extensions Copilot policy to "Disabled" or "No Policy".

Is there an allowlist/blocklist at the enterprise level?

No, there is no allowlist or blocklist at the enterprise level.

As a member of an organization, how can I get access to Extensions Copilot?

To access Extensions Copilot as a member of an organization, the organization that assigned you a GitHub seat must enable the Extensions Copilot policy. Additionally, the same organization must install and authorize the extension to access any organization owned repositories.

For example, if you are a member of multiple organizations and Organization A has assigned you a GitHub seat, you will only have access to extensions if Organization A has enabled the policy. If Organization B has enabled extensions but you do not have access, it is because Organization A has disabled the Extensions Copilot policy.