OpenAI Dots proactive research is the read-only mode that lets OpenAI's new always-on agents check permitted connected sources for updates before a user prompts them, while blocking messages, content edits, browser control, and computer control. OpenAI announced Dots at DevDay 2026 on September 29, according to Adweek and Wired. Search Engine Journal reported on September 30 that OpenAI's help pages place tighter limits on unattended work than the launch demos suggest.
The change is that ChatGPT is getting persistent agents that can retain context, connect to apps, run scheduled checks, and work across conversations. Adweek reported that Dots are available to ChatGPT Pro and Business Premium users, with each user initially getting one agent, and that OpenAI plans to raise that limit. Search Engine Journal reported a narrower rollout detail: Pro users in various markets are included, the European Economic Area, Switzerland, and the UK are excluded, Business Premium users get access across supported ChatGPT regions, and Enterprise, Edu, and Healthcare workspaces can try an off-by-default beta.
How OpenAI Dots proactive research works
OpenAI Dots proactive research works by letting a dot read permitted connected sources and save private notes without taking direct actions. Search Engine Journal quotes OpenAI's help content: "Your dot can also look for useful updates before you make a request. This is called proactive research. It can read information from permitted connected sources and save private notes, but its research tools cannot directly: Send messages to other people. Change content through plugins. Control a browser or computer."
Scheduled checks are separate from proactive research, even though both can appear in the same dot conversation. Search Engine Journal reported that scheduled work can run one-time or recurring tasks, monitor changes, and respond to supported events from Gmail, Slack, or GitHub, while proactive research is the mode that runs before a new prompt. The practical distinction is permissioned action: a scheduled task may be assigned as work, but the unattended proactive mode remains read-only under the help-page limits.
Dots use the plugin connections a user has already set up, and those permissions are shared across dots, ChatGPT, ChatGPT Work, and Codex, according to Search Engine Journal. The same report says the plugin catalog has more than 4,000 apps, and disconnecting an app stops new access but does not erase what a dot has already saved. Users currently cannot view or edit individual dot memories; resetting a dot deletes conversations, saved memories, and scheduled tasks.
Where the reporting differs
The reporting differs most on how broadly Dots browse and how readers should understand "always on." Wired wrote that Dots "constantly crawl the web" to complete assigned tasks, while Search Engine Journal focused on OpenAI's help pages and said proactive research checks permitted connected sources. Those descriptions are not identical. The supported claim is narrower for unattended work: proactive research reads allowed sources and saves notes.
Adweek reported that Dots can work across connected apps, run several projects at once, learn user preferences, and use their own cloud computer and browser. It also quoted OpenAI saying, "Dots can do nearly anything using their own cloud computer, their own browser, and the apps you've connected." That sentence describes assigned agent work, not the proactive research limits quoted in OpenAI's help content by Search Engine Journal.
The evidence is thin on analytics, SEO platforms, and search console access. Search Engine Journal says that, as of September 30, the three Dots help pages it reviewed did not mention an analytics platform or search platform, and the examples included a calendar, Slack, and a personal email account. No supplied source says Dots can read Google Search Console, Google Analytics 4, Google Ads, Bing Webmaster Tools, Screaming Frog, Semrush, Ahrefs, or a rank-tracking platform through an official integration.
What marketers should check first
Marketing and search teams should treat Dots as a permissions and monitoring change before they treat it as a productivity feature. The first audit is not a content workflow. It is the set of apps a dot can read, the Custom Rules that gate action, the scheduled tasks that run without a fresh conversation, and the Enterprise admin settings that allow cloud browser, cloud network access, and cloud computer use.
| Check | Where to look | Why it matters |
|---|---|---|
| Connected apps | ChatGPT plugin connections shared with dots, ChatGPT, ChatGPT Work, and Codex | A dot can use existing permissions, and disconnecting an app does not erase saved dot memory. |
| Custom Rules | User rules for independent dot actions | Rules can allow, gate, or block actions, but they cannot override proactive research restrictions. |
| Scheduled tasks | One-time and recurring dot tasks in the conversation | Scheduled monitoring can keep context between conversations and differs from read-only proactive research. |
| Enterprise controls | Admin settings for cloud browser use, cloud network access, and cloud computer use | Admins can enable or disable these capabilities individually for assigned work. |
Teams should document which accounts are connected before a dot is assigned competitor monitoring, inbox review, calendar scanning, or campaign checks. If a dot is reset, Search Engine Journal says its conversations, saved memories, and scheduled tasks are deleted. If an app is disconnected, the same report says new access stops but previously saved dot memory remains, which makes reset behavior a real governance control rather than a cleanup detail.
What Dots mean for search visibility
For search visibility, the supported impact is monitoring, not ranking manipulation. A dot may read permitted sources, notice that a competitor page changed, preserve context from earlier checks, and report the change later. No source says Dots modify websites, influence Google rankings, submit indexing requests, or change ad bids. Any use in SEO or paid media depends on the connected apps OpenAI exposes and the permissions a team grants.
The inference for AI answers and citations is narrower but useful. If agents like Dots become routine research tools, they will repeatedly read the sources users permit and the public pages they are assigned to inspect during active work. That makes source clarity, stable URLs, visible dates, and checkable claims more important for pages that buyers, analysts, or internal teams ask agents to compare. The evidence does not show a direct ranking factor.
R1, a post in r/OpenAI on October 5, shows how quickly practitioners are testing agent-mediated research outside OpenAI. The Dot Commons post describes an independent community experiment where people copy a prompt to their Dot or another AI agent with internet access, assign a manageable research task, and return sources, methods, uncertainties, and contributor credit to a shared hub. The post also says it is not an OpenAI project or medical advice, so it is a signal of experimentation, not proof of Dots performance.
What happens next for Dots
The next thing to watch is access expansion and which work apps appear in the plugin catalog for Dots. OpenAI told users, according to Search Engine Journal, that they will later be able to add more dots and scale each one's output, including speed or monthly work capacity. Wired reported that Pro users start with one Dot and that OpenAI is expected to add support for controlling multiple agents at the same time.
The operational trigger is the Enterprise beta moving from off by default to broader deployment, or OpenAI documenting analytics, SEO, advertising, or webmaster integrations in Dots help pages. Until that changes, the supported use case for search and marketing teams is controlled monitoring across connected sources, with proactive research limited to read-only checks and saved notes.