Extension does not detect the current chat

Symptom

The extension popup, floating button, or export studio says no supported conversation is available.

Why the extension cannot detect a chat

RecallBase looks for supported conversation pages with visible messages. Detection can fail when the page is still loading, the URL is a home or settings page, the AI app changed its markup, or the browser has not granted the extension access to that site.

Most likely cause

The current page may not be listed in supported apps, may be a home/search/settings page instead of a chat, or may have a UI that changed after the extension was released.

Fix it

Check the supported apps list, refresh the conversation page, update the extension, and confirm site permissions are allowed.

1. 1

   Open a real conversation URL.

2. 2

   Check supported AI apps.

3. 3

   Refresh the page.

4. 4

   Update or reload the extension.

5. 5

   Try Save again.

Verify it worked

The extension should show the conversation title or export actions. Unsupported pages should show a clear unsupported state instead of saving the wrong content.

What to report safely

If the page still fails, report the AI app name, browser name, extension version, and whether the page is a real conversation URL. Do not share raw conversation text, cookies, tokens, or screenshots that reveal sensitive messages.

What RecallBase cannot verify

Support should not ask for raw DOM, cookies, tokens, or sensitive screenshots of the conversation.

Check page type first

Most detection failures are not account problems. They happen because the browser is on a product home page, a temporary loading state, a settings page, a search results page, or a newly changed conversation UI. Open a specific conversation with messages visible before testing again.