The TWIML AI Podcast
The TWIML AI Podcast

Codex, OpenAI’s Automated Code Generation API with Greg Brockman - #509

Today we’re joined by return guest Greg Brockman, co-founder and CTO of OpenAI. We had the pleasure of reconnecting with Greg on the heels of the announcement of Codex, OpenAI’s most recent release. Codex is a direct descendant of GPT-3 that allows users to do autocomplete tasks based on all of the

Featured Speakers

Greg Brockman Guest

Topics Discussed

Episode Summary

Executive Summary: Greg Brockman discusses Codex, OpenAI’s code-focused descendant of GPT-3, explaining how it was trained on text plus public code, evaluated with runnable programming tasks, and designed to help with code generation, tutoring, and workflow automation. He argues that progress in AI still depends on scale plus continual algorithmic innovation, while noting major implications for productivity, education, safety, copyright, and bias.

Main Topics: Origin of Greg Brockman’s AI interest (Priority: 5/5): Brockman traces his path from reading Turing’s 1950 paper to early NLP, programming languages, startups, and eventually deep learning in 2015 as the field that felt most aligned with his original fascination: machines that solve problems beyond human reach. What Codex is and how it relates to GPT-3 and Copilot (Priority: 5/5): Codex is presented as a descendant of GPT-3, trained on internet text plus public code. GitHub Copilot is the first product built on Codex, created with GitHub and Microsoft to validate real-world usefulness from the start. Training data, evaluation, and sandboxing (Priority: 5/5): OpenAI uses human-written programming puzzles (HumanEval) and executable tests to measure Codex, emphasizing that code generation must be evaluated in a safe sandbox because model outputs can be unpredictable or harmful if run directly. How Codex behaves versus GPT-3 (Priority: 4/5): Brockman says GPT-3 often felt inconsistent and short-attention-spanned, while Codex is more reliable because code has tighter structure: instructions like comments or docstrings more directly imply the next tokens and desired output. Future directions: prompts, examples, fine-tuning, and task decomposition (Priority: 4/5): He highlights prompt iteration, examples, and upcoming fine-tuning as ways to improve performance, and suggests a promising path in using Codex not just to emit code but to decompose complex tasks and orchestrate other tools. Societal implications: jobs, copyright, and bias (Priority: 5/5): Brockman argues AI is likely to automate slices of many jobs rather than eliminate whole occupations, believes training on public text/code is fair use, and stresses the need for technical and societal alignment to manage bias and safety risks. Access, rollout, and competition (Priority: 3/5): OpenAI plans a private beta rollout starting Tuesday and a programming competition on Thursday using Codex as both teammate and competitor, aiming to gather feedback from students, academics, and broader users.

Key Arguments: Codex is not a separate paradigm but a code-specialized descendant of GPT-3, built by adding public code and substantial engineering improvements. The best evaluation for code models is runnable task performance, not just perplexity, because coding is about solving a problem correctly, not only predicting tokens. Sandboxing is essential because generated code can be unsafe, resource-intensive, or system-breaking if executed without isolation. Code is structurally different from ordinary text, which makes Codex more reliable and more faithful to instructions than GPT-3. The biggest near-term value of Codex is reducing drudge work and barrier-to-entry tasks, freeing humans for architecture, product thinking, and creativity. AI progress still depends on scaling compute and data, but algorithmic improvements remain a major frontier and should not be neglected. Codex could become a programming tutor, code explainer, and tool for education by generating comments, docs, tests, and explanations. OpenAI believes training on publicly available text and code is fair use and wants a public conversation as the law catches up. Bias and alignment matter more as models become capable of producing executable code with real-world consequences. The rollout strategy is to learn from real users via staged access and competitions before broad deployment.

Data Points: Podcast episode reference: Episode 74 - Brockman was last on the show in November 2017, and the podcast is now over 500 episodes. Codex development time: About 1 year - Brockman says OpenAI had been building the Codex model for roughly a year. HumanEval dataset: Open source - HumanEval is described as an open-source dataset of human-written programming puzzles used as a North Star metric. OpenAI internal effort: About a quarter of OpenAI - Brockman says roughly a quarter of the company worked on Codex. Languages Codex is good at: About a dozen - He says Codex works across roughly a dozen languages despite being trained primarily on Python. Primary training focus: Python - OpenAI says it trained Codex mainly to be as good at Python as possible. Suggested temperature setting: 0 - Brockman says his experiments usually used temperature = 0 for deterministic output. Output quality estimate: 80% - He describes Codex as often completing about 80% of a programming task before missing a detail. Competition timing: Thursday, 10 a.m. - A programming competition with Codex was scheduled for Thursday at 10 a.m. Rollout timing: Tuesday - Codex API invites were planned to start rolling out on Tuesday, relative to the interview release timing. Text/data source scope: All the text on the internet and all public code - Brockman characterizes Codex training as a descendant of GPT-3 expanded to include public code.

Pivotal Quotes: "Codex is take all the text on the internet and all the public code and do that same process." — Greg Brockman: Explaining how Codex differs from GPT-3 in training data and purpose. "The highest order bit is actually achieving that first thing." — Greg Brockman: Arguing that large-scale compute and data are still the primary drivers of progress. "We need to figure out what values go into these systems." — Greg Brockman: Discussing bias, safety, and alignment concerns for executable AI systems.

Implications: Codex points toward AI that augments software development, learning, and workflow automation. It could lower barriers for beginners and boost productivity, but also raises urgent questions about safety, bias, copyright, and how humans supervise executable AI.

🔓 Sign Up for Unlimited Episode Search

About The TWIML AI Podcast

View all episodes from The TWIML AI Podcast