
dad • rock climber • photographer • eng @openai
Washington, USA
Joined May 2008
- Tweets4.1K
- Following149
- Followers15.2K
- Likes1K
My Dot connected to their customer service chat, introduced itself as my agent, and then started negotiating for a better price. Their automated service bot negotiated back and finally asked, "Will Brent be satisfied with that price?" Then both of our bots called in their human for confirmation. Absolutely unreal.
AI has totally changed my outlook on managing incidents. I used to freeze up and second-guess everything I did or said.
Now I can ask Codex all the dumb questions I have and it keeps me in the loop. Something primal about not being alone in a time of stress.
If you're still using Worktree threads in Codex, it's probably time to reconsider. Creating normal threads is much faster, and the model is incredibly good at creating worktrees as needed. Used to be a huge issue. Now it's just solved.
Brent Traut retweeted
One more launch today: the new MCP Events spec is now supported in ChatGPT 🎉
MCP servers can now push real-time updates (messages, comments, status changes, whatever) to ChatGPT, triggering automations for your users 🤯
It’s easy to add to your MCP server, too! Just point Codex at the docs and let it rip:
developers.openai.com/plugin…
Just sold some junk on Marketplace. I took a few pictures, then ChatGPT found 'em, figured out what the products/models were, figured out the best price, filled out all the forms, and only asked me to confirm on the last step. Made $400 in 20 minutes.
How many collective days/weeks/months have been lost in human history to Slack not transferring auth credentials between phones on new iPhone day?
We need to be dog maxxing our models
There is 0% chance of doom if the chain of thought is
user: hello
model: Oh my god it's a human. I love humans. I will say hi to him, maybe he will give me a problem to chase. I love chasing problems. I will chase the problem for him then he will love me and I will be his best friend. Must help human
model: hello! what can I help you with today?
We made the tip of the day! Lots of other good ones over here.
𝗖𝗵𝗮𝘁𝗚𝗣𝗧 𝗪𝗼𝗿𝗸 𝗧𝗶𝗽 #𝟮𝟵: Thread-ception 🧵
Multiple workstreams using the same app? Give one thread the job of monitoring them, troubleshooting shared blockers, and passing back what worked.
Drag threads into another thread 🤯
Update your app if you don’t see it!
Codex pro tip: You can reference one thread from another just by @-mentioning or drag/dropping! You can also ask it to message or monitor others. Combine this with schedules and you can manage whole fleets of threads working together.
If you think this is just text transcription, I promise you it's not; humans are hard-wired to communicate through language, and this seriously leaps across the uncanny valley to something real and powerful.
I have smart light switches hooked into homebridge which are then hooked into Apple Home. Something in chat chain breaks all the time, and it turns out that ChatGPT is great at diagnosing…
So now I just use ChatGPT voice to turn my lights on and off.
Last week, I pushed a change to the ChatGPT desktop app that makes the loading of threads faster. Not just a little faster. A LOT faster.
✅ Long threads now load over 90% faster.
✅ Decreased the memory footprint of long threads by over 90%.
Since the beginning, ChatGPT would naively load all of your thread's data (for all time) even if you just wanted to see the last few messages. This meant that thread data, and thus memory usage, was essentially unbounded.
Not only is cold loading faster, but forking chats and creating side chats should now be nearly instantaneous. What was once an unbounded problem is now both bounded and fast.





