A Visual Studio Code extension that helps you view and manage your GitHub Copilot chat history organized by workspace.
The extension now features a completely redesigned chat renderer that closely matches the official VS Code Copilot Chat interface:
- Authentic VS Code Styling: CSS styles based on the official VS Code Copilot Chat repository
- Professional Icons: SVG icons for user and Copilot avatars instead of emoji
- Advanced Markdown Support:
- Four-backtick code blocks (like official Copilot)
- Better formatting for lists, quotes, links, and tables
- Proper syntax highlighting integration
- Responsive Design: Optimized for different screen sizes
- Theme Integration: Full VS Code theme support with proper color variables
- Native look and feel matching VS Code's design language
- Better typography and spacing
- Enhanced readability with proper contrast ratios
- Professional message layout with improved avatars
- π Workspace Organization: Chat sessions grouped by workspace for easy navigation
- π Search & Filter: Quickly find specific chat sessions by title or content
- π Quick Access: Open workspaces directly from chat history with inline buttons
- π Smart Titles: Automatically generates meaningful titles from chat content
- π² Tree View: Clean, collapsible interface in the Activity Bar
- β‘ Fast Performance: Efficient scanning and caching of chat data
- Open VS Code
- Go to Extensions (Ctrl+Shift+X)
- Search for "Copilot Chat History"
- Click Install
- Download the latest
.vsixfile from Releases - Open VS Code
- Go to Extensions (Ctrl+Shift+X)
- Click the "..." menu and select "Install from VSIX..."
- Select the downloaded file
- Look for the "Copilot Chat History" icon in the Activity Bar (left sidebar)
- Click to open the panel
- Browse your chat sessions organized by workspace
- Expand/collapse workspaces as needed
- Click the search icon (π) in the panel header
- Enter keywords to filter chat sessions
- Use the clear filter button (ποΈ) to reset
- Use the inline arrow buttons next to workspace names:
- β Open workspace in current window
- β Open workspace in new window
- Click the refresh button (π) to reload chat history
- Automatically scans for new chat sessions
The extension scans your VS Code workspace storage for Copilot chat sessions:
- Location:
%APPDATA%\Code\User\workspaceStorage\[workspace-id]\chatSessions\ - Grouping: Sessions are grouped by their associated workspace
- Titles: Uses custom titles or generates them from first message
- Paths: Resolves workspace paths from stored configuration
- Visual Studio Code 1.103.0 or higher
- GitHub Copilot extension (for generating chat sessions)
This extension contributes the following settings:
Currently, no additional settings are required. The extension works out of the box.
- Workspace paths may not resolve correctly if projects have been moved
- Search is case-insensitive and searches in session titles only
- Large numbers of chat sessions may impact performance
Contributions are welcome! Please feel free to submit a Pull Request.
- Clone this repository
- Run
npm installto install dependencies - Press
F5to open a new Extension Development Host window - Test your changes
# Development commands
npm run compile # Compile TypeScript
npm run watch # Watch for changes
npm run package # Build for production
# Create installable package
npm run package:vsix # Creates .vsix file for installation
# Publishing (requires tokens)
npm run publish:vsce # Publish to VS Code Marketplace
npm run publish:ovsx # Publish to Open VSX Registry
npm run publish:both # Publish to both marketplaces- Build VSIX package:
npm run package:vsix - Install locally:
code --install-extension copilot-chat-history-1.0.3.vsix - Reload VS Code and test functionality
This project is licensed under the MIT License - see the LICENSE file for details.
- Initial release
- Workspace-based chat organization
- Search and filter functionality
- Inline workspace opening buttons
- Smart title generation
Enjoy managing your Copilot chat history! π
If you encounter any issues or have feature requests, please file them in the GitHub Issues.