AI Update
May 29, 2026

OpenAI's Codex Rewrites Enterprise Engineering at Cisco and Endava

OpenAI's Codex Rewrites Enterprise Engineering at Cisco and Endava

OpenAI just turned software engineering from a bottleneck into a production line—and the world's biggest companies are already shipping with it.

In a coordinated wave of case studies this week, OpenAI revealed how Codex—its agentic coding platform—is fundamentally restructuring how enterprises build software. Cisco is using it to automate defect remediation and scale "AI-native development." Endava collapsed requirements analysis from weeks to hours. MUFG is building AI-powered financial services at scale. These aren't pilot projects. They're production deployments at companies with tens of thousands of engineers.

What Codex Actually Does

Codex isn't ChatGPT with a code editor bolted on. It's an orchestration layer that coordinates multiple AI agents across the entire software lifecycle—requirements gathering, architecture design, code generation, testing, deployment, and maintenance. Think of it as a project manager, senior engineer, and QA team rolled into one system that never sleeps.

The Cisco deployment is particularly revealing. They're using Codex to accelerate "AI Defense work"—the unglamorous but critical task of hunting down security vulnerabilities and technical debt in massive legacy codebases. This is work that traditionally requires senior engineers with deep institutional knowledge. Codex is doing it faster.

The Agentic Organization Playbook

Endava's approach shows the broader pattern emerging across these deployments. They're not just automating tasks—they're rebuilding their entire organisational structure around what they call an "agentic organization." Requirements that once took weeks of back-and-forth between business stakeholders and engineering teams now get translated directly into executable specifications by AI agents that understand both domains.

This is the real shift: AI isn't replacing developers. It's replacing the friction between intent and execution. The question is no longer "can we build this?" but "should we build this?"—and that question gets answered in hours, not quarters.

What This Means for Learners

If you're learning to code in 2026, you're not learning to write code—you're learning to direct code. The skill isn't syntax; it's architecture, requirements clarity, and knowing what to build. Understanding how AI agents work is now as fundamental as understanding version control.

For senior engineers, the game has changed too. Your value isn't in writing boilerplate or debugging null pointer exceptions. It's in system design, security thinking, and translating messy business problems into clear specifications that agents can execute. If you're still measuring productivity in lines of code, you're measuring the wrong thing.

The companies winning with Codex aren't the ones with the best developers—they're the ones who've rethought their entire AI strategy from the top down. That's the meta-lesson here: AI adoption isn't a technical problem. It's an organisational design problem.

Sources