By playing, you agree to uListen's Terms and Privacy Policy and YouTube's Terms of Service.
How I AIThe power user’s guide to Codex | Alexander Embiricos (product lead)
Summaries, chapters, transcripts, and FAQs on this page are made by uListen, not YouTube.
At a glance
WHAT IT’S REALLY ABOUT
Power user playbook for Codex: planning, worktrees, and reviews
- Codex is presented as a thorough coding agent that shines on complex tasks, used both for answering questions about unfamiliar codebases and for implementing changes via natural-language prompts.
- The episode demos a zero-to-one setup in VS Code and the terminal, then shows how to run multiple tasks in parallel safely using Git worktrees.
- For larger efforts, Embiricos advocates structured planning (via a shared Plans.md template) and iterating on the plan in the same chat before executing implementation.
- They highlight “harness” differentiation (product + workflow around the model), especially automated GitHub code review that catches issues with high confidence and can even fix them on request, plus broader integrations (web/cloud, Slack, Linear) and personalization via Atlas/Sidechat.
IDEAS WORTH REMEMBERING
5 ideasTreat Codex as a teammate for both questions and code changes.
Embiricos emphasizes that a high-frequency use case is simply asking questions—how to run a repo, what a feature flag does, or whether something shipped—reducing friction and avoiding unnecessary pings to engineers.
Parallelize work, but manage conflicts intentionally.
Small independent tasks can run in parallel chats; when changes might collide, switch to serial execution or isolate work using Git worktrees so each change remains reviewable and non-conflicting.
Use Git worktrees as the “safe parallelism” primitive.
Worktrees let one repo track multiple working directories (e.g., “French” and “German” variants) so Codex can execute concurrent edits without stepping on the same files/branch state.
For hard problems, planning beats one-shot prompting.
The Sora Android app story underscores that agents don’t remove architecture work; teams moved fast by defining the shape of the system, then using detailed plans as the contract Codex executes against.
Adopt a reusable planning spec (Plans.md) to standardize outcomes.
Copying a “how to plan” template into Plans.md makes plans self-contained and milestone-driven; Codex’s thoroughness becomes an advantage when it’s guided into consistent structure.
WORDS WORTH SAVING
5 quotesPeople love how thorough and diligent Codex is. It's not the fastest tool out there, but it is the most thorough and best at hard, complex tasks.
— Alexander Embiricos
We used Codex to build the Sora app for Android in twenty-eight days, and it immediately became the number one app in the App Store.
— Alexander Embiricos
With coding agents, it doesn't get easier, but you just move way faster.
— Alexander Embiricos
If you have a chat where Codex is producing these plans and you want to change something, it's actually really nice for the model if you just use the same chat to ask for changes to the plan.
— Alexander Embiricos
The bottlenecks are kind of like thinking about what code to write and then making sure that code is good, reviewing it and landing it.
— Alexander Embiricos
High quality AI-generated summary created from speaker-labeled transcript.
