I lost all my chats, context, etc after software update

Q&A
,
2

Hi @rfelberg

Welcome to the Quick community!

I ran into a similar issue and was able to resolve it with the steps below. The good news is that your data is almost certainly not lost, it’s still on your machine.

Amazon Quick stores all data locally under ~/.quickwork/profiles/<profile-id>/. Each sign-in identity gets its own profile folder. The behavior you described, sometimes loading with full history, sometimes blank and suggests that two profiles exist on your machine, and the app was intermittently loading the wrong one. After the recent update, it appears to be consistently loading the newer (empty) profile.

Troubleshooting Steps:

Note: Close Amazon Quick completely before performing any of the steps below.

1. Locate your profile folders:

  • macOS: Open Finder → Go → Go to Folder → ~/.quickwork/profiles/
  • Windows: Navigate to C:\Users\<username>\.quickwork\profiles\

You should see one or more folders with IDs like social-abc123def456. The larger folder (by size) is the one that contains your full history and conversations, knowledge graph, memory, connections, etc.

2. Identify the correct profile: Look inside each profile folder for a sessions/ subfolder containing sessions.db. The one with the larger file size is the profile with all your history.

3. Migrate your sessions:

  • In the newer (empty) profile folder, rename the sessions folder to something like sessions.old (this preserves it as a backup, just in case).
  • Copy the sessions folder from the older (larger) profile into the newer profile folder.

4. Verify: Open Amazon Quick and confirm your conversation history has been restored.

If the issue persists after trying these steps, I would recommend filing a case with AWS Support where we can dive into the details so that we can help you further. Here are the steps to open a support case.

If your company has someone who manages your AWS account, you might not have direct access to AWS Support and will need to raise an internal ticket to your IT team or whomever manages your AWS account. They should be able to open an AWS Support case on your behalf. Hope this helps!