Skip to content

README.md

Latest commit

 

History

History
27 lines (17 loc) · 2.1 KB

README.md

File metadata and controls

27 lines (17 loc) · 2.1 KB
Raw

VS Code Copilot Chat Viewer

A lightweight, zero-dependency, self-contained Windows application for viewing, searching, and rescuing your localized GitHub Copilot Chat history.

Are you a heavy GitHub Copilot user worried about losing chat histories when you switch or clear out VS Code workspaces? This script will automatically traverse your local VS Code workspace storage directory, identify fragmented conversations, and beautifully render both your legacy workspace.json payloads and modern incremental .jsonl stream files right from your local machine.

Features

  • Double-Click Executable: No web-server setup, Python installations, or Node.js modules are required.
  • Universal Format Support: Handles reading Copilot's newer chronological .jsonl text streams as well as older flattened .json histories natively.
  • Secure & Local: Everything translates within an embedded edge container window via passing safe file:/// protocols locally; nothing leaves your machine.
  • Embedded Web Rendering: Features a responsive, native-feeling GUI that effortlessly formats inline codeblocks, tables, and messages using an injected lightweight marked.js markdown parser.

Usage

Simply download and double-click CopilotChatViewer.cmd.

  1. The script will dynamically read your %APPDATA%\Code\User\workspaceStorage\ folder to map existing sessions.
  2. An elegant embedded interface will launch showing a sidebar of all detected projects grouped cleanly (even handling missing or renamed workspaces).
  3. Search and browse locally. Select an orphaned chat to review the messages.

Installation

You only need CopilotChatViewer.cmd provided in this repository! Download it to any local directory and run it.

Why a .cmd wrapper script?

The tool relies on PowerShell dynamically intercepting and decoding the chat files, but we wanted it to be accessible via standard double-click actions without triggering ExecutionPolicy roadblocks typically associated with raw .ps1 files. As such, the application is actually a hybrid Polyglot batch script that flawlessly bootstraps itself as a PowerShell process.