GitHub says Copilot Automations can now study what happens to their output and draft changes to their own prompts, tools, or triggers. GitHub’s changelog posted it on 28 October 2026.
The signal is whatever people do afterward on GitHub. A triage automation sees whether someone relabels its issues. A code reviewer can check which comments developers accept. An automation that opens performance pull requests can count how many of them maintainers merge.
To get one, you ask Copilot for a self-improving automation and it may build a pair. One does the job, such as reviewing each new pull request. A weekly one reads the reactions and suggests refinements to the first. GitHub notifies you when a proposal arrives, and you accept or reject it before anything takes effect.
That approval step matters because an automation editing its own instructions unattended would be hard to audit. The changelog offers no results showing the loop raises quality, so “better results over time” is GitHub’s claim for now.
Plans from Pro through Enterprise include it. Teams already running review automations can switch on the weekly loop and judge it by how many proposals they end up accepting.
Reported by the GitHub Changelog on 28 October 2026.
