Summary
1Password and OpenAI introduced a Codex integration that routes credential access through the 1Password Environments MCP Server instead of exposing raw secret values in prompts, repositories, or local env files. The setup requires explicit user approval and keeps the secrets outside the model context window.
What changed
1Password launched a Codex-specific Environments MCP Server that brokers task-scoped secret access with user approval while keeping secret values out of model-visible context.
Why it matters
This is a concrete secret-management control for coding agents, not a generic security claim. As Codex and similar tools take on more execution work, approval-gated runtime secret brokering could become a baseline requirement for teams that want agent speed without leaking credentials into code or prompts.
Evidence excerpt
1Password says the Environments MCP Server for Codex issues credentials just in time, requires explicit user approval, and keeps secret values outside the model context window and off disk.