Troubleshooting common issues with GitHub Copilot

For questions about the general use of GitHub Copilot, product impact, human oversight, and privacy, see the comprehensive list of GitHub Copilot FAQs.

If GitHub Copilot stops working, check GitHub's Status page for any active incidents.

Unable to use the GitHub Copilot extension in the IDE

We recommend you follow the quickstart guide for GitHub Copilot while setting up GitHub Copilot on your machine. For more information, see Inicio rápido para GitHub Copilot.

The GitHub Copilot extension is frequently updated to fix bugs and add new features. It's important to keep your extension up to date because older clients cannot communicate with the GitHub Copilot servers. Update your GitHub Copilot extension on all the machines you have it installed.

Si usas un plan de Copilot para una cuenta de cuenta de usuario administrada en GHE.com, tendrás que actualizar algunos valores antes de iniciar sesión. See Using GitHub Copilot with an account on GHE.com.

For more information about configuring GitHub Copilot in a supported IDE, see Configuring GitHub Copilot in your environment.

GitHub Copilot not working in some files

If you're using GitHub Copilot with a Copilot para empresas or Copilot para empresas license, you may not see code completion suggestions in your editor for some files. This happens when a file is excluded from being used by GitHub Copilot. Content exclusion can be configured by a repository administrator, or by an organization owner.

When a file is affected by a content exclusion setting, GitHub Copilot will not suggest code completion in that file, and the content of that file will not be used to inform code completion suggestions in other files.

Si un archivo se ha configurado como contenido excluido para GitHub Copilot, el icono de la barra de estado tendrá una línea diagonal cruzada. Mantenga el puntero sobre el icono para ver la información sobre herramientas que indica qué configuración ha aplicado esta restricción.

Para más información, consulta Exclusión del contenido de GitHub Copilot.

GitHub Copilot content exclusions are not being applied

Content exclusion can be configured at the repository, organization, and enterprise level. The scope of the exclusion is determined by the level at which the rule is set:

• Los administradores del repositorio solo pueden excluir contenido de sus propios repositorios. Esto afecta a los usuarios de Copilot que trabajan en esos repositorios específicos.

• Los propietarios de la organización pueden excluir el contenido de los usuarios que tienen asignado un puesto de Copilot a través de su organización.

• Los propietarios de las empresas pueden aplicar reglas de exclusión a todos los usuarios de Copilot de la empresa.

Después de agregar o cambiar las exclusiones de contenido, puede tardar hasta 30 minutos en surtir efecto en los IDE en los que la configuración ya está cargada. Puedes aplicar cambios a tu propio IDE, forzándolo a volver a cargar la configuración de exclusión de contenido. For more information, see Exclusión del contenido de GitHub Copilot.

Error: "GitHub Copilot could not connect to server. Extension activation failed"

This error indicates that you do not have a Copilot plan, or there was an error connecting to the GitHub API to request a token to use GitHub Copilot.

To request another token from api.github.com, try signing in and out of Copilot from your IDE. Once you've logged out, Copilot will prompt you to sign back in.

If you cannot connect to the server, you can create a discussion in our discussion forum. You can include log files from your IDE to help us troubleshoot the issue. For more information on obtaining log files from your specific IDE, see Viewing logs for GitHub Copilot in your environment.

Copilot not suggesting multiple lines of code

This is a known issue and our team is working towards a fix. For more information, see this comment on a GitHub Community discussion.

Error: "No valid OAuth token detected" in GitHub Copilot en la CLI

This error suggests that a classic or fine-grained personal access token might be in use, either via the GITHUB_TOKEN or GH_TOKEN environment variables, or during a gh auth login attempt. GitHub Copilot en la CLI currently only supports using the GitHub CLI OAuth app.

For more information, see the Copilot en la CLI extension repository.

Error: "Sorry, your request was rate-limited."

This error suggests that you have exceeded the rate limit for Copilot requests. GitHub uses rate limits to ensure everyone has fair access to the Copilot service and to protect against abuse.

Most people see rate limiting for preview models, like OpenAI’s o3 and o4-mini, which are rate-limited due to limited capacity.

Service-level request rate limits ensure high service quality for all Copilot users and should not affect typical or even deeply engaged Copilot usage. We are aware of some use cases that are affected by it. GitHub is iterating on Copilot’s rate-limiting heuristics to ensure it doesn’t block legitimate use cases.

In case you experience repeated rate-limiting in Copilot, contact Soporte de GitHub.

Can't find Copilot Chat in my IDE

If you can't find Copilot Chat in your editor, make sure you have checked the "Prerequisites" section of Asking GitHub Copilot questions in your IDE.

Latest Copilot Chat does not work in Visual Studio Code

Los cambios en coinciden con los lanzamientos de Visual Studio Code, debido a la profunda integración de la interfaz de usuario de . Como resultado, cada nueva versión de solo es compatible con la versión más reciente de Visual Studio Code. Esto significa que si usa una versión anterior de Visual Studio Code, no podrá usar la versión más reciente de .

Solo las versiones más recientes de usarán el gran modelo de lenguaje más reciente proporcionado por el servicio Copilot, ya que incluso las actualizaciones de modelos menores requieren cambios y correcciones de solicitudes en la extensión. Una versión anterior de seguirá usando la versión más reciente de .

To use Copilot Chat, make sure you are using the latest version of Visual Studio Code.

Authentication problems with cuenta de usuario administrada accounts

Si usas un plan de Copilot para una cuenta de cuenta de usuario administrada en GHE.com, tendrás que actualizar algunos valores antes de iniciar sesión. See Using GitHub Copilot with an account on GHE.com.

Authentication problems in Visual Studio Code

If you are signed in to GitHub but Copilot is unavailable in Visual Studio Code, it may be due to an authentication problem. Try the following steps to resolve the issue:

1. In the bottom left corner of the Visual Studio Code window, click the Accounts icon, hover over your GitHub username, and click the Sign out button.
2. To reload Visual Studio Code, press F1 to open the command palette, and select Developer: Reload Window.
3. After Visual Studio Code reloads, sign back in to your GitHub account.

Authentication problems in Visual Studio

If you experience authentication issues when you try to use Copilot Chat in Visual Studio, you can try the following steps to resolve the issue.

1. Check that the GitHub ID you are signed into Visual Studio with is the same as the one you have been granted access to Copilot Chat with.

2. Check whether your GitHub ID/credentials need refreshing in Visual Studio. For more information, see Work with GitHub accounts in Visual Studio in the Visual Studio documentation.

3. Try removing and re-adding your GitHub ID to Visual Studio and restarting Visual Studio.

4. If the above steps don't work, click the Share feedback button and select Report a problem to report the issue to the Visual Studio team.

   

Interrupted chat responses on GitHub.com

If a chat response terminates unexpectedly, before the response is complete, try resubmitting the question.

In Copilot Chat's immersive view (the github.com/copilot page), you can resubmit your question by clicking the button under the chat response.

Further reading

• GitHub y controles comerciales