Most developers start with a narrow view of what a code-editing AI agent can do. They ask it to write code, generate a diff, run tests, and maybe open a pull request. That’s fine—writing code is still Codex’s core strength. But here’s the thing: almost everything we do on a computer is, at its heart, code-adjacent. Terminal commands, web browsing, API calls, exporting docs, responding to events, triggering workflows. When Codex reaches into those areas, it stops being a programming helper and starts being a full-time assistant that lives in your machine.
The shift is real because of the new features in Codex. Threads now remember context. They can call tools, show artifacts, and carry conversations across sessions. You no longer start from scratch every time. To get the most out of Codex, you need to combine a few of these capabilities.
Let’s walk through them.
Durable threads are the foundation. Instead of throwing away context after each chat, you pin a thread and it stays alive—always remembering your decisions, preferences, and where you left off. Think of a “chief of staff” thread for daily errands, a release thread for shipping, a docs review thread, or a monitoring thread that watches external data. Pin them with Command-1 through Command-9, and you can hop back into any of them instantly. Without this, you’d have to feed the same background info every time.
Voice input changes how you start. It captures raw, unpolished thoughts before you’ve shaped them into precise text. You might say, “There was a guy named Ben who mentioned this on Slack. I forget the details. Go find it.” That’s enough for an agent that can search, gather context, and report back. Even better: ramble for two or three minutes to let a half-formed idea spill out. The same goes for meeting recordings or spoken drafts—they keep the hesitation, emphasis, and half-finished sparks that a polished summary misses.
Steering and queuing give you real-time control. Steering interrupts Codex mid‑task to correct direction: “Make that smaller,” “The spacing between these two elements looks off,” “That line of copy is wrong.” Queuing, on the other hand, adds tasks to the end of the current work without interruption: “After this, send the preview link to Slack for review.” One changes what it’s doing now; the other schedules what comes next. Together, they keep you in the loop without micromanaging.
Tools and reach extend Codex beyond your codebase. $browser opens an in‑app browser in the side panel for reviewing and annotating web pages. @chrome pulls in your browser’s login state for workflows that need authenticated sessions. @computer handles tasks that rely on the desktop GUI—clicking through settings, filling forms, anything that lives outside a terminal. MCP servers and connectors push this even further: Slack integration, email, calendars. Most critical tasks start as a chat message or a meeting request, not a spec. Having Codex reach those touchpoints is what makes it feel like a real colleague.
Skills let you package a proven workflow so Codex can run it again without re‑learning. Once you have a reliable routine—say, deploy a preview and notify the team—save it as a Skill and invoke it next time.
Work from anywhere breaks the assumption that you need to be at your desk to get work done. Start a long‑running task on your Mac with all your files and permissions. Walk away. If Codex hits a question, reply from your phone, approve the next step, or redirect it before you get back to your seat. Your environment keeps chugging away; you keep moving.
Automations take this further. Goals let you tell Codex “research this topic and draft a summary,” then walk away. Thread automations trigger actions based on events—new GitHub issue, Slack message, scheduled time. Codex runs in the background, picks up context from durable threads, and does its work while you focus on other things.
The real art isn’t in any single feature. It’s in how they fit together: persistent memory, low‑friction input, real‑time control, broad reach, and the freedom to walk away. That’s how you get the most out of Codex.