Extension Not Detecting a Chat
Detection usually fails because the current page is unsupported, the AI product changed its UI, the page is not a conversation view, or browser permissions are missing.

Symptom
The popup, floating button, or Export Studio says no supported conversation is available.
Why the extension cannot detect a chat
RecallBase looks for a supported conversation page with visible messages. Detection fails 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 in the supported apps list. It may be a home, search, or settings page instead of a chat. Or the AI app may use 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
Open a real conversation URL.
- 2
Check supported AI apps.
- 3
Refresh the page.
- 4
Update or reload the extension.
- 5
Try Save again.
Verify it worked
The extension shows the conversation title or export actions. On unsupported pages it shows a clear unsupported state instead of saving the wrong content.
What to report safely
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 will 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 on a product home page, a loading state, a settings page, a search results page, or a newly changed conversation UI. Open a specific conversation with visible messages and test again.