Agent Upstart

Cool things people are building with agents — and practical help getting the most out of them.

Playbooks · Teams tasks

Copilot Automations learn from real outcomes

Written November 7, 2026

Copilot Automations now propose prompt improvements from real outcomes. What it learns from, what it proposes, and what to check before accepting.

What changed

GitHub's October 28 changelog says Copilot Automations can now learn from their outcomes and propose improvements to themselves. An automation is a cloud workflow in a repository that runs on a trigger or a schedule — sorting issues, reviewing pull requests, opening optimization pull requests. Writing its prompt is the easy part; keeping the prompt honest as the work changes is the hard part, and that is the gap this change addresses. The proposal is the whole feature: nothing about the automation changes until a person accepts it.

What "real outcomes" means here

Automations leave a trail of signals on GitHub that show how well they are working. The changelog names three:

Those are the outcomes the improvement loop reads. A label change, an accepted comment, and a merged pull request are all things people do after the automation acts — not scores the automation gives itself.

How the loop works

When you ask Copilot to set up a self-improving automation, it can create a group of automations that work together. The changelog's example is a custom code reviewer: one automation runs when a pull request opens, reviews the changes, and posts comments; a second, weekly improvement automation analyses how developers responded to those comments and proposes refinements to the first automation. When the improvement automation proposes a change to the original automation's prompt, tools, or triggers, GitHub notifies you. You review the proposal and accept or reject it before anything is applied.

Copilot Automations is available with Copilot Pro, Pro+, Max, Business, and Enterprise plans.

What to check before accepting a proposal

A proposal that optimizes the wrong outcome is worse than a stale prompt. The signals are ambiguous in specific ways, and each one is worth checking against the actual work before accepting:

The check is the same in each case: read the proposal against the outcome it claims to come from, not against the automation's own description of that outcome. The changelog offers no results showing the loop raises quality over time, so "better results over time" is GitHub's claim for now, not a measured result.

Limits

Related playbooks

Sources

Back to: Small-team playbooks hub · Also: Copilot reviews: how many get addressed · Decide whether Copilot should approve PRs · Triage a backlog of issues with an agent