> ## Content Index
> Fetch the complete content index at: https://analthropic.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# OpenAI gave ChatGPT always-on Dots, a cloud desk, and a warning they still screw up
- URL: https://analthropic.com/archive/openai-dots-always-on-agents-devday/
- Published: 2026-10-01T14:35:43.000Z
- Updated: 2026-10-01T14:35:43.000Z
- Description: Dots promise background agents with plugins and Auto-review. OpenAI still says they can change the wrong file.
- Author: Riste Ristevski
- Tags: #v3-run-analthropic-curated-20260930, #approved

**Technology analysis with satire** // SOURCED REPORTING

Dots promise background agents with plugins and Auto-review. OpenAI still says they can change the wrong file.

You wanted a helper that finishes the tab after you close the laptop. OpenAI answered by renting the work its own cloud desk and leaving the light on.

On September 29, 2026, the company introduced Dots: always-on agents powered by GPT-6 Astra, with app plugins, continuous background work, and a same-day safety memo insisting you remain in control. Honest-X card: what the slide says is sandboxed stamina plus Auto-review. What the decision still requires is a human who actually sets app access, reads Activity View, and stops a polite agent before it moves the wrong file or shares something meant to stay private. The subscription bought persistence. It did not buy omniscience.

OpenAI announced Dots on September 29, 2026 as always-on agents powered by GPT-6 Astra with a cloud computer, app plugins, and background work. It says rollout begins for Pro and Business Premium in eligible markets, with admin-enabled beta for Enterprise, Edu, and Healthcare. OpenAI describes permissions, Custom Rules, Activity View, and Auto-review, and still warns dots can make mistakes.

## ANALTHROPIC’S  
DAILY TOP 5:  
*HOW NOT TO GET* 
*FUCKED BY AI*

### Check if your plan actually grew a Dot

ChatGPT users hearing always-on hype in the feed Open the plan or billing page and the main ChatGPT UI the day you hear about Dots. Note Pro versus Business Premium, whether a Dot entry appears, and any admin or market gate. Save a dated screenshot of the plan badge and the Dot surface. OpenAI describes limited initial availability by plan and eligible market, not universal free access. You have a same-day screenshot showing plan name and whether Dots is offered. UI copy can lag entitlements; a missing button is a clue, not a legal denial letter. [\[S1\]](https://openai.com/index/introducing-dots/?ref=analthropic.com)

### Hand out app keys like house keys

Freelancers connecting mail, calendar, or files Before enabling Dot app access, list each app and the minimum scope you need. Grant only that list. Add Custom Rules that forbid external sends and purchases without your explicit OK. Keep passwords out of chat even if a login flow looks annoying. OpenAI says users choose app access and Custom Rules; secure sign-in is described for supported logins, and mistakes remain possible. A written app-and-scope list sits beside your Dot settings and matches what is enabled. Unsupported apps and broad plugin scopes remain your risk even when Auto-review exists. [\[S1\]](https://openai.com/index/introducing-dots/?ref=analthropic.com) [\[S2\]](https://openai.com/index/how-we-build-safety-security-and-privacy-into-dots/?ref=analthropic.com)

### Admin enabled is not accountability automated

Owners and leads on Business, Enterprise, Edu, or Healthcare paths If an admin can enable Dots beta, write an enablement note first: who flipped it, which workspace, which apps, and who reviews Activity View on a named cadence. Default connectors to least privilege until that note exists. OpenAI gates enterprise-class trial behind admin enablement and still warns agents can change the wrong file or share private information. The enablement note and named reviewer are on file before production connectors go live. Vendor safety architecture language is not a substitute for your access policy. [\[S1\]](https://openai.com/index/introducing-dots/?ref=analthropic.com) [\[S2\]](https://openai.com/index/how-we-build-safety-security-and-privacy-into-dots/?ref=analthropic.com)

### Make Activity View a shift, not a museum

Anyone running a primary Dot on a paid tier For the first two weeks, open Activity View once morning and once evening. Pause anything you do not recognize. Personally review consequential drafts before they reach clients, production files, or money—even if Auto-review already passed. OpenAI pairs progress tracking and auto-review with an explicit statement that dots can still make mistakes and consequential work should be reviewed. Calendar reminders exist and you logged at least one pause, edit, or explicit approval. Monitoring that can pause work only helps when a human actually looks. [\[S1\]](https://openai.com/index/introducing-dots/?ref=analthropic.com) [\[S2\]](https://openai.com/index/how-we-build-safety-security-and-privacy-into-dots/?ref=analthropic.com)

### Put purchases and sharing on a human leash

Small teams tempted to let background agents just handle it Write a three-line desk rule: purchases, credential changes, and external sharing require user approval or handoff—no silent completion. Keep proactive research in read-only tools as described. Reflect the same limits in Custom Rules. OpenAI says purchases and sensitive steps need approval or handoff, background research is restricted to read-only tools, and residual sharing and file-change risks remain. The three-line rule is in the team doc and mirrored in Dot rules you can screenshot. Workflow rules reduce blast radius; they do not certify every plugin path. [\[S2\]](https://openai.com/index/how-we-build-safety-security-and-privacy-into-dots/?ref=analthropic.com)

## OKAY, HERE’S THE ACTUAL SHIT

OKAY, HERE'S THE ACTUAL SHIT.

On September 29, 2026, OpenAI published Introducing dots, describing Dots as always-on agents powered by GPT-6 Astra with their own cloud computer, app plugins, and continuous background work. Availability, as OpenAI states it, begins with Pro and Business Premium users in eligible markets. Enterprise, Edu, and Healthcare users can try a beta when an admin enables it. The first primary dot is included in the plan with an allowance for deeper work. [\[S1\]](https://openai.com/index/introducing-dots/?ref=analthropic.com)

OpenAI says users choose app access, set Custom Rules, follow progress in Activity View, and that dots use auto-review before consequential actions. It also says dots can still make mistakes and that consequential work should be reviewed. [\[S1\]](https://openai.com/index/introducing-dots/?ref=analthropic.com)

A same-day companion post describes each dot in its own cloud workspace with sandboxing, separate action checks called Auto-review, secure sign-in flows that keep passwords out of the model context for supported logins, and monitoring that can pause work. OpenAI says proactive background research is restricted to read-only tools and that purchases or sensitive steps require user approval or handoff. [\[S2\]](https://openai.com/index/how-we-build-safety-security-and-privacy-into-dots/?ref=analthropic.com)

OpenAI states an agent misunderstanding a request could change the wrong file or share information intended to stay private, and that protections will keep improving as it learns from real use. [\[S2\]](https://openai.com/index/how-we-build-safety-security-and-privacy-into-dots/?ref=analthropic.com) These are vendor product and safety narratives, not independent deployment audits.

## WHY AN ACTUAL HUMAN SHOULD CARE

WHY AN ACTUAL HUMAN SHOULD CARE.

Always-on is not a synonym for finished and correct. It means the process can keep moving while you sleep, commute, or ignore the badge. Freelancers and small teams already know the chatbot failure mode: a confident draft that invents a detail, a path, or a send state. Dots productize the next layer—connected apps, background research, a dedicated cloud workspace—while OpenAI itself writes residual risk into the launch packet. [\[S1\]](https://openai.com/index/introducing-dots/?ref=analthropic.com)[\[S2\]](https://openai.com/index/how-we-build-safety-security-and-privacy-into-dots/?ref=analthropic.com)

Observation: plan gates and admin switches mean this is not a universal free upgrade. Analysis: app-access choices, Custom Rules, Activity View, Auto-review, and approval for purchases only matter if a human configures them and keeps watching. Hypothetical example: a dot with files and calendar access helpfully updates the wrong client folder overnight because the instruction was ambiguous—the exact class of mishap OpenAI names. [\[S2\]](https://openai.com/index/how-we-build-safety-security-and-privacy-into-dots/?ref=analthropic.com)

Fair benefit: continuous background work can cut tab-sprawl for people already inside Pro or Business Premium workflows, if permissions stay narrow and review stays real. The invoice still hits a human. The external apology still needs a human throat.

## WHAT WE DON’T KNOW

WHAT WE DON'T KNOW.

We lack independent rates for how often Auto-review catches consequential errors, how eligible markets map to a given account, or what happens when deeper-work allowance is exhausted. [\[S1\]](https://openai.com/index/introducing-dots/?ref=analthropic.com) Control effectiveness and plan limits are OpenAI statements, not third-party measurements. [\[S1\]](https://openai.com/index/introducing-dots/?ref=analthropic.com)[\[S2\]](https://openai.com/index/how-we-build-safety-security-and-privacy-into-dots/?ref=analthropic.com) The supplied packet does not include audits of plugin abuse, sandbox failures, or real-world sharing incidents. OpenAI says protections will improve with use—that is roadmap language, not completed proof. [\[S2\]](https://openai.com/index/how-we-build-safety-security-and-privacy-into-dots/?ref=analthropic.com) Admin default postures, which logins count as supported secure sign-in, and how primary-dot allowances behave for shared teams remain unspecified here. Treat demos as attributed claims until your own tenant logs say otherwise.

## SATIRE: HUMANITY SUPPORT

Issue: Dot finished three tasks overnight and one of them was not mine.

Response: Thank you for contacting Humanity Support. Your agent completed continuous background work inside an approved cloud workspace. Auto-review stamped consequential actions. Residual misfile and overshare classes remain in the documented experience. Please review Activity View, revoke surplus app access, and accept that the apology channel is still staffed by carbon.

Status: Closed — process healthy; human unsettled

Dots are the productization of a simple bargain: pay for an agent that keeps working after your attention quits. OpenAI sold the desk, the plugins, and the control vocabulary on the same day it admitted the roommate can still move the wrong box. That is not a reason to panic-buy tin foil. It is a reason to treat always-on as a permissions problem with a punchline. Configure narrowly, watch Activity View like a shift handover, and keep money and sharing on a human leash. The cloud can stay up late. You still own morning.