Verify an AI memory connection end to end
Use a synthetic project to test capture, sync, tool access, and source-backed recall without exposing private conversation data.
Find and fix a missing piece 3 min read
Why is a chat missing from AI memory?
A missing chat can be a capture, sync, or retrieval problem. Confirm the right account and source scope first. Then check whether the source reached the memory system before judging the assistant’s answer.
ON THIS PAGE
Find the first missing step
Start where the data originates. For web chats, check the provider account, the extension’s capture settings and the history range. Chats from the ChatGPT and Claude desktop apps, phones and the Grok phone app are read from the signed-in site in the background, so check that the browser with Dray is running and signed in to that site; if it is signed out or closed, those chats are not saved until that is fixed. For coding sessions, run dray status to check this computer’s sign-in, capture and pending uploads. Claude Code capture uses hooks and does not require the browser extension.
MCP access is a separate check. For a coding agent, dray mcp shows whether its memory connection is in place, and dray mcp on restores one. A Dray plugin or connector can retrieve existing memory even when local capture is not signed in. Use dray setup for missing capture configuration, or dray login for an expired CLI sign-in, then restart the agent. Import older local sessions with dray import; Cursor hooks save new sessions only.
If the source is present locally but not available to a connected assistant, record that distinction. Upload and memory processing can take time; do not diagnose a missing extension from an empty search result.
Use one known source to test retrieval
Choose a harmless conversation you know was included. Search for a distinctive detail, then ask the assistant to consult Dray explicitly. If the tool returns the source but the answer ignores it, the failure is later in the chain.
Do not repeatedly disconnect and reconnect every provider while diagnosing a single missing chat. Change one thing at a time so you can tell which step helped. Keep private conversation text out of support screenshots unless it is needed and approved.
TAKE THIS WITH YOU
A useful support note
An illustrative template. Replace the details with material you are allowed to share.
Provider and intended account: […] Approximate conversation date: […] Chosen capture scope: […] Visible in provider: yes / no Visible in local archive: yes / no / unknown Sync status or sanitized error: […] Search tried: [non-sensitive description] What happened instead: […]
USING THIS WITH DRAY
Keep the context. Check the source.
Capture, server-side processing, and connected-agent access are separate parts of Dray. The setup guide explains how to check the connection without assuming all history is present. If you hid the chat from the Dray menu, Dray leaves it out until you choose “Restore this chat to Dray” there.
Available sources and connections depend on your setup. Read the privacy policy before granting access.
Sources & next reads
Product details are grounded in the guides below. Example projects and prompts are illustrative, not customer results.