GitHub shipped targeted model rules on May 26. Per the GitHub blog: “Customers on Copilot Business and Copilot Enterprise plans can use targeted model rules.” The feature is in public preview.

What the rules do

The blog post’s load-bearing sentence: “Enterprise owners now have granular control over which GitHub Copilot models are available to each organization. With targeted model rules, you can allow specific models for specific organizations instead of relying on a single enterprise-wide setting.” Previously, an enterprise had a single policy that governed every organization under it; the targeted rules tier now sits between the enterprise-wide setting and the developer.

Enabled or Optional per model

Each model in the catalog is set to one of two values. The exact wording from the GitHub blog: “Enabled (automatically on for all organizations) or Optional (organizations decide whether to enable it).” An Enabled model is on by default for every organization under the enterprise unless a rule overrides it. An Optional model requires the organization to enable it explicitly.

A second Copilot change shipped the same day

The same May 26 changelog window also added CLI controls to Copilot Memory — /memory on, /memory off, and /memory show with persistent settings across sessions, plus a clarified store_memory permission prompt that explicitly states whether the entry will be a user-level preference or a repository-level fact. The walkthrough is in Copilot Memory: the CLI controls.

Where this sits in the model-picker story

The May 22 release (Copilot adds GPT-5.3-Codex as enterprise base) set the enterprise base model. Today’s rules layer per-organization control on top of that base — the picker moves to the organization, not yet to the developer. The reframe is in the org chart picks your model; the predecessor in the arc is you didn’t pick this model.