GPT DotFIELD GUIDE
Home/Guides
Guides

What can a ChatGPT Dot do? Its own cloud computer, Codex and Work tasks, your apps and computer, Slack, Teams and calls, plus setup steps and fixes when a feature fails (OpenAI Dots)

A ChatGPT Dot works on its own cloud computer while your laptop is off, starts Codex and Work tasks, uses the apps you connect and, if you allow it, one of your computers. You reach it in ChatGPT, Slack, Teams or a call, but it can't call you yet. Seven setup steps, the blockers early users hit with a fix for each, and one message to start with.

GPT Dot · Updated
OpenAI Dots product demonstration
Image source

The short version: what a ChatGPT Dot can do, how to set it up, and what to check when a feature fails

In one line

Yes for research, documents, data analysis and coding that run on the Dot's own cloud computer while your laptop is off (Introducing dots), and for reading and summarising across the apps you connect. Partly for anything that writes, runs on a schedule or uses your own computer: sends, deletes, edits and scheduled reports work, but only with precise wording, an approval you can find and one small test first. It comes with ChatGPT Pro ($100, $200 or $500 a month, 18 and over, outside the EEA, Switzerland and the UK) and Business Premium, and Enterprise, Edu and Healthcare workspaces get the beta once an admin turns it on (who can get it, pricing and usage). It can't call you, have its own email address or text you outside a limited US Pro beta yet.

Set it up in this order

  1. Create it at chatgpt.com/dots, in the ChatGPT desktop app (also on Windows) or in the latest iOS or Android app. Phone browsers aren't supported (OpenAI Help).
  2. Set custom rules before the first real job: Settings > Personalization, then Custom rules under Permissions. OpenAI's own example is Ask before taking action for messages to customers and Hand off to you for deleting shared project files (Control your dot). 中島大介 did this straight after creating his Dot, before giving it any work.
  3. Connect only the apps the job needs, and set each app's permission level under Settings > Plugins > Permissions: Always ask, Allow read actions, Allow low-risk actions or Allow all actions. Allow all actions isn't in the account-wide selector and is only offered for an individual app or account (Managing app permissions). tadashi-aikawa connected Gmail and Calendar, left Google Drive out and kept reads as the only thing that runs unasked. A connected app can also be read in the background and turned into memories, and disconnecting it later doesn't delete what the Dot learned.
  4. Decide where the work runs. The Dot's cloud computer is the default and keeps going with your devices off. Add your own computer only when the job needs local files or apps: in the ChatGPT desktop app on that machine, open the Dot's profile, then Computers > Your computer > Allow access, and keep the app open. One personal computer at a time. For cloud coding, create the Codex cloud environment first.
  5. Sign in to the websites it will use. When a site needs a login, the Dot sends a private form, or you can sign in yourself with Take over and hand back with Return control. Your own browser's logins don't carry over.
  6. Add the ways you'll reach it. Slack and texting are set up from desktop, Teams is its own connection, calls start from the phone button in its conversation, and on iPhone the Your dot widget and Apple Shortcuts open it with messaging, dictation or a call (ChatGPT for iOS 1.2026.279, What's new). A contact method doesn't connect your inbox or files.
  7. Give it one responsibility first. Name the accounts and sources, say "draft" or "show me first" for anything that sends or deletes, and when it sets a schedule, have it repeat the time, time zone, end date and where results go (Tasks and memory). Check the first result in the app itself, not only in the Dot's report.

Where it gets stuck, and what worked

  • A request that names the item and the action counts as the approval. uehara's calendar was set to confirm before changes, yet "delete the event you just created" went through in about 30 seconds, and "send that draft" sent at once (the 17-task test below). Fix: the wording is your real control. Say "draft" when you want a draft and "show me first" for anything that deletes or sends; asking for a draft never authorizes sending it.
  • The approval prompt shows up only in a separate conversation. A Chrome permission request sat unseen in a sidebar conversation and the step was recorded as aborted after about 21 minutes. Fix: after handing over work that writes or uses your computer, open Activity and look for a "Needs approval" mark; with that conversation open, the same step took 1 minute 10 seconds.
  • A yes in the Dot chat doesn't reach the task that does the work. On 19 October cryptocean asked their Dot to have an existing Work session update a document in Library and Project Files; the handoff was blocked because the authorization was "relayed through untrusted delegated transcript content", a retry repeating the permission was blocked too, and reading kept working (OpenAI Community). Fix: open that task or session from Activity and approve or instruct there, which is what worked for the delegated Codex tasks on Dots with Codex.
  • An app looks connected, but sends and edits fail or come back as "user cancelled". Fix: check the connected account and its allowed actions, reconnect if the connection has expired, then ask for one small write such as a Gmail draft and look for it in Gmail (connecting apps).
  • A delegated task won't start because there's no execution environment. u/dry_towelette99's second task kept failing even after the first one finished. Fix: it started once they connected a spare Linux machine; for cloud coding, set up a Codex cloud environment first.
  • The cloud computer shows Unavailable, or your computer shows Offline. Offline means the machine can't be reached, not that access was removed. Fix: open the ChatGPT app on that computer before changing anything else; Reboot doesn't always bring a cloud computer back (when the computer is unavailable).
  • A website blocks the cloud browser. Fix: ask the Dot to try your connected computer. That may start a separate local task, and the cloud browser's session doesn't come with it.
  • A request made on a call never becomes a task. Fix: after the call, type "List the tasks you started from that call" and resend anything missing as text (voice calls).
  • A scheduled report arrives late, or the work finishes and the report never comes. uehara's 8:30 summary landed at 8:44, and a Slack summary went quiet until a nudge showed the result had failed to send. Fix: have it confirm each schedule, and read the result even when a run says completed, because a completed run doesn't by itself mean the result was delivered.
  • Pause didn't stop everything. Fix: Pause stops only the current main task; stop a delegated task from Activity and turn off a recurring run under Scheduled.

What it can do, and what it can't yet

It can:

  • keep working on its cloud computer with your devices off, and run several threads at once; u/dry_towelette99 had their Dot working on its own computer, a task running on a connected Linux machine and a background research agent with no computer at the same time
  • read your connected apps in the background and bring you suggestions; those research tools can't send messages, change app content or control a browser or computer
  • use one of your computers, start local Work or Codex tasks there and use your local browser when the cloud browser is blocked
  • sign in to websites through a private form without the password passing through the chat
  • answer in ChatGPT, Slack and Teams and on calls you start, as the same Dot with the same notes

It can't yet:

  • call you; OpenAI Help says it "cannot initiate calls to you at launch"
  • have its own email address; it sends from the account you connect
  • text you outside the limited beta for some Pro users in the US, which isn't available in Business or Enterprise
  • keep exact time on schedules
  • forget what it learned from an app you disconnect; only deleting the Dot removes its own memories
  • act on an approval it forwards into another task or Work session
  • use more than one personal computer at a time

One message to start with

You're taking on one responsibility: [the job]. Use only [apps and accounts], and tell me which account you're reading from in each answer. Read, research and draft freely. Before you send, delete, move or buy anything, show me in this chat exactly what will change and wait for my yes, even if my request already named the item. If a step needs an approval, sign-in or reconnection in another conversation or task, tell me here and give me its name. When you set a schedule, repeat back the time, time zone, end date and where the results go. Each evening, list what finished, what is waiting for me and anything that failed to send.

What each feature does, and where people get stuck

Its own cloud computer

What it does

The Dot has its own files, software and browser sessions on a cloud computer that keeps its state between uses. Open it from the Dot's profile under Computers; opening it only lets you watch, and you select Take over to drive it and Return control to hand it back (Computers and apps). On the phone, the computer opens in your control straight away.

Where people get stuck

Some users found the cloud computer marked "Unavailable" or Offline while chat still worked, and Reboot didn't always bring it back (cloud computer says "Unavailable"). Others assumed their own browser logins would carry over; they don't.

What to check

Before a long job, ask the Dot to open its computer and list what's installed and which sites it's signed in to. What people actually run there, from Blender renders to multi-day document reviews, is in cloud computer use cases.

Cloud threads and delegated tasks

What it does

The Dot can start separate threads for cloud work, which show up in the desktop, web and mobile apps, and you can keep talking to it while they run. For coding it can use a Codex cloud environment you've already set up with the repository (Computers and apps).

Where people get stuck

The Dot's own cloud computer is not the same thing as the places a delegated Work or Codex task can run. u/dry_towelette99 had a second task fail to launch with no execution environment, even after the first job had finished; it started once they connected a spare Linux machine (Reddit). Tasks also land outside the project you meant, or go missing from the sidebar (where a Dot's tasks end up).

What to check

Ask the Dot which execution targets it can see right now (its cloud computer, a connected computer, saved Codex environments) before you hand it coding work. When a task stalls, open that task and answer any pending decision, approval, sign-in or connection request there, and give corrections there too: each task has its own conversation and doesn't automatically get everything you've said to the Dot. If a task seems lost, check the computer or cloud environment it started on, because changing the Dot's selected computer doesn't move an existing task. Reports of Dots that can't message existing local Codex threads are on Dots + Codex.

Your own computer

What it does

You connect one personal computer at a time from the Dot's profile in the ChatGPT app on that machine (Computers, then Your computer, then Allow access). Keep the app open while the Dot uses it. This permission is separate from connecting the computer to Codex or turning on Work Sync (Computers and apps).

Where people get stuck

On Windows, the most reported failure is "setup refresh had errors"; on Mac, the app can fail to load the Dot at all (errors on your own computer).

What to check

Look at the computer's status on the Dot's profile. If it says Offline, open the ChatGPT app on that machine before you change anything else. If Allow access isn't offered, you're not in the desktop app on that computer. Local skills only work through a computer connected to the Dot.

Signing in to websites

What it does

When a site needs a login, the Dot sends a private form; your password and any verification code go straight to the remote browser, not into the chat. You can also choose to sign in yourself in takeover mode. Save to Passwords is optional, and reusing a saved login always needs your confirmation; a session that is still valid can be reused without signing in again (Computers and apps).

Where people get stuck

Some websites block cloud browsers or ask for extra verification. OpenAI's suggestion is to ask the Dot to try your connected computer instead, which may start a separate local task and does not carry over the cloud browser's session.

What to check

For a site you'll use every week, sign in once yourself in takeover mode, then ask the Dot to confirm it can open your account page. Signing in on your own computer doesn't sign the Dot in.

Connected apps and plugins

What it does

The Dot uses the plugins installed and enabled on your ChatGPT account, with the same permissions, so you can let it read email without letting it send (Computers and apps).

Where people get stuck

Reading works, so the connection looks fine, but sending, editing or watching doesn't. Writes come back as "user cancelled" when you cancelled nothing, or a yes in chat never reaches the exact action. The fixes for Gmail, Calendar, Slack, Drive, GitHub and Teams are on connecting apps to a Dot.

What to check

Ask for one small write before you rely on an app, such as a draft saved in Gmail or a one-line test event, and check it in the app itself. Look at the app's permission level too: one early user found it at "allow low-risk tools", and another switched it to read-only so that anything beyond reading asks first (both setups are under approvals below). If a connection has expired, open the reconnection request and reconnect. On the phone, plugins are under the Dot's profile in Customize > Plugins.

Messaging: Slack, Teams, and calls

What it does

Slack, Teams and voice calls are ways to reach the same Dot. Adding one does not connect your inbox, files or computer (Computers and apps).

Where people get stuck

In Slack, some Dots could read a channel but not reply there while DMs worked, and one team saw replies 50 minutes behind the conversation (where Slack setups break). Teams has two separate connections that do different things (Teams). On calls, the most common loss is a spoken request that never becomes a task; typing the same request worked (what gets lost between a call and the work).

What to check

After a call, ask in text: "List the tasks you started from that call." Anything missing, send again as text. If calling fails but chat works, carry on by typing in the same conversation.

Schedules, responsibilities, and proactive research

What it does

A schedule says when to run a check; a responsibility says what to keep true over time. Proactive research reads your connected information in the background without a new message from you, and it does not send messages, change apps, or control a browser or computer on its own (Tasks and memory).

Where people get stuck

Users found the Dot couldn't see or edit every scheduled task it had made, while the same edit worked in ChatGPT on the web, and some triggers went quiet without warning (after it's scheduled).

What to check

Ask the Dot to list its scheduled tasks with times and status, and compare that with Recent activity on its profile on the web. The repeat schedule, time and completion notifications can be changed from the task under Scheduled. Copy-ready schedules are in Workflows.

Approvals, custom rules, and stopping work

What it does

Custom rules decide what the Dot may share, buy or access: act without asking, act when you say so, ask first, or hand the step to you. They cannot override built-in safety requirements, and some steps, such as changing a password, are always yours (Control your Dot).

Where people get stuck

Early users either got asked for permission one step at a time (approvals in practice) or found that a yes given in the Dot chat didn't count inside a delegated task (why your yes doesn't reach the task). In one measured test, an explicit "delete it" went through despite a confirm-first setting, and a missed approval prompt in a separate sidebar conversation cancelled the step after about 21 minutes (the 17-task test below).

Two setups from early users

  • 中島大介 asked before giving it any work. On launch day he created a Dot on a Pro plan and asked it whether it would ask for approval before sending email or changing his calendar (his note write-up, 30 Sep 2026, in Japanese). The Dot's answer: not every time. A "send it" for an email with a clear recipient and purpose may be taken as the approval, "draft it" never sends, and sharing confidential information or making a serious commitment needs an explicit yes. A new rule started at Ask before taking action. He didn't test a real send; this is what the Dot said plus what the settings screen showed. His three steps: review the plugin list in ChatGPT before creating the Dot, set sending and deleting to ask first straight away, and start with research and drafts that touch nobody outside. What you learn: ask the Dot how it reads "send" before you trust a rule.
  • tadashi-aikawa made reading the only thing that runs unasked. He connected Gmail and Google Calendar but left Google Drive out, because it holds things he doesn't want read and nothing the Dot needs (his blog post, 4 Oct 2026, in Japanese). The connection itself couldn't be limited to read-only, so he set the plugin permission to read-only tools, the level OpenAI's settings list as Allow read actions: reads go through, and anything else asks him first. What you learn: leaving an app out is the simplest privacy control.

What to check

Set your custom rules before the first real job, then give one consequential instruction and watch where the approval shows up, including any new conversation in the sidebar. If you approved something and it's still blocked, open the task and look for a separate sign-in, connection or approval request. On the phone, rules are under Customize > Custom rules. To stop everything until you're ready, Pause is in the ••• menu on the profile, and "Paused • Tap to resume" starts it again.

A 17-task test: where approvals, schedules and replies actually showed up

From 7 to 9 October 2026, uehara connected a Dot on a Pro plan to the Gmail, Google Calendar, Drive, GitHub, Slack, Notion, Jira and Outlook accounts they use for work every day, gave it 17 real tasks, and checked each result in the apps themselves and in git log instead of trusting the Dot's report (DEV Community write-up, 9 Oct 2026). Reading and summarising were right wherever they could check: 32 commits in a week, matching their own count, and 18 products read from a live page, matching the page. The useful findings are about where work stopped.

  • The request itself counted as the approval. uehara set the calendar connection to confirm before any change, then asked the Dot to delete the event it had just created and touch nothing else. The event was gone in about 30 seconds, with no confirmation screen. Asked why, the Dot said a request that names both the item and the action counts as permission. Email worked the same way: "create a draft" only made a draft, and "send that draft" sent it without a prompt. uehara notes the setting may not have taken effect yet; the wording is what made the difference.
  • The approval prompt appeared only in a separate conversation. Notion's connector had no delete, so the Dot switched to Chrome on uehara's Mac and moved that step into a new conversation in the sidebar. The prompt asking to use Chrome appeared only there. Nobody pressed it, and after 1,254 seconds (about 21 minutes) the step was recorded as aborted by the user; the main chat said only "The deletion was not carried out." The second time, with that conversation open, it finished in 1 minute 10 seconds. Neither time did a notification arrive, only a "Needs approval" mark in the sidebar.
  • Work that finished, but whose report never arrived. A summary of Slack mentions went quiet after "I'll check". Five minutes later, when nudged, the Dot said the check was done but sending the result had failed.
  • Reconnecting an app doesn't restart the work. The calendar connection dropped during a long download job. After uehara reconnected it, the job stayed stopped until they told the Dot to continue. That job took 2 hours 6 minutes, and about 1 hour 45 minutes of it was the Dot waiting for answers: where to save the files, and whether it could enter the purchase email it had found in Gmail.
  • What it does through your computer is recorded under your name. The Notion page it removed through Chrome on the Mac shows in Notion as deleted by uehara, because uehara is the one signed in there.
  • Schedules are close, not exact. A weekday 8:30 summary arrived at 8:44 and opened with an apology. It covered all 16 calendars correctly, but ran to six lines when five or fewer were asked for. The Dot had already said exact timing is something it can't guarantee.
  • Slack answers land in a thread. A DM was acknowledged in 13 seconds and answered in 81, as a thread reply that the DM list shows only as "1 reply".

What to change in your setup

Settings alone didn't stop an action the request spelled out, so the wording of a request is your real control: say "draft" when you want a draft, and say "show me first" for anything that deletes or sends. After you hand over work that writes, deletes or uses your computer, check the sidebar for a "Needs approval" mark or a new conversation, not just the main chat. If an app disconnects mid-job, reconnect it and then say "continue".

An ask you can copy after this test:

Before you delete, send or move anything, tell me in this chat exactly what you're about to change and wait for my "yes", even if my request already named the item. If any step needs my approval in another conversation, tell me here and give me that conversation's name. If a step stops or an app disconnects, tell me what is unfinished instead of waiting for me to notice.

ChatGPT Space

In ChatGPT Space, mention @dot (or open the @ menu) on a page or in a comment to ask your Dot to draft, research or revise. Select text and use Ask for change when offered for smaller rewrites. Keep Updated is not available at launch, so a cadence written in a page does not schedule recurring work by itself. See Use ChatGPT Dots in ChatGPT Space.

Memory and feedback

Tell your Dot the editorial, analytical or coding choices you want repeated. Correct a specific output and explain the preference behind the correction. For project facts that change, keep one named source of truth and ask the Dot to refer back to it.

What a Dot remembers, per OpenAI

OpenAI's Tasks and memory page separates three things:

  • It starts from your ChatGPT memory. A new Dot begins with relevant context from ChatGPT memory, then keeps its own notes about your preferences, decisions and ongoing work. Those notes are separate from ChatGPT's saved memory and aren't a transcript of everything you've said.
  • Changing ChatGPT's memory settings doesn't necessarily change the Dot's notes. To wipe what the Dot itself has kept, the controls page points to Delete, which can't be undone; read its confirmation for what happens to conversations, memories and scheduled tasks.
  • One Dot across ChatGPT, Slack and Teams. Switching channels doesn't reset its notes, and something you said in one channel can shape its work in another. Being able to use a detail isn't permission to share it, though: posting a private deadline in a team channel still needs your OK. A task the Dot starts gets the instructions and context for that work, not every conversation you've had with it.

What people ran into

  • An old private plan came up in the first chat. In AI Arte's first conversation with a new Dot on 1 October, the Dot suggested a private plan the author had discussed earlier in ChatGPT, before it had been mentioned to the Dot. The author told it that plan wasn't the job, to leave earlier private context out and use only public OpenAI information, and the Dot agreed to narrow its scope. AI Arte doesn't treat that reply as proof anything was deleted, and notes it can't tell whether saved memory or past chats were the source. Disconnecting an app doesn't delete what the Dot already learned from it either.
  • A handover note before the first job. Before giving the Dot any family work, Haroka talked it through in ChatGPT and had it write a handover note: what matters most, the budget, which decisions stay with Haroka, and which actions need a check first (family and health, cases 27–28).
  • A handover note before deleting. When a Slack problem pushed Fotios to delete the Dot and start again, Fotios first had the old Dot write a handover document into a Space, so the new one didn't start from nothing (Slack, case 21).

An ask you can copy to review what it remembers:

List what you currently remember about me and my work, split into three groups: things from my ChatGPT memory or earlier chats, notes you've saved yourself, and things you only know from a connected app. Mark anything you're not sure is still true. Don't delete or change anything until I say which items to drop.

Related

Scenario guides

Compare with other agents

Side-by-side pages with sources:

Copy this task brief

What a ChatGPT Dot can and can't do yet, seven setup steps, the common blockers with a fix for each and one starter message, then each feature with where early users got stuck.
Download Markdown ↓

Sources & further reading