Adding GitHub Copilot cloud agent to your organization

Enable Copilot cloud agent for your members and control the repositories where it is available.

For an introduction to Copilot cloud agent, see AUTOTITLE.

Enabling Copilot cloud agent for your members

Copilot policies are also managed at the enterprise level. If your enterprise owner has selected a specific policy, such as enabling a feature everywhere, disabling it everywhere, or enabling it for selected organizations only, you cannot override that setting at the organization level. For information on how policies combine, see AUTOTITLE.

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 organization Organizations.
Select an organization by clicking on it.
Under your organization name, click gear Settings. If you cannot see the "Settings" tab, select the More dropdown menu, then click Settings.
In the sidebar, under "Code, planning, and automation", click copilot 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.

Controlling automations in your repositories

Automations let users run Copilot cloud agent automatically, on a schedule or in response to events. See AUTOTITLE.

Automations are allowed by default in repositories where Copilot cloud agent is available. You can control whether automations are allowed in repositories owned by your organization, separately from the Copilot cloud agent policy.

In the upper-right corner of GitHub, click your profile picture, then click organization Organizations.
Select an organization by clicking on it.
Under your organization name, click gear Settings. If you cannot see the "Settings" tab, select the More dropdown menu, then click Settings.
In the sidebar, under "Code, planning, and automation", click copilot Copilot, and then click Cloud agent.
To allow or block automations, toggle the Allow automations setting.

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 AUTOTITLE.

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 AUTOTITLE.
Encourage members to educate themselves about setting up their repository to get the most from Copilot cloud agent. Useful resources: