# 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.

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.

### 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](https://learn.chatgpt.com/docs/dots/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"](/dots-not-showing/)). 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](/use-cases/cloud-computer/).

### 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](https://learn.chatgpt.com/docs/dots/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](https://www.reddit.com/r/ChatGPT/comments/1wuzlvp/i_spent_a_day_poking_dots_with_sticks_heres_what/)). Tasks also land outside the project you meant, or go missing from the sidebar ([where a Dot's tasks end up](/use-cases/codex-orchestration/)).

#### 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](/use-cases/codex-orchestration/).

### 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](https://learn.chatgpt.com/docs/dots/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](/dots-not-showing/)).

#### 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](https://learn.chatgpt.com/docs/dots/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](https://learn.chatgpt.com/docs/dots/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](/integrations/).

#### 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](https://learn.chatgpt.com/docs/dots/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](/use-cases/slack-assistant/)). Teams has two separate connections that do different things ([Teams](/integrations/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](/use-cases/voice-calls/)).

#### 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](https://learn.chatgpt.com/docs/dots/tasks-and-memory#proactive-research)).

#### 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](/use-cases/morning-brief/)).

#### 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](/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](https://learn.chatgpt.com/docs/dots/controls#stop-work)).

#### Where people get stuck

Early users either got asked for permission one step at a time ([approvals in practice](/what-is-dots/)) 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](/use-cases/codex-orchestration/)). 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](https://note.com/merilinc/n/n6ef4574698a3), 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](https://nocturne.mamansoft.net/posts/2026-10-04-started-openai-dots/), 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.

Source: https://gptdot.net/features/
