ChatGPT Dots vs Codex vs ChatGPT Work: which to open, how a Dot hands work to Codex, and what 93 real cases show
Codex writes and tests code, ChatGPT Work runs a delegated task, and your Dot owns an ongoing job and hands coding to Codex. Where each task runs, what counts toward Codex usage, and fixes from 93 real cases.

Short answer
ChatGPT Dots, Codex and ChatGPT Work are not three versions of the same thing. OpenAI's own Meet dots page splits them by job:
- Codex is for building, debugging, testing and reviewing software, working directly with code and developer tools.
- ChatGPT Work is for a task you want to delegate, such as research, analysis or creating a file, either now or on a schedule.
- Your Dot is for an ongoing responsibility: it keeps track of it, works out next steps as things change, follows up between conversations, keeps you updated in ChatGPT, Slack or Teams, and can delegate tasks to ChatGPT Work or Codex.
So for most developers the question isn't "Dots or Codex?" but "does this job need a coordinator on top of Codex?" In the 93 Dots + Codex cases, the setups that ran overnight all had the same shape: the Dot coordinates, Codex writes and tests the code, and the owner merges.
Which one to open first
- Open Codex directly for a single coding change you're going to watch. It is the shortest path, and it skips a layer that can fail. Kamimoto's Dot went 20 minutes without noticing that Codex had failed at a node install on his Windows PC; typed straight into Codex, the same instruction worked.
- Use ChatGPT Work for a one-off or scheduled task that isn't mainly code: a research summary, an analysis, a document. A Dot can also start these for you.
- Give it to your Dot when the work keeps going after the first answer: a bug queue, CI that has to stay green, several repos, or several Codex threads you want to follow from your phone. Kurt Bell went to bed with a bug and a data issue and woke up to tested fixes and a morning report; Eduardo (@martiano) went out for dinner while his Dot merged 16 PRs and waited for CI; 余佳恆 (@tachichocolate) gives the Dot tickets, task splitting, acceptance checks and merges, and leaves Codex the implementation and review.
- Ask your Dot for status, not Codex when you're away from your desk. Kevin Ly asked his Dot "Dex" from his phone where a project stood, and it checked his connected Mac and listed what was done and what was left. Kurt Bell asked on a walk and heard that 1,148 tests had passed.
How a Dot hands work to Codex
OpenAI's Tasks and memory page describes four cases:
- A new local Work or Codex task. The Dot creates it on a computer connected to the Dot. That computer has to stay online with the ChatGPT app open.
- An existing local Codex task. The Dot can continue it on the connected computer. Name the task and say what you want to change.
- A new cloud coding task. The Dot creates it in a Codex cloud environment you've already set up, with the repository and setup configuration. Your computer can be offline.
- A task the Dot created. The Dot checks results and sends follow-up instructions through the task's original computer or cloud environment.
Three details explain a lot of the confusion users report:
- Each new task starts with its own conversation. It gets the instructions and context the Dot passes along, not your whole history with the Dot. John Voorhees (MacStories) found the same with his Dot "Puck": a new Codex thread doesn't know what was in the last one unless someone hands the context over.
- Connecting a computer to Codex, or turning on Work Sync, doesn't give your Dot access to it. The Dot's local-computer permission is separate and is set from the Dot's profile (computers and apps). Changing the Dot's selected computer later doesn't move a task that already exists.
- Activity is where you see the real state. In the desktop app, open the Dot's profile, select Activity and open a task to see its progress, files, results and requests for input, or to give it instructions yourself.
The October 5–9 update added more Codex reach: a Dot can now start work in Codex, follow up on existing threads, use context from your existing Codex threads and automations, and decide better when to continue an old thread and when to start a new one. It can also read and edit ChatGPT Work automations.
What counts toward your Codex usage
OpenAI's Access terms say that conversations with your Dot don't count toward your ChatGPT usage limits, that tasks your Dot starts or manages in Work or Codex count toward those products' usage limits as usual, and that your plan includes an allowance for deeper work, with extended limits for the first month after launch. ChatGPT Work and Codex share usage.
That is why the same setup can look cheap for one user and expensive for another:
- Barely any Codex usage: @uhak_crew had the Dot steer a planning job and correct Codex when it drifted, and says his usage barely moved; 余佳恆 still had 96% of his Codex allowance left with six of seven priority tasks running through the Dot; clggest had the Dot build and release a project on its own cloud computer, which by his account used none of his Codex allowance.
- Most or all of it: habibi gave the Dot an overnight summary job with about 20% of Codex usage left and woke up to 0%, six new Codex tasks and work that had failed at an authentication step; @ev.gert nearly hit his Codex limit on the $100 plan.
- Both meters at once: どりゃー (@doryaaa3) found that having Codex do the work through the Dot draws down Dots usage as well as Codex usage, so they point the Dot at the existing GitHub PR instead of briefing it from scratch.
- The rule polaris on linux.do gave: work the Dot hands to the Codex on your own computer runs in Codex and uses your Codex allowance, because the Dot is only coordinating.
If usage matters, tell the Dot where the work should run and how many Codex tasks it may start before asking you. Current plan prices, the deeper-work allowance and 16 users' meter readings are on ChatGPT Dots pricing and usage limits.
Where the handoff breaks, and what got it moving
Every case below is already on the Dots + Codex page, with a link to the original post or issue.
- You approved it in the Dot chat, but the task still refuses. From Oct 2–9, many users found a delegated task treated a relayed approval as untrusted text. What worked was opening the task from Activity and approving there, or typing the request into that task yourself.
- The Dot says it can't reach your local Codex. polaris's fix for soloist: sign in to Codex on that computer and allow remote connection, on top of the Dot's own computer permission.
- "No available execution environment". u/dry_towelette99 found that the Dot's own cloud computer isn't a target for a Work or Codex task. Connecting a spare Linux computer through the desktop app fixed it, and both machines then ran work.
- The task exists, but not where you expected. Chase's Codex task landed in Recents instead of the project folder, and 22 users reported chats outside the project they meant or tasks missing from the sidebar. Opening the task from the Dot's chat or from Activity usually brought it back.
- Silence instead of a failure report. Kamimoto waited 20 minutes before asking "status?", and only then did the Dot find that Codex had failed. Ask for a report within a set time if a delegated step fails.
- The link to your Mac drops. fistre's Dot lost its connection to the Codex app on a Mac mini every few hours, and he had to restart Codex by hand each time.
- The wrong machine for the build. Robert Ellison's Dot fixed three bugs and shipped a feature on his blog through GitHub and Codex, but its Linux cloud computer doesn't suit his Windows and Android builds.
If the Dot itself stops answering, the fixes are on Dots not showing or not working; if it says "Your dot is on a break", see what that message means.
A handoff ask you can copy
A handoff ask you can copy:
You coordinate my Codex work on [repo]. For each job, decide first: a Codex cloud task in the [environment name] environment, or a local Codex task on [computer]. Tell me which before you start. Write the repo, the goal and how to test it into every new task. Don't start more than [number] Codex tasks without asking me. If a step fails or waits for my approval, tell me within 15 minutes and name the task in Activity. Open draft PRs only; merges and deploys wait for me. Send me one morning summary: done, tested how, and what needs my review.
To set up the Dot itself, start with getting started; quick answers on cost, access and limits are in the ChatGPT Dots FAQ.
Related
- Dots + Codex: 93 real cases, from overnight PRs to stuck delegated tasks
- Dots + GitHub: 17 real examples · Build apps, websites & games: 45 real projects, for when the Dot builds the thing itself
- Cloud computer: 50 real cases, for long jobs on the Dot's own machine
- Pricing and usage limits · FAQ · Getting started
- Dots not showing or not working: 75 real reports · ChatGPT Dots vs Grok Bot vs Meta Muse
Copy this task brief
When to open Codex, ChatGPT Work or your Dot, how a Dot starts and follows Codex tasks (local, cloud, existing threads), why Codex usage can stay flat or hit zero, and seven handoff failures with what got them moving.Download Markdown ↓