AgentComparison
OpenAI · product · personal assistant

OpenAI dots

OpenAI's personal assistant that uses plugins and shared ChatGPT memory.

Group: Personal agents you message

OpenAI dots uses shared ChatGPT/plugin permissions and memory for connected work, proactive private research, and permitted local or cloud computer tasks. Its FAQ distinguishes read-only proactive research, action approvals, Custom Rules and takeover, while Enterprise workspace controls separately govern access and messaging.

Documentation researched, not testedChecked 23 October 2026Vendor documentation, not a test

The decision in plain English

Check plan, region and the 18 November transition before choosing dots. Current OpenAI docs list Pro rollout outside the EEA, Switzerland and UK, Business Premium in supported regions subject to workspace eligibility, and eligible Enterprise/Edu/Healthcare access during a 4-18 November admin preview. Enterprise preview is free through 18 November; billing starts then for enabled dots, with delegated Work/Codex billed separately. We have not verified exact dollar rates or account signup eligibility. Access, action permissions, retained data and independent tasks are separate controls.

Best fit

Personal connected-app work with shared ChatGPT context.

Poor fit

A user needing per-memory inspection and deletion.

Documented capabilities

Vendor statements, not verified task outcomes.

  • Shared connections: Plugin permissions apply across dots, ChatGPT, Work and Codex; enabling dots does not grant all apps. Manage actual plugin scopes separately. Source · checked 2026-10-09
  • Proactive research: Permitted sources can feed private notes, but research tools cannot directly send messages, change plugin content or control browser/computer. Follow-up actions use normal authorization. Source · checked 2026-10-09
  • Local device access: Connect the device and grant camera/mic/screen access in device settings. Enterprise local command/file access additionally needs admin enablement; app must be open and device online. Source · checked 2026-10-09
  • Cloud computer: Browser, network, desktop and password-manager capabilities are separately managed. Cloud does not inherit local VPN, sign-ins or device policies. Source · checked 2026-10-09
  • Rules and approvals: Custom Rules support boundaries but cannot remove core safeguards/Autoreview. Sensitive transfers/password changes require takeover; some messages and purchases accept specifically scoped advance approval. Source · checked 2026-10-09
  • Messaging channels: the desktop app connects messaging channels such as Slack or texting; dots are not supported on mobile web. Source · checked 2026-10-29

Permissions and human control

  • Plugin permissions are shared across dots, ChatGPT, ChatGPT Work and Codex.
  • Custom Rules add boundaries but cannot override core safeguards. Sensitive actions can require takeover or approval; scoped advance approval is supported for some actions.
  • Enterprise access is off by default during the admin preview through 18 November, then available by default unless admin opts out; app authorization and local/cloud permissions are separate.
  • Only owner instructions direct an Enterprise dot; other people's Slack DMs/mentions do not start work. Posts in channels are visible to members.
  • Proactive research tools cannot directly message others, write through plugins or control browser/computer. A follow-up action still needs normal authorization; Custom Rules cannot remove this restriction.
  • Password changes and money transfers require takeover. Saved-card purchases and recurring messages may use narrowly scoped advance approval, not open-ended ongoing authority.

Documented controls do not prove that an agent always follows them.

Limits and open questions

  • Individual dot memories cannot currently be viewed or edited
  • Disconnecting services does not delete retained context
  • Phone messaging is unavailable for Enterprise at launch, according to workspace docs.

Privacy and security

OpenAI says content is encrypted in transit and at rest. Disconnecting stops new plugin access, not deletion of retained context. Delete the dot to delete its context; separately stored files, conversations and ChatGPT Memory remain separate. Individual dot memories cannot currently be viewed or edited. Business, Enterprise and Edu data is not used for training by default; personal plans use the Improve the model for everyone setting. Human safety review can still occur. Vendor statements, not an audit. Proactive notes are not directly used for training, but information brought into eligible conversations/tasks may be, depending on settings. Turning off shared Memory does not erase received context. Supported secure-login forms differ from passwords sent in chat/plugin content.

Feature-by-feature: what is documented and what is not

Official sources checked 23 October 2026. A documented feature is a vendor statement, not proof of success.

FeatureEvidence statusDetail and limit
Shared connectionsDocumentedPlugin permissions apply across dots, ChatGPT, Work and Codex; enabling dots does not grant all apps. Manage actual plugin scopes separately. Source
Proactive researchRead/notes onlyPermitted sources can feed private notes, but research tools cannot directly send messages, change plugin content or control browser/computer. Follow-up actions use normal authorization. Source
Local device accessSeparate permissionConnect the device and grant camera/mic/screen access in device settings. Enterprise local command/file access additionally needs admin enablement; app must be open and device online. Source
Cloud computerDistinct controlsBrowser, network, desktop and password-manager capabilities are separately managed. Cloud does not inherit local VPN, sign-ins or device policies. Source
Rules and approvalsNot universal ask-firstCustom Rules support boundaries but cannot remove core safeguards/Autoreview. Sensitive transfers/password changes require takeover; some messages and purchases accept specifically scoped advance approval. Source
MemoryDeletion distinctionShares ChatGPT memories/context; turning Memory off stops sharing, not existing context. Individual dot memories cannot be inspected/edited/deleted individually. Source
Delete/disconnectDifferent effectsDisconnect stops new access. Delete dot removes its own context; files, Codex threads, ChatGPT conversations and Memory remain separate. Source
TrainingPlan/setting-dependentPersonal plans use Improve the model for everyone; Business/Enterprise/Edu not trained by default. Proactive notes are not directly trained on, but their content in eligible work may be. Source
Work messagingEnterprise caveatSupported Slack/Teams setup needs admin grants and member connection; Slack may require app approval. Only owner directs dot; others' mentions/DMs do not start work. Phone iMessage/RCS/WhatsApp unavailable at Enterprise launch. Source
Credentials and purchasesSupported-flow limitsSecure login form keeps supported credentials from the model; chat/plugin passwords are not covered. Auth checks may need takeover; saved-merchant-card purchases require scoped approval. Source
Price and eligibilityPlan/region dependentPro and Business Premium access is plan/region dependent; eligible Enterprise free preview through 18 November, then billing for enabled dots. Delegated Work/Codex separate. Exact dollar rates unverified. Source

How to start with OpenAI dots narrowly

  1. Confirm your actual account has dots access; published Enterprise guidance is not proof of personal-plan eligibility or a free standalone service.
  2. Workspace admins: review effective roles and Use dots access before the 18 November default-enable and Enterprise billing transition, plus local/cloud permissions and app authorizations. Do not assume enabled access creates a dot or disabling access stops every independent task.
  3. Review shared plugin access in ChatGPT and set narrow Custom Rules before delegating a task. Select a draft/read-only task first.
  4. If using a computer, connect it and grant only necessary device permissions; distinguish local access from cloud sessions and their separate sign-ins.
  5. Review Activity View and stop/change instructions as needed. Before removing access, separately consider dot context, stored files/conversations and ChatGPT Memory; disconnecting alone is not deletion.

Official product/setup source. These are documentation-based steps, not a hands-on setup test.

Common questions about OpenAI dots

What is OpenAI dots for?

Personal connected-app work with shared ChatGPT context. The vendor describes it as: OpenAI dots uses shared ChatGPT/plugin permissions and memory for connected work, proactive private research, and permitted local or cloud computer tasks. Its FAQ distinguishes read-only proactive research, action approvals, Custom Rules and takeover, while Enterprise workspace controls separately govern access and messaging.

Who should look elsewhere?

A user needing per-memory inspection and deletion.

How much does OpenAI dots cost?

Current getting-started docs describe eligible Enterprise flat-rate or scaled-consumption billing. Free preview 4-18 November 2026; billing starts 18 November for enabled dots. Work/Codex delegated threads billed separately at standard rates. No exact dollar rates established here. Pro and Business Premium access is listed separately; no universal free standalone service claimed.

What can it access and what needs my approval?

Plugin permissions are shared across dots, ChatGPT, ChatGPT Work and Codex. Custom Rules add boundaries but cannot override core safeguards. Sensitive actions can require takeover or approval; scoped advance approval is supported for some actions. Enterprise access is off by default during the admin preview through 18 November, then available by default unless admin opts out; app authorization and local/cloud permissions are separate. Only owner instructions direct an Enterprise dot; other people's Slack DMs/mentions do not start work. Posts in channels are visible to members. Proactive research tools cannot directly message others, write through plugins or control browser/computer. A follow-up action still needs normal authorization; Custom Rules cannot remove this restriction. Password changes and money transfers require takeover. Saved-card purchases and recurring messages may use narrowly scoped advance approval, not open-ended ongoing authority.

What happens to my data?

OpenAI says content is encrypted in transit and at rest. Disconnecting stops new plugin access, not deletion of retained context. Delete the dot to delete its context; separately stored files, conversations and ChatGPT Memory remain separate. Individual dot memories cannot currently be viewed or edited. Business, Enterprise and Edu data is not used for training by default; personal plans use the Improve the model for everyone setting. Human safety review can still occur. Vendor statements, not an audit. Proactive notes are not directly used for training, but information brought into eligible conversations/tasks may be, depending on settings. Turning off shared Memory does not erase received context. Supported secure-login forms differ from passwords sent in chat/plugin content.

What changes for workplace dots on 18 November 2026?

OpenAI documents eligible Enterprise/Edu/Healthcare admin preview until 18 November, then default availability unless admins opt out. Its getting-started page says Enterprise billing begins on that date for enabled dots; delegated Work/Codex usage is separate. Admin pause or access removal does not delete data or prove all independent work stopped. Review effective roles, cost tiers, separate tasks and residency eligibility. Vendor documentation, not our test.

Source · Source

Has AgentComparison tested it?

No. This record is built from the vendor's own documentation, checked 2026-10-23. Vendor claims are attributed, not confirmed.

How to evaluate OpenAI dots yourself

  1. Pick one low-risk task that matches its documented capabilities: shared connections: plugin permissions apply across dots, chatgpt, work and codex; enabling dots does not grant all apps. manage actual plugin scopes separately..
  2. Write the expected output and what counts as failure before you start.
  3. Connect the minimum access needed, and check approval settings first.
  4. Run it twice and compare, then review every action it took.
  5. Check cost after any free allowance. Unknown price is not free.

Related

Documented use cases: Personal email, calendar and reminders.

Sources and history

Change history

Documentation overview expanded with current pricing/access sources. No hands-on results claimed.

Report a correction