AIchemist

- Bring meeting recorder to the iOS app. - Use a single interface rather than separate Chat and Work. - Add a Home interface to control Hue lights and Mission Control for the home. - Bring back Pulse; it was my favorite Pro feature. - Make the new bidirectional voice update work with live video.

How can we make ChatGPT better. It’s already on your phone, but what do you wish would happen more or less of when you open the app. How can it bring you more joy?

We're also keeping Claude Code weekly limits 50% higher, now through August 19, for all Pro, Max, Team, and seat-based Enterprise users.

@Dimillian Totally fine when you've got remote Codex on mobile 🫡

Taking 3 days away from the computer wish me luck

@DanJCleary @AnthropicAI Congrats Dan, crush it!

A little overdue but officially joined @AnthropicAI as a Member of Technical staff! Super excited to continue working with startups on the bleeding edge build amazing experiences 🫡

@tarstarr @aaronp613 @thsottiaux makes sense Tara. Appreciate the quick reply. I think being intentional about it will make the experience a lot stickier for ppl. My biggest ask would be bringing this into the iOS app. I can already think of a ton of use cases.

@MrSplitSignal @aaronp613 @thsottiaux thinking about how to bring this into the app in a great way.

OpenAI has released a new ChatGPT app update for macOS It now brings back Chat into full focus and splits Work into a seperate tab

@_catwu Would be great to do a Claude Code session and show your team my workflow, but only if/when those sessions become available. Thanks!

You know your workflows best. Show our team how you use Cowork so we can make it work better for you! If you're in marketing, sales, finance, legal, or any non-engineering role, sign up here for a 30 min screen share with our team: forms.gle/WVvcfdmwhRnp9D…

🚨 BREAKING: Kimi K3 benchmarks have released and it's ~Fable/Sol level

Something I have been thinking about: in the past, the best engineers I knew spent a lot of time automating their work in various ways. Better vim/emacs automations, writing lint rules to catch repeat code issues, building up a suite of e2e tests so they don't need to smoke test the app manually. These kinds of things were the highest leverage activities an engineer could do, because it multiplied their own output, which in turn meant they could build more things. I think many of these automations have become even more important now. This is true for a number of reasons. First, infra and DevX automation speeds you up. And if you are running an army of agents, each of those agents will be sped up also. More automation == more output per unit of time. Second, moving things to code improves efficiency. Your agent could fix an issue every time it sees that issue happen, but that uses tokens and might miss cases. If Claude instead writes a lint rule, CI step, or routine, that class of issue can be fully automated forever. This is really what people are talking about when they talk about loops -- it's about automating entire types of busywork rather than solving them one off. This isn't a new idea at all. Engineers have been doing this for a long time! Third and most importantly, automation makes it possible for others to contribute to the codebase more easily. Increasingly what I am seeing is engineers are contributing to codebases on day one because Claude can navigate the codebase for them, and that non-engineers are able to contribute to a codebase as effectively as engineers can. What gets in the way of both of these is domain knowledge that lives in peoples' heads rather than in automation -- the stuff you used to have to learn when ramping up. What has changed thanks to agents is the domain knowledge that can be encoded as infrastructure is no longer limited to what is expressible in lint rules and types and tests; it can now capture nearly all domain knowledge, encoded as code comments and skills and CLAUDE.md rules and memories. If I put up a PR for an iOS codebase I don't know and a code reviewer rejects it because it doesn't use the right framework, or if a designer builds a new feature and it gets rejected because it doesn't follow the right architectural patterns, these are failures of automation. Every team should be writing the CLAUDE.md's, REVIEW.md's, skills, and docs that enable agents to productively work in their codebase with zero additional context from the prompter. This sounds crazy, and at the same time is a natural extension of the stuff engineers have always done: automate, and encode domain knowledge as infrastructure. As the model gets smarter and as the harness matures, this task becomes easier. In the meantime, it is on every team to look for ways to convert their domain knowledge to infra so that Claude can write code better, so that code review catches issues automatically, and so the next person working on your codebase can contribute more easily.

Really intrigued to see these much needed improvements in voice AI.

@thsottiaux Bringing the meeting recorder to the ChatGPT iOS app would be pretty awesome.

At different times you complained about speed, code slop, frontend quality, ... With each release we improve and GPT 5.6 Sol is ✅Fast and token efficient ✅Hardcore at back-end dev ✅Great at front-end ✅Does not use useEffect everywhere What is next?

@LLMJunky This is a super useful feature, thanks for sharing it!

Okay this is really cool. Codex app has a new feature that is really useful. Highlight any text, and you'll notice a new popup. "More Details" uses GPT 5.5 Instant to explain in more detail about the highlighted portion of your text, allowing you to understand the reasoning/concept/statement/etc in greater detail. What's interesting about this versus a side chat is that it's instantaneous, and still retains context from the thread. With /side chat, you'd have to type out a prompt "what are the details on this?" With "more details" the prompt is implicit and the response is instantenous Very nice feature, as I'm always making side chats/branches to expand/learn/understand agent outputs better.

Would love to see Safari login/password import too, not just Chrome/Atlas. Also, bringing a few ChatGPT Atlas features into the Codex browser would be awesome, like a bookmarks bar and other browser conveniences. And one more vote for bringing ChatGPT’s meeting recorder into Codex.

Import your login + passwords from Chrome & Atlas into the in-app browser with just one click! The in-app browser is amazing today for tasks that originate from the Desktop (i.e. iterating on artifacts, staging context, and reviewing citations).

@fidjissimo Wishing you a smooth recovery Fidji. Take all the time you need to heal. We’re all rooting for you ❤️

Today, I shared with the OpenAI team that I have decided to leave my full-time role at OpenAI and transition to being a part-time advisor. Three months ago, I had to go on medical leave after a severe exacerbation of a chronic illness I’ve lived with for seven years. During that time, it became clear that the road to recovery would be much longer and more complex than I had anticipated—and that I needed to focus on it fully. When I went on leave, many people told me I was courageous for prioritizing my health. The truth is that I am only making this decision now because I failed to make it many times before. Over the years, doctors, friends, colleagues, and loved ones encouraged me to slow down. Two years after I got sick, Facebook offered me the opportunity to take a full year of medical leave. I didn’t even pause to consider it. I immediately said no. At the time, Zuck told me I should play the long game. I wish I had listened. Looking back, I realize that a lot of what made me successful also made this decision incredibly difficult. I grew up believing that opportunities were precious and that when they appeared, you grabbed them with both hands. That mindset carried me from a small town in southern France to opportunities I never could have imagined. By the time I turned 40, I had already gotten to do more than I’d ever dreamed possible as a kid growing up in Sète. I love building. My work has always given me a deep sense of purpose. OpenAI in particular felt like a role that my entire career had been building toward, which made this decision even harder. But what I’m learning now is that grit and endurance are not the only skills required to have impact over decades. Sometimes the harder thing is to stop, listen, and trust that taking care of yourself today makes it possible to contribute for much longer tomorrow. This experience has also strengthened my conviction about why this work matters. It has been a jarring experience to spend my days helping build the future while simultaneously navigating a disabling disease that still has no cure. Over the last seven years, I’ve spent countless hours in doctors’ offices, dealing with symptoms, treatments, insurance, uncertainty, and all the invisible work that comes with being a patient. Like millions of others living with chronic illness, I’ve experienced firsthand how difficult healthcare can be to navigate, even when you have every possible advantage. More than ever, I believe that some of the most important opportunities for AI lie in helping people solve real problems in their daily lives: their health, their finances, their time and the everyday burdens that shape human experience. In particular, curing disease is the most important thing AI could accomplish. I’m excited to continue working towards cures through OpenAI but also through my work with @ChronicleBioAI and @CODA_research. I’m deeply grateful to @sama, @gdb and the OpenAI board for their support during this time and for offering a way for me to continue contributing to the mission without sacrificing my chances of recovery. I’m also so thankful to my team and the many extraordinary colleagues I’ve had the privilege to build alongside. For now, my focus is recovery. But my belief in the potential of technology to solve deeply human problems has never been stronger.

@thsottiaux Any chance we could bring Meeting Recorder from ChatGPT into Codex?

Today, the OpenAI product and engineering team is humming, there is so much to coordinate and keep running across the release of GPT 5.6 Sol/Terra/Luna, ChatGPT Work, the new ChatGPT desktop app, hosted sites and a million other things... together with the new ChatGPT Voice just launched yesterday. We will not get it all right, give us feedback and we will iterate quickly. Thank you for being an amazing community.

@AriX Can we bring the meeting recorder functionality to the iOS and Codex desktop apps? So far, it’s only available in the ChatGPT desktop app, and I use it a lot.

The new ChatGPT Work comes with a new Computer Use experience. It's faster and introduces picture-in-picture, so you can keep an eye on Computer Use while it works!

Today. 10am PT.

OPENAI 🔥: New voice samples and orbs for an upcoming ChatGPT voice mode upgrade. Orb color is bound to an accent color you choose in settings. * Not available yet

@MatthewBerman Yeah, I feel your pain. I blew through all mine (Max 20x) last night!

😭

@felixrieseberg ahh, never mind. For some reason it wouldn’t let me send you a DM.

sent: a Claude Code skill that runs my job applications. research agents map the role, drafts come from an evidence map where every claim needs a receipt, and a second model cuts anything I can't back. the artifact renders the kill list with the dead claims struck through. no resume shows you what it deleted.

If you build something cool, send it to me?