Copilot in the cloud is a connected experience that lets users start and resume cloud sessions across the GitHub website, GitHub Mobile, Copilot CLI, and the Copilot app. See GitHub Copilot en GitHub.com.
The Copilot in the cloud policy determines:
- Whether users can access the chat interface or assign work to Copilot on the GitHub website and GitHub Mobile
- Whether users can start sessions in cloud sandboxes from local clients (Copilot CLI and the Copilot app)
This feature is enabled by default. To ensure data security, chat sessions are scoped by default to either a single organization or the user's personal repositories. If you have enabled single sign-on (SSO), users will need to authenticate with SSO to access session data from a repository associated with that organization.
Enabling Copilot in the cloud for your members
Nota:
Copilot Las políticas también se gestionan a nivel empresarial. Si el propietario de la empresa ha seleccionado una directiva específica, como habilitar una característica en todas partes, deshabilitarla en todas partes o habilitarla solo para organizaciones seleccionadas, no podrá invalidar esa configuración en el nivel de organización. Para más información sobre cómo se combinan las directivas, consulta directivas de GitHub Copilot para empresas y organizaciones.
Copilot in the cloud is enabled 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 or disable these features for members on the Copilot policies page for their organization. See Enabling Copilot features in your organization.
- For the "Copilot in the cloud" policy, select "Enabled".
- Optionally, for the "MCP servers on GitHub.com" policy, select "Enabled".
Disabling the cloud agent in your repositories
By default, GitHub's cloud agent is available in all repositories in an organization where Copilot in the cloud is enabled. However, you can block the agent from being used in some or all repositories owned by your organization.
-
En la esquina superior derecha de GitHub, haz clic en la foto del perfil y luego en Your organizations.
-
Seleccione una organización haciendo clic en ella.
-
Debajo del nombre de la organización, haz clic en Settings. Si no puedes ver la pestaña "Configuración", selecciona el menú desplegable y, a continuación, haz clic en Configuración.

-
En la barra lateral, en "Código, planeamiento y automatización", Haga clic en Copilot y, a continuación, haga clic en Cloud agent.
-
Use the "Repository access" control to define which repositories allow the agent.
-
If you choose "Selected repositories", in the "Select repositories" dialog, select the repositories that allow Copilot cloud agent, then click Select.
Once the agent is enabled for a repository, any user with access to Copilot and write permission for the repository can delegate work to Copilot.
Controlling automations in your repositories
Automations let users run Copilot sessions automatically, on a schedule or in response to events. See automatizaciones de Copilot.
Automations are allowed by default in repositories where Copilot in the cloud is available. You can control whether automations are allowed in repositories owned by your organization, separately from the Copilot in the cloud policy.
-
En la esquina superior derecha de GitHub, haz clic en la foto del perfil y luego en Your organizations.
-
Seleccione una organización haciendo clic en ella.
-
Debajo del nombre de la organización, haz clic en Settings. Si no puedes ver la pestaña "Configuración", selecciona el menú desplegable y, a continuación, haz clic en Configuración.

-
En la barra lateral, en "Código, planeamiento y automatización", Haga clic en Copilot y, a continuación, haga clic en Cloud agent.
-
To allow or block automations, update the Allow automations setting.
Managing the agent firewall for your organization
Organization owners can configure the firewall for their organization to determine which external hosts and URLs the cloud agent can access. For more information, see Personalización o deshabilitación del firewall para GitHub Copilot.
Next steps
-
Tell the members of repositories where Copilot in the cloud is available that they can start cloud sessions and delegate work to Copilot on GitHub.
-
Encourage members to educate themselves about setting up their repository to get the most from Copilot. Useful resources: