ChatGPT/Atlas/Q/Is ChatGPT Atlas blocked by the Chrome extension web store when installing extensions like Obsidian Web Clipper? If so, what recourse do users have?

• Is ChatGPT Atlas blocked by the Chrome extension web store when installing extensions like Obsidian Web Clipper? If so, what recourse do users have?

  • My Notes

    • Symptom while trying to add Obsidian Web Clipper: Chrome Web Store showed Switch to Chrome to install extensions and themes, Add to Chrome showed a spinner, then nothing installed.

  • Answer

    • AI/Response
      • Short answer: You are mostly running into compatibility and client-detection limits, not a public “Atlas is banned” announcement. Google Chrome Web Store often refuses or breaks the install flow when the browser is not recognized as Google Chrome, and ChatGPT Atlas (a separate Chromium-based browser from OpenAI) has partial, uneven extension support that can produce exactly the Switch to Chrome banner and failed / stuck installs. Treat Web Clipper on Atlas as unsupported / best-effort until OpenAI documents otherwise.
      • Why the store says “Switch to Chrome”: The Web Store is built around Chrome as the supported install target. Chromium derivatives that do not present the full Chrome identity / capabilities frequently get nudged or blocked at install time. Third-party writeups on Atlas (for example LogRocket’s Atlas overview) call out that message in the context of Atlas not matching Chrome’s extension surface end-to-end. That is store + browser behavior, not proof of a named blocklist against Atlas.
      • What OpenAI has said: The Introducing ChatGPT Atlas post lists safeguards so the agent cannot install extensions for you; that is about automated agent actions, not every manual UI path, but it sits alongside a roadmap that still promises improved developer tools rather than claiming full Chrome parity. Product changes land in ChatGPT / Atlas release notes.
      • Reality on the ground: Users and extension authors report mixed results—some extensions install or partially work, others fail silently or show odd UI (OpenAI Developer Community — extensions in Atlas). Vendor threads (for example 1Password on Atlas) illustrate work when Atlas + store cooperate, and gaps when deeper integration is missing.
      • Practical recourse
        • Clip from a supported browser (recommended): Obsidian documents Web Clipper for Chrome, Brave, Arc, Orion, other Chromium, Edge, Firefox, and Safari (obsidian.md/clipper, obsidianmd/obsidian-clipper README). Install in Google Chrome (or another listed browser), clip there, and keep using Atlas for what it does well—your vault path is unchanged.
        • Use Atlas’s own extension management (if present in your build): Some flows install from the store inside Atlas settings better than opening the store in a random tab; behavior varies by version, so update Atlas and re-check release notes.
        • Advanced / fragile: If Atlas exposes chrome://extensions with Developer mode, you can try Load unpacked after building the extension from the obsidian-clipper repo (see README “Install the extension locally”). This depends on Atlas actually exposing the same hooks as Chrome; if those pages are missing or neutered, this path will not work.
        • Expect the situation to move: Press coverage and update notes have mentioned extension import during onboarding in some Atlas builds; if installs suddenly start working after an update, that is consistent with the product still maturing rather than a single permanent “blocked” state.