PromptVault — GitHub Copilot Logger for VS Code
Why PromptVault?Every developer has been there: you asked Copilot something brilliant three days ago, got a perfect answer, closed the tab, and now it's gone. VS Code does not persist Copilot chat history beyond the current session. PromptVault fixes that. It works as a native chat participant inside your existing Copilot Chat panel — no separate app, no browser, no clipboard tricks. You chat exactly as you always do, just prefixed with Features at a Glance
Requirements
InstallationOption A — Install from VSIX (recommended for enterprise)This is the standard way to distribute internal VS Code extensions without publishing to the Marketplace. Step 1 — Build the VSIX package Open a terminal, navigate to the project folder (note the quotes — the folder name has a space), and run:
This produces Step 2 — Install in VS Code Via terminal:
Via the VS Code UI:
Step 3 — Verify installation
Option B — Run in development mode (F5)Useful if you want to test or modify the code before packaging.
Then open the ConfigurationStep 1 — Open VS Code SettingsPress Step 2 — Set your save path (optional but recommended)By default, logs are saved to Via Command Palette:
Via settings.json:
Step 3 — (Optional) Pin your preferred modelIf your enterprise subscription has multiple models and you always want a specific one:
Supported values include: Step 4 — (Optional) Pause logging without uninstalling
When Full Settings Reference
How to UseEveryday usage — just prefix with
|
| Command | What it does |
|---|---|
@promptvault /help |
Full help card with today's stats and all settings |
@promptvault /status |
Today's prompt count, total days logged, save path, auto-save state |
@promptvault /export |
Opens today's .txt log file directly in the VS Code editor |
@promptvault /clear |
Confirmation dialog, then deletes all log files permanently |
Command Palette (Ctrl+Shift+P)
Search "PromptVault" to find:
| Command | Description |
|---|---|
| PromptVault: Open Today's Log | Open today's log file in the VS Code editor for reading |
| PromptVault: Export Today's Prompts | Save a copy of today's log to any folder you choose |
| PromptVault: Export All Prompts | Combine all days into one file and save to a chosen location |
| PromptVault: Clear All Saved Prompts | Permanently delete all log files (confirmation required) |
| PromptVault: Set Save Path | Open a folder picker to change where logs are stored |
| PromptVault: Show Status | Show a quick notification with today's count and log path |
Log File Format
Each day produces one file: prompts_YYYY-MM-DD.txt
╔══════════════════════════════════════════════════════╗
║ PROMPTVAULT — GitHub Copilot Log ║
╚══════════════════════════════════════════════════════╝
📅 2026-05-08
━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
[001] 09:15 AM 🤖 copilot/gpt-4o
PROMPT:
How do I paginate a SQL query efficiently for large datasets?
RESPONSE:
For large datasets, prefer keyset (cursor-based) pagination over
OFFSET/FETCH because OFFSET scans and discards all preceding rows...
────────────────────────────────────────────────────────
[002] 10:42 AM 🤖 copilot/gpt-4o
PROMPT:
Write a Python dataclass for a User with validation on the email field.
RESPONSE:
Here's a dataclass using __post_init__ for email validation...
────────────────────────────────────────────────────────
Every file is:
- Plain UTF-8 text — readable in any editor, Notepad, or terminal
- Searchable with
grep,Ctrl+F, or any search tool - Safe to commit to a private repo, back up to cloud, or email
- Numbered sequentially — entries are never overwritten or merged
Use Cases
For individual developers
- Build a personal "Copilot knowledge base" — search your own past conversations to avoid asking the same question twice
- Review what you asked Copilot at the end of a sprint to write better commit messages or PR descriptions
- Keep a running log of solutions to tricky bugs you solved with AI assistance
For teams using GitHub Copilot Enterprise
- Maintain a shared audit trail of AI-assisted decisions during architecture sessions
- Onboard new team members by sharing a curated log of common patterns your team has already solved with Copilot
- Satisfy internal documentation requirements around AI tool usage
- Build a team-wide prompt library by syncing the save path to a shared network drive
For compliance and governance
- Demonstrate responsible AI usage with a timestamped, model-tagged log of every AI interaction during a project
- Quickly distinguish what was generated by AI vs. written by hand on any given day
- Retain records of AI-assisted code decisions for regulated industries (finance, healthcare, legal)
For learning and upskilling
- Review how you've been using Copilot — are your prompts getting better over time?
- Export a week of logs to identify knowledge gaps and follow up with deeper study
- Spot patterns in your questions and build a library of prompts that reliably get great results
Advantages Over Native Copilot Chat
| Copilot Chat (native) | PromptVault | |
|---|---|---|
| History persists after VS Code closes | No | Yes |
| History survives a VS Code update or reinstall | No | Yes |
| Searchable with grep / text tools | No | Yes |
| Exportable to share with teammates | No | Yes |
| Organized into daily files automatically | No | Yes |
| Timestamps every entry | No | Yes |
| Shows which model answered each prompt | No | Yes |
| Works with all enterprise Copilot models | Yes | Yes |
| Requires internet beyond Copilot itself | Yes | No |
| Sends data to third-party servers | No | No |
Privacy & Security
- All data stays on your machine. Log files are written to a local directory you control.
- No telemetry. PromptVault does not phone home, collect usage statistics, or contact any external server.
- No additional credentials. PromptVault uses the same GitHub Copilot authentication already established in VS Code. It never reads or stores your token.
- Prompts go only to GitHub Copilot's API — the exact same endpoint used by the built-in Copilot extension. No extra hops.
- Safe for enterprise environments with strict data-residency requirements — logs never leave the machine unless you explicitly export them.
Troubleshooting
@promptvault does not appear in the chat suggestions
- Verify both
GitHub.copilotandGitHub.copilot-chatare installed and enabled (Ctrl+Shift+X) - Verify PromptVault itself shows as Enabled in the Extensions panel
- Reload VS Code:
Ctrl+Shift+P→ "Developer: Reload Window" - Confirm VS Code is version 1.93 or later:
Help → About
"No GitHub Copilot language model is available"
- Open a regular Copilot Chat conversation (without
@promptvault) and check it works — if it doesn't, the issue is with the Copilot extension, not PromptVault - Make sure you're signed in to GitHub:
Ctrl+Shift+P→ "GitHub Copilot: Sign In" - Check that your enterprise Copilot license is active in your GitHub organization settings
Logs not appearing in the configured folder
- Run
@promptvault /status— it shows the exact path PromptVault is currently writing to - If the path shows
~/.promptvaultinstead of your configured value, re-checkpromptvault.savePathin Settings - Ensure VS Code has write permission to the target folder (especially important for network shares)
The log file has no entries even though I used @promptvault
- Confirm
promptvault.autoSaveistruein Settings - Check for any error notifications from PromptVault in the bottom-right corner of VS Code
The chat panel does not open with Ctrl+Shift+I
- The shortcut may differ depending on your keyboard layout or other installed extensions
- Alternatively: click the chat bubble icon in the VS Code Activity Bar (left sidebar) to open Copilot Chat
Building from Source
# 1. Install dependencies
npm install
# 2. Type-check — no output means zero errors
npm run compile
# 3. Build the extension bundle (outputs to dist/extension.js)
npm run build
# 4. Watch mode for development — auto-rebuilds on every file save
npm run dev
# 5. Package as a .vsix for distribution
npm run package
The bundled extension is a single file at dist/extension.js (~10 KB). The .vsix package includes only the files needed to run — source files and node_modules are excluded.
Project Structure
PromptVault/
├── src/
│ ├── extension.ts Entry point — activates the extension
│ ├── participant.ts @promptvault chat participant and slash commands
│ ├── storage.ts File I/O — reads and writes daily .txt logs
│ └── commands.ts Command Palette commands
├── icons/ Extension icons (16px, 48px, 128px)
├── dist/ Compiled bundle (generated by npm run build)
├── package.json Extension manifest, settings schema, npm scripts
├── tsconfig.json TypeScript compiler configuration
├── .vscodeignore Files excluded from the .vsix package
└── .gitignore
Version History
| Version | Date | Notes |
|---|---|---|
| 1.0.0 | 2026-05-08 | Initial release — chat participant, slash commands, daily logs, export |
PromptVault v1.0.0 — Built for GitHub Copilot Enterprise users who take their work seriously.