OpenAI's Codex developer experience lead sits down with a former comedian turned ML engineering lead for a conversation about what happens when computer use agents stop being a novelty and start actually running your day. The conversation moves through building an AI-powered morning brief that reads every email, Slack message, and tweet before you've even opened your laptop, letting pinned threads check in on themselves every 30 minutes, and a skills system built to mirror how a person actually writes and reviews code. There's a close look at the guardrails and permission layers that keep an autonomous agent from pushing to the wrong repo or replying to the wrong tweet, how a codebase merging thousands of pull requests a day survives thanks to self-healing review before anything hits CI, and the idea of AI deference - when an agent should push through a task alone versus stop and ask for help. The back half gets personal: why developing taste and vocabulary now matters more than working harder, what it actually takes to delegate to an agent the way you'd onboard a new employee, and why this might be the year voice-orchestrated computer use finally makes everyone feel like they're talking to Jarvis.

A deep dive into the "design-by-intuition" tax in AI engineering, comparing convergent and divergent agent loops. It introduces agent-evolutions, a genetic search framework that spawns variants in parallel, evaluates them against frozen binary gates and numeric rubrics, and relies on a robust file-based sub-agent contract rather than chat parsing.

Many coding agents fail because they improvise internal planning loops, leading to unchecked code or runaway sessions. This article details how externalizing a structured Plan-Do-Check-Act (PDCA) engineering loop into a disk-based workflow acts as a leverage multiplier. By forcing agents through an explicit, step-by-step verification process, developers can reliably guide agents to finish what they start with minimal human intervention.