Help & Support

The connection needs three things: the desktop app running, the ChatsRecall extension installed, and that browser open. If the connector count in the sidebar stays at zero:

• Open Chrome or Edge and give it a few seconds. The count updates on its own.
• Check that the extension is still enabled in the browser's extension settings.
• Restart the browser.

The desktop app may already be running in the system tray even if you see no window. Launching it again never starts a second copy; it just brings the window back.

Yes. Chrome and Microsoft Edge can be connected at the same time, and syncing runs in every connected browser. Each conversation remembers the account it came from, so using different accounts in different browsers or profiles stays tidy. The Extensions page lists every connected browser and the extension version it runs.

Never. ChatsRecall does not ask for or store any credentials. It reads conversations through the browser where you are already signed in. If a source shows a signed-out note in the sync history, sign in to that site in the connected browser and run the sync again.

That is a sync run at work. Each run opens one minimized window per connected browser, visits your sources one after another in a single tab, and closes the window when the run finishes. You can keep using your other windows normally the whole time.

Live capture saves new prompts and responses within moments, while you chat on a source site in a connected browser. Sync is the scheduled or manual pass that brings in your existing history and anything live capture could not see. Both feed the same library, so nothing shows up twice.

Scheduled sync only runs while a connected browser is open. ChatsRecall never launches a browser by itself; a scheduled run simply waits until the browser is open again.

Also check that the source is switched on on the Sync page. Copilot and Read AI ship switched off until you opt in.

Finding a conversation and saving its messages are separate steps, so a conversation can appear in the library before its content arrives. Content is fetched in the background across sync runs.

The conversation itself tells you where things stand: still queued for an upcoming sync, tried a few times so far, or given up with the reason recorded. A Full Refresh from the Sync page retries everything, including conversations sync had given up on.

Automatic syncing fills in content for roughly the last 18 months. Older conversations still get their entry in the library. To pull in their full content as well, run a Full Refresh from the Sync page.

Deletions carry over: the next sync notices the conversation is gone on the source side and removes it from the library as well.

Eleven today: ChatGPT, Claude, Claude Code, Claude Cowork, Gemini, Google AI Mode, Perplexity, Grok, Copilot, Wave, and Read AI. All of them sync; most also capture live as you chat.

Copilot and Read AI ship switched off. Turn them on from the Sync page when you want them. Read AI needs extension version 0.1.5 or newer.

Six common sources are visible out of the box. Open the sources filter  next to the SOURCES label in the sidebar to show the rest, reorder them, or hide the ones you do not use.

Open the sources filter  next to the SOURCES label in the sidebar. Every source has a row there, with three settings:

• Shown: hides nothing.
• No sidebar: removes the sidebar row only. That source's conversations still appear under All Sources and in search.
• Hidden: removes the sidebar row and keeps that source's conversations out of the list and out of search.

Nothing you hide stops syncing, and nothing is deleted. Set a source back to Shown whenever you want it back in the list. Drag a row by its handle  to change the order the sources appear in.

That is by design. Google AI Mode is captured through a non-Chrome browser, such as Edge, with extension version 0.1.3 or newer. This applies to syncing, opening saved searches, and New Chat.

Claude Code and Claude Cowork sessions that ran on this computer are read from files on this computer, and they are grouped under a "local" account in the sidebar. These conversations always open inside ChatsRecall, since there is no web page to send you to.

Only their names and types. Cards and the conversation view show which files went into a prompt and which files the assistant produced, but file contents are never read or stored. Wave and Read AI are meeting sources, so file attachments do not apply there.

Search covers every conversation from every source. Queries match whole words and the beginnings of words, so short queries stay precise. Results are ordered newest first.

Long pasted code blocks are deliberately left out of the index so a common identifier does not flood your results. Short snippets, error messages, and inline code remain searchable.

From a result you can open the conversation inside the app, or on the original site: the page scrolls to the exact message and highlights your search terms.

Ask a question in plain language, like "what did I decide about the kitchen renovation?", and get an answer grounded in the conversations you actually saved, with citations that open the exact conversations behind it. It is set up under Settings, and every run reports the tokens it used.

In a local database on your computer. Your conversations are never uploaded, and there is no ChatsRecall server holding a copy. The full details are on the Privacy page.

Conversation content stays local. Anonymous usage analytics may be sent to help improve the app; they never include conversation content, titles, or links, and the Privacy page lists exactly what is and is not included.

The one content exception is Agentic Search, and only when you use it: answering your question sends the small set of excerpts the run selects to the model provider. Nothing runs in the background.

Closing the window hides ChatsRecall to the system tray so capture keeps working while you chat. Click the tray icon  to bring the window back. To exit completely, use Quit in the tray icon's menu.

When a new version is available, an update strip appears in the app. You see the release notes first, then the update installs in place and the app restarts. Updates install cleanly even while a browser is connected. The full history is under Release Notes on the Download page.

During the beta, a fresh installer can be new to Microsoft SmartScreen, so Windows may show "Windows protected your PC". First make sure your download came from this site's Download page. Then choose "More info", followed by "Run anyway".