01 What happened
On October 28, 2026, GitHub started rolling out Shared Copilot Automations — a feature that enables teams to collaboratively create and maintain AI-powered workflows that belong to a repository, not to a single user.
02 Key details
- Shared Copilot Automations are rolling out to Copilot Pro, Pro+, Max, Business, and Enterprise users; availability varies as the rollout progresses.
- Shared automations are visible to anyone with read access; users with write access can edit them.
- AI credits are billed to the repository owner, actions are attributed to Copilot, and automations persist if the original creator leaves.
- For organization-owned repositories, an admin must enable the 'Allow use of Copilot cloud agent billed to the organization' policy.
- Users choose Shared or Personal type when creating an automation; the type cannot be changed afterward.
03 Why it matters
Previously, Copilot automations were personal — only the creator could view and edit them, and AI credits came from the individual's quota. The new shared mode transfers ownership to the repository: anyone with write access can modify the workflow, billing shifts to the repository owner, and actions on GitHub are attributed to Copilot. This reduces friction for team-wide automation maintenance and ensures workflows keep running even if the original author leaves.
04 Who it matters to
AI developers and enterprise administrators.
Original source