GitHub Copilot Automations go team-wide: repo-owned shared automations, 24 new triggers, 20 new tools and AI credit limits
At GitHub Universe on Oct 28, GitHub shipped a batch of Copilot Automations updates. Shared automations now belong to the repository, act as Copilot, bill AI credits to the repo owner and keep running after their creator leaves. Automations gain 24 new GitHub event triggers, REST API triggers from external systems and chaining, plus 20 new tools and custom MCP servers. Teams can cap AI credits per run, day, week or month, automations can propose improvements to their own prompts from real outcomes, and VS Code 1.144 can run them in the cloud.
Key Takeaways
- Shared automations belong to the repository: anyone with read access can view them, anyone with write access can edit, actions are attributed to Copilot and AI credits bill to the repo owner
- 24 new triggers across issues, pull requests, discussions and security alerts, plus REST API triggers from systems like Jira, Sentry and PagerDuty
- 20 new GitHub tools (merge PRs, retry workflow runs, upload screenshots and more) and support for custom MCP servers
- AI credit limits can be set per run, day, week or month; org repos need an admin to enable the "Allow use of Copilot cloud agent billed to the organization" policy
- Rolling out to Copilot Pro, Pro+, Max, Business and Enterprise; VS Code 1.144 runs them in the cloud with chat.automations.cloud.enabled
Linked Models & Agents: