Codex as a Delegation Loop: Your First Personal AI Agent Workflow

Key Takeaways

• Give the computer jobs, not questions. Instead of "draft this / summarize this," Nate hands Codex end-to-end work: find the transcript, read the folder, compare versions, render the file, check it opens, drive the browser — keep going until there's something to inspect.
• The name is misleading. Developers see Codex first because code has clean files, diffs, tests, and logs to engage with — but the same delegation habit applies to research, documents, spreadsheets, running a small business, or just living in a dozen browser tabs. It's on Windows now too.
• Build a "chief-of-staff" thread. Rather than scattering work across many one-off chats (which makes you the router), keep one persistent thread pointed at the work — it knows the goal, the folders, the current artifacts, and the standard, and spins out smaller jobs without re-explaining the project each time.
• Give the objective, not the ask. "Read these sources, produce this artifact, check it against the standard, and don't stop at the first plausible draft" changes the relationship from requesting a response to assigning a job. Threads can use sub-agents for the smaller steps.
• Token burn is a receipt, not a target. Nate's Codex usage hit ~500M tokens in a day — not from chatting more, but because the unit of work scaled up. He's clear: don't chase the number; it just reflects that more of his computer activity now runs through agents.
• The compute paradigm is shifting. For ~40 years computing was app-first with the human moving between apps. Codex points at an agent-first model where the human sits above the work and delegates, and tokens are the cost of letting the agent compute for you. He expects Anthropic to land in the same place.
• Turn repeated corrections into reusable workflows — the playbook for this is still being written by the people pushing the tools hardest.