OpenAI Operator

Overview

OpenAI Operator was OpenAI’s first consumer computer-using agent: a research-preview product that controlled a remote browser (click, type, scroll) to complete multi-step web tasks for you. It launched on January 23, 2025 at operator.chatgpt.com, initially for ChatGPT Pro users in the U.S., powered by the Computer-Using Agent (CUA) model—GPT‑4o vision plus reinforcement learning on GUIs.

As of mid‑2026, Operator is not a separate product. On July 17, 2025, OpenAI folded Operator (and deep research) into ChatGPT agent (“agent mode”) inside the main ChatGPT composer. The standalone Operator site was shut down afterward (commonly dated August 31, 2025). Help Center docs still state that Operator functionality lives under agent mode and that the Operator website is no longer accessible.

In July 2026, OpenAI’s product surface shifted again: Help Center notes that the named ChatGPT agent experience is being superseded by ChatGPT Work for longer multi-step research and finished deliverables, with cloud browser for supported public-web workflows. So “Operator” is a historical brand; the practical path for the same job class is ChatGPT’s agentic/Work + browser stack (and, for developers, computer-use tooling on the OpenAI API / Agents SDK where exposed).

Key features

Features below cover the original Operator research preview and the agent capabilities that inherited them. Exact UI labels change as OpenAI consolidates modes.

• Remote visual browser (CUA) — Sees the page via screenshots; acts with virtual mouse/keyboard. No custom site API required for many flows—same interface humans use.
• Multi-step web tasks — Classic demos: forms, grocery orders, reservations, shopping research, meme tools, travel browsing. Success varies widely by site complexity (CAPTCHAs, fragile JS checkouts).
• ChatGPT agent unified toolbox (mid‑2025+) — Combined Operator-style browsing with deep research synthesis, a terminal (limited network) for analysis and deliverables (slides/spreadsheets), text browser for lighter navigation, and direct API paths where useful.
• Connectors / apps — Pull context from connected apps (e.g. Gmail, calendars, GitHub-class tools) for prep work; consequential actions on live sites still expected user confirmation / takeover.
• Takeover mode — Agent pauses for sensitive inputs (logins, payment fields). While you control the browser, OpenAI documents that screenshots are not captured for those entries—reducing credential exposure in agent history.
• Confirmations & watch mode — Designed to ask before high-impact actions (submit order, send email) and require closer supervision on sensitive categories (email, finance).
• Task limitations / refusals — Trained to decline some high-stakes categories (e.g. certain banking flows, hiring decisions) and to refuse disallowed content under usage policies.
• Custom instructions & saved prompts (Operator-era) — Site-specific preferences (airlines, shopping defaults) and reusable homepage prompts for recurring chores.
• Parallel / scheduled work — Operator allowed multiple concurrent conversations; agent/Work paths later added scheduling and recurring tasks (counts against usage where agent invocations apply).
• On-screen narration — Agent mode showed step-by-step what it was doing so you could interrupt, re-steer, or stop and keep partial results.
• Safety layers against prompt injection — Monitor model, cautious navigation, detection pipelines; still not zero risk when connectors or logged-in sessions expand the blast radius.
• Cloud browser (Work-era, 2026) — Current Help docs describe a remote browser for supported public tasks when apps cannot finish the job. At launch: no credential entry, no autofill/password managers, no payments; task stops if sign-in or payment is required.
• Developer lineage — CUA research and later Agents SDK / computer-use style tools extend the same “pixels + mouse/keyboard” idea beyond the consumer Operator UI.

Pricing

Operator never had a standalone SKU. Access always rode on ChatGPT plan pricing. Historical and current framing:

Era	How you paid	Access notes
Operator preview (Jan 2025)	ChatGPT Pro (then ~$200/mo)	U.S. Pro first at operator.chatgpt.com; research preview
ChatGPT agent (from Jul 17, 2025)	Plus / Pro / Team / later Business, Enterprise, Edu	Agent mode in ChatGPT tools dropdown; Free excluded
Work + cloud browser (mid‑2026 rollout)	Paid tiers (cloud browser: paid except Free & Go, per Help)	Work for deliverables; cloud browser for public web tasks

Individual ChatGPT list prices (USD, mid‑2026 public references): Free $0; Go ~$8/mo; Plus ~$20/mo; Pro from ~$100/mo (5× usage) or ~$200/mo (20× usage). Business often ~$20/user/mo annual ($25 monthly). Enterprise custom. Regional pages may show local currency (e.g. SGD); always confirm on chatgpt.com/pricing.

Agent-mode message caps (OpenAI Help, while agent mode was documented):

• Plus: 40 agent messages/month
• Pro: 400 agent messages/month
• Business & Enterprise: 40/month (or 30 credits per message under flexible pricing)

Only the initial user-initiated agent request counted toward the limit; intermediate clarifications/auth steps did not. Concurrent tasks were rate-limited. Scheduled agent runs also counted.

What this means in practice: Plus was fine for occasional agent experiments; Pro made heavy multi-step browsing realistic. Early Operator-only Pro exclusivity left many $20 Plus users cold—community write-ups frequently called pure Operator-for-$200 a poor deal until agent mode broadened access.

Limits & gotchas

• Product name churn — Operator → ChatGPT agent → Work / cloud browser. Blog posts, tutorials, and help articles lag; always check the live ChatGPT UI and Help Center.
• Reliability on hard sites — CUA posted strong early benchmarks (e.g. WebVoyager ~87%, WebArena ~58%, OSWorld ~38% at Operator launch) but real checkouts, CAPTCHAs, multi-factor flows, and dense calendars still fail often. Early reviews called Operator “clunky” and not worth a Pro upgrade alone.
• Cloud browser is stricter at launch (2026) — Public pages only; no sign-in, no payments. Many classic Operator demos (logged-in grocery carts, paid bookings) are out of scope unless completed by you or via a connected app path.
• Prompt injection risk — Hidden instructions on web pages can try to redirect an agent with connectors or active sessions. OpenAI layers mitigations, but users must disable unused apps, avoid vague “handle my inbox” prompts, and stop suspicious runs.
• Screenshot & data retention — Visual browsing uses screenshots stored with chat history until you delete the chat (deletion propagates on OpenAI’s stated timelines). Consumer training opt-out lives under Data Controls; Business/Enterprise default: no training on business data.
• Cookies persist — Remote browser convenience can leave session cookies; clear browsing data in settings after sensitive work.
• Geographic / workspace gates — Rollouts were region- and plan-gated (EU delays early on). Enterprise owners can toggle agent off (default OFF historically), apply RBAC, and request domain blocklists.
• Not full OS control for consumers — Operator/agent browser is not a general desktop RPA suite. Desktop ChatGPT Work can go further with local files/apps where permitted; that is a different surface than the original Operator site.
• Website blocks — Sites may block automated access; OpenAI may refuse categories for safety/compliance. CAPTCHA often ends the run.
• Human still owns liability — Confirmations help, but wrong carts, wrong forms, or misread policies remain user responsibility.

Community sentiment

Across Reddit (r/ChatGPT, r/ChatGPTPro), tech press (TechCrunch, CNBC), and hands-on blogs from 2025–2026, Operator is remembered as a landmark demo that under-delivered as a daily driver in its first months.

Praise: First major OpenAI product that “used the web like a human”; clear takeover/confirmation UX; partner demos (Instacart, OpenTable, travel/commerce brands); later agent mode’s fusion with deep research and file deliverables felt more useful than pure clicking.

Criticism: Slow, fragile on complex UIs; CAPTCHAs and logins interrupt autonomy; $200 Pro gate at launch felt extractive for a research preview; Medium/YouTube reviews with titles like “hanging up on Operator” reflected buyer’s remorse when agents stalled on basic flows. After the fold-in, users still hit 40 vs 400 message cliffs and greying-out agent UI when limits or project context got messy.

By 2026, people searching “Operator alternatives” usually want either (1) a still-working ChatGPT browser agent path, (2) Anthropic-style computer use APIs, or (3) dedicated agent products (Manus, Perplexity browser agents, open browser-use stacks) with different reliability and pricing tradeoffs.

Who should use it

• ChatGPT Plus/Pro users who want occasional multi-step web research, public-page lookups, or draft bookings—with time to supervise and finish payments themselves.
• Knowledge workers using agent/Work for competitor briefs, spreadsheet/slide deliverables, and connector-backed prep (calendar + news), not unattended banking.
• Teams on Business/Enterprise that need RBAC, training opt-outs, and domain blocks—if admins enable agentic features.
• Developers building agents who care about CUA lineage and OpenAI’s computer-use / Agents SDK surfaces more than the retired Operator domain.
• Less ideal: Anyone needing reliable unattended purchases; regulated workflows without human-in-the-loop; free-tier only users; users who refuse to monitor screenshots and confirmations.

Alternatives

• Manus — General cloud computer agent (research, browser, slides/apps) with its own credit tiers; often compared head-to-head with Operator-era demos.
• ChatGPT — Current home of Work, cloud browser, and residual agent features; start here instead of the dead Operator URL.
• Claude / computer-use stacks — Anthropic’s computer-use direction is API/product competitive for GUI agents; different UX and trust model.
• Perplexity — Strong research/browsing product line; agentic browser experiments (e.g. Comet-class tools) attract users who bounced from Operator reliability.
• OpenAI Codex — When the “agent” job is software engineering, not web shopping—Codex is the coding-specialized sibling surface.
• n8n — Deterministic automation with APIs/webhooks when you need reliable, auditable workflows rather than vision-based clicking.
• Open-source browser-use / Playwright agent frameworks — Self-hosted control, bring-your-own model, ops burden on you.

Verdict

OpenAI Operator mattered historically more than it matters as a product name in 2026. It introduced CUA-style browser agency to a mass ChatGPT audience, then was correctly absorbed into ChatGPT so context, research, and action could share one thread. The standalone Operator site is gone; agent mode’s monthly caps and reliability gaps taught that “AI that books stuff for you” still needs a human co-pilot; July 2026’s move toward ChatGPT Work and a more constrained cloud browser is another honesty pass on what is safe to automate.

Bottom line: Do not buy a plan “for Operator”—that SKU is dead. Buy ChatGPT Plus or Pro if you already want the broader product and will use supervised multi-step work sparingly. For mission-critical automation, prefer API/connector workflows or dedicated RPA. For exploratory agent demos, try Work/cloud browser and keep your hand on the takeover control—the feature is real, the autonomy ceiling is still low, and the branding will likely change again.