Always-On Agentic AI Assistant

OpenAI Dots Wiki

Learn how OpenAI Dots uses GPT-6 Astra, dedicated cloud computers, connected apps and persistent agents to automate long-running work across ChatGPT.

Open ChatGPT

OpenAI Dots Resources

Everything you need to set up, connect, and automate work with OpenAI Dots

Latest Updates

Discover the newest guides, tips, and content

OpenAI Dots DevDay: Announcements, Features & Setup Guide

Everything announced about OpenAI Dots at DevDay 2026: GPT-6 Astra, cloud computers, 4,000+ app connections, setup steps, permissions, and use cases.

Sep 30, 2026devday
Read more →
OpenAI Dots vs AI Agents: 2026 Comparison & Verdict

OpenAI Dots vs Meta Muse vs Grok Bot: pricing, features, and security compared. Find the best always-on AI agent for work, life, or development.

Sep 30, 2026comparison
Read more →
OpenAI Dots Alternative: Free, Open-Source Setup Guide

Looking for an OpenAI Dots alternative? Compare Open Dots: free, open source, any model, local data storage, and a permission-based safety checkpoint.

Sep 30, 2026comparison
Read more →
OpenAI Dots Email Marketing: Setup Guide & Workflow Tips

Learn how to use OpenAI Dots for email marketing: campaign setup, AI-assisted copywriting, audience segmentation, and workflow automation tips.

Sep 30, 2026business
Read more →
OpenAI Dots One Person Business: Setup Guide & Tips

Learn how to use OpenAI Dots to run your one-person AI business: setup, task assignment, guardrails, and data control strategies.

Sep 30, 2026business
Read more →
OpenAI Dots Personal Assistant: Setup Guide & Key Features

OpenAI Dots personal assistant guide: GPT-6 Astra, cloud computer, 4,000+ app connections, scheduled tasks, permissions, and step-by-step setup.

Sep 30, 2026features
Read more →
OpenAI Dots GPT: Setup Guide, Features & Access Explained

Learn how OpenAI Dots GPT works: always-on AI assistants, GPT-6 Astra power, plugin access, security controls, and who can try it in 2026.

Sep 30, 2026chatgpt
Read more →
OpenAI Dots vs ChatGPT: Key Differences Explained

Compare OpenAI Dots vs ChatGPT: always-on agents, GPT-6 Astra, cloud computers, connected apps, and which to use for your workflows.

Sep 30, 2026comparison
Read more →
OpenAI Dots Availability: Plans, Regions & Access Guide

Where OpenAI Dots is available in 2026: supported plans (Pro, Business Premium, Enterprise beta), regional limits, pricing, and setup steps.

Sep 30, 2026access
Read more →
OpenAI Dots Pro: Setup Guide, Plans & Pro Workflow Tips

OpenAI Dots Pro guide covering GPT-6 Astra agents, cloud computers, apps, automations, permissions, and pro-level workflows for power users.

Sep 30, 2026pricing
Read more →
OpenAI Dots Cloud Computer: Setup Guide & Features Explained

Learn how OpenAI Dots cloud computer works: setup steps, proactive agents, permissions, pricing, and safety rules for first-time users.

Sep 30, 2026features
Read more →
OpenAI Dots Supported Regions: 2026 Availability Guide

Where OpenAI Dots is available in 2026: rollout phases, plan and admin requirements, and how to check access in your region.

Sep 30, 2026access
Read more →

OpenAI Dots Beginner Guide

OpenAI Dots are persistent AI assistants designed to keep working toward assigned goals instead of relying only on one-off chat sessions. Start by creating a dot, defining what it should accomplish, and giving it a clear first task.

1

Create Your Dot

Open the Dots experience in ChatGPT and start a new dot. Give it a clear name that reflects the job or project it will handle.

2

Define the Goal

Describe the ongoing outcome you want the dot to work toward. A focused goal gives the dot a stable direction across multiple actions and work sessions.

3

Set Its Working Instructions

Add instructions describing what the dot should prioritize, what boundaries it should follow, and how independently it should operate.

4

Assign the First Task

Give the dot a concrete task connected to its main goal. The dot can use its configured workspace and available tools to work through the task.

5

Review Ongoing Activity

Check the dot's activity and outputs as it works. Unlike a normal ChatGPT conversation, the dot is organized around persistent goals and continued task execution.

Quick Tips

  • Name each dot after the job it handles so multiple dots stay easy to tell apart.
  • A focused goal beats a broad one: one clear outcome gives the dot direction across sessions.
  • Start with one dot per project, then add more once you know how each workflow behaves.
  • Check the activity view regularly to see what the dot has completed and what is still in progress.

OpenAI Dots Availability and Plans

Dots availability depends on ChatGPT plan, workspace configuration, rollout status, and supported platform. Workspace administrators can also control whether members are allowed to use Dots.

CategoryAvailabilityDetails
ChatGPT AccessPlan-dependentDots access is tied to supported ChatGPT plans and the current product rollout. Eligible users can access Dots from supported ChatGPT interfaces.
Workspace AccessAdmin-managedBusiness and organizational workspaces can manage Dots availability through workspace controls and administrator settings.
Desktop WebSupportedUsers with access can create, configure, and manage Dots through the desktop web version of ChatGPT.
Desktop AppSupportedDots can be accessed through supported ChatGPT desktop experiences for users included in the rollout.
MobileRollout-dependentMobile access can vary by account, platform, and rollout stage, while more advanced configuration is centered on desktop experiences.
Enterprise WorkspacesControlled rolloutEnterprise access can be enabled through supported workspace deployments with administrator control over availability and connected tools.

OpenAI Dots Setup Guide

A well-configured Dot starts with a specific purpose and clear working rules. Use the setup process to define what the Dot should accomplish, provide useful context, and decide how it should handle ongoing work.

1

Start a New Dot

Open Dots from ChatGPT on desktop web or the supported desktop experience and choose the option to create a new dot.

2

Choose a Name

Give the dot a short, descriptive name based on its responsibility, such as a project, workflow, research topic, or recurring operational task.

3

Define Its Goal

Write a clear goal describing the result the dot should continually work toward instead of giving it only a single isolated prompt.

4

Configure Autonomy

Set instructions and boundaries that determine how the dot approaches tasks, when it should act, and when additional user input or approval is appropriate.

5

Attach Context and Files

Add relevant files and supporting information so the dot has the project context it needs when completing assigned work.

6

Open the Activity Dashboard

Use the dot's activity view to review its work, inspect completed actions, follow current tasks, and manage its ongoing configuration.

OpenAI Dots Apps and Integrations

Connected apps expand what a Dot can access and accomplish. Each connection follows the permissions available to the user or workspace, allowing a Dot to work with approved information and communication channels.

Slack

Team Communication

Connect supported Slack access so a Dot can work with permitted workspace communication and use relevant channel context as part of its assigned workflows.

Uses authorized user or workspace access

Email

Communication

Connect supported email access to give a Dot permission to work with approved messages and communication-related tasks within the configured account.

Limited to granted account permissions

Files

Knowledge and Context

Attach files or provide supported file access so a Dot can use project documents, reference material, and other context while completing work.

Uses files explicitly provided or authorized

Workspace Apps

Productivity

Supported connected apps can extend a Dot's workflow with external information and actions while remaining subject to workspace configuration and app permissions.

Controlled by connected-app and workspace settings

Communication Channels

Notifications and Interaction

Configured communication channels provide additional ways for users and Dots to exchange task information, updates, and workflow context.

Requires supported channel configuration

OpenAI Dots Scheduled Tasks

Scheduled tasks turn a dot into an ongoing assistant rather than a one-time chat. Users can assign work that runs later or repeats on a schedule, then review active, upcoming, and completed activity from one place.

1

Create a Scheduled Task

Tell the dot what should happen and when. Tasks can be configured for a specific future time or set to repeat on a recurring schedule.

2

Run Recurring Checks

Use scheduled work for repeated activities such as reviewing updates, checking connected information, or preparing recurring summaries.

3

Receive Proactive Updates

A dot can surface results after scheduled work finishes, allowing useful information to arrive without starting a new conversation manually.

4

Review Task Activity

Open the task management view to see active, scheduled, and completed work and keep track of what the dot is doing over time.

OpenAI Dots Cloud Computer

The cloud computer gives a dot its own remote working environment for multi-step tasks. Users can inspect what is happening, interact when needed, and keep cloud execution separate from optional access to a local computer.

A dot can work inside its own cloud-based computer environment instead of depending on the user's current browser tab or local machine.

Independent Execution

Cloud-based work can continue while the user moves on to other activities, making the environment useful for longer multi-step workflows.

Users can open the dot's computer view to inspect the current state of its work and understand what actions are taking place.

Interact When Needed

The user can step into the computer session when manual input, review, or intervention is useful.

The dedicated cloud computer is separate from optional local-computer capabilities, allowing users to distinguish remote agent execution from access involving their own device.

OpenAI Dots Permissions and Controls

Permissions define the boundaries within which a dot can operate. Controls cover connected services, computer capabilities, autonomous behavior, and organization-level availability so access can match the needs of each workflow.

ControlScopeDescription
Connected App PermissionsUser and workspaceControls which connected applications and services a dot is allowed to access while completing assigned work.
Cloud Computer AccessDot capabilityControls whether the dot can use its dedicated cloud computer for browser-based and multi-step computer tasks.
Local Computer AccessOptional user capabilitySeparates optional interaction with the user's own computer from work performed inside the dot's dedicated cloud environment.
Autonomy SettingsUser configurationDefines how independently the dot can continue work, perform ongoing tasks, and act between direct user interactions.
Workspace AvailabilityAdministratorWorkspace administrators can manage whether Dots are available and which capabilities members can use inside managed environments.
Enterprise Access ControlsEnterprise administratorEnterprise controls allow organizations to apply workspace-level restrictions and governance to Dots and their connected capabilities.

OpenAI Dots Use Cases

The strongest use cases for Dots are ongoing workflows where context and work need to persist. A dot can repeatedly gather information, review connected data, run scheduled tasks, and continue complex work without starting from zero each time.

Ongoing Research

Assign a research topic that evolves over time and let the dot continue collecting, organizing, and updating relevant findings across multiple work sessions.

Calendar Review

Use connected calendar access to review upcoming events, identify important meetings, and prepare recurring schedule summaries.

Reminders and Follow-Ups

Schedule reminders or future follow-up work so important tasks can be surfaced at the appropriate time.

Recurring Monitoring

Have a dot repeatedly check information that changes over time and surface meaningful updates as part of an ongoing workflow.

Combine information and actions across permitted connected apps so the dot can complete workflows that span multiple services.

Delegate longer workflows involving research, browser interaction, organization, and follow-up actions that would be cumbersome to complete in a single chat.