Browser Use, Memory, Personal Workflows

Why OpenAI is merging Codex and ChatGPT and the future of knowledge work | Andrew Ambrosino

Topic 13 of 17

Published Jun 28, 2026 · Clip 47:58–52:05 (4:06)

Andrew explains that OpenAI watches which personal workflows click across many users and promotes them to first-class experiences — memory is the clearest example, since people shouldn't have to build Obsidian or Notion 'mind palaces' when a generic memory feature could do it; other setups are just how you do your job and shouldn't become primitives. On Dan Shipper's prediction of running SaaS apps inside Codex, he reviews the browser-shaped attempts so far: Operator, agent mode, Atlas, the in-app browser, and the Chrome extension. The original in-app browser was Electron-based and meant only for front-end dev testing; moving to the OWL stack that powers Atlas added multitab and enterprise security so you can log into your sites. The hard question is the browser's shape — agent-only tool vs general browser — with messy trade-offs like keyboard-shortcut mapping across VS Code, Chrome, and Linear, and the app must serve total novices through power users, though Andrew doubts he'll convert Peter, 'the last terminal holdout.'