We’re having way too much fun working through your feedback. (Please, keep it coming.) Keyboard shortcuts are now customizable. Set Codex up around how you actually work, then tweak shortcuts from settings instead of adapting to our defaults.

Thanks for the feedback on Codex in the ChatGPT mobile app. While it’s in preview, we’re working to improve it fast. What you can expect next: push notifications, /fork, ability to restore after revoking, better reconnects, fixing the ability to control other devices, fewer mobile thread errors, better git diff & full-file, no plan mode issues, and lots more polish/bug fixes.

You can now use your ChatGPT subscription in the Zed agent, with the same usage and rate limits you benefit from in Codex directly. We're grateful that @openaidevs continues to support subscription-based access for third-party tools, even as others move toward usage-based billing.

I’ve been testing Codex on mobile and it’s addictive Earlier today I was at a bar with my cofounders, we had an idea, and I literally asked Codex to build the website while I was still sitting there (Yes, I left my Mac lid open)

My laptop has become a “satellite device” since I started using Codex from my phone. And my Mac mini has become the “home.” It’s clunky, but the end state feels more like how we’re going to be working in the near future: I’m currently running the Codex app on 2 devices: 1. my MacBook 2. my Mac mini My laptop isn’t reliably connected to Wi-Fi enough, so I keep a Mac mini on my desk that is always connected. When I kick off new threads from my phone, I start them on the Mac mini. When I’m working from my desk, I run them there too. The cool part is that I’ve added my MacBook and Mac mini as connected devices to each other. That means I can start and resume threads from either device. So if I’m in a meeting but want to continue a thread on my laptop that was started on my Mac mini, I can do that. I’ve also set up mutual SSH for Mac mini <> MacBook, so files are easy to access from either side. It’s not fully seamless yet, but the model works. What this means: - I have an always-on Codex that is accessible from my phone, with its own dev environment - All threads are always accessible from any of the 3 devices - I can run heartbeat threads that stay on 24/7 It’s a little makeshift today, but the shape of it feels very real to me: Codex is no longer tied to whichever computer happens to be open in front of me. It starts to feel like something I can stay connected to across whatever device I’m using.

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

Codex is getting easier to automate and customize around your code. 🪝 Hooks customize the Codex loop with scripts that run at key points in a task: • Run validators before or after work • Scan prompts for secrets • Log conversations to internal systems • Create memories or customize behavior by repo or directory ⚙️ Programmatic access tokens provide scoped credentials for Business and Enterprise teams: • Create tokens from ChatGPT workspace settings • Use them in CI, release workflows, and internal automations • Set expirations or revoke access when needed • Keep usage tied back to the workspace

To bring Codex to Windows, we had to answer a hard question: how do you let coding agents stay useful without forcing developers to choose between constant approval prompts and full machine access? Here’s how we built the Windows sandbox for Codex:

Want to (officially) use Codex at work? Send this post to your CTO to bring your team to Codex. Eligible enterprise customers who switch in the next 30 days get 2 free months of Codex usage for new users.

Codex can now use the in-app browser to test your app at different viewport sizes! It will control the device tool bar and click through your app at different breakpoints to validate & iterate. If it's a long run, Codex will take screenshots at key moments during testing and show them to you at the end of the turn, so you can verify its work. To speed up testing, Codex can hide the IAB to disable animations, and accelerate testing by 1-2x. Separately, we also made annotations send faster and consume less tokens. Hope you enjoy the updates and let us know what you think!

💡 Small Codex tip: You don't have to be limited to looking at one thread at a time. 🪟 Open multiple full windows in parallel 💬 Use /side to fork a conversation to ask temporary follow ups 🛟 You can also set a hot key for the Codex pop up Window to quickly fire off new tasks

Computer use lets Codex work across your apps without taking over your Mac. @AriX talks with @romainhuet about what changes when agents can click, type, and keep working in the background.