Delegate work in Codex to your dot. Your dot can now start work in Codex and follow up on existing threads, drawing on your ChatGPT conversations, Codex threads, and automations. It’s also better at deciding when to keep a thread going or start fresh. Your dot can also review... and edit Scheduled Tasks in ChatGPT Work, too. Ask what’s scheduled or update a recurring task as plans change.show more

Fresh updates for dots. First up: you can now create your dot straight from your phone in the ChatGPT app on iOS and Android.

And finally, a bunch of small fixes that you’ve been asking for: • Faster browsing, smoother scrolling • Fewer unnecessary notifications • Cleaner code blocks and attachments • Easier Outlook setup • Clearer plans and easier retries • More reliable Enterprise access on web and voice

Sorry; could you clarify what changed, here? I’ve been orchestrating codex threads with my dot since day 1 using, among other things, a native Codex tool integration for messaging other threads.

Dot could send codex fine until a couple days ago then an update killed that, did this just bring that back as a feature?

I won’t lie this sounds amazing but what is the point if so many things are blocked by policies?

NOT IN THE UK IT CAN'T Can somebody please just respond about when this is coming to the rest of the world and what the problem is? Is it that difficult? Ask your Dot!!

OpenAI's dots page lists Pro 100, 200 and 500 only for users outside the EEA, UK and Switzerland, while Business Premium and Enterprise roll out worldwide. So in Europe, dots go to work plans, not even to the top consumer tier.

The real power isn't delegating tasks. It's building systems that know what needs to be done next.

I need a second dot

This is awesome!

wait my dot was already spinning up and running codex tasks like a week ago lol

No it's not working well, you really need to fix this issue to make Dots work as a cross-platform always-on agent that developers can work on their mobile.

this makes the experience of arbitrary refusals and permissions so much more fun tbh - find the broken session is my dot's favorite new game.

I note how you have used the phrase "your dot" multiple times.. and not "your dots" Sounds like we're not getting multiple dots anymore?

I like to think I helped getting this pushed faster 😁

Silly question… haven’t we been doing this since launch? Or did it only work with Codex Cloud?

Please fix this papercut: In Codex you can press return when dictating to finish dictation and send in one go. Great UX, its missing for dots. @ajambrosino

Yeah, that’s a fucking good plan. Considering how dumb the models are recently… let another one be in charge…

The biggest AI breakthrough might not be smarter models. It's AI that remembers what it's working on, picks up where it left off, and actually gets things done without constant hand-holding. We're getting closer to that.

Hago eso desde el primer dia... no es novedad.

@pvncher Been doing this for a week. Can they actually talk to chats I already made or only the chats they made? Asked for that feature the first day dots came out.

I've been having a lot of problems with my DOT today Give it a task and slack, it doesn't answer me, it doesn't tell me it got blocked, and then it gives me an elicitation to click and approve but the elicitation is broken.

When dot will me release in EU?

This should've been a day one feature just saying but nonetheless, very useful!

how is this better than a normal session

This already existed…?

Yes! This was what it was missing.

I’d genuinely love to use the version of this feature described in the announcement. It worked for me at launch. Then direct communication with my existing Codex sessions disappeared. A delegated task could still act as a relay, until it lost the tools needed to reach those sessions too. After seeing this post, I had my dot audit its entire available tool set and run fresh checks: Native Codex list/read/send/wait tools: missing. cloud_threads.read on an existing session: “unsupported placement format version 1.” cloud_threads.send_message to that session: “Cloud thread not found.” Existing delegated task: receives the request and replies, but confirms it has no onward communication tools. Visible-app fallback on my connected, authorized Mac: blocked from accessing the Codex app for safety reasons. So what, specifically, am I missing? What is the supported communication tool my dot should be using to follow up on my existing Codex threads? Is there a required app version or a rollout still in progress? Any actual troubleshooting guidance would be appreciated.

@grok c'est dispo sur le plan free

Wasn’t it already been doing it since day 1?

Oh I noticed this!! Was super impressed.😎

This is big news & I am excited for the QoL improvements to Dots. But you guys know the big gap Dots still have. Browser control for Dots & orchestrated sessions. I heard so many openAI devs claiming browser control was solved. Where did it go?

Scheduled talks aren’t working for me I get notifications but can open the conversation and my dot cannot connect to my Mac or windows PC one gets error 1 and one gets error 2

Can it start threads inside my projects in Codex?

OMG, about time !!!!