An agent that continues between conversations
OpenAI's DevDay 2026 recap introduced dots as always-on agents designed to take on ongoing responsibilities. The announcement describes agents that keep working on a person's behalf rather than waiting for every individual prompt. OpenAI's ChatGPT release notes likewise describe dots as making progress between conversations.
This changes the central question for users. With a conventional chat interaction, the immediate concern is whether the next answer is helpful. With ongoing delegated work, the concern becomes whether the system is pursuing the right objective over time. That requires more explicit expectations about scope, updates, permissions, and the point at which a person should become involved.
Availability is narrower than the headline
The DevDay recap says dots are available on Pro and Business Premium in eligible markets. That is not a statement of universal availability across every subscription, country, or workspace. Anyone planning a deployment should verify the current eligibility and controls in their account before designing a process around the feature.
It is also important to distinguish a product announcement from a measured business outcome. The description establishes the intended operating pattern: ongoing responsibility and continued work. It does not establish that every user will save a particular number of hours, or that the agent can safely perform every activity associated with a job. Those conclusions require workload-specific evidence.
Delegate an outcome, not an unlimited mandate
Consider a hypothetical weekly competitor briefing. A useful assignment would specify which companies to watch, which sources are acceptable, how often to report, and which changes deserve immediate attention. It would also state that the agent must not contact those companies or purchase access without authorization.
That level of detail is more valuable than asking an agent to keep an eye on the market. Ongoing work creates opportunities for scope drift: a reasonable first step can lead to a broader action that the user never intended. Clear boundaries make the difference between proactive assistance and an open-ended mandate that becomes difficult to supervise.
Design updates around human attention
An always-on agent should not create an always-on interruption problem. For any deployment, users should decide which results belong in a scheduled digest and which require an urgent notification. A routine source update and a blocked task are different events, and the reporting process should reflect that difference.
Completion reports should distinguish work actually performed from work planned or attempted. If a source could not be accessed, the agent should say so rather than quietly extrapolating from older material. A concise record of actions, evidence, and unresolved issues makes the continuing workflow reviewable without requiring the user to replay every intermediate step.
The operational question is controlled persistence
Persistence can be useful when a task genuinely benefits from monitoring or repeated follow-through. It is less compelling when the underlying objective is vague or the information sources are unreliable. Before delegating ongoing work, define what success looks like and when the responsibility should end, pause, or return for approval.
A careful pilot can compare the agent's reports with the existing manual process over several cycles. Track missed developments, false alarms, correction effort, and whether the work remains within scope. The important development in dots is the product shift toward continued responsibility. Whether that becomes useful assistance depends on how clearly the responsibility is defined and how effectively people retain control over consequential actions.
Sources and editorial note
Reporting checked on November 2, 2026. Product descriptions reflect the cited announcements; availability and terms may change. Workflow examples and recommendations are editorial analysis, not independently measured product results.