{"meta":{"title":"Troubleshooting GitHub Copilot cloud agent","intro":"Learn how to resolve problems that may occur when you assign tasks to Copilot.","product":"GitHub Copilot","breadcrumbs":[{"href":"/en/copilot","title":"GitHub Copilot"},{"href":"/en/copilot/how-tos","title":"How-tos"},{"href":"/en/copilot/how-tos/use-copilot-agents","title":"Use Copilot agents"},{"href":"/en/copilot/how-tos/use-copilot-agents/cloud-agent","title":"Cloud agent"},{"href":"/en/copilot/how-tos/use-copilot-agents/cloud-agent/troubleshoot-cloud-agent","title":"Troubleshoot cloud agent"}],"documentType":"article"},"body":"# Troubleshooting GitHub Copilot cloud agent\n\nLearn how to resolve problems that may occur when you assign tasks to Copilot.\n\n## Copilot is not available in the \"Assignees\" list on my issue\n\nYou can only assign issues to Copilot if you have access to Copilot through a paid Copilot plan.\n\nIf you do not already have a subscription for one of these plans, click this button for more information: Sign up for Copilot\n\nIf you *do* have a paid Copilot plan, check that Copilot cloud agent has not been manually disabled for the repository:\n\n* For organization-owned repositories, the availability of Copilot cloud agent in the repository is managed by the organization and/or enterprise administrators. See [Adding GitHub Copilot cloud agent to your organization](/en/enterprise-cloud@latest/copilot/how-tos/administer-copilot/manage-for-organization/add-copilot-cloud-agent).\n\n* For personal repositories, the availability of Copilot cloud agent in the repository is configured in your account settings. See [Managing GitHub Copilot policies as an individual subscriber](/en/copilot/how-tos/manage-your-account/manage-policies#disabling-or-enabling-copilot-cloud-agent-in-your-repositories).\n\n> \\[!NOTE]\n> You can check whether Copilot cloud agent has been enabled for you in the features page of your Copilot settings: [github.com/settings/copilot/features](https://github.com/settings/copilot/features).\n\n## I have an Enterprise Managed User account and Copilot won't work in my personal repository\n\nCopilot cloud agent is not available in personal repositories owned by managed user accounts. This is because Copilot cloud agent runs on GitHub-hosted runners, which are not available to personal repositories owned by managed user accounts. For more information, see [GitHub-hosted runners](/en/actions/concepts/runners/github-hosted-runners).\n\n\n\nIf you have an managed user account and try to assign Copilot to an issue in a personal repository, you may see an error message reporting that GitHub Actions are not available for your repository.\n\nTo use Copilot cloud agent, you'll need to work with repositories owned by your organization instead of personal repositories.\n\n## Copilot can't create a pull request from Copilot Chat\n\nIf you asked Copilot to create a pull request and it responds that it cannot directly create a pull request, check that Copilot cloud agent is available.\n\n> \\[!IMPORTANT]\n> In VS Code, Visual Studio, and JetBrains IDEs, you must mention the `@github` chat participant in your prompt. You can omit this in Copilot Chat on GitHub.com.\n\n## I assigned an issue to Copilot, but nothing is happening\n\nWait a while, then refresh the page. You should see Copilot leave an 👀 reaction on the issue. Shortly after this, Copilot will open a draft pull request linked to the issue, which will be shown in the issue timeline.\n\n## Copilot has opened a pull request, but nothing is happening\n\nIf there is a \"Copilot started work\" event in the pull request timeline, click **View session** to see the session logs. These will stream live, and you will be able to see what Copilot is doing.\n\n## Copilot won't respond to my pull request comments\n\nCopilot only responds to comments from people who have write access to the repository.\n\nIf you do have write access, and you mention `@copilot` on a pull request that is assigned to Copilot, the comment is passed to Copilot cloud agent. An eyes emoji (👀) is added to your comment to indicate that Copilot cloud agent has seen your comment. Shortly after, a \"Copilot started work\" event is added to the pull request timeline.\n\nIf this doesn't happen, Copilot may have been unassigned from the pull request, or you may not have write access. Note that Copilot only responds to mentions in open pull requests. Once a pull request is merged or closed, Copilot cloud agent will not respond to new mentions or comments to better focus on active development work.\n\n## Based on the agent session logs, Copilot appears to be stuck\n\nCopilot can appear to be stuck for a while, and then get moving again.\n\nIf the session remains stuck, it will time out after an hour. You can retry by unassigning the issue and then reassigning it to Copilot.\n\nIf Copilot got stuck while responding to a comment, try adding the same comment to the pull request again.\n\n## My GitHub Actions workflows are not running when Copilot pushes\n\nGitHub Actions workflows will not run automatically when Copilot pushes changes to a pull request.\n\nTo allow GitHub Actions workflows to run, click the **Approve and run workflows** button in the pull request's merge box. See [Review output from Copilot](/en/copilot/how-tos/copilot-on-github/use-copilot-agents/review-copilot-output).\n\n## Copilot is pushing changes which don't pass my CI checks\n\nWhile working on an issue, Copilot has access to its own ephemeral development environment, powered by GitHub Actions, where it can execute automated tests and linters to validate its work before it pushes.\n\nIt is most likely to do this if given clear instructions on what to do. The best way to do this is with a `.github/copilot-instructions.md` file. See [Best practices for using GitHub Copilot to work on tasks](/en/copilot/tutorials/cloud-agent/get-the-best-results#adding-custom-instructions-to-your-repository).\n\n## There is a warning from GitHub Copilot about the firewall\n\nBy default, Copilot's access to the internet is limited by a firewall.\n\nLimiting access to the internet helps to manage data exfiltration risks, where surprising behavior from Copilot or malicious instructions given to it could lead to code or other sensitive information being leaked to remote locations.\n\nIf Copilot tries to make a request which is blocked by the firewall, a warning is added to the pull request body (if Copilot is responding to an issue assignment) or to a comment (if Copilot is responding to a comment). The warning shows the blocked address and the command that tried to make the request.\n\n\n\nFor more information, see [Customizing or disabling the firewall for GitHub Copilot](/en/copilot/how-tos/copilot-on-github/customize-copilot/customize-the-firewall).\n\n## Copilot is not picking up attached screenshots\n\nThe maximum image size allowed by Copilot cloud agent is 3.00 MiB. Images larger than this will be removed from the request.\n\n## Further reading\n\n* [Best practices for using GitHub Copilot to work on tasks](/en/copilot/tutorials/cloud-agent/get-the-best-results)\n* [Configure the development environment](/en/copilot/how-tos/copilot-on-github/customize-copilot/customize-cloud-agent/customize-the-agent-environment)"}