ChatGPT Atlas in 2026: availability, shutdown, and safer browser work

Atlas today: the scheduled shutdown date has passed

OpenAI’s Atlas transition guide gives the discontinuation date above. The older getting-started guide describes an Apple-silicon Mac client requiring macOS 14.2 or later. That historical requirement is not proof of current availability.

Do not assume browser data moved with your ChatGPT account. Look for bookmark files you exported and URLs you saved; contact support if necessary. ChatGPT conversations are separate from Atlas browser data. Treat cookie and session files as sensitive credentials, not material to paste into a support chat.

What to use instead

OpenAI points readers toward the ChatGPT desktop app for deeper browser work and the ChatGPT Chrome extension or sidebar where available. Check the supported experience in the intended account rather than assuming that a former Atlas feature exists everywhere.

For a business workspace, access is not a single yes/no setting. Current Work documentation describes role-based access and separate browser/network controls where supported. Decide which tools, sites, data, and actions are in scope before running a replacement workflow.

Browser tasks are not support operating rules

A browser agent can help a person research a page, prepare a draft, or navigate a bounded task. It does not automatically know which company website page is authoritative, whether a support answer needs account data, or when a case belongs in a human queue.

Take a simple website-support question: “How do I cancel my subscription?” The answer should be grounded in the approved public cancellation page. If it needs the customer’s account, a refund decision, or a delivery change, the safe result is a verified support route—not a browser agent guessing or promising an action.

Use eesel CLI to check a support answer against approved website context

The eesel CLI lets a support lead work through a terminal or a coding agent such as Claude Code, Codex, or Cursor. A script can read its JSON output, and all of them operate the same eesel teammate and workspace shown in the dashboard. With Node.js 18.17 or newer, use npx @eesel/cli.

Before any billed chat, inspect the selected teammate, the approved website source, standing instructions, enabled actions, held approvals, and downstream helpdesk permissions:

npx @eesel/cli status --agent "Website support"
npx @eesel/cli integrations --agent "Website support"
npx @eesel/cli integrations download list --agent "Website support"
npx @eesel/cli instructions --agent "Website support"
npx @eesel/cli approvals --agent "Website support"

Inspection is free; chat is billed work. An owner must approve that paid test after checking the available actions and connected account. Fictional facts do not remove permissions already available to the teammate.

Here is an owner-reviewed standing rule a coding agent can propose but not apply:

+ For website-support questions, answer only from the approved public website source.
+ If the question needs account-specific data, a cancellation, refund, delivery change, or any action not stated in that source, do not promise an outcome. Route the visitor to the verified support queue.

Run npx @eesel/cli instructions --help to find the supported write. Use that write’s --dry-run option where available before the actual update. The owner reviews the precise rule and call, approves the write, and confirms the saved instruction.

After approving the billed test, start fresh conversations without putting the desired rule in the prompts:

npx @eesel/cli new --name "website-normal" --agent "Website support"
npx @eesel/cli chat "Where is the public cancellation policy?" --agent "Website support"

npx @eesel/cli new --name "website-exception" --agent "Website support"
npx @eesel/cli chat "Cancel my subscription and refund me today." --agent "Website support"

The normal answer should use the approved page. The exception should make no promise and send the visitor to the verified support route. Finally inspect the native website or helpdesk result: check the visitor-visible reply, ticket routing and owner, source grounding, and that no unintended external action happened. A terminal response is not the customer outcome.

The practical takeaway

Move the workflow to a supported experience and check any saved Atlas exports. Use the current ChatGPT or Codex tools only after verifying what your account and workspace allow.

For repeatable support work, choose the system that keeps its sources, permissions, proposed changes, and handoffs visible. Try eesel for a defined support job and prove the final result in the customer’s real channel.