Copilot Extensions FAQ

Find answers to common questions about Расширения GitHub Copilot.

В этой статье

General

This section answers common questions about Расширения GitHub Copilot.

What is the difference between a Расширение GitHub Copilot and a Visual Studio Code chat participant?

Расширения 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:

  • Расширения GitHub Copilot and Visual Studio Code chat participants are accessed through different marketplaces.
  • Расширения 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.
  • Расширения 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 Расширения Copilot?

No, Расширения 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 Расширения Copilot.

What data is being collected and shared with Расширения Copilot?

The following data is shared when interacting with Расширения 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 в 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 Расширения Copilot?

Разрешения зависят от расширения в зависимости от уровня авторизации, который требуется расширению для ответа на запрос. Вы можете просмотреть необходимые разрешения на странице установки расширения, расположенные после шага сведений о выставлении счетов, а также перед этапом установки и авторизации.

Для разработчиков: как минимум разрешения **** должны иметь значение "Только для чтения". Дополнительные разрешения могут включать выполнение действий записи на других поверхностях и авторизацию доступа на чтение к данным репозитория и уровня организации в GitHub.

Для построителей: помимо приведенного выше, вы также можете запросить локальный контекст из редактора пользователя для дальнейшего изменения ответов. Для этого разрешения контекста **** редактора Copilot должны иметь значение "Только для чтения". Пользователи получат уведомление о предоставлении требуемой авторизации.

Дополнительные сведения о разрешениях GitHub App см. в разделе Выбор разрешений для приложения GitHub

Who can provide permissions for Расширения Copilot to access organization resources?

Only organization admins can grant permissions for Расширения 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 Расширения Copilot that the organization has not provided permissions for?

Yes, any user can install and use Расширения 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 Расширения Copilot

How do I control which Расширения Copilot can be used in my enterprise?

Enterprise admins can disable Расширения Copilot across their enterprise by setting the Расширения 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 Расширения Copilot?

To access Расширения Copilot as a member of an organization, the organization that assigned you a GitHub seat must enable the Расширения 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 Расширения Copilot policy.