What official OpenAI documentation establishes
| Product type | An always-on agent that continues work between conversations and asks for input when judgment is needed. |
|---|---|
| Environment | Its own cloud computer and browser. Cloud work can continue while your devices are off. |
| Context | The active conversation, relevant ChatGPT memory, and the dot's saved notes about preferences and ongoing responsibilities. |
| Connections | Supported plugins, messaging channels, and—when separately allowed—one connected personal computer. |
| Work surfaces | ChatGPT, supported mobile access, calls, Slack and Microsoft Teams, subject to availability and permissions. |
| Review | Activity shows delegated work and requests for input; Scheduled lists recurring work. |
Three connections that do different things
Lets you talk to the same dot and receive updates. Adding Slack does not connect your inbox or computer.
Lets the dot use that service's information and tools within the connected account's permissions.
Makes local files, apps and supported tasks available while that computer is online and the ChatGPT app is open.
Provides a separate browser, files and software that can continue working when your device is off.
Use a dot for work that changes over time
- Monitoring: check approved sources and report only meaningful changes.
- Coordination: maintain decisions, deadlines, owners and unanswered questions.
- Preparation: keep drafts, briefs, analyses or code changes ready for review.
- Follow-through: revisit an open responsibility as new information arrives.
A one-off question may be better handled in a normal ChatGPT conversation. A dot becomes useful when the responsibility persists, the sources are known, and the finish line can be checked.
Availability is still rolling out
As documented on October 8, 2026, dots are rolling out gradually. OpenAI lists eligible Pro users over 18 outside the EEA, United Kingdom and Switzerland; Business Premium and Enterprise are rolling out worldwide, with Enterprise disabled until a workspace administrator enables it. Eligible users may still not see the feature immediately.
Create a dot in the desktop app or a desktop browser. After setup, the same dot can be used in the mobile app when the supporting update is available; mobile web is not supported. Treat plan, region and device details as time-sensitive and check the official access section before purchasing or changing a plan.
Define the job before widening access
- State the responsibility. Name the result the dot should keep current, not a vague goal such as “manage my work.”
- Limit the sources. Connect only the apps and accounts needed for the first responsibility.
- Set interruption rules. Say which changes deserve a message and which routine updates can wait.
- Keep consequential actions gated. Require review before sending, publishing, deleting, buying or changing an account.
- Inspect the source of truth. Review Activity and then verify important outcomes in the original app, account or repository.
Official documentation used
- OpenAI: Meet dots
- OpenAI: Get started with your dot
- OpenAI: Tasks and memory
- OpenAI: Computers and apps
- OpenAI: Control your dot
Official documentation establishes product behavior and access requirements, not the success of a particular workflow. Dots can make mistakes; review consequential work and current documentation.