Deploy and manage coding agents at scale with the Unity Gateway CLI

In the last six months, GPT-6, Claude Opus 5.5, Gemini 3.8, and Grok 4.7 all shipped, alongside strong open-weight models like Kimi K3, GLM-5, and DeepSeek V4.1. There’s a new frontier model roughly every five days, and as the cost-performance frontier keeps moving, the model that was the best choice for a job a few months ago often has a better or cheaper alternative today.

That pace puts the teams that own developer tooling in a squeeze. Standardize on one provider, and you risk missing the better models or lower costs available elsewhere. Support many agents and providers, and you give engineers a real choice, but scatter access, budget controls, security policies, and usage logs across separate systems. What organizations actually need is both: the freedom to adopt the best option whenever it appears, and a consistent way to govern it across thousands of developers.

Today, we're introducing the Unity Gateway CLI to deliver both. In Unity Gateway, admins manage approved models, tools, and spending policies from one place. Developers keep working the way they prefer, launching any approved agent with a command like ug claude or ug codex, while Unity Gateway handles authentication and applies the published settings for them. When a better model or a more efficient workflow emerges, teams roll it out across every supported agent at once. The result is a coding setup that keeps pace with the cost-performance frontier as it moves.

New in Unity Gateway: Configure coding agents centrally and roll them out with ug

Unity Gateway now provides admins with a single place to configure coding agents, including their default models, MCP servers, skills, Smart Routing, and spending policies. Admins can manage these settings in Unity Gateway → Govern → Agent Configuration.