Codex adds enterprise MCP auth projects can't override

Codex added ema_auth, an enterprise MCP authorization mode that project settings and plugins are forbidden from touching, in the pull request introducing ema_auth.

Enterprise admins get a lock that individual projects can't pick. Registrations for MCP servers come from one non-project configuration layer, and nothing downstream can weaken it, which also means the OAuth login flow and credential fallback that solo users rely on to connect a server without central setup stop working once the mode is on.

A project can't override that layer to re-enable a server the enterprise disabled or change its authorization. A plugin that declares ema_auth for itself gets rejected outright. Before this mode existed, a project could re-enable a disabled server through its own settings. A plugin could claim its own auth path around whatever the org configured. Both routes are closed now.

The same repository also added a task-level cost view for admins, in the pull request adding the cost view. It prices each task in tokens, credits and USD on a one-minute refresh, covers Business and Enterprise plans that support it, and clears cached usage whenever an account changes or reconnects.

Neither PR says whether ema_auth is enforced on Codex's servers or only inside the client that ships it. That gap decides whether the lock holds once someone builds their own binary from the open-source code.