Why did the team choose Rust to build Codex when models weren't yet optimized for it?
The team chose Rust from first principles to ensure the agent's core was robust, secure, and engineered for high scale and efficiency. Although the model wasn't initially well-optimized for Rust, they believed compile-time validation would benefit agents and that Rust would quickly become viable with effort. They prioritized structural correctness and clean architectural boundaries over immediate language convenience.
How does Codex achieve lower latency for token generation?
OpenAI uses WebSockets to connect user devices directly to the API, delivering about 1.75x faster tokens without extra cost. Additionally, a fast mode can be enabled to squeeze out an extra 2x speed improvement.
Why did OpenAI decide to open-source the Codex CLI, SDK, and app server?
Open-sourcing allowed the team to build a coding agent while actively pointing it at itself to gather direct community feedback and contributions. They recognized that open source and the role of code were changing, making direct participation in the developer community essential. It also provided a level playing field that encouraged widespread tinkering and exploration during the early days of coding agents.
What features does native work tree support provide in the Codex app?
The Codex app allows developers to manage individual projects and work on multiple features or bug fixes simultaneously inside the same project. Using native work trees prevents tasks from interfering with one another and reduces the need to context switch.
Why does Codex support other model providers instead of just OpenAI?
Codex supports multiple model providers to give users optionality and avoid artificial vendor lock-in. Forcing users onto a single model would create unnecessary forks and prevent the team from learning from other models.
Plugins bundle together skills, apps, and Model Context Protocol servers into a single reusable package. This eliminates the need to manually install multiple skills, connect various apps, or set up external tool connections one by one.
How are AI models changing the role of code reviews?
Automated code review models now handle deep logic verification and security checks that previously required hours of human effort. This shifts human discussion away from syntax and toward high-level intent and architecture. Pull requests flagged with security vulnerabilities are now blocked automatically.
How can developers use automated background workflows in Codex?
Developers can set up automations that act like cron jobs running in the background to handle repetitive tasks. For example, Codex can be configured to summarize daily Slack messages or check for specific notifications automatically.
How does AI impact the cost and process of software maintenance?
Routine maintenance tasks like dependency upgrades are now fully automated by models that can read change logs and update codebases. Rearchitecting systems also happens much faster because models reduce the friction of rewriting legacy code. Consequently, the maintenance tax on software projects is significantly lowered.
How does Codex code review handle changes across a repository?
Codex code review evaluates pull requests by contextualizing changes against the entire model repository rather than just looking at the direct diff. This enables it to catch second-order effects and bugs in modules that were not touched in the pull request itself. It is so effective that 100% of pull requests across OpenAI internal repositories are reviewed by default.
When are rigid harnesses like slash goal no longer needed?
Rigid harnesses were originally necessary as a crutch to keep models on track for multi-day tasks. With newer, more advanced generations of models, these explicit goal harnesses are no longer required. Developers can simply instruct the model to work independently for a week without extra constraints.
When should I configure a subagent to use read-only mode?
You should configure subagents like review agents or cybersecurity vulnerability scanners to always operate in read-only sandbox mode. This ensures the model cannot execute arbitrary code or make unintended write modifications while performing its analysis. In contrast, tasks like documentation writers require write access to execute actions and create bug reports.
What were the main engineering challenges when merging Codex and ChatGPT?
The merge required combining completely different stacks, moving from a fully local coding agent to a managed cloud-based system. The team had to build a cloud environment capable of running the full Codex harness alongside a powerful cloud computer. This unified product allows tens of millions of users to access the same advanced intelligence efficiently.
What is the purpose of Guardian approvals in Codex?
Guardian approvals prevent the safety risks of running coding agents in unfettered YOLO mode by intercepting privileged tasks. Whenever Codex needs to run a privileged command, it spawns a subagent to verify whether human intervention is actually required. This mechanism successfully automates safe approvals and reduces developer fatigue.
How can session hooks be used for long-running tasks in Codex?
Session hooks allow developers to programmatically trigger scripts based on events like session startup, tool usage, or stopping. For example, a developer can configure a stop hook that runs a Python script to tell Codex to keep going after each turn. This enables automated, continuous execution for long-running tasks without manual prompting.
How do I hand off a local task to a cloud agent when closing my laptop?
You can seamlessly hand off your current task from the Codex app directly to a cloud agent before closing your laptop. The app allows you to select cloud execution and even parallelize runs, such as running a task multiple times in the cloud to pick the best output. This capability is built directly into the Codex app, IDE extension, and web interface.
▶ 19:06
Building Codex with Tibo Sottiaux
