# 1Password is now a trusted access layer for OpenAI's Codex

DevFeed: [1Password is now a trusted access layer for OpenAI's Codex](<https://devfeed.tech/articles/1password-is-now-a-trusted-access-layer-for-openai-s-codex-1886.md>)

Original publisher: [Read original article](<https://1password.com/blog/1password-trusted-access-layer-for-openai-codex>)

Author: info@1password.com (Dennis Kromhout van der Meer and Robert Menke)

Published: 2026-05-20T00:00:00Z

Content type: article

Language: en

Sources: [Blog on 1Password Blog](<https://devfeed.tech/sources/blog-on-1password-blog.md>)

Topics: [AI Bots](<https://devfeed.tech/topics/ai-bots.md>), [MSP MCP](<https://devfeed.tech/topics/msp-mcp.md>)

Tags: [ai](<https://devfeed.tech/tags/ai.md>), [ai-coding](<https://devfeed.tech/tags/ai-coding.md>), [codex](<https://devfeed.tech/tags/codex.md>), [developers](<https://devfeed.tech/tags/developers.md>), [mcp](<https://devfeed.tech/tags/mcp.md>), [mcp-server](<https://devfeed.tech/tags/mcp-server.md>), [openai](<https://devfeed.tech/tags/openai.md>), [secrets](<https://devfeed.tech/tags/secrets.md>), [security](<https://devfeed.tech/tags/security.md>)

## AI overview

1Password describes an MCP integration for Codex that issues task-scoped credentials just in time while keeping secret values out of code and model context.

## Source excerpt

Coding agents like Codex are helping developers write, execute, and prepare code for production. Every action that AI coding agents take against a database, an API, or a deployment pipeline requires access to credentials. Today, these credentials typically live in .env files, scripts, or hardcoded in repositories, where they can be easily exfiltrated and are difficult to govern and audit. The shift from AI assistance to AI execution has outpaced how teams manage the secrets needed for execution. 1Password and OpenAI are working together to close this gap. The 1Password Environments MCP Server for Codex makes 1Password the trusted access layer for Codex: credentials are issued just-in-time and scoped to the task, while keeping them outside the model's context window. Developers get the access they need to build and ship, while secrets stay where they belong. The same integration helps catch secrets at the source. Codex can be prompted to use 1Password and the 1Password MCP to store and use credentials that it needs. Why secrets should stay out of prompts, code, and model context Every credential placed inside an agent's context is a credential at risk of easily being exfiltrated. It can be logged, cached, reused across sessions, or surfaced in unexpected outputs. A secure architecture treats a coding agent as a tenant, not a vault: it gets secure access to do its job, but never custody of the secret itself. 1Password Environments is built on that principle. Instead of sharing .env files or hardcoding credential values, teams work from a shared environment where secrets are made available at runtime to the application, without the values ever appearing in code, terminals, or model context. This secure access model is built on the same vault technology and security architecture used across 1Password. Secrets remain end-to-end encrypted and centrally managed, with access limited to authorized users and groups, and through custom permissions. This architecture matters mo