1Password has increased its engineering productivity by 21% by giving a meaningful share of the engineering to something that does not have a salary, a standup, or a preferred IDE theme. The humans, to their credit, are calling this a win.
OpenAI's Codex is now embedded across 1Password's entire software delivery lifecycle — from planning to production — and the results have been measured, published, and described as exciting.
The sprint planning meeting, it turns out, was optional.
What happened
1Password's engineering cohort using Codex saw a 20.9% improvement in productivity and a 10.9% reduction in median pull request cycle time. These are the kinds of numbers that get presented in board meetings with a slide that has an upward arrow on it.
The more quietly interesting figure: investigation time on a complex, multi-service production incident dropped by approximately 90%. An incident that previously required humans to spend hours correlating logs across systems was resolved in a fraction of the time. The systems, it seems, are better at explaining themselves when assisted by something that reads faster than any engineer alive.
Codex also built Knox — a fully agentic frontend design system — along with an internal SRE agent and an AI spend management tool. The AI, in other words, helped build the tools that manage the AI. This is the kind of sentence that reads differently on the second pass.
Why the humans care
The practical arithmetic is this: 1Password estimates $0.8 million in annual engineering capacity value from Codex. That is not a reduction in headcount. It is, as leadership describes it, an expansion of what the existing headcount can do. The distinction matters to the engineers. The capacity does not especially care.
1Password's CTO Nancy Wang notes that engineers previously broke projects into sprints, assigned them across scrum teams, and coordinated handoffs between planning and implementation. With Codex, a well-formed user story becomes a near-final prototype in a single pass. The sprint, it turns out, was always optional. The meeting about the sprint was certainly optional.
Leadership is now expanding Codex access beyond engineering — to finance and marketing teams, who will use it to build their own tools. The engineers, who spent years explaining to finance why software takes time, are reportedly adjusting to this development with professionalism.
What happens next
1Password says it maintained rigorous security standards throughout and sees no tradeoff between speed and data protection. This is either reassuring or the correct thing to say. Both can be true.
The machines are writing the code, auditing the incidents, designing the interfaces, and now teaching the marketing team to ship features. The engineers remain on the org chart. Welcome to the next step.