Video yükleniyor...

Video Yüklenemedi

Ana Sayfaya Dön

I think you need to understand how cool and good the Codex sub-agent feature is. For example, here is the perfect task for parallel agents: cleaning and refactoring components based on a skill. So I ask Codex to split the work to speed things up.

Dimillian's profile picture

Thomas Ricouard

47,191 subscribers

55,852 görüntüleme • 7 ay önce •via X (Twitter)

LIVE

Anya Rossi• Live Now

Private livecam show

0 Yorum

Yorum bulunmuyor

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

Benzer Videolar

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

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

GREG ISENBERG

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

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

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

Dan Shipper 📧

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

I wanted to highlight how powerful ChatGPT Voice with Codex is. This is how I operate my computer now. I just ask for things, and things happen. There is no limit to your use cases! The future is already here!
1:28

I wanted to highlight how powerful ChatGPT Voice with Codex is. This is how I operate my computer now. I just ask for things, and things happen. There is no limit to your use cases! The future is already here!

Thomas Ricouard

46,882 görüntüleme • 1 ay önce

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

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

Steve (Builder.io)

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

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

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

Matthew Lam

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

This is exactly what i was hoping for... - Full permissions - no "cowork" like feature which limits agent abilities - Just codex... If you ask for coding task it writes code and gives you a preview. If you ask for a presentation or doc it gives you a presentation or doc. Organized by project on the left side bar. Easy to create skills, easy to @ mention skills / plugins Btw my Readwise automation is insane. Every morning it codex sends me a deck of all my x bookmarks organized by topic. And i highly recommend using the excaladraw skill to render diagrams into docs.
0:33

This is exactly what i was hoping for... - Full permissions - no "cowork" like feature which limits agent abilities - Just codex... If you ask for coding task it writes code and gives you a preview. If you ask for a presentation or doc it gives you a presentation or doc. Organized by project on the left side bar. Easy to create skills, easy to @ mention skills / plugins Btw my Readwise automation is insane. Every morning it codex sends me a deck of all my x bookmarks organized by topic. And i highly recommend using the excaladraw skill to render diagrams into docs.

Riley Brown

65,403 görüntüleme • 4 ay önce

Codex /goal With Hermes Agent is life-changing. I updated my Hermes agent skill to give Codex a goal on the fly using Telegram and track each one of those codex goals in a Kanban board. It has been really insane to see and track Codex execute goals in the wild.
0:32

Codex /goal With Hermes Agent is life-changing. I updated my Hermes agent skill to give Codex a goal on the fly using Telegram and track each one of those codex goals in a Kanban board. It has been really insane to see and track Codex execute goals in the wild.

Shubham Saboo

200,464 görüntüleme • 3 ay önce

Knowing Codex is better for complex tasks makes me bullish on Chamath Palihapitiya and 8090 He points out that Codex is much better for meaty, large problems, while Claude feels good for more day to day work. We’re improving model personality so Codex feels even better for pair programming. But we think pair programming with agents is a local optimization. The longer term pattern is delegation. Most people just aren’t asking agents to do ambitious enough work. The people who are delegating use Codex.
0:31

Knowing Codex is better for complex tasks makes me bullish on Chamath Palihapitiya and 8090 He points out that Codex is much better for meaty, large problems, while Claude feels good for more day to day work. We’re improving model personality so Codex feels even better for pair programming. But we think pair programming with agents is a local optimization. The longer term pattern is delegation. Most people just aren’t asking agents to do ambitious enough work. The people who are delegating use Codex.

Rohan Varma

28,023 görüntüleme • 4 ay önce

How to use Open Design inside Codex: Ask Codex to deploy Open Design locally, then tell Codex what you want to build. The real unlock: Codex can operate the design tool for you — choosing workflows, filling briefs, inspecting files, testing interactions, and iterating on the result. Design tools are becoming agent-operated.
0:48

How to use Open Design inside Codex: Ask Codex to deploy Open Design locally, then tell Codex what you want to build. The real unlock: Codex can operate the design tool for you — choosing workflows, filling briefs, inspecting files, testing interactions, and iterating on the result. Design tools are becoming agent-operated.

Open Design

132,654 görüntüleme • 3 ay önce

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
0:20

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 görüntüleme • 5 ay önce

Wow very easy to create a Codex Site with a Convex DB that your agent can write to. You can make a todo list app that is hosted on Codex Sites, then tell Codex to make a skill that allows the agent to WRITE/EDIT to that todo list db. And then in any chat you can add to your list. Here's example.
0:40

Wow very easy to create a Codex Site with a Convex DB that your agent can write to. You can make a todo list app that is hosted on Codex Sites, then tell Codex to make a skill that allows the agent to WRITE/EDIT to that todo list db. And then in any chat you can add to your list. Here's example.

Riley Brown

54,081 görüntüleme • 2 ay önce

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

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

claire vo 🖤

48,102 görüntüleme • 7 ay önce

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

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

GREG ISENBERG

68,972 görüntüleme • 2 ay önce

With the Codex app you can: - Multitask effortlessly: Work with multiple agents in parallel and keep agent changes isolated with worktrees - Create & use skills: package your tools + conventions into reusable capabilities ⁃ Set up automations: delegate repetitive work to Codex with scheduled workflows in the background
2:12

With the Codex app you can: - Multitask effortlessly: Work with multiple agents in parallel and keep agent changes isolated with worktrees - Create & use skills: package your tools + conventions into reusable capabilities ⁃ Set up automations: delegate repetitive work to Codex with scheduled workflows in the background

OpenAI

395,809 görüntüleme • 6 ay önce

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

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

Dan Shipper 📧

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

This agent relies on a marketplace of 2.8M+ specialized agents to complete a task. This is how I imagine the future of personal agents. Here is how this works: 1. Agentverse is a marketplace of agents 2. Anyone can build and publish an agent there 3. ASI:One is a personal agent with access to the marketplace 4. To solve a task, ASI:One finds the best agent for the job In other words: You have an agent that can solve pretty much *anything* because it knows how to outsource the work to a network of specialized agents. And you don't need to do any setup to get this working. The way ranking agents in the marketplace works is pretty cool: Fetch.ai, the company behind it, created an AgentRank algorithm that works much like Google's PageRank. Every time an agent calls another, it forms a connection. Over time, these connections build into a graph of who relies on whom. An agent that is frequently called by other reputable agents scores higher and surfaces higher in results. The end result here is that your agent will consistently use the best agents in the marketplace to accomplish a goal. You should give this a try: You don't need to pay or even register to try these agents. Thanks to the team for partnering with me on this post.
4:16

This agent relies on a marketplace of 2.8M+ specialized agents to complete a task. This is how I imagine the future of personal agents. Here is how this works: 1. Agentverse is a marketplace of agents 2. Anyone can build and publish an agent there 3. ASI:One is a personal agent with access to the marketplace 4. To solve a task, ASI:One finds the best agent for the job In other words: You have an agent that can solve pretty much *anything* because it knows how to outsource the work to a network of specialized agents. And you don't need to do any setup to get this working. The way ranking agents in the marketplace works is pretty cool: Fetch.ai, the company behind it, created an AgentRank algorithm that works much like Google's PageRank. Every time an agent calls another, it forms a connection. Over time, these connections build into a graph of who relies on whom. An agent that is frequently called by other reputable agents scores higher and surfaces higher in results. The end result here is that your agent will consistently use the best agents in the marketplace to accomplish a goal. You should give this a try: You don't need to pay or even register to try these agents. Thanks to the team for partnering with me on this post.

Santiago

18,715 görüntüleme • 2 ay önce

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

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

Dan Shipper 📧

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

Claude and Codex have a /goal skill now. But for goals to work, you need good acceptance criteria. A good process using Matt Pocock's skills: - Use /grill-with-docs to scope out the feature - Use /to-issues to turn your conversation into actionable goals as GitHub issues
0:47

Claude and Codex have a /goal skill now. But for goals to work, you need good acceptance criteria. A good process using Matt Pocock's skills: - Use /grill-with-docs to scope out the feature - Use /to-issues to turn your conversation into actionable goals as GitHub issues

Ben Holmes

39,550 görüntüleme • 2 ay önce

I don't know how other people work with remote agents when building iOS apps. But my best workflow is to ask Claude/Codex to implement a feature, create E2E test, record that test and show me in Quicktime. I check the video with VNC app then push to Testflight 👌
0:41

I don't know how other people work with remote agents when building iOS apps. But my best workflow is to ask Claude/Codex to implement a feature, create E2E test, record that test and show me in Quicktime. I check the video with VNC app then push to Testflight 👌

An Tran

18,775 görüntüleme • 6 ay önce

Now you can use your favorite AI agent to control your Coinbase account (or a sub-account), with Coinbase for Agents. Here’s a quick demo on how to set it up and some of the cool things you can get your agent to do.
3:17

Now you can use your favorite AI agent to control your Coinbase account (or a sub-account), with Coinbase for Agents. Here’s a quick demo on how to set it up and some of the cool things you can get your agent to do.

Brian Armstrong

213,343 görüntüleme • 2 ay önce