正在加载视频...

视频加载失败

返回首页

last night we hosted the first OpenAI Codex community meetup in Canada at Shopify Toronto. over 800+ signed up. couple of my fav demos: - Tarun Sachdeva showed us how he uses Codex to build Traces . com, a platform where you can share agent traces - @zedkay22 showed...

robjama's profile picture

Robleh

24,031 subscribers

11,567 次观看 • 5 个月前 •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 条评论

暂无评论

原始帖子的评论将显示在这里

相关视频

OpenAI released Codex Mobile App Directly on ChatGPT Here's everything you need to know: 1. How to set it up 2. How to fully vibecode from Codex Mobile 3. How to control your computer with Codex Mobile 00:00 Setting Up Codex Mobile on ChatGPT 02:15 Changing Settings - Chats First 03:01 Voice Mode 04:05 Plugins and Skills 05:07 Notifications and Permissions 06:52 Flaws of Vibe Coding Out of the Box 07:13 Vibe Coding Skill (Yolo Mode w Vercel) 10:28 Using ChatGPT app as Full Vibe Coding Platform 12:15 Using ChatGPT to Control my computer 13:33 Where I put all my Agent Skills @chorusskills
14:21

OpenAI released Codex Mobile App Directly on ChatGPT Here's everything you need to know: 1. How to set it up 2. How to fully vibecode from Codex Mobile 3. How to control your computer with Codex Mobile 00:00 Setting Up Codex Mobile on ChatGPT 02:15 Changing Settings - Chats First 03:01 Voice Mode 04:05 Plugins and Skills 05:07 Notifications and Permissions 06:52 Flaws of Vibe Coding Out of the Box 07:13 Vibe Coding Skill (Yolo Mode w Vercel) 10:28 Using ChatGPT app as Full Vibe Coding Platform 12:15 Using ChatGPT to Control my computer 13:33 Where I put all my Agent Skills @chorusskills

Riley Brown

92,106 次观看 • 2 个月前

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

199,205 次观看 • 3 个月前

🚨 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 次观看 • 1 年前

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,102 次观看 • 6 个月前

"You cannot walk from point A to B inside OpenAI without hearing Codex get mentioned." Here's my new episode with Rohan Varma (Codex PM) on how he uses Codex as his everything app to: → Prototype designs with Image Gen → Turn repeated work into automations → Turn project context into live Codex Sites → Use one Codex thread to manage others Some quotes from Rohan: "[Ask Codex] for something that seems 10x more ridiculous than you ever think it could do. And it probably can do 90% of it." "Over the course of the day, I'm probably doing 3-4x more than I would have without Codex." "For me, every time I do anything I basically think, could Codex have done this?" 📌 Watch now: Thanks to our sponsors: Wispr Flow: 4x faster than typing with your voice Riverside: All-in-one AI studio for podcasts and video
0:29

"You cannot walk from point A to B inside OpenAI without hearing Codex get mentioned." Here's my new episode with Rohan Varma (Codex PM) on how he uses Codex as his everything app to: → Prototype designs with Image Gen → Turn repeated work into automations → Turn project context into live Codex Sites → Use one Codex thread to manage others Some quotes from Rohan: "[Ask Codex] for something that seems 10x more ridiculous than you ever think it could do. And it probably can do 90% of it." "Over the course of the day, I'm probably doing 3-4x more than I would have without Codex." "For me, every time I do anything I basically think, could Codex have done this?" 📌 Watch now: Thanks to our sponsors: Wispr Flow: 4x faster than typing with your voice Riverside: All-in-one AI studio for podcasts and video

Peter Yang

141,221 次观看 • 24 天前

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,221 次观看 • 2 个月前

We're taking over one of the most iconic theatres in Toronto for the first BuildFuture x OpenAI Developers event. Live From the Future: a night of frontier demos on May 25th @ Scotiabank theatre for Toronto Tech Week we're putting out the casting call for Toronto's top builders and startups shipping with codex, even better if it's something people genuinely haven't seen before. apply to attend or demo ↓ shoutout to Shopify for helping us lock in the venue and @falcon_ide our design partners!.
1:00

We're taking over one of the most iconic theatres in Toronto for the first BuildFuture x OpenAI Developers event. Live From the Future: a night of frontier demos on May 25th @ Scotiabank theatre for Toronto Tech Week we're putting out the casting call for Toronto's top builders and startups shipping with codex, even better if it's something people genuinely haven't seen before. apply to attend or demo ↓ shoutout to Shopify for helping us lock in the venue and @falcon_ide our design partners!.

Robleh

12,169 次观看 • 2 个月前

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 次观看 • 3 个月前

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 次观看 • 4 个月前

"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,422 次观看 • 7 个月前

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 次观看 • 5 个月前

Met a guy making $1.6 million a year. Three days ago he was at a Meta conference. Told me he saw the best AI talk of his life. Boris Cherny was on stage. Showed how the Anthropic team actually uses Claude day to day. Boris deleted his IDE eight months ago. Now he codes from his phone. I watched it last night. Had to pause it twice. Not because it was hard. Because I realized I've been using Claude like a toy. He sent me the recording. It was never published. Posting it below.
39:15

Met a guy making $1.6 million a year. Three days ago he was at a Meta conference. Told me he saw the best AI talk of his life. Boris Cherny was on stage. Showed how the Anthropic team actually uses Claude day to day. Boris deleted his IDE eight months ago. Now he codes from his phone. I watched it last night. Had to pause it twice. Not because it was hard. Because I realized I've been using Claude like a toy. He sent me the recording. It was never published. Posting it below.

Raytar

1,213,765 次观看 • 1 个月前

here is the first look at realtime voice mode in codex the ui is already in the app, but the codex backend endpoint does not seem to be live yet i got it running by forcing the local feature gate and using my own openai api key, so it goes through the public realtime api instead it's incredible, but this demo alone cost me ~$4 gpt realtime 2 is very expensive, which makes me wonder how they're going to handle it - part of the normal usage limit, or a separate limit like we had with gpt 5.3 codex spark? i'm turning it off until the official rollout but get excited, the next few weeks are going to be amazing
1:01

here is the first look at realtime voice mode in codex the ui is already in the app, but the codex backend endpoint does not seem to be live yet i got it running by forcing the local feature gate and using my own openai api key, so it goes through the public realtime api instead it's incredible, but this demo alone cost me ~$4 gpt realtime 2 is very expensive, which makes me wonder how they're going to handle it - part of the normal usage limit, or a separate limit like we had with gpt 5.3 codex spark? i'm turning it off until the official rollout but get excited, the next few weeks are going to be amazing

🥔🥔🥔

39,508 次观看 • 1 个月前

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

68,477 次观看 • 1 个月前

Excited to share this conversation with Peter Steinberger 🦞! We recorded it in SF a couple weeks ago, before he joined OpenAI. Peter is one of the most creative builders I know. We talked about OpenClaw🦞 🦞, where his ideas come from and how you can just… build things! Full interview 👇
0:38

Excited to share this conversation with Peter Steinberger 🦞! We recorded it in SF a couple weeks ago, before he joined OpenAI. Peter is one of the most creative builders I know. We talked about OpenClaw🦞 🦞, where his ideas come from and how you can just… build things! Full interview 👇

Romain Huet

156,110 次观看 • 5 个月前

.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,406 次观看 • 27 天前

"We used to say build the MVP. Now you should build the system that builds the MVP first." Here's my new episode with Ryan Carson where he shared how he runs his startup solo with AI agents: ✅ OpenClaw as his AI chief of staff to triage emails, book meetings, and do sales outreach ✅ Codex and Devin as his AI eng team to ship features while he sleeps Some quotes from Ryan: "Spend a lot of time upfront setting up your skills + documentation. Then you've suddenly unlocked the work of 10 people." "Treat your agent like a real employee. Give it a real email address, calendar access, and GitHub account." "Pay a designer to set up your design system and brand. After that, you can use AI to generate on-brand assets." 📌 Watch now: Thanks to our sponsors: Wispr Flow: Don't type, just speak Linear: The AI agent platform for modern teams
0:39

"We used to say build the MVP. Now you should build the system that builds the MVP first." Here's my new episode with Ryan Carson where he shared how he runs his startup solo with AI agents: ✅ OpenClaw as his AI chief of staff to triage emails, book meetings, and do sales outreach ✅ Codex and Devin as his AI eng team to ship features while he sleeps Some quotes from Ryan: "Spend a lot of time upfront setting up your skills + documentation. Then you've suddenly unlocked the work of 10 people." "Treat your agent like a real employee. Give it a real email address, calendar access, and GitHub account." "Pay a designer to set up your design system and brand. After that, you can use AI to generate on-brand assets." 📌 Watch now: Thanks to our sponsors: Wispr Flow: Don't type, just speak Linear: The AI agent platform for modern teams

Peter Yang

74,393 次观看 • 2 个月前

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)

42,501 次观看 • 1 个月前

We couldn't live with Alex Scott at The Emirates in April. The way he protected the ball, carried through tight spaces, the punchy passing and the goal that killed us, showed how rounded he's become. He'd add a lot of technicality to #Arsenal's build up.
3:33

We couldn't live with Alex Scott at The Emirates in April. The way he protected the ball, carried through tight spaces, the punchy passing and the goal that killed us, showed how rounded he's become. He'd add a lot of technicality to #Arsenal's build up.

Adam Keys

74,374 次观看 • 1 个月前

"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,423 次观看 • 3 个月前