Local developer viewer for VS Code Copilot Chat sessions.
Copilot Debugger reads local VS Code Copilot Chat transcript and debug JSONL files and shows them in a compact web UI.
It scans local VS Code storage, normalizes sessions, and displays session metadata, turns, models, tools, agents, token usage, and estimated AI usage costs.
The app does not send your data anywhere. It reads files from your machine and serves the UI locally. It does not call GitHub, Microsoft, Copilot, or any external analytics API.
Default data sources:
GitHub.copilot-chat/transcripts/*.jsonlGitHub.copilot-chat/debug-logs/*/*.jsonl
Main stack:
- React + Vite frontend in
src/ - Node.js + Express backend in
server/ - REST API under
/api/*
Requirements:
- Node.js 20.9 or newer
- VS Code with local Copilot Chat session logs
Run the published package:
npx copilot-debuggerLocal development:
npm install
npm run devDefault local URLs:
- Web UI:
http://127.0.0.1:5173 - API:
http://127.0.0.1:4317
Useful commands:
npm run typecheck
npm run build
npm run startOptional environment variables:
PORT- backend portVSCODE_WORKSPACE_STORAGE_ROOT- custom VS CodeworkspaceStoragerootVSCODE_COPILOT_SESSION_ROOT- direct root for test/session dataSESSION_POLL_INTERVAL_MS- fallback refresh interval
Example:
VSCODE_WORKSPACE_STORAGE_ROOT="/path/to/workspaceStorage" npm run dev- No sessions are shown: check that VS Code has Copilot Chat logs under
workspaceStorage. - Wrong storage location: set
VSCODE_WORKSPACE_STORAGE_ROOTexplicitly. - Port is already used: set
PORT, for examplePORT=4321 npm run dev. - Broken or incomplete data: Copilot Chat log formats are not a stable public API and may change between VS Code versions.
- TypeScript errors after changes: run
npm run typecheckbefore debugging runtime behavior.
![]() |
![]() |
![]() |
Application previews are shown here. |
- Mirek Holec
- Microsoft MVP
- Web: holec.ai
- GitHub: mirekholec
Issues and pull requests are welcome. Keep changes small, focused, and tested with npm run typecheck.
MIT. See LICENSE.


