Note
For an introduction to Copilot cloud agent, see About GitHub Copilot cloud agent.
Prerequisites
- For general information, see Piloting GitHub Copilot cloud agent in your organization.
- For information on premium requests and Actions minutes, see Allowance usage for Copilot cloud agent.
- For information on MCP servers, see Extending GitHub Copilot cloud agent with the Model Context Protocol (MCP).
Enabling Copilot cloud agent for your members
Note
Copilot policies are also managed at the enterprise level. If your organization is part of an enterprise, and explicit settings have been selected at the enterprise level, you cannot override those settings at the organization level. For information on how policies combine, see GitHub Copilot policies to control availability of features and models.
Copilot cloud agent and use of third-party MCP servers are disabled by default for organization members assigned a GitHub Copilot Enterprise or Copilot Business license by your organization.
Organizations with Copilot Enterprise or Copilot Business can enable these features for members on the Copilot policies page for their organization. See Enabling Copilot features in your organization.
- For the "Copilot cloud agent" policy, select "Enabled".
- For the "MCP servers on GitHub.com" policy, select "Enabled".
Disabling or enabling Copilot cloud agent in your repositories
By default, Copilot cloud agent is available in all repositories for users who have access to the agent, but you can block it from being used in some or all repositories owned by your organization. You can manage repository availability using the following instructions, or programmatically using the REST API.
- In the upper-right corner of GitHub, click your profile picture, then click Organizations.
- Next to the organization, click Settings.
- In the sidebar, under "Code, planning, and automation", click Copilot, and then click Cloud agent.
- Use the "Repository access" control to define which repositories allow Copilot cloud agent.
- If you choose "Selected repositories", in the "Select repositories" dialog, select the repositories that allow Copilot cloud agent, then click Select.
Once Copilot cloud agent is enabled for a repository, any user with access to Copilot cloud agent and write permission for the repository can delegate work to Copilot.
Managing the agent firewall for your organization
Organization owners can configure the Copilot cloud agent firewall for their organization, including whether it is enabled for the organization and which external hosts and URLs the agent can access. For more information, see Customizing or disabling the firewall for GitHub Copilot cloud agent.
Next steps
-
Tell the members of repositories where Copilot cloud agent is available that they can delegate work to the cloud agent.
-
Configure the default runner type for Copilot cloud agent in your organization. For more information, see Configuring runners for GitHub Copilot cloud agent in your organization.
-
Encourage members to educate themselves about setting up their repository to get the most from Copilot cloud agent. Useful resources: