Loading video...

Video Failed to Load

There was a problem loading this video. This could be due to a temporary network issue or the video might be unavailable.

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... show more

Emanuele Di Pietro

11,521 subscribers

40,166 views • 7 months ago •via X (Twitter)

Anya Rossi• Live Now

Private livecam show

15 Comments

Theo - t3.gg7 months ago

How can we get Remodex supported natively? I really want control from my phone

Emanuele Di Pietro7 months ago

you mean from openai itself? i think @Dimillian will work on it once he starts working in openai

Theo - t3.gg7 months ago

@Dimillian Nah - I mean T3 Code (specifically the `npx t3` package/ws server) to work with Remodex 👀

Emanuele Di Pietro7 months ago

@Dimillian I'd love to find a way out

Torsten Sandor7 months ago

@theo @Dimillian Please make it happen, Remodex is great 🤞

Emanuele Di Pietro7 months ago

@torstensandor @theo @Dimillian if theo agrees we can do something!

Thomas Ricouard7 months ago

@torstensandor @theo So in Codex Monitor, I've made the mistake of writing my own protocol and server daemon, and I deeply regret it. I should have adopted the raw Codex App Server because it was just so painful to add new app server features every day...

Emanuele Di Pietro7 months ago

@torstensandor @theo yeah that makes sense, that's why i wanted to do the app-server

Emanuele Di Pietro7 months ago

Really amazing work @theo This is so well done, will use this as base for one of my next project

Emanuele Di Pietro7 months ago

This is Remodex btw! It is also available on the AppStore!

Julius7 months ago

@theo Biggest thing to solve with these integrated browsers is the auth part. None of the existing ones uses the keychain/passwords from my existing browsers or let me log in with passkeys etc which just makes them unusable for ”real use”. But we defintely need to get it in somehow

Emanuele Di Pietro7 months ago

@theo yeah that makes perfect sense

Jan Drlý7 months ago

@theo Wish this would make it to the main branch with option to use my cookies and plugins from helium

George Valandis7 months ago

@theo What made Codex CLI better for you?

Umair Ali7 months ago

@theo theo team is so cooked tbh

Related Videos

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 views • 5 months ago

Random side project: I’m building a Codex-like agent orchestrator but with a sidebar that doesn't make me question whether the ppl who make sidebars ever use them extensively. I think Codex/Claude code's desktop app's sidebars kinda suck, so I’m going Arc-style instead with one colored space per big project, split screen, smooth dragging, folders, a command + T pannel (not demoed below).... just for myself for now. It’s written in Swift and already feels great. I’m lowkey planning to switch off Codex entirely once I polish it up, the main thing holding me back is Codex’s STT, which is genuinely excellent and sadly isn’t exposed through OAuth :( (Basically forked Theo - t3.gg / maria’s T3 code and wrapped it in an Arc-like sidebar I had already made for

Random side project: I’m building a Codex-like agent orchestrator but with a sidebar that doesn't make me question whether the ppl who make sidebars ever use them extensively. I think Codex/Claude code's desktop app's sidebars kinda suck, so I’m going Arc-style instead with one colored space per big project, split screen, smooth dragging, folders, a command + T pannel (not demoed below).... just for myself for now. It’s written in Swift and already feels great. I’m lowkey planning to switch off Codex entirely once I polish it up, the main thing holding me back is Codex’s STT, which is genuinely excellent and sadly isn’t exposed through OAuth :( (Basically forked Theo - t3.gg / maria’s T3 code and wrapped it in an Arc-like sidebar I had already made for

Yousr

45,986 views • 3 months ago

I've unlocked 10x more from Codex since I've let the agent prompt and manage itself. I call this "The Orchestrator Rule". Here's why it works so well: - Models like GPT 5.6 Sol are getting better at inferring your intent. - Codex has the ability to create, monitor, and send messages to other Codex threads. - So you can just tell Codex the outcome you want, and Codex can turn that into detailed prompts, spin up one or more threads to do the work, and bring the results back to you. This changed my job as a builder: Instead of writing perfect prompts, I described outcomes with success criteria and verification methods. And Codex wrote the prompts and orchestrated the work for me. Hence the "Orchestrator" Rule. Here are 2 ways to let Codex prompt and manage itself: (1) Ask Codex to kick off a task in a new thread. - You can give it a short description of the outcome you want to achieve, and Codex will expand that into the detailed instructions it needs to deliver. (2) Keep one parent thread for each project and let Codex spin up new child threads for individual tasks - This pairs really well with Voice mode. - You can talk to your parent thread like a chief of staff. It can kick off the work using child threads and report back when it needs your input or when the task is complete. I demo both these methods below:

I've unlocked 10x more from Codex since I've let the agent prompt and manage itself. I call this "The Orchestrator Rule". Here's why it works so well: - Models like GPT 5.6 Sol are getting better at inferring your intent. - Codex has the ability to create, monitor, and send messages to other Codex threads. - So you can just tell Codex the outcome you want, and Codex can turn that into detailed prompts, spin up one or more threads to do the work, and bring the results back to you. This changed my job as a builder: Instead of writing perfect prompts, I described outcomes with success criteria and verification methods. And Codex wrote the prompts and orchestrated the work for me. Hence the "Orchestrator" Rule. Here are 2 ways to let Codex prompt and manage itself: (1) Ask Codex to kick off a task in a new thread. - You can give it a short description of the outcome you want to achieve, and Codex will expand that into the detailed instructions it needs to deliver. (2) Keep one parent thread for each project and let Codex spin up new child threads for individual tasks - This pairs really well with Voice mode. - You can talk to your parent thread like a chief of staff. It can kick off the work using child threads and report back when it needs your input or when the task is complete. I demo both these methods below:

Avthar

62,604 views • 2 months ago

I built a plugin for Codex so it can Create and Animate sprites for your game Install from inside codex app, connect your SpriteCook account, and tell it to what to create! Available here (experimental):

I built a plugin for Codex so it can Create and Animate sprites for your game Install from inside codex app, connect your SpriteCook account, and tell it to what to create! Available here (experimental):

Kimo

32,898 views • 7 months ago

We just shipped in-app visualization capabilities in T3 Code. This enables agents to build cool dynamic experiences within the thread. Huge shoutout to Ben Davis for pushing us on this (and building most of it). Didn't expect to dig it so much.

We just shipped in-app visualization capabilities in T3 Code. This enables agents to build cool dynamic experiences within the thread. Huge shoutout to Ben Davis for pushing us on this (and building most of it). Didn't expect to dig it so much.

Theo - t3.gg

488,457 views • 27 days ago

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 views • 4 months ago

WOW! I'm so excited about this. OpenAI Developers said Codex was good at Computer Use, but I wasn't prepared for this. For the last two weeks I've been working on a Computer Use skill to work with Linux. And while I had some success, it was a pretty frustrating experience. That is...until the breakthrough. Using accessibility tools, Codex can now control my entire computer, not just the browser. There are limits to this, of course, but what a time to be alive. This Computer Use skill will unlock and entirely new set of automations, all powered by Codex. Demonstration below 👇

WOW! I'm so excited about this. OpenAI Developers said Codex was good at Computer Use, but I wasn't prepared for this. For the last two weeks I've been working on a Computer Use skill to work with Linux. And while I had some success, it was a pretty frustrating experience. That is...until the breakthrough. Using accessibility tools, Codex can now control my entire computer, not just the browser. There are limits to this, of course, but what a time to be alive. This Computer Use skill will unlock and entirely new set of automations, all powered by Codex. Demonstration below 👇

am.will

79,698 views • 7 months ago

We just launched Sites into Codex! Software creation was always about more than writing code. Sites in Codex fundamentally gives the power of end-to-end software creation to every user, no matter their technical fluency. These Sites are fully deployed to a URL, private to workspaces, come with authentication, can have static files, and can store dynamic data in databases. It is in preview for business and enterprise teams and will be rolling out to all workspaces over the next day. Give it a try by typing @ Sites into Codex and ask it to build anything! This project took a massive amount of effort across hundreds of people at OpenAI - proud that we were able to get this out and excited to see what you all build with it!

We just launched Sites into Codex! Software creation was always about more than writing code. Sites in Codex fundamentally gives the power of end-to-end software creation to every user, no matter their technical fluency. These Sites are fully deployed to a URL, private to workspaces, come with authentication, can have static files, and can store dynamic data in databases. It is in preview for business and enterprise teams and will be rolling out to all workspaces over the next day. Give it a try by typing @ Sites into Codex and ask it to build anything! This project took a massive amount of effort across hundreds of people at OpenAI - proud that we were able to get this out and excited to see what you all build with it!

Rohan Varma

1,074,970 views • 5 months ago

🚨 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 views • 1 year ago

Hacking a Polaroid printer with Codex: the printer didn't have a Mac app or any way to connect to a laptop, so I got Codex to reverse engineer the bluetooth connectivity and build a native swift app. We then also built a Codex skill to get it to print something fun. With coding assistants you can now avoid being stuck with badly design native software, but build something yourself that you'll like and enjoy - whether it is a printer, digital photo frame or some other IoT device gathering dust around the house. It is really not that hard to do anymore.

Hacking a Polaroid printer with Codex: the printer didn't have a Mac app or any way to connect to a laptop, so I got Codex to reverse engineer the bluetooth connectivity and build a native swift app. We then also built a Codex skill to get it to print something fun. With coding assistants you can now avoid being stuck with badly design native software, but build something yourself that you'll like and enjoy - whether it is a printer, digital photo frame or some other IoT device gathering dust around the house. It is really not that hard to do anymore.

Peter Gostev

23,225 views • 8 months ago

$I just compared Claude Code vs Codex vs Cursor CLI The task was to build a Next.js app with Tailwind 4 and shadcn components to collect customer feedback and showcase it with a widget. I gave all three the same prompt and let them go for 30 minutes to see what they came up with. Claude Code with Opus 4.1 Even though I told it to set up the app in the existing project folder, it tried to create a directory for it. After I interrupted and told it not to do that, it built a demo form and landing page with no errors. I had to ask it to make the demo interactive so users could submit a testimonial and preview it. The landing page looked like AI and was pretty basic, but it worked and it was done in a fraction of the time of the others. Total tokens used: 33k Codex with GPT-5 At the end of the 30 minutes I just could not get Codex to produce a working app. It got stuck in a loop of not being able to set up Tailwind 4 and despite many, MANY, attempts, I ended up with a "failed to compile" error. Total tokens used: 102k Cursor Agent with GPT-5 This was the slowest agent by far and a couple of times I actually thought it got stuck in a loop and was close to Ctrl+C'ing to cancel it. The TUI is really nice though, especially how it shows diffs and it did eventually build a working app (after one or two slight errors that needed fixing) The demo was interactive and it had a very minimal design that looked bare but also a lot less like an "AI generated" app than the Opus 4.1 design. It also wasn't too chatty and just did what it needed to do! Code quality was on a par with Opus 4.1, but it did use 5.5x as many tokens to get there. Still cheaper than Opus on a direct comparison but not when you factor in a Claude Code Max subscription. Total tokens: 188k I'll be able to do a proper comparison and record some videos when I'm back from holiday but for now, Opus is still the more capable model out of the box and Claude Code is the more complete CLI product. It will be interesting to see how Cursor evolve their CLI though with commands and subagents because I think with GPT-5 they have a real shot at providing competition for Claude Code if they can optimise output to get similar quality with less tokens. Jump to 0:40 in the video to see the two apps. Which do you think is which? ;)$

I just compared Claude Code vs Codex vs Cursor CLI The task was to build a Next.js app with Tailwind 4 and shadcn components to collect customer feedback and showcase it with a widget. I gave all three the same prompt and let them go for 30 minutes to see what they came up with. Claude Code with Opus 4.1 Even though I told it to set up the app in the existing project folder, it tried to create a directory for it. After I interrupted and told it not to do that, it built a demo form and landing page with no errors. I had to ask it to make the demo interactive so users could submit a testimonial and preview it. The landing page looked like AI and was pretty basic, but it worked and it was done in a fraction of the time of the others. Total tokens used: 33k Codex with GPT-5 At the end of the 30 minutes I just could not get Codex to produce a working app. It got stuck in a loop of not being able to set up Tailwind 4 and despite many, MANY, attempts, I ended up with a "failed to compile" error. Total tokens used: 102k Cursor Agent with GPT-5 This was the slowest agent by far and a couple of times I actually thought it got stuck in a loop and was close to Ctrl+C'ing to cancel it. The TUI is really nice though, especially how it shows diffs and it did eventually build a working app (after one or two slight errors that needed fixing) The demo was interactive and it had a very minimal design that looked bare but also a lot less like an "AI generated" app than the Opus 4.1 design. It also wasn't too chatty and just did what it needed to do! Code quality was on a par with Opus 4.1, but it did use 5.5x as many tokens to get there. Still cheaper than Opus on a direct comparison but not when you factor in a Claude Code Max subscription. Total tokens: 188k I'll be able to do a proper comparison and record some videos when I'm back from holiday but for now, Opus is still the more capable model out of the box and Claude Code is the more complete CLI product. It will be interesting to see how Cursor evolve their CLI though with commands and subagents because I think with GPT-5 they have a real shot at providing competition for Claude Code if they can optimise output to get similar quality with less tokens. Jump to 0:40 in the video to see the two apps. Which do you think is which? ;)

Ian Nuttall

195,173 views • 1 year ago

I love when Codex outsmarts me! Asked Codex to hack this badge that I got from Temporal's conference by putting Codex pets on it. I also gave it a photo of the badge along with it. Codex found the actual firmware of the badge on GitHub to have a starter 😂

I love when Codex outsmarts me! Asked Codex to hack this badge that I got from Temporal's conference by putting Codex pets on it. I also gave it a photo of the badge along with it. Codex found the actual firmware of the badge on GitHub to have a starter 😂

dominik kundel

35,125 views • 5 months ago

OpenAI just killed the worst part of building iOS apps with AI. The new Codex "Build iOS Apps" plugin can now: → run your app in an in-app browser → open SwiftUI previews → hot reload edits all without leaving Codex. No more copy-paste-build-screenshot loop. The agent sees what it ships. This is the loop indie devs have been begging for.

OpenAI just killed the worst part of building iOS apps with AI. The new Codex "Build iOS Apps" plugin can now: → run your app in an in-app browser → open SwiftUI previews → hot reload edits all without leaving Codex. No more copy-paste-build-screenshot loop. The agent sees what it ships. This is the loop indie devs have been begging for.

Blaida

852,106 views • 4 months ago

I designed this mobile app in Figma and decided to build it with Claude Code. These are some of the interactions I’ve built so far. Compared to the last time I tried building a mobile app with Claude Code for a client, this has been sooo much easier.

I designed this mobile app in Figma and decided to build it with Claude Code. These are some of the interactions I’ve built so far. Compared to the last time I tried building a mobile app with Claude Code for a client, this has been sooo much easier.

Wuraola | Product Designer

18,246 views • 1 month ago

I solved building decks with AI agents — by giving them a CLI tool like Powerpoint or Google Slides. AI could already make a beautiful deck if you asked it to using Ant's pptx skill. The problem was working with it. If it made one alignment mistake, fixing it on one slide would break something on another, and it became a game of whack-a-mole. One time I spent two days playing AI roulette, hoping the next prompt would finally fix the thing, and ended up building the whole deck by hand because I was on a deadline. So I built Hands-on Deck. And the reason it works is that this isn't just a skill — this is PowerPoint. The actual application: PowerPoint, Google Slides, Keynote, whatever you use. This is that, but for an agent, presented as a CLI. Every gesture you make in a deck app maps to a command. Click a box and type, drag a shape from here to there, look at a slide – agent can do it all in a command. And that changes how the agent behaves. With this CLI it works and thinks like a designer — it looks, makes an edit, looks again, makes another surgical edit. Compare that to Anthropic's pptx skill, built on the idea that Claude is a great programmer: it literally writes code to manipulate the deck, hand-editing XML and hoping it doesn't break anything else in the middle. The real test isn't creating something once — it's whether it can make surgical edits like you want. That's what I did in this video walkthrough and my claude crushed it! Check it out for yourself. So decks can be built like a designer now — with real flavor and taste. If you spend hours every week on decks, this gives those hours back. You can install it as a skill in Claude Code, Codex, whatever you use. Works every harness that supports skills. Let me know if you make something cool with it.

I solved building decks with AI agents — by giving them a CLI tool like Powerpoint or Google Slides. AI could already make a beautiful deck if you asked it to using Ant's pptx skill. The problem was working with it. If it made one alignment mistake, fixing it on one slide would break something on another, and it became a game of whack-a-mole. One time I spent two days playing AI roulette, hoping the next prompt would finally fix the thing, and ended up building the whole deck by hand because I was on a deadline. So I built Hands-on Deck. And the reason it works is that this isn't just a skill — this is PowerPoint. The actual application: PowerPoint, Google Slides, Keynote, whatever you use. This is that, but for an agent, presented as a CLI. Every gesture you make in a deck app maps to a command. Click a box and type, drag a shape from here to there, look at a slide – agent can do it all in a command. And that changes how the agent behaves. With this CLI it works and thinks like a designer — it looks, makes an edit, looks again, makes another surgical edit. Compare that to Anthropic's pptx skill, built on the idea that Claude is a great programmer: it literally writes code to manipulate the deck, hand-editing XML and hoping it doesn't break anything else in the middle. The real test isn't creating something once — it's whether it can make surgical edits like you want. That's what I did in this video walkthrough and my claude crushed it! Check it out for yourself. So decks can be built like a designer now — with real flavor and taste. If you spend hours every week on decks, this gives those hours back. You can install it as a skill in Claude Code, Codex, whatever you use. Works every harness that supports skills. Let me know if you make something cool with it.

Nityesh

70,086 views • 4 months ago

Today, we launched browser use inside Codex to further close the build & verify loop for local development! Now, you can ask Codex to build your front end, and test it like a user would by clicking through the app. Codex sees everything a user sees through vision & checks the network/console logs to help debug & fix any issues that it finds. This change brings us closer to fully autonomous coding agents that delivers high quality and tested changes. Watch Codex test my app in the browser, catch & fix a real bug, and doing that loop again with a brand new feature.

James Sun

227,571 views • 6 months ago

The /handoff skill is so great. I use it to plan with Claude Code using /grill-me, and delegate that plan to multiple worktrees running Codex

The /handoff skill is so great. I use it to plan with Claude Code using /grill-me, and delegate that plan to multiple worktrees running Codex

Ben Holmes

70,049 views • 5 months ago

With all the buzz around the Codex App, OpenAI Developers quietly snuck out a new CLI update (0.94.0) as well. And boy is it an important update! Codex Plan mode is now officially released to the general audience! I am very excited about this one as it has a really strong prompt that is unlike any other plan mode I've personally used. Codex Plan mode doesn't necessarily just ask you 3 questions up front. It goes, collects context, asks questions, collects more context, asks more questions (sometimes), and then writes an incredibly high quality plan. It is my favorite implementation of plan mode thus far. It also comes with Codex's own version of "AskUserQuestion!" Although, it only works in Plan mode for now. They really need to allow people to use it in Code mode as well, but one win at a time. npm i -g @openai/codex Below is a demo of how it works. Let me know what you think!

With all the buzz around the Codex App, OpenAI Developers quietly snuck out a new CLI update (0.94.0) as well. And boy is it an important update! Codex Plan mode is now officially released to the general audience! I am very excited about this one as it has a really strong prompt that is unlike any other plan mode I've personally used. Codex Plan mode doesn't necessarily just ask you 3 questions up front. It goes, collects context, asks questions, collects more context, asks more questions (sometimes), and then writes an incredibly high quality plan. It is my favorite implementation of plan mode thus far. It also comes with Codex's own version of "AskUserQuestion!" Although, it only works in Plan mode for now. They really need to allow people to use it in Code mode as well, but one win at a time. npm i -g @openai/codex Below is a demo of how it works. Let me know what you think!

am.will

57,121 views • 9 months ago

Wanted to make it easier for T3 Code users to debug their setups when things go wrong. Just shipped a new feature on nightly to help. `npx t3@nightly triage` It collects info on your setup, writes a prompt, then kicks you to Claude Code or Codex to debug and fix

Wanted to make it easier for T3 Code users to debug their setups when things go wrong. Just shipped a new feature on nightly to help. `npx t3@nightly triage` It collects info on your setup, writes a prompt, then kicks you to Claude Code or Codex to debug and fix

Theo - t3.gg

82,867 views • 2 months ago

yesterday, at the Codex hackathon, i ended up solving this problem by building an MCP connector app that turns ChatGPT into Codex, sort of. 1. you get to use GPT-5.5 Pro by exposing your local dev environment to ChatGPT, so you can use 5.5 pro for planning and handover to codex to execute it 2. you get to 2x your rate limits, just like last month, because apparently ChatGPT and Codex have separate rate limits here is the quick demo

yesterday, at the Codex hackathon, i ended up solving this problem by building an MCP connector app that turns ChatGPT into Codex, sort of. 1. you get to use GPT-5.5 Pro by exposing your local dev environment to ChatGPT, so you can use 5.5 pro for planning and handover to codex to execute it 2. you get to 2x your rate limits, just like last month, because apparently ChatGPT and Codex have separate rate limits here is the quick demo

waishnav

558,372 views • 4 months ago