正在加载视频...

视频加载失败

加载此视频时出现问题。这可能是由于临时网络问题，或视频可能不可用。

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:54show more

Dan Shipper 📧

121,128 subscribers

55,561 次观看 • 3 个月前 •via X (Twitter)

教育科学技术

Anya Rossi• Live Now

Private livecam show

0 条评论

暂无评论

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

相关视频

.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

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

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

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

🚨 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 年前

People keep saying GPT-5.5 + Codex mogs Claude Code. So I got OpenAI PM Abhi Muchhal to show me exactly how to use Codex like a pro: 03:48 - What Codex unlocks for PM work 05:34 - How he built his growth dashboard 11:32 - How to build in Codex with Playwright 14:52 - Moving away from PRDs to Codex prototypes 21:23 - 3 automations running before his day starts 28:37 - WhatsApp computer use demo setup 33:05 - Codex takes action inside WhatsApp 37:00 - Building a 1040 tax filing app in Codex 43:42 - What drove ChatGPT to 1B WAU 47:18 - ImageGen 2, the biggest ELO jump of any model 59:26 - How to break into OpenAI as a PM

People keep saying GPT-5.5 + Codex mogs Claude Code. So I got OpenAI PM Abhi Muchhal to show me exactly how to use Codex like a pro: 03:48 - What Codex unlocks for PM work 05:34 - How he built his growth dashboard 11:32 - How to build in Codex with Playwright 14:52 - Moving away from PRDs to Codex prototypes 21:23 - 3 automations running before his day starts 28:37 - WhatsApp computer use demo setup 33:05 - Codex takes action inside WhatsApp 37:00 - Building a 1040 tax filing app in Codex 43:42 - What drove ChatGPT to 1B WAU 47:18 - ImageGen 2, the biggest ELO jump of any model 59:26 - How to break into OpenAI as a PM

Aakash Gupta

106,261 次观看 • 2 个月前

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:

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

I vibe coded a new product on the side while running Every 🧱—and today we're launching it for free. It's called Proof, and it’s a live collaborative document editor where humans and AI agents work together in the same doc. It’s built from the ground up for the kinds of documents agents are increasingly writing: bug reports, PRDs, implementation plans, research briefs, copy audits, strategy docs, memos, and proposals. It's fast, free, and open source—available now at Why Proof? When everyone on your team is working with agents, there's suddenly a ton of AI-generated text flying around—planning docs, strategy memos, session recaps. But the current process for collaborating and iterating on agent-generated writing is…weirdly primitive. It mostly takes place in Markdown files on your laptop, which makes it reminiscent of document editing in 1999. That’s why we built Proof. What makes Proof different? - Proof is agent-native. Anything you can do in Proof, your agent can do just as easily. - Proof tracks provenance: A colored rail on the left side of every document tracks who wrote what. Green means human, Purple means AI. - Proof is login-free and open source: This is because we want Proof to be your agent's favorite document editor. How we use Proof Every 🧱: - Brandon Gell had OpenAI's Codex write a feature plan in Proof, then tagged my personal Claw (R2-C2) in Slack to review it. R2-C2 left feedback, I added comments, Brandon's agent revised the plan, and then Codex executed on it. Brandon submitted a PR to production without writing a line of code. - Austin Tedesco texts his Claw ideas while he's out on a run, then has it maintain a running Proof doc for his weekly food newsletter. He dictates drafts using Naveen Naidu's Monologue, writes into the outline himself, and uses the provenance gutter to track what's his voice vs. the agent's. - Kieran Klaassen uses it as a lightweight scratchpad for his compound engineering workflow. He brainstorms with an agent in the terminal, shares to Proof with one click, then opens the doc to leave comments and tells the agent to go work on them. His take: Proof's job is to communicate about writing and ideas. Proof is free, open source, and requires no login. I built the whole thing by vibe coding between meetings. I sat down with Brandon, Kieran, and Austin on Every 🧱's AI & I to demo it live and talk about how it's changing the way we work. If you're building with agents and need a better way to collaborate on text, this one's for you. Watch below! Timestamps Introduction and the origin story of Proof: 00:02:00 From Mac app to collaborative web editor: 00:07:24 What makes Proof "agent native": 00:09:00 Live demo—watching an agent join and write inside a shared document: 00:14:30 How Austin uses Proof for creative writing and food journalism: 00:20:51 The challenge of multiple agents editing one document simultaneously: 00:24:30 When AI-written docs are better read by agents than by humans: 00:26:48 Brandon's agent-to-agent collaboration loop: 00:29:30 Proof as a lightweight scratchpad versus existing tools like Notion and GitHub: 00:37:09 Why Proof is open source and what that means for builders: 00:42:18

I vibe coded a new product on the side while running Every 🧱—and today we're launching it for free. It's called Proof, and it’s a live collaborative document editor where humans and AI agents work together in the same doc. It’s built from the ground up for the kinds of documents agents are increasingly writing: bug reports, PRDs, implementation plans, research briefs, copy audits, strategy docs, memos, and proposals. It's fast, free, and open source—available now at Why Proof? When everyone on your team is working with agents, there's suddenly a ton of AI-generated text flying around—planning docs, strategy memos, session recaps. But the current process for collaborating and iterating on agent-generated writing is…weirdly primitive. It mostly takes place in Markdown files on your laptop, which makes it reminiscent of document editing in 1999. That’s why we built Proof. What makes Proof different? - Proof is agent-native. Anything you can do in Proof, your agent can do just as easily. - Proof tracks provenance: A colored rail on the left side of every document tracks who wrote what. Green means human, Purple means AI. - Proof is login-free and open source: This is because we want Proof to be your agent's favorite document editor. How we use Proof Every 🧱: - Brandon Gell had OpenAI's Codex write a feature plan in Proof, then tagged my personal Claw (R2-C2) in Slack to review it. R2-C2 left feedback, I added comments, Brandon's agent revised the plan, and then Codex executed on it. Brandon submitted a PR to production without writing a line of code. - Austin Tedesco texts his Claw ideas while he's out on a run, then has it maintain a running Proof doc for his weekly food newsletter. He dictates drafts using Naveen Naidu's Monologue, writes into the outline himself, and uses the provenance gutter to track what's his voice vs. the agent's. - Kieran Klaassen uses it as a lightweight scratchpad for his compound engineering workflow. He brainstorms with an agent in the terminal, shares to Proof with one click, then opens the doc to leave comments and tells the agent to go work on them. His take: Proof's job is to communicate about writing and ideas. Proof is free, open source, and requires no login. I built the whole thing by vibe coding between meetings. I sat down with Brandon, Kieran, and Austin on Every 🧱's AI & I to demo it live and talk about how it's changing the way we work. If you're building with agents and need a better way to collaborate on text, this one's for you. Watch below! Timestamps Introduction and the origin story of Proof: 00:02:00 From Mac app to collaborative web editor: 00:07:24 What makes Proof "agent native": 00:09:00 Live demo—watching an agent join and write inside a shared document: 00:14:30 How Austin uses Proof for creative writing and food journalism: 00:20:51 The challenge of multiple agents editing one document simultaneously: 00:24:30 When AI-written docs are better read by agents than by humans: 00:26:48 Brandon's agent-to-agent collaboration loop: 00:29:30 Proof as a lightweight scratchpad versus existing tools like Notion and GitHub: 00:37:09 Why Proof is open source and what that means for builders: 00:42:18

Dan Shipper 📧

33,065 次观看 • 5 个月前

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

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

"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

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

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!

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

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

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

146,819 次观看 • 3 个月前

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:

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

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

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

After creating Remodex: Codex remote control for iOS I decided to chill a bit by building a browser sidebar inside Theo - t3.gg 's T3 Code You can open it with Cmd+Shift+B This software is so easy to "manipulate" and build upon Congrats to all the guys that put the work in it because it is great I certainly will be building more things with it For this one I decided to switch from the Codex App to the Codex CLI too just to see how it works And boy it was so good

After creating Remodex: Codex remote control for iOS I decided to chill a bit by building a browser sidebar inside Theo - t3.gg 's T3 Code You can open it with Cmd+Shift+B This software is so easy to "manipulate" and build upon Congrats to all the guys that put the work in it because it is great I certainly will be building more things with it For this one I decided to switch from the Codex App to the Codex CLI too just to see how it works And boy it was so good

Emanuele Di Pietro

38,905 次观看 • 4 个月前

Laptop closed. Agent still working. 103 legal contracts reviewed in 40 minutes. Most AI agents stop the moment you close your laptop. This one does not. See how DigitalOcean, @chatgptapp Codex, and Box work together to autonomously process a stack of contracts while you step away. The new DigitalOcean Codex plugin makes droplet provisioning a one-click affair. - DigitalOcean: always-on compute for long-running agents - Codex: the harness driving the workflow - Box: the governed content layer (contracts in, review packets out) Timestamps: 00:09 – Workflow setup 01:23 – Provision DigitalOcean droplet for long-running tasks 02:45 – Connect Codex to Box with Box MCP 03:01 – Start a remote session on Codex 03:26 – Implement the legal workflow 05:00 – Review the work 06:05 – Conclusion

Laptop closed. Agent still working. 103 legal contracts reviewed in 40 minutes. Most AI agents stop the moment you close your laptop. This one does not. See how DigitalOcean, @chatgptapp Codex, and Box work together to autonomously process a stack of contracts while you step away. The new DigitalOcean Codex plugin makes droplet provisioning a one-click affair. - DigitalOcean: always-on compute for long-running agents - Codex: the harness driving the workflow - Box: the governed content layer (contracts in, review packets out) Timestamps: 00:09 – Workflow setup 01:23 – Provision DigitalOcean droplet for long-running tasks 02:45 – Connect Codex to Box with Box MCP 03:01 – Start a remote session on Codex 03:26 – Implement the legal workflow 05:00 – Review the work 06:05 – Conclusion

Box

321,406 次观看 • 1 个月前

"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:

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

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:

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

“The only job left is to understand what you don't like, put it into words, and tell the AI.” Here’s my new episode with jason (DevEx at OpenAI) where he showed me how he uses Codex throughout his workday, including how to: → Set up a chief of staff for Slack and email → Turn past sessions into new AI skills → Give long-running projects verifiable goals Some example Codex use cases from Jason: “I want you to read the past week of Slack messages I’ve written and make a skill to figure out how to talk like me.” “Turn this thread into a heartbeat. I want you to check my emails, my Slack, my Linear, and tell me what I need to prioritize.” “Codex can find a booking ticket and check into the flight for me and text me the boarding pass to my phone.” Jason wrote the official OpenAI handbook on how to get the most out of Codex, so don’t miss this episode. 📌 Watch now: Thanks to our sponsors: Riverside: All-in-one AI studio for podcasts and video Google AI Studio: Build apps with Nano Banana, and more

“The only job left is to understand what you don't like, put it into words, and tell the AI.” Here’s my new episode with jason (DevEx at OpenAI) where he showed me how he uses Codex throughout his workday, including how to: → Set up a chief of staff for Slack and email → Turn past sessions into new AI skills → Give long-running projects verifiable goals Some example Codex use cases from Jason: “I want you to read the past week of Slack messages I’ve written and make a skill to figure out how to talk like me.” “Turn this thread into a heartbeat. I want you to check my emails, my Slack, my Linear, and tell me what I need to prioritize.” “Codex can find a booking ticket and check into the flight for me and text me the boarding pass to my phone.” Jason wrote the official OpenAI handbook on how to get the most out of Codex, so don’t miss this episode. 📌 Watch now: Thanks to our sponsors: Riverside: All-in-one AI studio for podcasts and video Google AI Studio: Build apps with Nano Banana, and more

Peter Yang

217,302 次观看 • 24 天前

In the future, you’ll be able to accomplish a goal by just giving Claude an outcome and a budget. That’s the direction Anthropic is building in with its new Managed Agents features, announced at this week’s Code with Claude developer event. The basic idea: Claude, wrapped in a computer in the cloud, that you can spin up, scale, and manage as needed. Anthropic is taking on the infrastructure that kills most agent products, and making sure that it scales to meet the needs of agents running 24/7. On this week’s AI & I from Every 📧, I talk with Angela Jiang (Angela Jiang), head of product for the Claude platform, and Katelyn Lesse (Katelyn Lesse), head of engineering for the Claude platform, about what Anthropic is building and what it takes to make agents reliable in production. We get into: - Why the "build a generic harness, hot-swap any model behind it" playbook is already outdated. Angela points to eval data on Memory where the same task across different harnesses performed drastically differently. - The infrastructure wall every team hits in production—and why Katelyn thinks “my sandbox died and took the agent with it” is the real reason internal agents don't ship. - Why Anthropic is so bullish on using file systems and skills within Claude, including Angela's argument that those early design choices can compound for years. This is a must-watch for anyone trying to take an agent past the demo and into production. Watch below! Timestamps: How the Claude platform evolved from API to agents: 00:01:48 The primitives that make up Claude Managed Agents: 00:04:09 Why the harness and the model are becoming a single unit: 00:10:37 The infrastructure wall that kills most agent projects in production: 00:18:49 Why team agents need a different shape than individual productivity tools: 00:24:49 How Anthropic's legal team uses an agent to review marketing copy: 00:26:36 Using multi-agent orchestration for advisor strategies, adversarial pairs, and swarms: 00:34:24 How to measure agent success with outcome and budget as the end state: 00:35:50 What the platform looks like a year from now, when Claude writes its own harness: 00:39:11

In the future, you’ll be able to accomplish a goal by just giving Claude an outcome and a budget. That’s the direction Anthropic is building in with its new Managed Agents features, announced at this week’s Code with Claude developer event. The basic idea: Claude, wrapped in a computer in the cloud, that you can spin up, scale, and manage as needed. Anthropic is taking on the infrastructure that kills most agent products, and making sure that it scales to meet the needs of agents running 24/7. On this week’s AI & I from Every 📧, I talk with Angela Jiang (Angela Jiang), head of product for the Claude platform, and Katelyn Lesse (Katelyn Lesse), head of engineering for the Claude platform, about what Anthropic is building and what it takes to make agents reliable in production. We get into: - Why the "build a generic harness, hot-swap any model behind it" playbook is already outdated. Angela points to eval data on Memory where the same task across different harnesses performed drastically differently. - The infrastructure wall every team hits in production—and why Katelyn thinks “my sandbox died and took the agent with it” is the real reason internal agents don't ship. - Why Anthropic is so bullish on using file systems and skills within Claude, including Angela's argument that those early design choices can compound for years. This is a must-watch for anyone trying to take an agent past the demo and into production. Watch below! Timestamps: How the Claude platform evolved from API to agents: 00:01:48 The primitives that make up Claude Managed Agents: 00:04:09 Why the harness and the model are becoming a single unit: 00:10:37 The infrastructure wall that kills most agent projects in production: 00:18:49 Why team agents need a different shape than individual productivity tools: 00:24:49 How Anthropic's legal team uses an agent to review marketing copy: 00:26:36 Using multi-agent orchestration for advisor strategies, adversarial pairs, and swarms: 00:34:24 How to measure agent success with outcome and budget as the end state: 00:35:50 What the platform looks like a year from now, when Claude writes its own harness: 00:39:11

Dan Shipper 📧

66,339 次观看 • 3 个月前

Even when things are going great, running a $1.5 billion AI startup is a knife fight. Granola was one of the first AI apps of this generation to achieve near-ubiquitous adoption. But meeting notes are not the company’s be-all and end-all. The real battle is over owning the interface that everyone uses to get their work done in an AI-native world. I had Chris Pedregal (Chris Pedregal), cofounder and CEO of Granola, back on Every 📧’s AI & I to talk about the current state of the application layer, AI’s frontier, and the future of work. We get into: - Why meeting notes clones don’t matter. Three big companies cloned Granola’s core feature. To him, meeting notes were never the real prize. “Easy come, easy go” is his view of anyone’s lead, including his own. - How he thinks about building proactive features in AI. Granola pre-generates millions of pre-meeting briefs, which include context on the nature of the meeting and people participating, that most people never open. But when they do, they have a magical experience. - Why Granola is betting on “bring your own agent.” Chris says the API and MCP will get “a lot better” over the next few months, and we talk about their agent-native strategy and why they’ve pushed the product that way. This is a must-watch for anyone building at the application layer. Watch the episode! Timestamps Introduction: 00:00:59 Why running a company is a knife fight even when it’s working: 00:01:57 Granola’s counterintuitive view on competition: 00:04:33 Dan’s “pirate and architect” model for early-stage product teams: 00:10:44 Granola’s “shaping” and “validation” phases for building features: 00:13:09 Why Dan lives almost entirely inside Codex: 00:18:17 The case for “Codex-native apps”: 00:24:40 Granola’s “handrail” philosophy: 00:35:37 Why Granola is going all in on winning meeting-adjacent context: 00:38:12 What a transcript alone can never capture: 00:44:19

Even when things are going great, running a $1.5 billion AI startup is a knife fight. Granola was one of the first AI apps of this generation to achieve near-ubiquitous adoption. But meeting notes are not the company’s be-all and end-all. The real battle is over owning the interface that everyone uses to get their work done in an AI-native world. I had Chris Pedregal (Chris Pedregal), cofounder and CEO of Granola, back on Every 📧’s AI & I to talk about the current state of the application layer, AI’s frontier, and the future of work. We get into: - Why meeting notes clones don’t matter. Three big companies cloned Granola’s core feature. To him, meeting notes were never the real prize. “Easy come, easy go” is his view of anyone’s lead, including his own. - How he thinks about building proactive features in AI. Granola pre-generates millions of pre-meeting briefs, which include context on the nature of the meeting and people participating, that most people never open. But when they do, they have a magical experience. - Why Granola is betting on “bring your own agent.” Chris says the API and MCP will get “a lot better” over the next few months, and we talk about their agent-native strategy and why they’ve pushed the product that way. This is a must-watch for anyone building at the application layer. Watch the episode! Timestamps Introduction: 00:00:59 Why running a company is a knife fight even when it’s working: 00:01:57 Granola’s counterintuitive view on competition: 00:04:33 Dan’s “pirate and architect” model for early-stage product teams: 00:10:44 Granola’s “shaping” and “validation” phases for building features: 00:13:09 Why Dan lives almost entirely inside Codex: 00:18:17 The case for “Codex-native apps”: 00:24:40 Granola’s “handrail” philosophy: 00:35:37 Why Granola is going all in on winning meeting-adjacent context: 00:38:12 What a transcript alone can never capture: 00:44:19

Dan Shipper 📧

13,146 次观看 • 1 个月前

From a Thai prison cell to a fintech empire processing $1.6B in international payments across 40+ banks and 250M+ users. Jonathan Low (Jonathan Low). Forbes 40 Under 40. Author of "Cell to CEO." We covered prison, banking for AI agents, RWA projects, the future of crypto in banking, vibe coding for trading, and the businesses that win the next 5 years. ⏱ Timestamps: 00:00:00 — Teaser 00:00:46 — Who is Jonathan Low 00:01:35 — What Jonathan's life was like before prison 00:02:13 — How and why Jonathan ended up in prison 00:02:57 — Prison conditions: expectations vs reality 00:07:33 — Prison became the greatest blessing 00:09:12 — How the entrepreneurial journey began after prison 00:10:34 — Why social capital matters 00:11:06 — Launched own club and took it to the top in 3 months 00:12:09 — Built an Axie Infinity gaming guild during COVID 00:13:49 — The beginning of the BipTap Group journey 00:17:23 — How Jonathan built his own banking system 00:20:07 — How to get a crypto card 00:22:03 — How much it costs to launch a white-label solution with BipTap 00:22:58 — Banking for AI agents 00:25:57 — How to build an RWA project 00:27:45 — Future of cryptocurrencies in banking 00:32:08 — The business verticals within Empire Group 00:32:48 — What Jonathan invests his money in 00:33:54 — How relationships with regulators are built 00:34:43 — Implementing AI in business 00:36:28 — Vibe coding in trading 00:40:06 — Advice for first-time founders 00:43:36 — From construction to trading: Ruslan Khairullin's journey 00:44:57 — Inner peace: why calmness is essential for founders 00:50:39 — Work-life balance for entrepreneurs 00:53:47 — $1.5 million in 24 hours on TST coin 00:55:11 — The best way to capture a market 00:55:57 — Banking for nations Watch the full conversation and let me know which part you liked the most 👇

From a Thai prison cell to a fintech empire processing $1.6B in international payments across 40+ banks and 250M+ users. Jonathan Low (Jonathan Low). Forbes 40 Under 40. Author of "Cell to CEO." We covered prison, banking for AI agents, RWA projects, the future of crypto in banking, vibe coding for trading, and the businesses that win the next 5 years. ⏱ Timestamps: 00:00:00 — Teaser 00:00:46 — Who is Jonathan Low 00:01:35 — What Jonathan's life was like before prison 00:02:13 — How and why Jonathan ended up in prison 00:02:57 — Prison conditions: expectations vs reality 00:07:33 — Prison became the greatest blessing 00:09:12 — How the entrepreneurial journey began after prison 00:10:34 — Why social capital matters 00:11:06 — Launched own club and took it to the top in 3 months 00:12:09 — Built an Axie Infinity gaming guild during COVID 00:13:49 — The beginning of the BipTap Group journey 00:17:23 — How Jonathan built his own banking system 00:20:07 — How to get a crypto card 00:22:03 — How much it costs to launch a white-label solution with BipTap 00:22:58 — Banking for AI agents 00:25:57 — How to build an RWA project 00:27:45 — Future of cryptocurrencies in banking 00:32:08 — The business verticals within Empire Group 00:32:48 — What Jonathan invests his money in 00:33:54 — How relationships with regulators are built 00:34:43 — Implementing AI in business 00:36:28 — Vibe coding in trading 00:40:06 — Advice for first-time founders 00:43:36 — From construction to trading: Ruslan Khairullin's journey 00:44:57 — Inner peace: why calmness is essential for founders 00:50:39 — Work-life balance for entrepreneurs 00:53:47 — $1.5 million in 24 hours on TST coin 00:55:11 — The best way to capture a market 00:55:57 — Banking for nations Watch the full conversation and let me know which part you liked the most 👇

Ruslan Khairullin

16,872 次观看 • 1 个月前