OpenAI launches Dots, always-on AI agents rivalling Meta Muse

What happened

OpenAI has introduced Dots, a new class of always-on AI agents designed to work continuously in the background rather than waiting for a user prompt. According to The Decoder, Dots run on dedicated cloud infrastructure and can independently carry out tasks such as fixing software bugs or chasing up unpaid invoices, in some cases acting before a human has explicitly asked.

Users interact with Dots through existing workplace channels, including ChatGPT, Slack and Microsoft Teams, rather than a standalone interface. When not actively directed, the agents continue operating with read-only access to relevant systems, scanning for opportunities to be useful without being able to make changes until instructed. The launch positions OpenAI directly against Meta, which has been developing its own persistent agent system, Muse.

Why it matters

This marks a shift from AI assistants that respond to requests towards agents that operate continuously and proactively across an organisation's tools. For enterprises pursuing digital transformation, the significance lies in what becomes possible when software can monitor workflows, spot issues and take limited action without a person initiating every step.

The read-only default while idle is a notable design choice: it signals that OpenAI is building in guardrails to limit autonomous action until a human authorises it, an approach likely to shape how other vendors calibrate the trust and control trade-offs in agentic AI.

The Renascence take

The real story here isn't the novelty of an "always-on" agent — it's the behavioural shift this forces inside organisations. Employees have spent years being trained to prompt AI; now they must learn to supervise it, deciding when silence from a background agent means "all is fine" versus "nothing was checked." That ambiguity is where operational risk, and opportunity, actually lives.

Most commentary will focus on the productivity upside of agents that catch problems before anyone notices. What gets missed is the trust design problem: a system that quietly watches and occasionally intervenes needs to make its own confidence and limits legible to the humans relying on it, or it will either be over-trusted into blind spots or under-trusted into irrelevance. Read-only-by-default is a sensible starting posture, but the decisive factor will be how clearly Dots communicates what it noticed, what it didn't, and why it chose to act or wait — that's the service-design layer that determines whether always-on agents earn a permanent seat in the workflow or get quietly switched off after the first bad surprise.