ChatGPT Atlas pricing: what to know after its discontinuation

What the old Atlas price actually meant

OpenAI’s October 2025 launch announcement described Atlas browser access across several ChatGPT plans, with agent mode initially previewed for Plus, Pro, and Business. The browser and its AI features were not one universal paid tier.

That explains why older articles call Atlas free while others quote a ChatGPT subscription price. They are discussing different parts of the launch offering. Neither description establishes current availability after discontinuation.

It also does not follow that a discontinued browser cancels the broader ChatGPT subscription. Check the account and billing provider where you subscribed before assuming that renewal stopped.

Current ChatGPT costs are a separate decision

These are the individual dollar prices documented by OpenAI, checked September 9, 2026. They are not an Atlas purchase menu. Confirm the final currency, taxes, eligibility, and billing terms shown for your account.

The Plus help page gives the $20 monthly price and states that API usage is billed separately. The Pro tier guide distinguishes $100 and $200 options with different allowances. Do not assume that a higher subscription means unlimited use of every model or feature.

The broader ChatGPT pricing page lists current plans and surfaces. For a team, compare the actual business offer rather than treating an individual account as a substitute for workspace administration.

Budget for the supported workflow, not an old feature name

Current ChatGPT Work documentation describes research, analysis, deliverables, and scheduled or triggered tasks where eligible. Access depends on the plan, device, rollout, and workspace controls. Work follows the Codex usage structure, while using your own API key has separate API billing.

For example, a weekly supplier-research brief needs more than a subscription price. Check the sources it may open, how often it runs, what happens at the usage limit, and who verifies the resulting comparison. A failed or incomplete run can still require review; do not calculate savings as though every output is accepted unchanged.

For browser migration, keep data transfer separate from plan selection. OpenAI says Atlas browser data does not automatically move with your ChatGPT conversations. If you already exported bookmarks, use that file; if data is missing, follow the current support guidance. Do not send cookie or session files to a support bot or an untrusted person.

Use eesel CLI to scope a support-cost test

If your real goal is handling support work, compare the cost of that job rather than the price of a browser seat. eesel CLI lets an operations lead, script, or coding agent such as Claude Code, Codex, or Cursor inspect the same eesel teammate and workspace used in the dashboard.

Suppose a team is estimating the work involved in answering software-subscription questions. Before running a batch of test chats, the lead can inspect the current workspace and choose one teammate. With Node.js 18.17+ installed, replace the example name with the actual teammate:

npx @eesel/cli status --agent "IT support"
npx @eesel/cli billing --agent "IT support"
npx @eesel/cli activity --agent "IT support"
npx @eesel/cli instructions --agent "IT support"

These commands return JSON. billing is read-only eesel billing information, not a quote for the next task, an OpenAI invoice, or a per-ticket savings calculation. Activity helps identify the work to investigate; it does not prove that every attempt produced a usable answer.

Ask the coding agent to compare the standing rules with an approved copy of the company’s subscription policy. Imagine that replies currently confuse “we stopped using this browser” with “the subscription was canceled.” The agent can propose this specific change for the owner to review:

+ Distinguish product availability from subscription status. Answer general plan questions from the approved current source. For an account-specific renewal or cancellation claim, require an authorized billing record; otherwise route the request to the subscription owner without claiming a change was made.

Inspect npx @eesel/cli instructions --help for the supported update arguments. Preview that write with --dry-run, obtain approval for the exact diff, and read back the saved rule. The CLI changes the same teammate used by the dashboard; it does not cancel any vendor subscription.

Before billed chat, the owner checks enabled actions, connected sources, and downstream helpdesk and billing permissions, then approves the test budget. A request for text only is not a permission boundary. Use two fresh conversations: one asks for the approved general plan information; the other asks whether an individual renewal was canceled, with no verified account record supplied. Do not repeat the desired rule in the test prompts.

Review the actual helpdesk response and handoff. The first case should use the approved source; the second should reach the subscription owner without an invented cancellation confirmation. Record accepted answers, corrections, and escalations alongside the available billing evidence. This gives the team a bounded comparison to investigate further, not a guaranteed automation rate or projected return on investment.

Make the next purchase about the job

Do not upgrade solely to revive Atlas. Choose a supported browser and AI experience, verify its account access, and check what the subscription and usage charges cover.

For a company support role, try eesel and use its dashboard or CLI to inspect a small, approved workflow. Base the next rollout decision on checked answers and actual channel outcomes, not the old price of a browser feature.