Frequently asked questions

Find the question or symptom that matches your situation, then work through the checks. If you still need help, please let us know.

Do I need an account or a purchase?

You can scan, browse conversations, search within the free scope, and export individual conversations without registering or purchasing.

The following features require a purchase and activation:

• Searching all past conversations Context has found.
• Exporting multiple conversations at once.

See the pricing page and Activation and device management.

Does Context upload my conversations?

Context does not upload conversation text. Scanning, searching, reading, and exporting all run on this computer.

Purchases, activation, license verification, and update checks require internet access. See the Privacy policy for how related information is handled.

No sources found, or the scan found no conversations

Check these three things in order:

1. Is your app or entry point supported? Check Supported Agents. Conversations with the same model may be saved differently depending on the app or entry point you use.
2. Are conversations saved on this computer? Check that a supported client has saved conversation records on this computer.
3. Can Context read the source directory? Check that the directories shown in Agent Sources exist and that Context has permission to read them.

Once you have confirmed that the Agent has saved conversations, click Scan now in Agent Sources.

Why are new messages from my Agent missing?

Context scans automatically each time you launch it. If Context is already open, click Scan now in Agent Sources to bring in newly saved conversations and messages.

If the Agent is still generating a reply, wait for it to finish saving before scanning. See Scan conversations.

A conversation opens, but some content is missing

First, check whether the content is hidden. System messages, reasoning, tool calls, and tool results are hidden by default. Enable them under Display content in the conversation toolbar.

If content is still missing, check Parsing details at the bottom of the conversation. Common reasons include:

• The Agent did not save that content.
• Information in the record could not be decrypted.
• The current version of Context does not fully support that type of record.

If the original client displays it correctly but Context is clearly missing it, please let us know.

If an attachment will not open, check the note beside it and whether the file has been moved or deleted. Context may also be unable to find the file if the original record did not save a locatable attachment reference. See Attachments, links, and source files.

A conversation is listed but does not appear in search

Check the scope message below the search box. Confirm that the conversation is included and the text is in a user or AI message, then check your keywords, filters, and whether new content is ready.

See Search conversations: If you cannot find what you need for the full checks.

Cannot open a conversation or jump to the original message

Expand Source files at the bottom of the conversation to check the original file locations. The files may have been moved, deleted, or changed since the last scan.

If the files still exist, check that Context has permission to read them. Then scan again and reopen the conversation or search again.

If the files exist and are readable but the issue persists after scanning, please let us know. Issues that start after an Agent update may be related to changes in the record format that the current version of Context does not yet support.

Does adding a favorite save another copy?

No. A favorite only marks a conversation so it is easier to find. Reading still requires the original records saved on your computer by the Agent.

To keep a conversation long term, export it. If it has attachments, make sure those files are saved too. See Data and privacy.

Export failed or only partly completed

If Context reports that the range contains too many conversations, keep each batch to 10,000 or fewer. Filter by Agent, working directory, or modification date to split the export into batches.

Export progress shows separate counts for conversations exported, skipped, and not exported. Expand the details for conversations that were not exported, then follow the relevant steps:

• The original file cannot be read: check the path and permissions through Source files, then scan again.
• The conversation changed during export: wait for the Agent to finish saving, then retry.
• A file cannot be written: check the destination folder’s permissions, available disk space, and whether another program is using a file with the same name. You can also choose another destination.
• Activation is required: exporting multiple conversations at once requires activation. Check your status under Settings → Benefits and license.

If a file was skipped, check whether you selected Skip existing file. In that case, the file with the same name at the destination was kept.

Cancelling does not delete files already created. Before exporting again, check how existing files will be handled so you do not overwrite a version you want to keep.

Activation failed or the license is unavailable

Start activation in Context, then complete device authorization in the browser. First, check:

1. Whether your internet connection can reach the website.
2. Whether you signed in with the account you used to purchase.
3. The status or message shown when you return to Settings → Benefits and license.

See Activation and device management for the full process.

If the device is already linked to a license but shows Online license verification required, reconnect to the internet. If a Verify online button is available, you can also verify manually.

If you have reached your device limit, open Device management and deactivate an old device you no longer use. To check payment results or account benefits, visit your account.

Use Clear local license only if the app offers it and you have confirmed that you need to resolve a local license issue. First deactivate the device on the website, then clear its local license information and activate it again. Clearing local information alone does not free up a device seat on the website. For an ordinary connection failure, reconnect and try again first.

Still need help?

If these steps do not resolve the issue, please let us know. Include the following to help us investigate:

• App version, operating system, and processor architecture.
• The Agent and client you used, such as a command-line tool or VS Code extension.
• What you did before the issue occurred, and whether you can reproduce it.
• The full error message shown in the app, and diagnostic codes from Parsing details, if available.

Redact private information from screenshots and logs before sharing them, and do not attach original conversation files. For local data and internet access, see Data and privacy.