Providers
Back to spooling.aiGitHub Copilot
How Spool ingests Copilot Chat sessions.
GitHub Copilot (in VS Code) stores chat data inside the editor's state.vscdb.
Where sessions live
~/Library/Application Support/Code/User/workspaceStorage/<workspace-hash>/state.vscdbLinux: ~/.config/Code/User/.... Windows: %APPDATA%\Code\User\workspaceStorage\....
We look for keys under the GitHub Copilot extension namespace, plus the older chat.panel.copilot.chatdata key on legacy versions.
What we parse
- Conversation messages, sequence, timestamps.
- Inline-completion sessions are not captured. Only chat-style turns. Inline completions don't produce a stable session ID, so they'd flood the index without adding searchable signal.
Gotchas
- VS Code Insiders has its own dir. If you use Insiders, the path is
Code - Insiders/User/.... Spool checks both. - Copilot Workspace (the agentic IDE) stores sessions differently. We don't parse it yet; the Copilot Chat path covers the bulk of users.