Don't forget about the UI for AI
· Summarized
Key takeaways
- OpenAI wants ChatGPT and Codex to become a continuous experience, but will not merge their interfaces until quick questions and long-running coding tasks can be routed without an awkward mode switch.
- The desktop app’s main advantage is local computer access: files, Git checkouts, Node.js tools, and browser testing are easier to manage outside browser restrictions.
- ChatGPT Spaces uses personal agents and memories alongside shared artifacts instead of forcing a team into one lowest-common-denominator group chat.
- As agents make software development faster, product judgment, interaction design, and restraint become more important because users cannot absorb unlimited new features.
- OpenAI’s safety approach combines sandboxing, user-configurable permissions, and a separate approval model that checks whether proposed actions are safe and actually requested.
Summary
Why ChatGPT and Codex are moving toward one experience
Andrew Ambrosino says OpenAI wants one place where users can type or speak a request and have the most capable models and agents handle anything from software development to knowledge work and quick answers. ChatGPT has more than a billion consumers, while Codex’s coding-agent app grew rapidly earlier in the year. ChatGPT Work brought Codex’s harness to a broader audience, but the products remain separate tabs because a quick search should not trigger a long Codex reasoning process. OpenAI will merge the experiences only when it can provide a continuous spectrum without forcing users to choose a mode.
Why OpenAI still ships a desktop app
Ambrosino argues that local computer access makes the desktop app useful even though most software now runs in browsers. Codex can work with files, a Git checkout, local Node.js calls, and a browser for testing—capabilities constrained by browser security and sandboxing. OpenAI is also bringing cloud Codex into the browser, while the desktop app can act as a bridge to the user’s own computer and browser when an existing checkout is available. He says sandboxing remains important and that OpenAI has additional work in progress around desktop security.
Spaces keeps personal agents separate while teams collaborate
OpenAI’s new ChatGPT Space is intended as a collaborative workspace where people, their agents, and shared artifacts can work together in real time. Rather than putting everyone into one chat—with competing memories, connectors, and permissions—each person keeps an agent with personal tools and preferences, then collaborates on pages, sites, and documents. Ambrosino says this avoids reducing the group to the lowest common denominator of available connections. Teams can plan a feature on live pages, tag an agent to research weekly users, insert an interactive chart, and revise it collaboratively.
The five-week CRDT build and the feel of agent collaboration
To support character-level document editing, live cursors, brief disconnections, and offline states, the team built a full CRDT system in five or six weeks. The harder product questions involved agents editing alongside people: whether multiple tagged requests should run in parallel, how their threads should be organized, and how everyone sees updates. Ambrosino compares the solution to Codex’s fluid computer-use cursor. The cursor is not necessary for the model, but its motion helps users understand what is happening; similarly, animated document changes let people feel which text was edited instead of watching content jump unpredictably.
Taste is the bottleneck in an era of rapid software releases
Ambrosino says OpenAI launched more than 20 things at Dev Day while simultaneously redesigning Spaces, the desktop sidebar, and the browser version of ChatGPT. He believes the speed of development creates a new problem: users and organizations cannot absorb a new feature every day, even if agents can build features quickly. Judgment and taste determine which explorations belong together and which are not ready. OpenAI tries to test products internally first; if employees do not love something, the team does not rationalize that another audience will. He also says the terminal remains important, including in a new Codex CLI refresh.
Harness design, safety approvals, and dogfooding Spaces
The Codex product, research, and core-harness teams work closely on features such as code mode, where the model writes code to plan several computer-use steps instead of reasoning through every action individually. Plugins now provide a cleaner extension mechanism than stuffing behavior into developer prompts. For safety, an approval model judges whether a tool action is safe and matches the user’s request; settings can approve or block applications and websites, while some delegation capabilities remain restricted. Spaces itself was developed inside its own pages using interactive visualization blocks, letting the team generate mock-up variations, test single-player or multiplayer behavior, and tag Codex to build the chosen design.
Sponsors
- Raytheon · Raytheon is hiring software, systems, and hardware engineers to work on complex technical challenges.
Show notes
Recorded at OpenAI Dev Day 2026, Ryan sits down with Andrew Ambrosino, member of the technical staff at OpenAI, for a conversation on OpenAI's strategy for merging ChatGPT and Codex into a unified experience, the advantages of localized computer access in their successful desktop application, and the technical hurdles of constructing ChatGPT Spaces to support real-time multi-agent collaboration.
Episode notes:
ChatGPT Space is a newly launched collaborative workspace within ChatGPT and Codex that allows software engineering teams and their active AI agents to work together in real-time.
Connect with Andrew on X.
See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.
Follow this show on AudioBrevity and new episodes get summarized for you. Create a free account