Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

If you use Codex, Tibo needs no introduction. We talked 100% about Codex (fun fact: he started building it!), and 0% about resets. Timestamps: 00:00 Intro 07:21 Working at Google 12:41 What drew Tibo to OpenAI 15:19 The early days of Codex 18:20 Why Codex was built in Rust...

GergelyOrosz's profile picture

Gergely Orosz

354,721 subscribers

76,617 görüntüleme • 2 gün önce •via X (Twitter)

Bilim & TeknolojiEğitim
LIVE

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

Orijinal gönderinin yorumları burada görünecek

Benzer Videolar

Three months ago, Codex was trash for knowledge work. Now it's my daily driver. I use it for writing, recruiting, deep engineering work, and everything in between. It even keeps me at inbox 0. I chatted with Every 🧱's head of growth Austin Austin Tedesco on Every 🧱's AI & I about what changed, and why he now spends 80% of his working time in the Codex desktop app too. We get into: - How Codex went from making Austin feel like an idiot to being the place he goes to get stuff done, including complex tasks like writing go-to-market plans using existing material from Slack, Notion, and meeting transcripts. - Why the Codex’s desktop app, which is faster and more reliable than Claude Desktop/Cowork, is the real differentiator. - How I source candidates with Codex by having it identify career arcs, not keywords—my go-to move is identifying organizations likely to teach the skills Every needs for a role, and then find candidates from that pool who have since gone on to work in AI. This is a must-watch for anyone who's wondering whether it’s finally time to give Codex a try. Watch below! Timestamps How Codex went from a tool for senior engineers to a daily driver for knowledge work: 00:00:57 How Claude Code proved that a great coding agent works for any knowledge work: 00:02:42 Austin's switch to Codex: 00:07:24 How Austin set up Codex with folders, keys, and reviewer agents: 00:13:48 Using Codex to brainstorm automations across Gmail, Slack, and Notion: 00:18:24 How Austin manages the human review step when Codex is drafting communications: 00:22:42 Using Codex to build specialized agents inspired by product executive Claire Vo: 00:28:54 Synthesizing meeting transcripts and Slack threads into a go-to-market plan: 00:31:09 Building a live KPI tracker in Notion that agents can read: 00:40:15 Using Codex for recruiting: 00:44:54
58:23

Three months ago, Codex was trash for knowledge work. Now it's my daily driver. I use it for writing, recruiting, deep engineering work, and everything in between. It even keeps me at inbox 0. I chatted with Every 🧱's head of growth Austin Austin Tedesco on Every 🧱's AI & I about what changed, and why he now spends 80% of his working time in the Codex desktop app too. We get into: - How Codex went from making Austin feel like an idiot to being the place he goes to get stuff done, including complex tasks like writing go-to-market plans using existing material from Slack, Notion, and meeting transcripts. - Why the Codex’s desktop app, which is faster and more reliable than Claude Desktop/Cowork, is the real differentiator. - How I source candidates with Codex by having it identify career arcs, not keywords—my go-to move is identifying organizations likely to teach the skills Every needs for a role, and then find candidates from that pool who have since gone on to work in AI. This is a must-watch for anyone who's wondering whether it’s finally time to give Codex a try. Watch below! Timestamps How Codex went from a tool for senior engineers to a daily driver for knowledge work: 00:00:57 How Claude Code proved that a great coding agent works for any knowledge work: 00:02:42 Austin's switch to Codex: 00:07:24 How Austin set up Codex with folders, keys, and reviewer agents: 00:13:48 Using Codex to brainstorm automations across Gmail, Slack, and Notion: 00:18:24 How Austin manages the human review step when Codex is drafting communications: 00:22:42 Using Codex to build specialized agents inspired by product executive Claire Vo: 00:28:54 Synthesizing meeting transcripts and Slack threads into a go-to-market plan: 00:31:09 Building a live KPI tracker in Notion that agents can read: 00:40:15 Using Codex for recruiting: 00:44:54

Dan Shipper 📧

55,561 görüntüleme • 4 ay önce

When I talk to serious software engineers, they tell me everyone is sleeping on Codex + GPT 5.2 from OpenAI Which is why I was hyped to get an insiders "how to" from Alexander Embiricos product lead for Codex, showing us how he and the team use Codex to ship almost everything at oai. He'll show us how to: - jump into a new repo and start contributing, even as a non-technical PM - run git worktrees to parallelize agent tasks across codex instances - use best practices and to spec out your work and let codex rip We also talk model vs. harness and how to spy on codex development (which is all OSS!) to understand how to optimize your own implementations. This episode is brought to you by our amazing sponsors 🧠🤑 Brex - The intelligent finance platform built for founders 🦎🐛 Greptile - Your AI code review platform Watch it here:
0:47

When I talk to serious software engineers, they tell me everyone is sleeping on Codex + GPT 5.2 from OpenAI Which is why I was hyped to get an insiders "how to" from Alexander Embiricos product lead for Codex, showing us how he and the team use Codex to ship almost everything at oai. He'll show us how to: - jump into a new repo and start contributing, even as a non-technical PM - run git worktrees to parallelize agent tasks across codex instances - use best practices and to spec out your work and let codex rip We also talk model vs. harness and how to spy on codex development (which is all OSS!) to understand how to optimize your own implementations. This episode is brought to you by our amazing sponsors 🧠🤑 Brex - The intelligent finance platform built for founders 🦎🐛 Greptile - Your AI code review platform Watch it here:

claire vo 🖤

48,134 görüntüleme • 8 ay önce

Michael Bolin (Michael Bolin) is the tech lead of the Codex open source repository at OpenAI and formerly a distinguished eng (E9) at Meta. I asked him for all the details on his career story and how he uses Codex for max benefit. Timestamps: 00:00:00 - Intro 00:00:56 - Chickenfoot 00:02:45 - Working at Google 00:06:34 - Overhauling Facebook's build system 00:16:36 - Rewriting Facebook's IDE 00:26:01 - Struggles after Principal Eng (E8) promo 00:28:39 - Building a virtual filesystem for Facebook 00:35:47 - Delayed Distinguished promo (E9) and learnings 00:39:56 - Joining OpenAI 00:43:05 - Research-led vs engineering-led cultures 00:44:53 - The story behind Codex 00:51:00 - How he uses Codex 00:57:00 - Why Codex's harness is open source 00:59:50 - Top technical book recommendations 01:05:02 - Why deep technical skills are still valuable (for now) 01:11:07 - How to start projects well 01:14:27 - Advice on writing better and career planning 01:17:06 - Advice for his younger self 01:19:10 - Outro He was a dream guest of mine and I'm excited to share his story with you all! Other places to watch: • YouTube: • Spotify: • Apple Podcasts: • Transcript:
1:20:03

Michael Bolin (Michael Bolin) is the tech lead of the Codex open source repository at OpenAI and formerly a distinguished eng (E9) at Meta. I asked him for all the details on his career story and how he uses Codex for max benefit. Timestamps: 00:00:00 - Intro 00:00:56 - Chickenfoot 00:02:45 - Working at Google 00:06:34 - Overhauling Facebook's build system 00:16:36 - Rewriting Facebook's IDE 00:26:01 - Struggles after Principal Eng (E8) promo 00:28:39 - Building a virtual filesystem for Facebook 00:35:47 - Delayed Distinguished promo (E9) and learnings 00:39:56 - Joining OpenAI 00:43:05 - Research-led vs engineering-led cultures 00:44:53 - The story behind Codex 00:51:00 - How he uses Codex 00:57:00 - Why Codex's harness is open source 00:59:50 - Top technical book recommendations 01:05:02 - Why deep technical skills are still valuable (for now) 01:11:07 - How to start projects well 01:14:27 - Advice on writing better and career planning 01:17:06 - Advice for his younger self 01:19:10 - Outro He was a dream guest of mine and I'm excited to share his story with you all! Other places to watch: • YouTube: • Spotify: • Apple Podcasts: • Transcript:

Ryan Peterman

119,601 görüntüleme • 6 ay önce

OpenAI’s hottest app isn’t ChatGPT—it’s Codex. In the last few weeks alone, the Codex team shipped a desktop app, GPT-5.3 Codex (a new flagship model), and Spark, the fastest coding model I’ve ever used. Usage has grown fivefold since January and over a million people now use Codex weekly. Codex was also the app that OpenAI chose to run an ad for in the Super Bowl. I talked to Thibault (Tibo), head of Codex, and Andrew (Andrew Ambrosino), a member of technical staff who built the Codex app, for Every 📧’s AI & I about what OpenAI is building and how they’re using it internally. We get into: - Why they built a GUI instead of a terminal. Terminals work for quick tasks, they say, but feel limiting when you’re running multiple agents in parallel. The IDE, meanwhile, overwhelms users—and the Codex team wants the AI to dynamically decide which tools to show you for a given task. - How they’re teaching the model to read between the lines. Codex is great at following instructions, but optimize too hard in that direction, and it starts taking you literally—like copying a typo directly into the code. The team obsesses over this tradeoff, and is also introducing “personalities,” modes users can toggle between that control how blunt or supportive the model feels. - How OpenAI uses its own coding agent. Codex lets you schedule prompts to run on a recurring basis, and the team has dozens of automations running at all times. For example, one scans for merge conflicts every couple of hours so code is always ready to ship, and another picks a random file from the codebase multiple times a day and hunts for bugs no one would've gone looking for. - Why speed is a dimension of intelligence. OpenAI’s newest model (Spark) is so fast that they actually slow it down so you can read the output. They see the speed enabling three things: staying super in the flow, replacing brittle developer tools with intelligent ones that can adapt on the fly, and redirecting the model mid-task— especially with voice—so coding starts to feel more and more like a conversation. - Code review is the next bottleneck. Models can generate code faster than ever, but someone still has to verify that it works. The team is exploring a future where the model proves its own fix works—retracing the click path a user would take, screenshotting the results, and attaching the evidence to a pull request. This is a must-watch for anyone who uses AI coding agents—and is curious about the future of programming. Watch below! Timestamps: Introduction: 00:01:27 OpenAI’s evolving bet on its coding agent: 00:05:27 The choice to invest in a GUI (over a terminal): 00:09:42 The AI workflows that the Codex team relies on to ship: 00:20:38 Teaching Codex how to read between the lines: 00:26:45 Building affordances for a lightening fast model: 00:28:45 Why speed is a dimension of intelligence: 00:33:15 Code review is the next bottleneck for coding agents: 00:36:30 How the Codex team positions against the competition: 00:41:24
46:40

OpenAI’s hottest app isn’t ChatGPT—it’s Codex. In the last few weeks alone, the Codex team shipped a desktop app, GPT-5.3 Codex (a new flagship model), and Spark, the fastest coding model I’ve ever used. Usage has grown fivefold since January and over a million people now use Codex weekly. Codex was also the app that OpenAI chose to run an ad for in the Super Bowl. I talked to Thibault (Tibo), head of Codex, and Andrew (Andrew Ambrosino), a member of technical staff who built the Codex app, for Every 📧’s AI & I about what OpenAI is building and how they’re using it internally. We get into: - Why they built a GUI instead of a terminal. Terminals work for quick tasks, they say, but feel limiting when you’re running multiple agents in parallel. The IDE, meanwhile, overwhelms users—and the Codex team wants the AI to dynamically decide which tools to show you for a given task. - How they’re teaching the model to read between the lines. Codex is great at following instructions, but optimize too hard in that direction, and it starts taking you literally—like copying a typo directly into the code. The team obsesses over this tradeoff, and is also introducing “personalities,” modes users can toggle between that control how blunt or supportive the model feels. - How OpenAI uses its own coding agent. Codex lets you schedule prompts to run on a recurring basis, and the team has dozens of automations running at all times. For example, one scans for merge conflicts every couple of hours so code is always ready to ship, and another picks a random file from the codebase multiple times a day and hunts for bugs no one would've gone looking for. - Why speed is a dimension of intelligence. OpenAI’s newest model (Spark) is so fast that they actually slow it down so you can read the output. They see the speed enabling three things: staying super in the flow, replacing brittle developer tools with intelligent ones that can adapt on the fly, and redirecting the model mid-task— especially with voice—so coding starts to feel more and more like a conversation. - Code review is the next bottleneck. Models can generate code faster than ever, but someone still has to verify that it works. The team is exploring a future where the model proves its own fix works—retracing the click path a user would take, screenshotting the results, and attaching the evidence to a pull request. This is a must-watch for anyone who uses AI coding agents—and is curious about the future of programming. Watch below! Timestamps: Introduction: 00:01:27 OpenAI’s evolving bet on its coding agent: 00:05:27 The choice to invest in a GUI (over a terminal): 00:09:42 The AI workflows that the Codex team relies on to ship: 00:20:38 Teaching Codex how to read between the lines: 00:26:45 Building affordances for a lightening fast model: 00:28:45 Why speed is a dimension of intelligence: 00:33:15 Code review is the next bottleneck for coding agents: 00:36:30 How the Codex team positions against the competition: 00:41:24

Dan Shipper 📧

15,588 görüntüleme • 6 ay önce

🚨 OpenAI just launched Codex, a brand-new autonomous coding agent that can build features and fix bugs on its own. We’ve been using it Every 📧 for a few days, and I’m impressed. I invited Alexander Embiricos (ben davies), a member of the product staff responsible for Codex, to demo Codex and talk about it live on a special edition of AI & I: What Codex is and how it works Codex is designed to be used by senior engineers—it performs coding tasks like adding features or fixing bugs autonomously. It's built to allow you to start many sessions at once, so you can have multiple agents working in parallel. Codex is built to have "taste" OpenAI trained Codex to have the taste of a senior software engineer. It knows how big codebases work, how to write a good PR, and uses clean, minimal code. Why an “abundance mindset” is best for interacting with agents Codex is designed to allow users to delegate many tasks at once without getting caught up in the details. This lets you point an abundance of agents at a specific task like a difficult bug—it’s worth it even if only one of them succeeds. How OpenAI is thinking about agents Codex is one piece of a unified super-assistant OpenAI wants to eventually build—an agent that helps users easily get things done by selecting the right tools for them behind the scenes. OpenAI’s vision for the future of programming In the future developers will probably spend less time writing routine code and more time guiding agents, reviewing their work, and making strategy decisions. Programming will become more social, letting teams easily delegate multiple tasks at once, allowing people to focus on ideas and collaboration instead of routine coding. Watch below!
44:33

🚨 OpenAI just launched Codex, a brand-new autonomous coding agent that can build features and fix bugs on its own. We’ve been using it Every 📧 for a few days, and I’m impressed. I invited Alexander Embiricos (ben davies), a member of the product staff responsible for Codex, to demo Codex and talk about it live on a special edition of AI & I: What Codex is and how it works Codex is designed to be used by senior engineers—it performs coding tasks like adding features or fixing bugs autonomously. It's built to allow you to start many sessions at once, so you can have multiple agents working in parallel. Codex is built to have "taste" OpenAI trained Codex to have the taste of a senior software engineer. It knows how big codebases work, how to write a good PR, and uses clean, minimal code. Why an “abundance mindset” is best for interacting with agents Codex is designed to allow users to delegate many tasks at once without getting caught up in the details. This lets you point an abundance of agents at a specific task like a difficult bug—it’s worth it even if only one of them succeeds. How OpenAI is thinking about agents Codex is one piece of a unified super-assistant OpenAI wants to eventually build—an agent that helps users easily get things done by selecting the right tools for them behind the scenes. OpenAI’s vision for the future of programming In the future developers will probably spend less time writing routine code and more time guiding agents, reviewing their work, and making strategy decisions. Programming will become more social, letting teams easily delegate multiple tasks at once, allowing people to focus on ideas and collaboration instead of routine coding. Watch below!

Dan Shipper 📧

145,487 görüntüleme • 1 yıl önce

This week's guest on Uncapped is Brad Lightcap, COO at OpenAI. We talked about the history of OpenAI, the shift in AI from chat to agents, where new startups can endure, Codex, FDEs, working with Sam, and more. Hope you enjoy! (0:00) Intro (0:39) The early days of OpenAI (3:47) A research centric culture (7:32) Post-ChatGPT chapters (11:54) Sci-Fi future or good software (15:26) AI’s impact on rural communities (18:57) Codex and coding of the future (24:04) Doing a lot of things at once (27:55) What VCs should invest in (35:43) The software sell off (38:23) Using Codex over ChatGPT (42:32) FDEs and Private Equity (44:53) Working with Sam
49:33

This week's guest on Uncapped is Brad Lightcap, COO at OpenAI. We talked about the history of OpenAI, the shift in AI from chat to agents, where new startups can endure, Codex, FDEs, working with Sam, and more. Hope you enjoy! (0:00) Intro (0:39) The early days of OpenAI (3:47) A research centric culture (7:32) Post-ChatGPT chapters (11:54) Sci-Fi future or good software (15:26) AI’s impact on rural communities (18:57) Codex and coding of the future (24:04) Doing a lot of things at once (27:55) What VCs should invest in (35:43) The software sell off (38:23) Using Codex over ChatGPT (42:32) FDEs and Private Equity (44:53) Working with Sam

Jack Altman

120,785 görüntüleme • 5 ay önce

.Natalia rode so hard for Claude Code we devoted an episode to how she was using it to automate her job running Every 📧’s consulting practice. Fast forward to five months later, and she rides just as hard for Codex. I had her back on AI & I to talk about what caused her to make the switch, including how she ran a prompt in Codex before bed and woke up to a finished, custom CRM tool. We get into: - Why she finds Codex easier to use than Claude Code - How she’s using loops in Codex to create customized tools that work exactly how she needs them to - Why the consulting team still pays for SaaS products like Attio and Asana even though they could vibe code their own versions - How she built an app to manage her father’s medical care in Codex - How knowledge work is evolving from sculpting to gardening, in which you develop the context and logic you need for an agent to execute for you This is a must-watch for anyone trying to figure out whether to build their own tools or buy real software—and what it takes to get an AI agent to run unsupervised for hours and nail the output. Watch below! Timestamps 1. Introduction: 00:01:05 2. How Natalia manages Claudie, the consulting team’s AI project manager: 00:02:35 3. Why the consulting team still pays for SaaS products: 00:04:55 4. Codex as a game changer : 00:11:47 5. Building personalized learning guides and illustrated explainers with AI: 00:14:55 6. Inside Natalia's AI-powered email triage system: 00:21:40 7. The shift from knowledge work as sculpting to knowledge work as gardening: 00:26:44 8. Using Codex to on-shot a custom CRM: 00:28:57 9. Using Codex to build an app that coordinates her father’s medical care: 00:33:16
41:15

.Natalia rode so hard for Claude Code we devoted an episode to how she was using it to automate her job running Every 📧’s consulting practice. Fast forward to five months later, and she rides just as hard for Codex. I had her back on AI & I to talk about what caused her to make the switch, including how she ran a prompt in Codex before bed and woke up to a finished, custom CRM tool. We get into: - Why she finds Codex easier to use than Claude Code - How she’s using loops in Codex to create customized tools that work exactly how she needs them to - Why the consulting team still pays for SaaS products like Attio and Asana even though they could vibe code their own versions - How she built an app to manage her father’s medical care in Codex - How knowledge work is evolving from sculpting to gardening, in which you develop the context and logic you need for an agent to execute for you This is a must-watch for anyone trying to figure out whether to build their own tools or buy real software—and what it takes to get an AI agent to run unsupervised for hours and nail the output. Watch below! Timestamps 1. Introduction: 00:01:05 2. How Natalia manages Claudie, the consulting team’s AI project manager: 00:02:35 3. Why the consulting team still pays for SaaS products: 00:04:55 4. Codex as a game changer : 00:11:47 5. Building personalized learning guides and illustrated explainers with AI: 00:14:55 6. Inside Natalia's AI-powered email triage system: 00:21:40 7. The shift from knowledge work as sculpting to knowledge work as gardening: 00:26:44 8. Using Codex to on-shot a custom CRM: 00:28:57 9. Using Codex to build an app that coordinates her father’s medical care: 00:33:16

Dan Shipper 📧

25,701 görüntüleme • 2 ay önce

This is crazy, I can talk to OpenAI's realtime API, and it'll respond back with voice, and then help call Codex to help me code! Got curious about Codex and its realtime integration, and found codex's feature flag `realtime_conversation` integrated for the codex app-server. How it works: - launch codex app-server with realtime - connect a client to realtime through WebRTC voice connection - Codex app-server is also attached on the side - talk to realtime - realtime decides whether coding is needed, and responds back with events - Codex app-server takes these events and runs codex agent turns - codex writes code like your codex cli exp Keep in mind OpenAI hasn't released this officially, they're still actively working on it, I just created a fork. This is a completely new UX than the usual chat interface for agentic coding. For example, when the agent responds back in voice, it's actually faster for me to read the response, and I don't actually find voice response that useful unless it does so in the background. But image realtime working in the background, you can talk to it, realtime keeps track of the different agents working on your tasks and your status. More to come on demo side, i'll make a more polished version and include voice, but thought this was cool to share. You can see in the responses the distinction between my voice input, realtime response, and realtime calling Codex to do work!
0:28

This is crazy, I can talk to OpenAI's realtime API, and it'll respond back with voice, and then help call Codex to help me code! Got curious about Codex and its realtime integration, and found codex's feature flag `realtime_conversation` integrated for the codex app-server. How it works: - launch codex app-server with realtime - connect a client to realtime through WebRTC voice connection - Codex app-server is also attached on the side - talk to realtime - realtime decides whether coding is needed, and responds back with events - Codex app-server takes these events and runs codex agent turns - codex writes code like your codex cli exp Keep in mind OpenAI hasn't released this officially, they're still actively working on it, I just created a fork. This is a completely new UX than the usual chat interface for agentic coding. For example, when the agent responds back in voice, it's actually faster for me to read the response, and I don't actually find voice response that useful unless it does so in the background. But image realtime working in the background, you can talk to it, realtime keeps track of the different agents working on your tasks and your status. More to come on demo side, i'll make a more polished version and include voice, but thought this was cool to share. You can see in the responses the distinction between my voice input, realtime response, and realtime calling Codex to do work!

Matthew Lam

17,674 görüntüleme • 3 ay önce

THE 64 MINUTE OPENAI CODEX MASTERCLASS IS HERE if you've been meaning to learn Codex, this is the episode for you, we cover: 1/ Claude vs Codex (what's better?) 2/How to run Claude Code inside Codex (really cool) 3/Why GPT 5.5 changed everything for browser agents 4/How to create skills (reusable agents you build once and call by name forever) 5/How to connect Notion with surgical permissions (one database, not the whole workspace) 6/How to use Remotion inside Codex to create videos 7/ How to one-shot full mobile apps in Swift 8/The 4 projects to run on day one to get up to speed fast shoutout to Riley Brown for coming onto The Startup Ideas Podcast (SIP) 🧃 for the 5th time. every episode he delivers. this one is the Codex masterclass. if you've been meaning to learn Codex, this is the episode. 100% free i just want to see you build your ideas. watch
1:04:40

THE 64 MINUTE OPENAI CODEX MASTERCLASS IS HERE if you've been meaning to learn Codex, this is the episode for you, we cover: 1/ Claude vs Codex (what's better?) 2/How to run Claude Code inside Codex (really cool) 3/Why GPT 5.5 changed everything for browser agents 4/How to create skills (reusable agents you build once and call by name forever) 5/How to connect Notion with surgical permissions (one database, not the whole workspace) 6/How to use Remotion inside Codex to create videos 7/ How to one-shot full mobile apps in Swift 8/The 4 projects to run on day one to get up to speed fast shoutout to Riley Brown for coming onto The Startup Ideas Podcast (SIP) 🧃 for the 5th time. every episode he delivers. this one is the Codex masterclass. if you've been meaning to learn Codex, this is the episode. 100% free i just want to see you build your ideas. watch

GREG ISENBERG

200,125 görüntüleme • 4 ay önce

Is Claude Code Better Than Cursor? This video is a crystal clear explanation on what makes Claude Code different than Cursor, Codex and Windsurf. A classic whiteboard conversation! Next time he's on the pod (soon) he's going to build an app from scratch that will blow your mind. TIMESTAMPS: 00:00 Intro to Claude Code 00:28 Why Claude Code Is Best 02:38 Comparing Cursor, Windsurf & Claude Code 07:41 Using Claude Code with Other IDEs 12:41 Future of AI Coding Tools & Claude’s SDK 19:58 Integrating Codex with Chat GPT 21:14 Best AI Code Review Tools (Devon, CodeRabbit 26:49 Building an App with Claude Code (Step-by-Step) 35:32 Future Plans
37:07

Is Claude Code Better Than Cursor? This video is a crystal clear explanation on what makes Claude Code different than Cursor, Codex and Windsurf. A classic whiteboard conversation! Next time he's on the pod (soon) he's going to build an app from scratch that will blow your mind. TIMESTAMPS: 00:00 Intro to Claude Code 00:28 Why Claude Code Is Best 02:38 Comparing Cursor, Windsurf & Claude Code 07:41 Using Claude Code with Other IDEs 12:41 Future of AI Coding Tools & Claude’s SDK 19:58 Integrating Codex with Chat GPT 21:14 Best AI Code Review Tools (Devon, CodeRabbit 26:49 Building an App with Claude Code (Step-by-Step) 35:32 Future Plans

Riley Brown

115,665 görüntüleme • 1 yıl önce

GPT-Image-2 was just released... It's the best image model (By a wide margin) Heres how to use GPT-Image-2 in ChatGPT, OpenAI Playground and of Course - Codex. TIMESTAMPS 00:00 Intro 01:27 Initial Tests of GPT-Image-2 02:24 It can GENERATE working BARCODES? 03:40 11 Edits one Prompt 06:40 Creating Cartoons 07:40 Overlay Explanations 08:50 How to Get Started 10:51 IPhone Mockup Images (Amazing) 15:43 Using GPT-Image in OpenAI Playground 16:11 Generate images in 4k 17:44 The FIRST limitation... Its bad at counting 18:26 Using GPT-Image in Codex (Agentic Image Gen)
22:26

GPT-Image-2 was just released... It's the best image model (By a wide margin) Heres how to use GPT-Image-2 in ChatGPT, OpenAI Playground and of Course - Codex. TIMESTAMPS 00:00 Intro 01:27 Initial Tests of GPT-Image-2 02:24 It can GENERATE working BARCODES? 03:40 11 Edits one Prompt 06:40 Creating Cartoons 07:40 Overlay Explanations 08:50 How to Get Started 10:51 IPhone Mockup Images (Amazing) 15:43 Using GPT-Image in OpenAI Playground 16:11 Generate images in 4k 17:44 The FIRST limitation... Its bad at counting 18:26 Using GPT-Image in Codex (Agentic Image Gen)

Riley Brown

35,856 görüntüleme • 4 ay önce

Here's how I use BOTH Codex + Claude Code to vibe code games For my Final Fantasy Tactics game: → 1. GPT 5.4/5.3-Codex/5.2 → 2. Opus 4.6 → 3. Nano Banana 2 → 4. Playwright → Plans + AskUserQuestion → Queue + interrupt prompts → Auto test + bug fixing FULL workflow👇 00:00 Intro 02:07 Step 1: Game Overview 03:27 Step 2: Nano Banana 2 for Portraits 05:12 Step 3: GPT 5.2 / 5.4 for Planning 09:56 Step 4: AskUserQuestion in Codex 12:02 Step 5: Saving your plans and prompts 13:43 Step 6: GPT 5.3-Codex for Implementing 16:34 Step 7: Implementing Cutscenes 20:49 Step 8: LazyGit + Yazi - Staying in the terminal 22:46 Step 9: Reviewing the changes 23:49 Step 10: Steering Codex - Queued Prompts 25:36 Steo 11: Steering Codex - Interrupt Prompts 26:45 Steo 12: Claude Code and Opus 4.6 27:16 Step 13: xHigh Reasoning for Tricky Bugs 28:50 Step 14: Playwright for automated testing + fixes 30:56 Step 15: Claude Code Plan Mode Previews 32:56 Step 16: Steering Claude Code - Add Notes to Plans 35:05 Wrap-Up
35:19

Here's how I use BOTH Codex + Claude Code to vibe code games For my Final Fantasy Tactics game: → 1. GPT 5.4/5.3-Codex/5.2 → 2. Opus 4.6 → 3. Nano Banana 2 → 4. Playwright → Plans + AskUserQuestion → Queue + interrupt prompts → Auto test + bug fixing FULL workflow👇 00:00 Intro 02:07 Step 1: Game Overview 03:27 Step 2: Nano Banana 2 for Portraits 05:12 Step 3: GPT 5.2 / 5.4 for Planning 09:56 Step 4: AskUserQuestion in Codex 12:02 Step 5: Saving your plans and prompts 13:43 Step 6: GPT 5.3-Codex for Implementing 16:34 Step 7: Implementing Cutscenes 20:49 Step 8: LazyGit + Yazi - Staying in the terminal 22:46 Step 9: Reviewing the changes 23:49 Step 10: Steering Codex - Queued Prompts 25:36 Steo 11: Steering Codex - Interrupt Prompts 26:45 Steo 12: Claude Code and Opus 4.6 27:16 Step 13: xHigh Reasoning for Tricky Bugs 28:50 Step 14: Playwright for automated testing + fixes 30:56 Step 15: Claude Code Plan Mode Previews 32:56 Step 16: Steering Claude Code - Add Notes to Plans 35:05 Wrap-Up

Chong-U

47,264 görüntüleme • 6 ay önce

"I ran a startup for 5 years. I thought we moved fast. Then I joined OpenAI—and realized I had no idea what fast actually meant." Head of Product for OpenAI's Codex Alexander Embiricos and I chat about: 🔸 How OpenAI built the Sora Android app (which hit #1) in just 18 days by using Codex 🔸 Codex growing 20x since August 🔸 How they're thinking about the dev bottleneck shifting from coding to reviewing AI-generated work 🔸 Why coding will be a core competency for every AI agent—because writing code is how agents use computers best 🔸 Why the bottleneck to AGI-level productivity isn’t model capability—it’s human typing speed 🔸 The vision of Codex, and how they plan to win Listen now 👇 • YouTube: • Spotify: • Apple: Thank you to our wonderful sponsors for supporting the podcast: 🏆 WorkOS — Modern identity platform for B2B SaaS, free up to 1 million MAUs: 🏆 Fin — The #1 AI agent for customer service: 🏆 Atlassian Jira Product Discovery — Confidence to build the right thing:
1:38

"I ran a startup for 5 years. I thought we moved fast. Then I joined OpenAI—and realized I had no idea what fast actually meant." Head of Product for OpenAI's Codex Alexander Embiricos and I chat about: 🔸 How OpenAI built the Sora Android app (which hit #1) in just 18 days by using Codex 🔸 Codex growing 20x since August 🔸 How they're thinking about the dev bottleneck shifting from coding to reviewing AI-generated work 🔸 Why coding will be a core competency for every AI agent—because writing code is how agents use computers best 🔸 Why the bottleneck to AGI-level productivity isn’t model capability—it’s human typing speed 🔸 The vision of Codex, and how they plan to win Listen now 👇 • YouTube: • Spotify: • Apple: Thank you to our wonderful sponsors for supporting the podcast: 🏆 WorkOS — Modern identity platform for B2B SaaS, free up to 1 million MAUs: 🏆 Fin — The #1 AI agent for customer service: 🏆 Atlassian Jira Product Discovery — Confidence to build the right thing:

Lenny Rachitsky

334,586 görüntüleme • 9 ay önce

2026 is the year of Agents OpenClaw, Claude Code, Codex and Cursor... In this video, I broke it all down with Micky. Consider this a 2026, year in review for AI agents. 00:00 Intro 01:35 Q1 Belonged to Anthropic 03:02 Opus 4.5 Inflection 08:42 Codex vs Claude UX War 12:53 Cursor was first? 14:27 SpaceX Acquisition Deal with Cursor 21:45 OpenClaw and the Agentic Personal Computer 28:57 Reactive vs Proactive Work 30:30 Keep Agents Narrow 33:12 Memory Layer Matters 36:23 Computer Use will get FAST 39:28 Who Wins the Super App? (Codex so far) 41:06 The Problem With Google... 45:17 Prompting and Skills creation 51:30 Codex Skill Example 56:56 Integrations Beat Prompts 59:39 All the Muxes (CMUX, TMUX) 01:02:04 Bold Predictions 01:06:38 Agent Commerce
1:23:01

2026 is the year of Agents OpenClaw, Claude Code, Codex and Cursor... In this video, I broke it all down with Micky. Consider this a 2026, year in review for AI agents. 00:00 Intro 01:35 Q1 Belonged to Anthropic 03:02 Opus 4.5 Inflection 08:42 Codex vs Claude UX War 12:53 Cursor was first? 14:27 SpaceX Acquisition Deal with Cursor 21:45 OpenClaw and the Agentic Personal Computer 28:57 Reactive vs Proactive Work 30:30 Keep Agents Narrow 33:12 Memory Layer Matters 36:23 Computer Use will get FAST 39:28 Who Wins the Super App? (Codex so far) 41:06 The Problem With Google... 45:17 Prompting and Skills creation 51:30 Codex Skill Example 56:56 Integrations Beat Prompts 59:39 All the Muxes (CMUX, TMUX) 01:02:04 Bold Predictions 01:06:38 Agent Commerce

Riley Brown

20,154 görüntüleme • 4 ay önce

Three skills I use every day in Claude Code and Codex to solve my hardest problems: 1️⃣ /agent-watchdog When I have one agent like Codex working on a task and I don't fully trust it's going to do everything right, I'll open up another one like Claude Code and tell it to watchdog the Codex thread. You can copy the Codex deep link into Claude Code and it'll look at the prompt you sent, watch the Codex thread until it's done, then compare the Codex solution to how it was planning to solve it and automatically fix anything that Codex missed. It can also test the work of the other agent end-to-end. Similar to the idea of OpenRouter's new Fusion feature, I've definitely found that two models thinking through a problem and checking each other's work can be wildly more impactful than just one. 2️⃣ /plan-arbiter Similar ideas as /agent-watchdog - but with this one you have both make plans, compare plans, negotiate the differences, and make a final plan to execute. I find Claude Code is better at writing plans, but Codex is faster and cheaper to execute on them. Then I usually have Claude Code watchdog the Codex work and fix anything that was missed. 3️⃣ /read-the-damn-docs One thing that drives me crazy with coding agents is they're so reluctant to look up docs. They'll just guess and guess and guess at the right API surface for things, or the right solution to an integration of two things. Once I explicitly tell it to look up the docs, it says "Oh, I see the answer," and it fixes the problem. So I made the /read-the-damn-docs skill. Add it and your agents will know when and how to do efficient web searches to look up docs for the types of problems you really should look up docs for. All of these are totally open source over on my GitHub. If you try them, let me know your feedback. Will link to them below:
1:21

Three skills I use every day in Claude Code and Codex to solve my hardest problems: 1️⃣ /agent-watchdog When I have one agent like Codex working on a task and I don't fully trust it's going to do everything right, I'll open up another one like Claude Code and tell it to watchdog the Codex thread. You can copy the Codex deep link into Claude Code and it'll look at the prompt you sent, watch the Codex thread until it's done, then compare the Codex solution to how it was planning to solve it and automatically fix anything that Codex missed. It can also test the work of the other agent end-to-end. Similar to the idea of OpenRouter's new Fusion feature, I've definitely found that two models thinking through a problem and checking each other's work can be wildly more impactful than just one. 2️⃣ /plan-arbiter Similar ideas as /agent-watchdog - but with this one you have both make plans, compare plans, negotiate the differences, and make a final plan to execute. I find Claude Code is better at writing plans, but Codex is faster and cheaper to execute on them. Then I usually have Claude Code watchdog the Codex work and fix anything that was missed. 3️⃣ /read-the-damn-docs One thing that drives me crazy with coding agents is they're so reluctant to look up docs. They'll just guess and guess and guess at the right API surface for things, or the right solution to an integration of two things. Once I explicitly tell it to look up the docs, it says "Oh, I see the answer," and it fixes the problem. So I made the /read-the-damn-docs skill. Add it and your agents will know when and how to do efficient web searches to look up docs for the types of problems you really should look up docs for. All of these are totally open source over on my GitHub. If you try them, let me know your feedback. Will link to them below:

Steve (Builder.io)

43,089 görüntüleme • 2 ay önce

Vibe Coding with Codex - Complete Guide Build a Web App, Desktop App & iOS App with Codex + GPT‑5.5 (No Coding Needed, Beginner Friendly) In this video you will learn: > Vibe Coding Basics + Vocab > How to build a web app using Codex > Add db, auth + storage with Firebase > Github Basics > Add AI Features (API's) > Deploy to internet (Vercel) > Convert Web App into Desktop app & iOS App Chapters 00:00 Intro 01:12 Setting up Codex 01:57 The basics of Vibe Coding and Codex 02:20 Projects, Files, App 03:45 Example App - Microsoft Paint 04:25 Running app locally 06:39 Save My Code - Use Github 10:37 Quick Review before building app 12:24 Building a web app - The Prompt 15:32 Creating Web App Project 16:34 Explaining Firebase (Database, Storage, Auth) 18:42 Setting up Firebase Project 22:54 Prompting Codex to build our app 24:49 Inspect Element - Console 26:24 Verify Data being Stored in Database 27:51 Making Changes to App 31:29 Fixing Storage Permissions with Codex 32:20 GPT API - Adding AI to our app 36:20 Making more changes using screenshots 39:02 Queuing vs Steering 40:23 Deploying our app to Vercel (App on Internet) 43:09 Convert web app to desktop app and iOS app 47:15 Web App and Desktop App work Now 48:36 Now let's run the iOS app 50:27 All three apps work! 51:11 Making Changes to iOS app 52:51 Testing agent skill feature of our app 53:55 Summary of what we did
55:24

Vibe Coding with Codex - Complete Guide Build a Web App, Desktop App & iOS App with Codex + GPT‑5.5 (No Coding Needed, Beginner Friendly) In this video you will learn: > Vibe Coding Basics + Vocab > How to build a web app using Codex > Add db, auth + storage with Firebase > Github Basics > Add AI Features (API's) > Deploy to internet (Vercel) > Convert Web App into Desktop app & iOS App Chapters 00:00 Intro 01:12 Setting up Codex 01:57 The basics of Vibe Coding and Codex 02:20 Projects, Files, App 03:45 Example App - Microsoft Paint 04:25 Running app locally 06:39 Save My Code - Use Github 10:37 Quick Review before building app 12:24 Building a web app - The Prompt 15:32 Creating Web App Project 16:34 Explaining Firebase (Database, Storage, Auth) 18:42 Setting up Firebase Project 22:54 Prompting Codex to build our app 24:49 Inspect Element - Console 26:24 Verify Data being Stored in Database 27:51 Making Changes to App 31:29 Fixing Storage Permissions with Codex 32:20 GPT API - Adding AI to our app 36:20 Making more changes using screenshots 39:02 Queuing vs Steering 40:23 Deploying our app to Vercel (App on Internet) 43:09 Convert web app to desktop app and iOS app 47:15 Web App and Desktop App work Now 48:36 Now let's run the iOS app 50:27 All three apps work! 51:11 Making Changes to iOS app 52:51 Testing agent skill feature of our app 53:55 Summary of what we did

Riley Brown

147,542 görüntüleme • 4 ay önce

I just built an entire app in 7 minutes using Codex Spark. EveryMCP: a universal MCP server installer that configures 15+ coding agents from a single CLI command. 12 Codex Spark subagents. All running in parallel. At the same time. The project itself isn't complicated, but just imagine what this looks like when you scale the complexity. My setup: • Codex 5.3 High to plan • Codex 5.3 Medium to orchestrate • 12 Codex Spark agents (xhigh) to implement in one shot Spark isn't competing with the big models. It's a different tool entirely. You orchestrate it. You run it in swarms. And it moves at a speed that wasn't possible before, even for the top 1% of AI coders. More complex workflows coming soon. Comment below if you want me to tell you how I did it.
4:29

I just built an entire app in 7 minutes using Codex Spark. EveryMCP: a universal MCP server installer that configures 15+ coding agents from a single CLI command. 12 Codex Spark subagents. All running in parallel. At the same time. The project itself isn't complicated, but just imagine what this looks like when you scale the complexity. My setup: • Codex 5.3 High to plan • Codex 5.3 Medium to orchestrate • 12 Codex Spark agents (xhigh) to implement in one shot Spark isn't competing with the big models. It's a different tool entirely. You orchestrate it. You run it in swarms. And it moves at a speed that wasn't possible before, even for the top 1% of AI coders. More complex workflows coming soon. Comment below if you want me to tell you how I did it.

am.will

16,916 görüntüleme • 6 ay önce

EVERYTHING YOU NEED TO KNOW ABOUT CHATGPT'S "LOVABLE KILLER" CODEX SITES (in 25 mins): TLDR; the coolest part is that apps you build can update themselves autonomously 1. Codex Sites is not Replit or Lovable or Bolt. Those are great for one-prompting a full app. Codex Sites is for building apps that the agent keeps improving without you touching them. 2. Your personal website can update its own stats. Your internal dashboard can refresh its own data. Your product can add features while you sleep. The app is alive. 3. Start by invoking at-sites. Use realistic sample data. Always say "save for review, do not deploy." This unlocks building a real product, not a homepage. 4. Add persistent storage so the app remembers everything between visits. Without this it resets every time. Ask Codex to show you the data model before it builds. 5. Create safe actions. These are the specific things the agent is allowed to do to your app: add data, update cards, move things, score things. You define the boundaries. The agent operates within them. 6. Build skills so any future Codex chat knows how to interact with your app. The skill is basically a manual for the agent. Without it, every new chat starts from zero. 7. Save gate like a video game. Codex doesn't auto-save. Create checkpoints before you deploy so you can roll back if something breaks. 8. Close the autonomous loop. This is the magic. Once memory, safe actions, and skills are set up, the agent can update your app from any chat, any context, without you switching tabs. 9. Use the plugins most people are sleeping on. Figma, Canva, HeyGen for avatar videos, Game Studio for interactive experiences, FAL for image generation, Hugging Face for open source models. Worth adding a few. 10. The big picture: we went from building apps to raising apps. You set up the structure, the guardrails, and the skills. The agent does the rest. That's autonomous product building and it's here right now. Tbh, Codex sites isn't perfect. Still a lot to be desired like domains, db, authentication etc. But it's a glimpse into this idea that apps can be updated/improved upon automonously. And Codex Sites is REALLY good if you live in Codex everyday. Which more and more of are. And that's really cool. Will be interesting to see how Lovable, Bolt, Replit etc react to this. full tutorial on The Startup Ideas Podcast (SIP) 🧃 where you get your pods watch share with a friend i'm rooting for you What do you think of Codex and Codex sites?
24:41

EVERYTHING YOU NEED TO KNOW ABOUT CHATGPT'S "LOVABLE KILLER" CODEX SITES (in 25 mins): TLDR; the coolest part is that apps you build can update themselves autonomously 1. Codex Sites is not Replit or Lovable or Bolt. Those are great for one-prompting a full app. Codex Sites is for building apps that the agent keeps improving without you touching them. 2. Your personal website can update its own stats. Your internal dashboard can refresh its own data. Your product can add features while you sleep. The app is alive. 3. Start by invoking at-sites. Use realistic sample data. Always say "save for review, do not deploy." This unlocks building a real product, not a homepage. 4. Add persistent storage so the app remembers everything between visits. Without this it resets every time. Ask Codex to show you the data model before it builds. 5. Create safe actions. These are the specific things the agent is allowed to do to your app: add data, update cards, move things, score things. You define the boundaries. The agent operates within them. 6. Build skills so any future Codex chat knows how to interact with your app. The skill is basically a manual for the agent. Without it, every new chat starts from zero. 7. Save gate like a video game. Codex doesn't auto-save. Create checkpoints before you deploy so you can roll back if something breaks. 8. Close the autonomous loop. This is the magic. Once memory, safe actions, and skills are set up, the agent can update your app from any chat, any context, without you switching tabs. 9. Use the plugins most people are sleeping on. Figma, Canva, HeyGen for avatar videos, Game Studio for interactive experiences, FAL for image generation, Hugging Face for open source models. Worth adding a few. 10. The big picture: we went from building apps to raising apps. You set up the structure, the guardrails, and the skills. The agent does the rest. That's autonomous product building and it's here right now. Tbh, Codex sites isn't perfect. Still a lot to be desired like domains, db, authentication etc. But it's a glimpse into this idea that apps can be updated/improved upon automonously. And Codex Sites is REALLY good if you live in Codex everyday. Which more and more of are. And that's really cool. Will be interesting to see how Lovable, Bolt, Replit etc react to this. full tutorial on The Startup Ideas Podcast (SIP) 🧃 where you get your pods watch share with a friend i'm rooting for you What do you think of Codex and Codex sites?

GREG ISENBERG

69,219 görüntüleme • 3 ay önce

The Codex Super-App (Full Beginners Guide) The All Purpose Interface for AI Agents Part 1: Codex Basics Install Codex, Projects, Chats, Documents, Plugins, Custom Skills, Automations Part 2: Multitasking with Codex - iOS App Designs - Build an iOS App - Landing Page - Launch Video - Investor Deck - Social Media Automation TIMESTAMPS: Part 1: Codex Basics 00:00 Intro 02:54 Downloading Codex 03:20 Overview of Codex interface 03:56 Chats, Prompting, & Built in Search 04:53 Creating Projects 07:37 Creating Spreadsheet 09:43 How Files are stored and mentioned within projects 10:42 Quick Codex Overview 12:47 Search (CMD G) and Folder Organization 14:29 Skills and Plugins 16:29 Using Calendar Plugin 18:07 Creating Automations on Codex 19:18 Learn about Plugins (Figma) 21:37 Built in Image Gen 22:37 MCP Example (Paper for Design) 24:17 Opening Chats in mini-window 25:26 Steering vs Queueing the Agent 27:35 Creating Own Skill with API's 31:34 Using YouTube Researcher Skill (That we created) 33:24 Creating Automation with your custom skill Part 2: Multitasking (More chaotic and fun) 35:27 Part 2 Multitasking: Building iOS App, Web App, Investor Deck, Launch Video, Mobile Designs, and Automated X Posts 37:54 Creating Project 38:31 Planning my 6 Projects 40:25 Mobile Design Skill 41:47 Setting up iOS App 45:08 Implementing Desings into Mobile app 46:13 Creating a landing page that collects user info 46:45 Tally for form submission (Great for lead magnets) 49:43 Organizing and Renaming Chats for multitasking 52:12 Database for Mobile App (Supabase) 53:19 Generating app icons 54:08 Launch Video (Remotion) 59:32 Remotion Video Timeline and Seeing the Video Editor 01:05:37 Editing instructions for Remotion (Gridlines) 01:07:11 Editing Web App 01:09:46 Using CLAUDE CODE Inside Codex for Design (Terminal) 01:17:20 Forking a Chat to create investor deck 01:19:09 Using Claude 4.7 Opus for Designing Deck 01:20:22 Testing Canva Export (It's good) 01:22:33 Running Mobile App on Actual Phone (Not Simulator) 01:28:58 Finishing up All Projects (Mobile App, Landing Page Launch Video) 01:31:56 Exporting Deck and making changes in Canva 01:33:13 Deploy to Vercel using the Vercel Plugin 01:33:44 Adding Song to Remotion Video 01:35:26 Setting up x Post automations (Typefully) 01:37:57 Our App is on Testflight! 01:39:58 Final Remotion Video 01:41:04 Final Thoughts, Reflections, Summary
1:43:13

The Codex Super-App (Full Beginners Guide) The All Purpose Interface for AI Agents Part 1: Codex Basics Install Codex, Projects, Chats, Documents, Plugins, Custom Skills, Automations Part 2: Multitasking with Codex - iOS App Designs - Build an iOS App - Landing Page - Launch Video - Investor Deck - Social Media Automation TIMESTAMPS: Part 1: Codex Basics 00:00 Intro 02:54 Downloading Codex 03:20 Overview of Codex interface 03:56 Chats, Prompting, & Built in Search 04:53 Creating Projects 07:37 Creating Spreadsheet 09:43 How Files are stored and mentioned within projects 10:42 Quick Codex Overview 12:47 Search (CMD G) and Folder Organization 14:29 Skills and Plugins 16:29 Using Calendar Plugin 18:07 Creating Automations on Codex 19:18 Learn about Plugins (Figma) 21:37 Built in Image Gen 22:37 MCP Example (Paper for Design) 24:17 Opening Chats in mini-window 25:26 Steering vs Queueing the Agent 27:35 Creating Own Skill with API's 31:34 Using YouTube Researcher Skill (That we created) 33:24 Creating Automation with your custom skill Part 2: Multitasking (More chaotic and fun) 35:27 Part 2 Multitasking: Building iOS App, Web App, Investor Deck, Launch Video, Mobile Designs, and Automated X Posts 37:54 Creating Project 38:31 Planning my 6 Projects 40:25 Mobile Design Skill 41:47 Setting up iOS App 45:08 Implementing Desings into Mobile app 46:13 Creating a landing page that collects user info 46:45 Tally for form submission (Great for lead magnets) 49:43 Organizing and Renaming Chats for multitasking 52:12 Database for Mobile App (Supabase) 53:19 Generating app icons 54:08 Launch Video (Remotion) 59:32 Remotion Video Timeline and Seeing the Video Editor 01:05:37 Editing instructions for Remotion (Gridlines) 01:07:11 Editing Web App 01:09:46 Using CLAUDE CODE Inside Codex for Design (Terminal) 01:17:20 Forking a Chat to create investor deck 01:19:09 Using Claude 4.7 Opus for Designing Deck 01:20:22 Testing Canva Export (It's good) 01:22:33 Running Mobile App on Actual Phone (Not Simulator) 01:28:58 Finishing up All Projects (Mobile App, Landing Page Launch Video) 01:31:56 Exporting Deck and making changes in Canva 01:33:13 Deploy to Vercel using the Vercel Plugin 01:33:44 Adding Song to Remotion Video 01:35:26 Setting up x Post automations (Typefully) 01:37:57 Our App is on Testflight! 01:39:58 Final Remotion Video 01:41:04 Final Thoughts, Reflections, Summary

Riley Brown

435,948 görüntüleme • 4 ay önce

"We write very few specs on the Codex team. We're talking 10 bullet points and that's it." Here's my new episode with Alexander Embiricos and Romain Huet where they gave me an inside look at how OpenAI's Codex team operates: → Live demo: Building in seconds with Spark → How the team built the beautiful Codex app → How they ship without traditional specs and roadmaps Some quotes from Alex and Romain: "The fewer people you need in a room to do anything, the more pure every decision is." "Our designers write more code now than was written by an engineer six months ago." "I'm much less likely to read someone's resume than their ideas and what they've built." Thanks to our sponsors: Granola: The best AI meeting notes app I've ever used Linear: The AI agent platform for modern teams 📌 Watch now:
0:41

"We write very few specs on the Codex team. We're talking 10 bullet points and that's it." Here's my new episode with Alexander Embiricos and Romain Huet where they gave me an inside look at how OpenAI's Codex team operates: → Live demo: Building in seconds with Spark → How the team built the beautiful Codex app → How they ship without traditional specs and roadmaps Some quotes from Alex and Romain: "The fewer people you need in a room to do anything, the more pure every decision is." "Our designers write more code now than was written by an engineer six months ago." "I'm much less likely to read someone's resume than their ideas and what they've built." Thanks to our sponsors: Granola: The best AI meeting notes app I've ever used Linear: The AI agent platform for modern teams 📌 Watch now:

Peter Yang

290,682 görüntüleme • 5 ay önce