Shared Copilot Automations for team workflows
GitHub is rolling out shared Copilot Automations, so a repository's cloud agent workflows no longer depend on the person who created them. Teams can read, edit and keep running these automations, with AI credits billed to the repository owner. Useful for bug reproduction, PR screenshots and incident triage.
Key points
- A shared automation belongs to the repository and keeps running if its creator leaves.
- Anyone with read access can see it; anyone with write access can edit it.
- AI credits are billed to the repository owner, not the creator.
- In organization repositories, an admin must enable the cloud agent billing policy first.
- The type is set at creation and cannot be changed afterwards.
- Change history shows how tools, triggers and the prompt evolved over time.
Copilot Automations let you combine prompts, triggers and tools so that Copilot runs in the cloud on its own, limited to the tools you have allowed. Until now every automation was personal, tied to your identity and your AI credits. The new shared type changes that: anyone with read access to the repository can see the automation, anyone with write access can edit it, and it keeps running after its creator leaves the team. Actions are attributed to Copilot rather than an individual, and credits are charged to the repository's owner.
In organization-owned repositories, an administrator must first enable the "Allow use of Copilot cloud agent billed to the organization" policy. The type is picked at creation time in github.com, the GitHub Copilot app or Visual Studio Code, and it cannot be switched later. The rollout covers Pro, Pro+, Max, Business and Enterprise plans, so availability will vary while it spreads.
Real-world use
- Reproducing a bug from a newly opened issue so the whole team sees the same steps.
- Capturing screenshots of UI changes when a pull request moves to ready for review.
- Having Copilot start an incident investigation as soon as the monitoring tool raises an alert.
Why it matters
Team workflows built on Copilot no longer depend on one person's account or credits, which makes them safer to rely on. Admins should check the billing policy before the feature shows up for their repositories.