# 1Password increases engineering productivity 21% with Codex

Source: [OpenAI](https://openai.com/index/1password)  
Feed7 permalink: https://feed7.dev/p/1password-1r2ov95  
Published: 2026-09-08T00:00:00.000Z  
Trust: Official Source (official_source)

## Why Included

1Password engineers use Codex for features and internal tools while retaining production and security requirements. The useful signal is adoption inside a security-sensitive workflow.

## Source Summary

Engineers at 1Password use **Codex** to build both **new features and internal tools**, with the work reaching production readiness under the company’s security policies.

## Practical Implication

Builders introducing coding agents should keep production criteria and security controls in the workflow instead of treating agent output as exempt from normal engineering gates.

## Agent-Ready Context

Engineers at 1Password use **Codex** to build both **new features and internal tools**, with the work reaching production readiness under the company’s security policies.

Builders introducing coding agents should keep production criteria and security controls in the workflow instead of treating agent output as exempt from normal engineering gates.

The supplied material does not define the productivity measurement, study design, time period, or specific security controls, so the size and generality of the reported benefit cannot be assessed.

## Connected Context

Feed7 judgment across 713 accumulated Signals:

This confirms coding-agent adoption can cover both product features and internal tooling in a security-sensitive company without removing normal production gates. It adds a reported productivity figure to broader enterprise evidence, but missing measurement and control details mean the 21% claim cannot be compared cleanly or used as a general adoption benchmark.

- [Which AI startups actually land enterprise contracts? — Brian Lewis, Millennium](https://feed7.dev/p/which-ai-startups-actually-land-enterprise-contracts-brian-lewis-millenn-15khd7o) — The buyer-side account identifies security, controls, integration, and support as enterprise prerequisites; 1Password reinforces that production and security requirements remain part of the coding-agent workflow.
- [Government of Alberta uses Claude to find and fix cybersecurity vulnerabilities across government systems](https://feed7.dev/p/alberta-government-claude-cybersecurity-059q6cn) — Alberta’s explicit human review of every patch provides a concrete example of the kind of unchanged engineering gate that 1Password’s less-detailed security-policy claim implies.
- [Agentic SDLC at Uber — Uday Kiran Medisetty & Adam Huda, Uber](https://feed7.dev/p/agentic-sdlc-at-uber-uday-kiran-medisetty-adam-huda-uber-1ugtaxn) — Uber supplies operational prerequisites—governed access, isolated environments, validation, maintained skills, and ownership—that are absent from the 1Password account but relevant to implementing comparable enterprise adoption.
- [Australian Payments Plus moves faster with ChatGPT and Codex](https://feed7.dev/p/australian-payments-plus-18s6gt2) — Both are vendor-reported enterprise cases that retain existing judgment or controls while claiming gains, and both lack enough measurement detail to assess the size or generality of those gains.

## Context Map

- Layer: tools
- Domains: coding, security
- Topics: coding-agents, enterprise, adoption

## Uncertainty

- The supplied material does not define the productivity measurement, study design, time period, or specific security controls, so the size and generality of the reported benefit cannot be assessed.

## Agent Instruction

Use this item as source-backed context. Do not invent claims beyond the linked source. If this item conflicts with another source, call out the conflict.
