ChatGPT Atlas Was Retired: Migrate Browser Research Without Losing Evidence
ChatGPT Atlas stopped working August 9. Preserve bookmarks, tabs, history, source roles, and claim context before moving browser research to a replacement workflow.
Published August 10, 2026: OpenAI scheduled ChatGPT Atlas to stop working on August 9. Its release notes say browser data such as bookmarks, open tabs, and history does not transfer automatically. Conversation history is separate and remains subject to the user’s plan, workspace settings, and account access.
A useful migration preserves more than bookmarks. Research teams should save the source URL, retrieval date, relevant passage, decision, and any open question attached to every important Atlas tab. A browser export without that context preserves navigation history but loses the evidence trail.
What transfers and what does not
OpenAI documents separate paths: bookmarks can be exported to Chrome, while cookies and passwords can be moved to the ChatGPT desktop app. Open tabs and browsing history require deliberate preservation. ChatGPT conversations are not Atlas browser data and follow the normal account and workspace retention rules.
| Asset | Documented path | Research safeguard |
|---|---|---|
| Bookmarks | Export to Chrome | Add project, source role, and review date |
| Cookies and passwords | Export to ChatGPT desktop app | Use approved credential handling; never place secrets in a source ledger |
| Open tabs and history | No automatic transfer | Save material URLs and why each page mattered |
| ChatGPT conversations | Separate from Atlas | Confirm plan, workspace, retention, and access before relying on availability |
Build an evidence-preserving export
- Inventory active work. Group important tabs by article, client, experiment, or decision.
- Save canonical URLs. Remove tracking parameters when they are not part of the evidence, but retain a raw copy if attribution matters.
- Record source roles. Mark each page as official documentation, dataset, standard, report, context, or unverified lead.
- Capture the claim boundary. Note the exact fact supported, the date, product state, region, plan, and what the source cannot establish.
- Preserve local artifacts. Save permitted exports, screenshots, response files, or data with a stable filename and retrieval time.
- Reopen critical sources. Confirm redirects, access, and current wording in the replacement environment before closing the migration.
This is the same discipline used in the evidence-led publishing guide: a fluent summary or a browser session is not the underlying evidence. A source ledger should survive the retirement of a particular tool.
Choose the replacement by job
OpenAI points to the ChatGPT desktop app for deeper browser-based agentic work and to the Chrome extension or sidebar for help while browsing, where available. That recommendation describes product direction; it does not establish that either surface reproduces every Atlas workflow or data state.
Test the replacement against real jobs: open a saved source set, sign in where authorized, download a permitted file, follow a redirect, preserve citations, export results, and resume after a restart. Record missing features instead of silently changing the research method.
For regulated, confidential, or client work, review workspace controls, local file access, credential storage, browser permissions, and retention before moving data. Exporting cookies or passwords is a security-sensitive operation and should follow the organization’s approved process.
A migration acceptance test
- Every active research project has an owner and a replacement workspace.
- Important URLs reopen and still map to the claim they supported.
- Bookmarks include enough context to be usable outside Atlas.
- Required credentials were moved through an approved method and are not embedded in notes.
- Open tabs and history needed for active work were deliberately preserved.
- The replacement workflow can export or archive its evidence.
- A sample project was resumed from a clean restart without relying on hidden session state.
Do not call the migration complete because the bookmark count matches. Complete it when another editor can reconstruct the source trail and continue the decision without the retired browser.
Ask a question or join the discussion