PromptDust
Catalog/VS Code (Copilot Chat)

Transcripts

VS Code (Copilot Chat)

GitHub Copilot Chat history persists locally in per-workspace SQLite state stores.

Microsoft Linux · macOS · Windows SQLite

Exposure

High
Stores found
2
Holds
API keys · personal data · source code
Confidence
verified

Where it writes

2 stores in the current signature database. Paths shown for a typical macOS install.

Transcripts high

SQLite may hold API keys · personal data · source code

  • macOS ~/Library/Application Support/Code/User/workspaceStorage/**/state.vscdb
  • Linux ~/.config/Code/User/workspaceStorage/**/state.vscdb
  • Windows ~/AppData/Roaming/Code/User/workspaceStorage/**/state.vscdb

GitHub Copilot Chat history persists locally in per-workspace SQLite state stores.

  • Clear chat sessions from within VS Code to reduce local retention.
  • Keep the Code application-support folder out of cloud-synced locations.

Source: github.com

Transcripts high

SQLite may hold API keys · personal data · source code

  • macOS ~/Library/Application Support/Code/User/globalStorage/state.vscdb
  • Linux ~/.config/Code/User/globalStorage/state.vscdb
  • Windows ~/AppData/Roaming/Code/User/globalStorage/state.vscdb

VS Code global state, which can include Copilot chat and other AI extension data.

  • Keep the Code application-support folder out of cloud-synced locations.

What to do about it

PromptDust flags these stores and leaves them in place; cleanup is your call. If a store holds a live secret, rotate the secret first, since deleting the file won’t un-leak a key that already sat in plain text.

For ongoing work, keep sensitive material out of sessions where you can, and prune old transcripts and caches now and then.

This describes where VS Code (Copilot Chat) stores data. Metadata only, never your content. Confidence: verified. Spot a mistake? Tell us.

← PreviousvLLM Next →Warp

See if this one’s on your machine.

One pass finds every store, for this tool and the other 51.

Download PromptDust Back to catalog