Copilot Extensions FAQ

Find answers to common questions about Extensões do GitHub Copilot.

Neste artigo

General

This section answers common questions about Extensões do GitHub Copilot.

What is the difference between a Extensão do GitHub Copilot and a Visual Studio Code chat participant?

Extensões do 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:

  • Extensões do GitHub Copilot and Visual Studio Code chat participants are accessed through different marketplaces.
  • Extensões do 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.
  • Extensões do 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 Extensões do Copilot?

No, Extensões do 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 Extensões do Copilot.

What data is being collected and shared with Extensões do Copilot?

The following data is shared when interacting with Extensões do 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 Chat do Copilot no 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 Extensões do Copilot?

As permissões variam de acordo com a extensão, dependendo do nível de autorização exigido pela extensão para responder à consulta. Você pode exibir as permissões necessárias na página de instalação da extensão, localizada após a etapa de informações de cobrança e antes da etapa de instalação e autorização.

Para desenvolvedores: no mínimo, as permissões do Copilot Chat devem ser definidas como "Somente leitura". Permissões adicionais podem incluir a execução de ações de gravação em outras superfícies, e a autorização de acesso de leitura a dados no nível da organização e do repositório no GitHub.

Para criadores: além do indicado acima, você também pode solicitar o contexto local de um editor do usuário para ajustar ainda mais as respostas. Para fazer isso, as permissões do Copilot Editor Context devem ser definidas como "Somente leitura". Os usuários serão notificados para fornecer a autorização necessária.

Para obter mais informações sobre as permissões do GitHub App, confira Escolhendo permissões para um Aplicativo GitHub

Who can provide permissions for Extensões do Copilot to access organization resources?

Only organization admins can grant permissions for Extensões do 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 Extensões do Copilot that the organization has not provided permissions for?

Yes, any user can install and use Extensões do 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 Extensões do Copilot

How do I control which Extensões do Copilot can be used in my enterprise?

Enterprise admins can disable Extensões do Copilot across their enterprise by setting the Extensões do 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 Extensões do Copilot?

To access Extensões do Copilot as a member of an organization, the organization that assigned you a GitHub seat must enable the Extensões do 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 Extensões do Copilot policy.