Agent Upstart

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

Playbooks · Teams

Copilot's model-policy API is GA at four levels

Written November 13, 2026

GitHub's model-policy GET/PATCH endpoints are generally available at four levels. How an org decides which models stay selectable.

What changed

On October 19, GitHub announced that the REST API can now retrieve and update Copilot model policies, and that the GET and PATCH endpoints are generally available. A model policy is the setting that decides which models people in an enterprise can pick in Copilot. Until this release, changing that list meant working through settings screens at each level of the organization. Now the same decision is a resource an admin can read and write with an API call, which means it can live in a script, a review process, or a scheduled job like any other configuration.

The timing is the context. Copilot's model list has been changing in waves, with older models retiring and replacements arriving on their own schedule. Each retirement forces the same admin question: is the replacement model enabled for our people, and is the retiring one still selectable anywhere? A settings screen answers that one organization at a time. An API answers it everywhere at once.

The four levels

The changelog lists one GET and PATCH pair per level:

GET returns the policy in force at that level. PATCH updates it. Because the endpoints exist at every level, an admin can read the whole stack before changing any of it, which is the order that matters: a change at the enterprise level and a change at the organization level do not mean the same thing, and the delegation mode decides which one governs.

Delegation decides who governs

GitHub's changelog describes two delegation shapes. Enterprise policies can delegate model control to organizations in organization mode, or to teams and apps in enterprise teams mode. In the first shape, the enterprise sets the frame and each organization decides its own list. In the second, control sits with enterprise teams and agent apps instead. Either way, the level that holds the delegated control is the level whose policy people actually feel in the model picker.

That is the part to settle before writing any automation. A PATCH sent to a level that does not hold control in the current mode will not produce the picker your users see. Read the enterprise policy first, learn which mode is live, and only then change the level that governs.

A sensible working pattern

Limits

Related playbooks

Sources

Back to: Teams playbooks hub · Also: Re-pin Copilot models before retirements · Copilot Agent Merge: watch a PR and fix its blockers