- OpenAI Dots DevDay: Announced September 29, 2026 as OpenAI's always-on AI agent product
- Powered by GPT-6 Astra: The flagship model for complex reasoning, coding, and computer use
- Dedicated cloud computer: Each Dot runs its own browser and remote working environment
- 4,000+ app connections: Dots integrate with Slack, email, files, and workplace tools
- Persistent by design: Dots follow up through ChatGPT, SMS, email, and Slack between sessions
OpenAI Dots DevDay Overview
OpenAI Dots debuted at DevDay on September 29, 2026 as OpenAI's answer to persistent, always-on AI assistants. Unlike a normal ChatGPT conversation that ends when you close the tab, a Dot is a durable agent built around long-running goals. It keeps its own cloud computer and browser, connects to your tools, and continues working between your interactions.
The announcement centered on four pillars, and each one shapes how you should plan your first Dot.
GPT-6 Astra
- Flagship reasoning model
- Optimized for computer use and research
- Powers every Dot
Cloud Computer
- Dedicated per Dot
- Own browser environment
- Runs independently of your device
4,000+ Apps
- Connected tools ecosystem
- Slack, email, files, workspace apps
- Permission-based access
Always-On
- Persistent goals
- Scheduled and recurring tasks
- Proactive follow-ups
OpenAI's official safety documentation added a dedicated Dots section at launch, which signals how much weight the company is placing on permission and governance for always-on agents. The core technical explanation currently lives inside the GPT-6 Astra System Card under "Introducing: dots."
The most reliable primary sources are the GPT-6 Astra model page and System Card on OpenAI's site, plus the OpenAI Deployment Safety Hub for the new Dots safety section. Community discussion is active on r/OpenAI and the OpenAI Developer Community forum at community.openai.com.
Key DevDay Announcements
The DevDay reveal framed Dots around what makes them different from one-off chats: continuity, tool access, and independent execution. Here is how the headline announcements break down.
| Announcement | What It Means | Practical Impact |
|---|---|---|
| Always-on agents | Dots persist around assigned goals | Work continues between conversations |
| GPT-6 Astra power | Flagship model for reasoning and computer use | Handles multi-step, browser-based tasks |
| Per-Dot cloud computer | Each Dot gets a remote machine and browser | Long jobs don't depend on your laptop |
| 4,000+ app connections | Broad connected-tool ecosystem | Cross-app workflows inside one agent |
| Multi-channel follow-up | ChatGPT, SMS, email, Slack touchpoints | Results arrive without re-prompting |
| Safety documentation | New Dots section in official safety docs | Permission and approval controls from day one |
The multi-channel follow-up deserves emphasis. A Dot does not wait passively for you to return. It can push updates through the channels you authorize, which turns it from a chatbot into something closer to a persistent operations assistant.
GPT-6 Astra is defined by OpenAI as the flagship model for complex reasoning, coding, computer use, research, and end-to-end work. It is the underlying engine of Dots rather than a separate user-facing feature, so you configure Dots directly rather than picking a model.
How to Set Up Your First Dot
Dots are created and managed inside ChatGPT, with the fullest configuration experience centered on desktop web and the desktop app. The workflow below reflects the recommended first-run path.
Open Dots in ChatGPT
On desktop web or the supported desktop app, open the Dots experience and choose to create a new dot.
Name It by Responsibility
Pick a short, descriptive name tied to a project, workflow, or recurring operational task so you can distinguish multiple Dots later.
Define the Goal
Write the ongoing outcome the Dot should work toward. A focused, durable goal gives the Dot stable direction across many work sessions.
Set Working Instructions and Autonomy
Describe priorities, boundaries, and how independently the Dot should act, including when it should seek your input or approval.
Attach Context and Files
Add project documents and reference material so the Dot has the background it needs from the start.
Assign the First Task and Review Activity
Give the Dot a concrete task connected to its goal, then monitor progress through its activity dashboard.
Dots access is plan-dependent and tied to the current rollout. Desktop web and desktop app are the primary supported surfaces, mobile access varies by account and rollout stage, and workspace administrators can restrict member access. Check your plan and workspace settings before expecting full functionality.
| Platform | Status | Notes |
|---|---|---|
| Desktop web | Supported | Full create, configure, and manage experience |
| Desktop app | Supported | Available to users included in the rollout |
| Mobile | Rollout-dependent | Varies by account, platform, and rollout stage |
| Enterprise workspaces | Controlled rollout | Admin-governed availability and tool access |
| Business workspaces | Admin-managed | Administrators control member access |
The Cloud Computer and Connected Apps
The cloud computer is the feature that most clearly separates Dots from ordinary ChatGPT conversations. Each Dot operates its own remote machine with a browser, so multi-step web work continues even when you close your laptop.
Independent Execution
- Cloud work runs without your local machine
- Suited to long, multi-step workflows
- Keeps running while you do other things
Inspectable Sessions
- Open the computer view to see current state
- Understand what actions are taking place
- Step in when manual review helps
Cloud vs Local Access
- Cloud computer is built-in per Dot
- Local computer access is a separate, optional capability
- Remote agent work stays distinct from your device
Connected apps expand what a Dot can reach. Connections follow the permissions granted by you or your workspace, and the 4,000+ app figure from launch materials makes this one of the most extensible parts of the product.
| Integration | Category | What a Dot Can Do |
|---|---|---|
| Slack | Team communication | Use permitted channel context in workflows |
| Communication | Work with approved messages and follow-ups | |
| Files | Knowledge and context | Use attached documents as project background |
| Workspace apps | Productivity | Extend workflows with external information and actions |
| Notification channels | Updates | Exchange task info and results across channels |
Begin with one or two connections tied to a specific goal, verify the Dot behaves as expected in its activity dashboard, and only then broaden permissions. This keeps early automation predictable and easy to audit.
Use Cases, Scheduled Tasks, and Permissions
The strongest Dots use cases share one trait: the work benefits from continuity rather than a single prompt.
Ongoing Research
- Evolving topic over multiple sessions
- Collects, organizes, updates findings
- Surfaces new material proactively
Calendar and Reminders
- Reviews upcoming events
- Recurring schedule summaries
- Timed follow-ups and reminders
Recurring Monitoring
- Watches information that changes over time
- Flags meaningful updates
- Reports on a schedule
Scheduled tasks follow a simple loop: define what should happen and when, let the Dot run recurring checks, receive proactive updates when work finishes, and review active, scheduled, and completed items in the task management view.
Permissions define the boundaries, and the control model is layered:
| Control Layer | Scope | What It Governs |
|---|---|---|
| Connected app permissions | User and workspace | Which services a Dot may access |
| Cloud computer access | Dot capability | Browser-based, multi-step task execution |
| Local computer access | Optional user capability | Interaction with your own device, kept separate |
| Autonomy settings | User configuration | How independently the Dot acts between interactions |
| Workspace availability | Administrator | Whether members can use Dots at all |
| Enterprise controls | Enterprise admin | Organization-wide restrictions and governance |
A focused launch plan produces better results than an open-ended one. Use the checklist below to get a Dot productive without over-permissioning it.
First-Week Dot Milestones:
- Create one Dot with a single, well-defined goal
- Attach relevant files and context before the first task
- Connect only the apps the goal requires
- Set autonomy boundaries and approval triggers
- Review the activity dashboard daily and adjust instructions
FAQ
Q: What was announced about OpenAI Dots at DevDay?
At DevDay on September 29, 2026, OpenAI introduced Dots as always-on AI agents powered by GPT-6 Astra. Each Dot has its own cloud computer and browser, connects to 4,000+ apps, and follows up through ChatGPT, SMS, email, and Slack. OpenAI also added a dedicated Dots section to its official safety documentation.
Q: Do I need a specific ChatGPT plan to use Dots?
Access is plan-dependent and tied to the current rollout. Desktop web and the desktop app are the primary supported surfaces, mobile access varies by rollout stage, and workspace administrators can control whether members can use Dots. Check your plan and workspace settings for current eligibility.
Q: How is a Dot different from a normal ChatGPT conversation?
A Dot is organized around a persistent goal rather than a one-off prompt. It keeps working between your interactions, uses its dedicated cloud computer for multi-step browser tasks, runs scheduled and recurring work, and can proactively send updates through channels like Slack and email.
Q: Can I control what my Dot is allowed to access?
Yes. Permissions cover connected apps, cloud computer use, optional local computer access, and autonomy levels. Workspace administrators and Enterprise admins can apply additional restrictions and governance on top of individual settings.