MODEL SIGNAL
Dots (OpenAI)
Always-on, GPT-6 Astra-powered agents built for asynchronous execution across ChatGPT, Slack, and Microsoft Teams.
Bottom line
OpenAI has introduced Dots as always-on agents designed to operate beyond single conversation turns. Powered by GPT-6 Astra, they are equipped with a native "cloud computer" infrastructure to browse, analyze data, create files, and run tools via connections to over 4,000 applications.
Signal
The defining technical feature of Dots is their asynchronous posture. According to the reconciled model profile, these agents maintain memory and recent conversation context to continue making progress toward goals between active user interactions. They are designed to operate across multiple interfaces, extending access beyond the core ChatGPT environment to include Slack and Microsoft Teams. Rather than functioning strictly as prompt-and-response models, they are built to take on ongoing responsibilities.
Noise
Phrases like "always-on" and "ongoing responsibility" are broad marketing terms that require rigorous operator validation in production environments. While the profile notes integrations with external platforms like Slack and Teams, the practical limitations—such as context window ceilings, long-running execution timeouts, and multi-turn failure rates—are not specified in the primary announcement.
What is not settled
The exact timeline and specific regional constraints of the release remain undefined, described only as "rolling availability for Pro and Business Premium in eligible markets." Furthermore, while the profile states that Enterprise, Edu, and Healthcare environments have beta access when enabled by a workspace administrator, the specific administrative controls, compliance boundaries, and rollout mechanics for those workspaces are not detailed in the primary source.
Where it fits
Dots are positioned for persistent workflows that require continuous context. Based on the confirmed features—specifically the cloud computer, memory, and access to thousands of app plugins—the directional signal suggests these agents fit best in roles requiring background research, prolonged data analysis, or asynchronous task execution where traditional stateless chat models would lose context.
Operator implications
The operator read here is significant: by natively providing a "cloud computer" and integrating thousands of external tools directly into the agent, the emerging pattern suggests OpenAI is moving toward providing a managed agent-orchestration layer out of the box. If these provider facts hold, the likely implication is that enterprises may eventually evaluate whether to offload operations, data monitoring, and continuous research to this first-party infrastructure rather than building and maintaining custom orchestration pipelines on top of raw APIs.