GitHub Lets Enterprises Set Model Policy Per Team

GitHub put per-team model policy targeting into public preview on July 31, per its changelog. That matters for anyone who assumes a coding agent's model setup travels with them. It doesn't anymore, not automatically.

Before the preview, Copilot Enterprise ran on a single model policy for the whole org, one allowed-model list for everyone. The July 31 change splits that policy by team instead of by org.

The same week, Cursor added its own version of that control. Its admin settings now let organizations restrict which of the Router's three modes, Cost, Balance, and Intelligence, a given team is allowed to enable. GitHub decides which models exist for a team; Cursor decides which mode that team can pick inside its own router.

Together, two tools developers use daily turned model choice into an administered setting instead of a personal one.

My take: this is less a safety guardrail than a cost lever wearing a governance label. Restricting a team to a cheaper Router mode or a smaller model list saves money before it prevents any risk. Watch whether either company ties these policies to usage-based billing next. That's the tell.