OpenAI Dots start web work on their own cloud computer, which includes a browser and can keep working while the user's devices are off. If a website blocks that cloud browser, the user can connect one personal computer and ask the Dot to try its local browser in a separate task. The cloud browser's session does not move to the local task.
OpenAI Dots key facts
- OpenAI says Dots are powered by GPT-6 Astra, have their own cloud computer, and are available 24/7.
- OpenAI maintains the cloud environment's Linux operating system and Chrome browser.
- A cloud browser keeps its own files, software, and browser sessions. It does not inherit a personal browser's logins.
- If a website blocks the cloud browser, the Dot can try a connected computer. OpenAI says this may create a separate local task.
- One Dot can connect to one personal computer at a time. The computer must be online with the ChatGPT desktop app open. Offline means unavailable, not revoked.
- OpenAI's enterprise guide requires ChatGPT desktop app version 26.929 or higher for Dot local computer access.
- Proactive research uses read-only tools and cannot send messages, change connected content, or control a browser or computer.
How OpenAI Dots run cloud browsers
Each Dot has its own cloud computer. It can browse, analyze information, create files, and run tools there. OpenAI maintains the Linux operating system and Chrome browser in that environment. Cloud work can continue while the user's devices are off, and the computer can keep its state between periods of use.
The cloud browser has its own sessions. A login in the user's personal browser does not sign the Dot in. For supported sign-ins, the Dot pauses while the user enters credentials into a private form. The form sends those credentials to the remote browser without exposing them to the model's context or the conversation.
Users can inspect the cloud computer from the Dot profile under Computers. Selecting Take over gives the user control of its mouse and keyboard. Return control hands it back to the Dot.
How OpenAI Dots use local browser fallback
OpenAI's documentation says to ask a Dot to try a connected computer when a website blocks its cloud browser. The connected computer can provide a local browser and local sign-in path. The handoff may create a separate local task in the ChatGPT sidebar.
The two browser paths remain separate:
Cloud path:
Dot -> own cloud computer (Linux + Chrome) -> website
|
website blocks cloud browser
v
Local path:
Dot -> cloud coordinator -> connected computer -> local browser -> websiteThe local task does not receive the cloud browser's session. OpenAI also says it cannot guarantee that a particular local browser is supported. If the connected computer goes offline, the local task does not automatically migrate to the cloud. The Dot may continue later work on its cloud computer, but the local task itself is not moved there.
To enable the connection, the user opens the Dot's profile in the ChatGPT desktop app, selects Computers, finds Your computer, and confirms Allow access. Only one personal computer can be connected to a Dot at a time. The connection persists between tasks, but the computer must stay online with the ChatGPT app open. Offline means the computer is unavailable. It does not revoke access. Revoke access removes the connection.
How enterprise admins control Dot execution
Enterprise Dots are initially off by default. Workspace administrators manage Dot access under Permissions & roles and manage cloud execution under Cloud computer capabilities.
Setting | What it controls |
|---|---|
| Whether workspace members can use Dots |
| Whether Dots can open and interact with websites in the cloud |
| Whether cloud code and shell commands can reach the internet |
| Whether Dots can interact with desktop applications in the cloud |
| Whether Dots can run supported tasks on connected computers |
These controls are separate. An administrator can allow cloud browser use while withholding local computer access. If any cloud policy enables enforce_residency, OpenAI makes Allow local computer access unavailable for Dots.
Auto-review checks certain planned actions against the user's instructions, Custom Rules, and safety requirements before they run. Proactive research has a narrower boundary: its tools can read permitted sources and save notes, but they cannot send messages, change connected content, or control a browser or computer.
Sources
- Introducing dots: https://openai.com/index/introducing-dots/ (read 2026-10-06)
- How we build safety, security, and privacy into dots: https://openai.com/index/how-we-build-safety-security-and-privacy-into-dots/ (read 2026-10-06)
- Getting started with your dot: https://help.openai.com/en/articles/20001530-getting-started-with-your-dot (read 2026-10-06)
- Manage dots in ChatGPT workspaces: https://help.openai.com/en/articles/20001554-manage-dots-in-chatgpt-workspaces (read 2026-10-06)
- Connect computers and apps to your dot: https://learn.chatgpt.com/codex/dots/computers-and-apps (read 2026-10-06)
- Local computer access for Work Cloud and dots: https://learn.chatgpt.com/docs/enterprise/cloud-local-access (read 2026-10-06)
- Dots privacy, security, and safety FAQs: https://help.openai.com/en/articles/20001529-dots-privacy-security-and-safety-faqs (read 2026-10-06)
Last verified: 2026-10-06.