Compatibility and troubleshooting

Isolate the site, action, and state before resetting data or sending again.

Content baseline: 2.5.0-dev. Store releases and browser builds may differ.

Collect a minimal reproduction

Do not begin by clearing all cookies, deleting all local records, or reinstalling everything. First distinguish provider outages, account restrictions, browser compatibility, and adapter problems.

  1. Note the extension version, browser version, affected site, and exact action.
  2. Enable only the affected site and check whether the issue remains.
  3. Check sign-in and basic chat on the original site, then compare it with the extension.

Blank pages, sign-in loops, or challenges

Wait for loading and check for sign-in, verification, or an optional cookie compatibility request. Use Open original site to complete the provider’s normal sign-in flow when needed.

Third-party cookies, tracking protection, and extension conflicts can affect embedded sites. Follow site-specific compatibility guidance instead of disabling browser protection indiscriminately.

A question has no answer

Different sites respond at different speeds. A delayed answer does not by itself prove sending failed. Check before retrying to avoid duplicates.

  1. Check that the site loaded, the input is complete, and @ chips point to the intended recipients.
  2. See whether that site received the question. Follow its message if quota, model access, or a provider error is involved.
  3. If the original site works but the workspace does not, check extension updates and report the steps and error text.

A file fails or misses one site

Check accepted file types, count, size, and quota. Distinguish uploading, processing, and failure states instead of checking only the local preview.

Use a small, non-sensitive sample on one site. Keep successful results and focus recovery on the site that failed.

Prompt and history problems

Retry the curated prompt library if loading fails and check website access. Saved personal prompts and downloaded catalog entries have different sources.

If a conversation is missing, clear search, time, and site filters and check that you are using the same browser and extension instance. Refreshing cannot automatically restore cleared local storage.

Send a useful report

Include expected and actual behavior, minimal reproduction steps, browser and extension versions, and the site name. Keep screenshots focused on the issue and remove account or private information.

Keep the reference returned after a successful submission. If submission fails, follow the page’s retry guidance. Never provide passwords or cookies for troubleshooting.

Send feedback ↗

Common questions

Do I need an API key?
No. Provider account and quota rules still apply.
If several AIs agree, is the answer guaranteed?
No. Check important claims against their sources.
Does local deletion clear the provider’s history?
No. Deleting on original sites is a separate action that requires confirmation.

Search docs

Enter a feature, action, or question.

    Enlarge image