Dominik Kundel
Developer and product leader focused on developer experience and generative AI. He works on Developer Experience and SDKs at OpenAI, and previously led Product and Design for Twilio’s Emerging Tech & Innovation organization.
GPT-5.6 Lets ChatGPT Complete Work Inside Existing Tools
OpenAI’s Dominik Kundel argues that ChatGPT’s GPT-5.6 desktop app is designed to complete work in the systems where it already resides, rather than merely generate instructions or text in a separate chat window. He divides that work by environment: an in-app browser for researching sites and assessing material, a Chrome connection for existing browser workflows such as expense entry, and computer use for desktop applications such as Apple Notes.
Codex Micro Brings Physical Controls to AI Workflows
OpenAI’s Dominik Kundel presents the Codex Micro, built with Work Louder, as a customizable hardware control surface for directing and monitoring Codex work. In a demo using GPT-5.6 Sol to build a browser word game, he uses dedicated controls for voice prompts, Plan mode, reasoning effort, task switching, permission approvals and queued follow-up requests. Kundel’s central claim is that users can map those actions to physical inputs around their own workflow rather than rely on a fixed keyboard layout.
ChatGPT Work Links Analytics, Computer Use, and Code Fixes
OpenAI’s Dominik Kundel presents ChatGPT Work as a mode for delegating work across connected apps, files, local projects, browser sessions, computer use and Codex, rather than as another chat interface. The walkthrough’s central claim is that ChatGPT can carry context through a full work chain: preparing recurring briefings, generating launch materials, analyzing product data, publishing a dashboard and, in the sharpest example, tracing a Mexico onboarding anomaly to a phone-validation bug and preparing the code fix for review.
Codex Can Now Work Inside Users’ Live Chrome Sessions
OpenAI’s Dominik Kundel presents Codex’s new Chrome extension for macOS and Windows as a way for the agent to work inside a user’s actual browser session, including logged-in apps, open tabs, cookies, and local context. He argues that plugins remain the faster route for structured tasks, but Chrome access matters when the work depends on a live web app, an existing browser state, or actions such as filling forms, uploading files, and coordinating work across multiple tabs without taking over the user’s browser.