Augment / Recovery

Augment support tools

Help your conversations
save again.

If new threads disappear after restarting VS Code, inspect your saved history for suspected blockers. Review the proposed change and create a local backup before recovery.

Download for Mac Read the recovery steps

Recovery runs on your computer. Your project files and conversation content are not uploaded.

01 / Choose your platform

Download Conversation Recovery.

Read the guide before opening the app. Keep VS Code closed throughout recovery and any immediate rollback.

Available for Mac

macOS · Apple Silicon

One complete ZIP download for Macs with Apple Silicon. This release does not include an Intel Mac build.

Download Mac ZIP

Unsigned and not notarized. macOS may show a security warning or block opening. Do not disable operating-system security protections globally; consult your support contact if you cannot open it.

Verify the download · SHA-256

Compare the SHA-256 digest of the complete ZIP with this value:

356f8bcb1a8e20aad91de66b9c5c99b811492b177d74970faa05c1b6f6f02766
Build/testing pending

Windows

The Windows build is not available. Packaging and testing must be completed before a download can be offered.

Build/testing pending. There is no announced release date.

02 / Recover deliberately

Inspect. Review. Recover.

The app highlights large histories as possible blockers. Size alone does not confirm the cause; review the selected conversation before making a change.

  1. Close every VS Code window

    Close all VS Code windows first, then open the recovery app and use Check closed. Do not reopen VS Code during the recovery operation.

  2. Locate saved workspace metadata

    The app discovers saved workspace metadata in the VS Code data folder, not your project folder. The standard roots are ~/Library/Application Support/Code on macOS and %APPDATA%\Code on Windows. Choose a custom data root if you use a nondefault location.

  3. Select your workspace and scan its history

    The main list shows recovery candidates with large histories and a supported recovery format, largest first. Other workspaces are hidden by default; use Show other workspaces to reveal them in muted text below the candidates. If there are none, the app says No recovery candidates found. That does not rule out other causes of disappearing threads. Choose the project where threads have been disappearing, then inspect its conversations. These indicators suggest where to start; they do not confirm the cause.

  4. Review and confirm the recovery

    Keep the suggested backup folder, then click Review recovery plan. Check the selected conversation and proposed change. When ready, click Back up and recover. Recovery requires your explicit confirmation. The app backs up the workspace database, workspace metadata, and conversation key-value (KV) store. It replaces the selected conversation with a recovered thread containing its latest saved compacted context and subsequent messages. Historical tool details are collapsed and can be expanded for reading; they are not executable actions. Existing KV files are left unchanged. Keep the backup private.

  5. Check that new conversations stay saved

    Open the same project in VS Code and inspect the recovered thread. At the bottom, Continue from here — last saved user prompt shows the last identifiable saved user prompt, not an automatic resend. If no standalone prompt can be identified, the app says so. Review the recovered context, then start a new thread and send a harmless test message. Close VS Code completely, then reopen the project and manually verify the new conversation is still listed after restarting VS Code.

    Undo recovery is optional, not a step needed to finish. Use it before reopening VS Code if you want the previous workspace state back. To protect newer work, automatic undo refuses changed state.

03 / Know the boundaries

Before you recover.

Is this a fix for every missing conversation?

No. This tool replaces a supported saved conversation suspected of blocking later saves with a shorter, context-only recovered thread. Similar symptoms can have other causes, and history size alone does not confirm the issue. It does not retrieve conversations that were never saved or change the extension's code. Verify that new threads survive a restart after recovery.

Does the app upload my data or run my project?

The app processes recovery data locally. It does not upload your data, require sign-in, or execute your project. This website serves the guide and downloads; its hosting infrastructure may retain standard request logs.

Why select the VS Code data folder instead of my project?

Saved workspace metadata is stored under VS Code's data root, separately from your project files. Use the standard data root shown in the guide, or choose your custom data root for a nondefault setup. Select the relevant saved workspace before scanning a candidate.

What does the local backup protect?

The recovery backup contains the selected workspace's database, workspace metadata, and a copy of its conversation key-value (KV) store. The original longer history remains in the backup; the recovered thread contains saved compacted context and subsequent messages. Existing KV files stay unchanged during recovery. This is not a full backup of all workspaces or your project files. Keep the backup private and retain your normal backups.

Can I undo recovery?

Yes. Before reopening VS Code, use Undo recovery to restore the saved workspace state. If you have already resumed work, keep your backup and contact support before restoring it, so newer conversations are not overwritten.

Do I need runtime instrumentation?

No runtime instrumentation is required for this workflow. After recovery, manually check your conversation history, a new thread, and a VS Code restart. If behavior is still wrong, consult your support contact rather than repeatedly applying changes.

Why might macOS warn me about this app?

The Mac application is unsigned and not notarized. Platform security warnings or opening restrictions are possible. Follow your organization's approved software policy and ask your support contact for help; do not globally disable OS security. Windows remains unavailable until its build and testing are complete.