Overview
Control which managed authentication routes members may newly configure, and understand the gateways behind model access.
Proliferate runs the coding agents your team already uses and lets each person choose how their agent reaches a model. This section covers the org-level levers on top of that: control which managed authentication routes members may newly configure — native agent use and existing selections are not disabled — and how model gateways fit in.
Agent authentication policy
Control which managed authentication routes members may newly configure, and read the Conflicts table.
Model gateways
How Proliferate's managed gateway works, and where self-hosted deployments attach their own.
The member-facing catalog of every supported agent lives in Agents. There is no separate admin agent list; that page is canonical.