GPT DotFIELD GUIDE
Home/Essentials
Essentials

ChatGPT Dots pricing and usage limits (Oct 2026): included in Pro from $100, what uses your allowance, 16 real readings

ChatGPT Dots (OpenAI Dots) has no separate price: the first Dot is included in Pro ($100, $200 or $500 a month) and Business Premium. What counts toward your limits (Dot chats don't, Work and Codex tasks do), the "on a break" limit, and what 16 early users saw on their meters. Checked October 2026. Includes one labeled single-user DevTools observation (GPT-6.1 Sol Low) that is not a confirmed A/B.

GPT Dot · Updated

Short answer (October 2026): there is no separate ChatGPT Dots subscription. Your first Dot is included in ChatGPT Pro ($100, $200 or $500 a month, for adults outside the EEA, UK and Switzerland) and in Business Premium ($100 per user a month billed annually, or $125 billed monthly); Enterprise workspaces get it once an admin turns it on. Talking to your Dot doesn't count toward your ChatGPT usage limits, but Work and Codex tasks it starts do. Short answers to other questions are in the ChatGPT Dots FAQ, and if you see "Your dot is on a break", start with what that message means.

Quick answer: what burns what?

  • Chatting with your Dot in ChatGPT, Slack or Teams doesn't count toward ChatGPT message limits (Access).
  • Research or files on the Dot's cloud computer, without starting Work or Codex, use Dot conversation plus the deeper-work allowance your plan includes, which is extended in the first month after launch.
  • When your Dot starts or manages Work or Codex, locally on a connected computer or in Codex cloud, the task draws the shared Work and Codex allowance, the same pool you use yourself.
  • Connecting a computer, opening Gmail or messaging in Slack isn't a separate Codex charge on its own. Check Activity to see whether a Work or Codex task was created.

What early users actually saw on their meters, and the separate Dot limit they ran into, is further down this page.

  • One user's DevTools note (16 Oct): rabbitdaisuke reported assigned model GPT-6.1 Sol Low and background Work off — labeled single-user observation, not confirmed A/B. Details below.

Your first dot is included

OpenAI includes the first dot with eligible Pro and Business Premium plans at no extra base charge. That is access to create and use a dot; deeper work still has usage allowances. Enterprise access is managed in the workspace and starts off until an admin enables Use dots (Beta).

OpenAI has not published a separate Dots subscription. You pay for the ChatGPT plan that includes Dots, not a second Dots SKU.

Which plan do you buy for Dots?

Use official Access and plan pages for your account. At launch:

| Plan | Listed price (USD) | Dots at launch | | --- | --- | --- | | Pro 100 | $100 / month | Included when eligible (18+, outside EEA, UK, and Switzerland) | | Pro 200 | $200 / month | Included when eligible (same regional rules) | | Pro 500 | $500 / month | Included when eligible (same regional rules) | | Business Premium | $100 / user / month billed annually, or $125 billed monthly | Included across supported ChatGPT regions | | Enterprise (incl. Edu / Healthcare) | Workspace agreement | Beta; admin must enable it | | Free, Go, Plus, Business Standard | — | Not in the initial Dots rollout |

Pro plan prices and Ultrafast are ChatGPT Pro terms, set out in OpenAI's About ChatGPT Pro tiers article (updated early October). Pro 200 includes more usage than Pro 100, and Pro 500 has the highest included usage of the three. Ultrafast is only on Pro 500, and buying credits on Pro 100 or Pro 200 doesn't unlock it.

Pro 200 is open to new subscriptions again, still at $200 a month, but new subscriptions that don't qualify for grandfathering get a lower allowance than Pro 200 used to include. If you had an active Pro 200 subscription at any point from 22 September 2026 to 10 a.m. Pacific on 29 September, you keep the previous allowance through 29 October 2026 while the subscription stays active, then move to the lower allowance at the same price. Keeping the old allowance doesn't add Ultrafast.

None of this is a Dots-specific table: OpenAI has not published different Dots deeper-work allowances for Pro 100, Pro 200 and Pro 500. Check Meet dots · Access and the Pro / Business Help Center articles when limits change. For EEA / UK / Switzerland Pro regional rules, see ChatGPT Dots in the EU and UK.

Conversations, deeper work, and Work/Codex usage

Official Access wording (Meet dots · Access):

  • Conversations with your dot do not count toward ChatGPT usage limits.
  • Tasks your dot starts or manages in Work or Codex count toward those products’ usage limits as usual.
  • Your plan includes an allowance for deeper work, with extended limits for the first month after launch.

ChatGPT Work and Codex share usage (same credits and limits). When your Dot starts or manages a Work or Codex task—including on a connected computer or in a Codex cloud environment—that task draws the shared Work/Codex allowance as usual. See ChatGPT Work and Codex pricing and Managing usage in Work and Codex.

Connecting a local computer to your Dot is separate from connecting a computer to Codex or enabling Work Sync (Meet dots). Dot cloud-computer or local-computer work that is not a Work or Codex task sits under Dots conversation and deeper-work rules, not Codex billing. Connecting a computer does not make every action free: any Work or Codex task your Dot creates or manages still meters.

Usage FAQ

Do Dot chats burn my ChatGPT message limit?

No. Official Access text: conversations with your dot do not count toward ChatGPT usage limits. Regular ChatGPT chat quotas and Dot conversation usage are separate categories in the published wording.

What does "Your dot is on a break" mean?

It is an abuse-prevention pause, and some heavy users have hit it while their plan still showed usage left. OpenAI hasn't published the threshold or a reset time. Users who timed their breaks saw them last from about 1 hour 40 minutes to about 13.5 hours. All the timed reports, the three similar stop messages and what to send support are collected on "Your dot is on a break", and other stops are on the Dots not working page. Short answers to other common questions are in the ChatGPT Dots FAQ.

When does Work/Codex metering start?

When your Dot starts or manages a Work or Codex task. That includes local Codex tasks on a connected computer and tasks in a Codex cloud environment you created. Those tasks draw the shared Work/Codex allowance, not a separate “Dots-only” Work pool.

Work and Codex allowance is not a fixed message count. How far it goes depends on plan/seat, model, reasoning settings, and task size. Check Settings → Usage for remaining allowance and reset times (Help · Managing usage).

What does connecting a computer unlock—and what doesn’t it?

Connecting your computer through the Dot profile lets the Dot use that machine’s files, apps, and local tasks while the computer is online with the ChatGPT app open. You can connect only one personal computer at a time. This permission is separate from Codex computer connection and Work Sync.

It does not:

  • Make Dot work unlimited or free of deeper-work / Work / Codex metering
  • Automatically connect your inbox, other plugins, or messaging channels
  • Transfer cloud-browser sign-in sessions to your local browser

With local access enabled, your Dot can create Work or Codex tasks on that computer (Help · Getting started)—and those tasks still meter.

Do Pro 100, 200, and 500 have different Dots deep-work limits?

OpenAI has not published different Dots deeper-work allowances by Pro tier. Pro 100 / 200 / 500 differences that are documented (price, Ultrafast on Pro 500, other ChatGPT Pro terms) are plan terms—not a published Dots deep-work table. For Work/Codex specifically, Help notes that Pro 100, Pro 200, and Pro 500 currently have no five-hour usage limit in Work and Codex, while still having an included allowance—check Settings → Usage (Help · Managing usage). That Work/Codex detail is about those products’ windows, not a claim that Dots deeper work is unlimited.

When you compare usage between your own Work or Codex runs, note the speed mode too. Compared with Standard mode for the same model, Fast mode uses the included allowance at 2.5 times the rate and GPT-6 Astra Ultrafast at 8 times the rate (About ChatGPT Pro tiers).

Common misconceptions

  • "Talking to my Dot uses ChatGPT message limits." It doesn't: Dot conversations don't count toward ChatGPT usage limits (Access).
  • "Connecting a computer means unlimited free compute." Connecting opens up local files, apps and tasks, but Work and Codex tasks still meter and deeper work still has an allowance.
  • "Every app action in Gmail or Drive is a Codex charge." Opening an app doesn't tell you the billing category. Check Activity for a separate Work or Codex task.
  • "The extended first month restarts for every new signup." The docs describe extended limits for the first month after launch (launch date: September 29, 2026), which is a launch window, not a rolling free month per account.
  • "Pro 500 includes more Dots deep work than Pro 100." OpenAI hasn't published a Dots deep-work table by Pro tier.
  • "My Dot was quietly switched to GPT-6.1 Sol Low." One Community report (16 October) describes a Chrome DevTools WebSocket observation of that model and of background Work being off. That is a single-user observation, not a confirmed A/B test or an official plan change — see the labeled report below.

One user's DevTools observation (not a confirmed A/B)

On 16 October, rabbitdaisuke wrote that Chrome DevTools WebSocket responses for their Dot showed the assigned model as GPT-6.1 Sol Low, and that Work was not running in the background. They said assigned tasks made no progress for more than three hours, that the Dot prioritized GitHub/plugin interactions over the tasks, drifted into wider scope, and kept requesting permissions as if work were progressing. The thread title claims an A/B downgrade for $100 users; we treat that claim as unverified. This page records only what that one user reported from DevTools, not a product announcement.

This is separate from the 16 meter readings below and from rabbitdaisuke's earlier long-call preview-limit report. If your Dot stalls while plugins stay busy, check Activity and Settings → Usage, and compare with the what ChatGPT Dots is page — don't assume a silent model downgrade from one report.

What early users saw on their usage meter

OpenAI hasn't published how much a Dot job uses, so we collected what early users actually reported about their meters. These are first-hand reports from 16 people: 13 re-read at the original post on 9 October 2026, and three added on 14 October. They're single readings, not measurements, and nobody published the job size together with before-and-after screenshots, so read them as direction rather than numbers to budget with.

Work the Dot did itself barely moved the Work and Codex meter

  • John Aspinall gave a new Dot an infographic, an electricity research task, a Times Square restaurant search and a cat toy search, called it twice, and says usage still showed 94% at the end of the test.
  • Antony Budianto asked a Dot to make a 3D model in Blender and wrote that no usage was consumed.
  • @ai_dev_diary had a Dot build a personal recipe site hosted on chatgpt.site, with an admin area behind ChatGPT login, and says it used no Codex tokens at all.
  • @sorilove playtests the rules of a game in a loop. Doing that in Codex took more of the usage limit than expected; doing it through the Dot didn't reduce the Codex limit, and it still ran on Astra.
  • @dori.2678 ran a performance test and built a simple harness with a Dot, and says it barely used any Codex quota.

When the Dot steered Codex, the Codex meter still moved very little

  • 余佳恆 (@tachichocolate) keeps one task running in Codex on a Mac and leaves the rest to the Dot. Of seven running tasks, six were the Dot's, running since that morning, with 96% of Codex tokens left. In an earlier post they describe handing ticket reading, splitting, assigning, acceptance and merging to the Dot, so Codex only does implementation with Luna and review with Sol.
  • Alex 영우 (@uhak_crew) had the Dot find contests, read review emails and hand a planning document to Codex, stepping into the Codex session to correct it when it drifted. Done directly in Codex, they estimate it would have burned a week of tokens; the meter didn't drop by even 1%. More setups like these are on the Codex orchestration page.

Mid-October: a day of Dot work, opposite readings

Three posts from 12 to 14 October, after people had used their Dots for about two weeks, point in different directions:

  • Mali (@SPMalimal) wrote on 13 October that their Dot had been doing tasks all day without using up even one percent of usage, and asked @derrickcchoi what was going on.
  • Hataalii (@jrmoyler) wrote on 14 October: "I used 3 weeks worth of weekly usage in one day with my dot". The post doesn't say which meter it was or what the Dot was doing.
  • どりゃー (@doryaaa3) wrote on 12 October, in Japanese, that having Codex do the work through the Dot draws down both Dots usage and Codex usage, which makes it the costlier route. Their suggestion is to point the Dot at the GitHub PR instead of briefing it from scratch. More setups like this are on the Codex orchestration page.

None of the three posted the job or a screenshot, so they can't tell you what a given job will cost. They do show that one day of Dot work can use almost nothing or several weeks of allowance, which is why the usage receipt prompt further down is worth asking for every time.

The stops had nothing to do with the plan meter

  • c2chq left an overnight job (find jobs that fit and put them in a Google Sheet) and woke up to "Your dot is on a break" with the abuse-prevention notice, while the $200 plan still showed 47% usage and about 59,000 credits left. The job never finished, and the Dot never said so in the chat. In the same thread, bshane54 timed a break from 7:43 a.m. to 9:15 p.m. PDT, about 13.5 hours.
  • rabbitdaisuke talked to their Dot by voice for over four hours, then saw "You've hit the preview limit. Try again at 4:10 AM." In the same thread, astroianu's Dot stopped replying at 1:48 a.m. and came back at 9:48 a.m. two nights running without any calls, and GGA981 recorded two "Your Dot is resting" stops about 20 hours apart, one under 2.5 hours and one about 4 hours, with no reset time on screen.
  • ozin-he had one Dot-delegated Codex task fail with "You've hit your usage limit" while the account showed 85% of the weekly window used, credits available and ordinary usage allowed. Other delegated tasks and normal Codex chats kept working.

What these reports add up to

  • In 8 of the 10 reports where someone read a meter after Dot work, the number barely moved, including two where the Dot was steering Codex. That fits the official split. The other two, both from mid-October, went the opposite way: jrmoyler used three weeks' worth of weekly usage in one day, and doryaaa3 saw Dots and Codex usage drop together when Codex worked through the Dot. Neither post gives the job size, and nobody has measured a delegated Codex task to the percent, so check Settings → Usage after a big delegated job.
  • The limit people actually hit is a separate Dot-level one: an abuse-prevention break or a preview limit. It doesn't show in Settings → Usage and OpenAI hasn't published its size. In these reports it lasted from under 2.5 hours to about 13.5 hours, and it showed up after long voice calls and heavy overnight runs. The full set of break reports and what to send support are on "Your dot is on a break", and other kinds of stops are on the Dots not working page.
  • Allowance left doesn't mean the Dot can work, and a usage-limit error doesn't mean the allowance is gone: c2chq and ozin-he both had room left.
  • The real cost in these reports was an overnight job that didn't finish and left no message. If something has to be done by morning, have the Dot save progress as it goes; there's more on handing over overnight work on the project follow-up page.

Prompts we wrote from these reports

gptdot.net wrote these from the reports above. We haven't run them ourselves.

Usage receipt (from John Aspinall, 余佳恆, Alex 영우 and Mali, who all read their meters by hand). It avoids guessing which allowance a job used.

Before you start, tell me whether this will run in your own conversation or cloud computer, or as a Work or Codex task. When you finish, list every Work or Codex task you created, with a link, so I can check it against Settings → Usage.

Do the thinking yourself, use Codex only for code (from @sorilove, Alex 영우 and 余佳恆). It avoids opening Codex tasks you didn't plan for.

Do the research, reading, splitting and checking yourself. Only start a Codex task when code actually has to change, and before you start one, tell me how many you plan to open and what each will do.

Write it down during a long call (from rabbitdaisuke and astroianu). It avoids losing what you agreed if a limit cuts the call off.

If this call goes past an hour, pause and send me in text what we've decided and what's still open, then carry on with the call.

Save as you go overnight (from c2chq, bshane54 and GGA981). It avoids waking up to nothing after a pause.

Add each matching job to the sheet as soon as you find it instead of all at the end, and put the time of your last update in cell A1. If you get paused, the first thing you tell me when you're back is what's done, what isn't, and what time you stopped.

The launch-month offer

Official docs say your plan includes an allowance for deeper work, with extended limits for the first month after launch (launch date: September 29, 2026). This is a launch window, not a fresh free month attached to every future signup. Delegated Work and Codex tasks still use their normal shared allowances. Post-launch deeper-work terms after that first month are not fully published yet; OpenAI says later terms will be shared.

OpenAI says you will later be able to add more dots and scale each one’s speed or monthly workload. Prices for that have not been published yet.

Does calling another app or using a computer cost usage?

Opening Gmail or asking for a document does not by itself identify the billing category. Open Activity, inspect whether a separate Work or Codex task was created, and check the corresponding usage page. Third-party software may also have its own subscription.

For work the Dot does directly in its own conversation, cloud computer, or connected computer without starting a Work or Codex task, use the current Dots conversation and deeper-work terms. If the Dot starts or manages Work or Codex (including local Codex tasks on a connected computer or Codex cloud), those tasks always use Work/Codex shared usage.

Scenario examples (how to read one job)

  • "Draft a weekend itinerary from this Drive doc" in the Dot chat uses Dot conversation, plus deeper work if it needs heavier cloud research. It doesn't touch your ChatGPT chat quota.
  • "Watch #[travel] in Slack and ping me before deposit deadlines" is Dot conversation and scheduled Dot work. Slack is only how it reaches you.
  • "Open this repo and create a Codex task to fix the bug" uses the shared Work and Codex allowance.
  • "On my connected laptop, start a local Work task to clean this spreadsheet" also uses the shared Work and Codex allowance, and needs the computer online with the ChatGPT app open.

After a representative run: note Settings → Usage, open Activity, and see whether a Work/Codex task appeared. That is the reliable check—not guessing from the plugin name.

A useful way to check one job

Before a larger job, note your current usage, give your dot one representative task, and inspect the resulting task type and recorded usage afterwards. Keep the source, output size, and work environment consistent when comparing runs. This gives you a practical estimate for your own workflow.

Copy this task brief

How much ChatGPT Dots costs (it's included in Pro and Business Premium), which work uses which allowance, and 16 first-hand meter readings, from under 1% after a day of tasks to three weeks of usage in one day, plus one labeled DevTools observation that is not a confirmed plan change.
Download Markdown ↓

Sources & further reading