Codex demos show end-to-end developer‑OS capabilities — file management, web browsing and installs
- OpenAI’s April 16 Codex update turned its coding agent into a broader desktop workflow tool, adding computer use, an in-app browser, image generation, and plugins. - The concrete jump is scope: Codex now works across files, terminals, SSH devboxes, public web pages, and 90-plus plugins in one flow. - That pushes coding assistants toward “developer OS” territory, where permissions, browser access, and tool orchestration matter as much as code generation.
Coding agents used to live in a pretty narrow box. They could read a repo, suggest edits, maybe run tests, and that was the job. OpenAI’s latest Codex update blows past that boundary. The interesting part is not one flashy feature — it’s that Codex now spans the stuff around coding too: files, terminals, browsers, images, plugins, and background tasks. ### What actually changed? On April 16, 2026, OpenAI shipped a major Codex app update for macOS and Windows. The new app can use your computer “alongside you,” which basically means it can see, click, and type with its own cursor, work across multiple apps, and keep several agents running in parallel without taking over your desktop. OpenAI also said more than 3 million developers were already using Codex every week. (openai.com) ### Why is that bigger than “better autocomplete”? Because autocomplete helps inside the editor. This update reaches across the whole workflow. Codex now supports multiple terminal tabs, direct file opening with previews for PDFs and docs, GitHub review comment handling, and SSH connections to remote devboxes in alpha. That is a different product shape — less “finish this function,” more “help me get this whole task over the line.” (openai.com) ### What does the browser add? A lot, turns out. Codex now has an in-app browser that both you and the agent can look at inside the same thread. You can open localhost pages, public pages, or file-backed previews, leave comments directly on broken UI, and ask Codex to fix exactly what you marked. With the Browser plugin enabled, Codex can click, type, inspect rendered state, take screenshots, and verify fixes in that browser. (openai.com) ### Is it a full browser agent? Not quite — and that limitation matters. The in-app browser is meant for pages that do not require sign-in. It does not support your normal browser profile, cookies, extensions, or existing tabs. OpenAI explicitly tells users not to paste secrets into browser flows, and Codex asks before using websites unless they are already allowed. So yes, this is browser use, but it is fenced browser use. (developers.openai.com) ### Where do installs and tools fit in? This is where the “developer OS” framing starts to make sense. OpenAI added more than 90 plugins that combine skills, app integrations, and MCP servers. The named examples include Atlassian Rovo, CircleCI, CodeRabbit, GitLab Issues, Microsoft Suite, Neon by Databricks, Remotion, Render, and Superpowers. In plain English — Codex is being wired into the systems developers already touch before and after writing code. (developers.openai.com) ### Can it work outside your machine? Yes. Codex also runs in the cloud, where it can work in the background and in parallel using its own environment. If you connect GitHub, Codex can work on repositories there and create pull requests from its changes. OpenAI also lets teams decide whether those cloud environments can reach the public internet, which tells you exactly where the product is heading: not just helper mode, but delegated work with policy controls. (openai.com) ### Why does this change the buying question? Because once an agent can browse, install tools, touch files, run commands, and open PRs, the hard problem stops being “is the model smart enough?” The hard problem becomes orchestration — approvals, entitlements, isolation, retries, and how much freedom you give the agent at each step. The value shifts from raw code generation to managed execution across a toolchain. That is a much bigger surface area, but also a much riskier one. (developers.openai.com) ### So what’s the bottom line? The real story is that coding assistants are getting promoted. Codex still writes code, obviously. But OpenAI is now packaging it as a command center for agentic software work — one that can move between planning, editing, previewing, reviewing, and shipping. Once that happens, “AI code editor” stops being the right mental model. “Developer OS” starts to fit. (openai.com 1) (openai.com 2)
