Documentation
Everything you need to set up PromptCase and keep your prompts flowing. Capture them wherever you write them, reuse them wherever you work — one library behind all of it.
Getting started
PromptCase captures the prompts you write — never AI responses, system prompts, or tool output — and syncs them to your account. Setup takes three steps.
- 1
Create an account
Sign up free — no credit card needed. Your dashboard is where every captured prompt lands.
- 2
Pick a capture client
The CLI captures prompts from the AI coding tools on your computer — Claude Code, Cursor, Copilot Chat, Codex and more. The browser extension captures prompts you submit on 13 AI chat sites. Use either or both — all plans include unlimited devices.
- 3
Generate a device token and connect
In your dashboard, open Dashboard → Devices and generate a token for your client. Paste it into the CLI or extension once — refresh is automatic after that.
CLI (coding tools)
The promptcase CLI runs a small background helper that picks up the prompts you write in the AI coding tools already installed on your computer, and syncs them to your account roughly every 60 seconds. Only your own messages are captured — assistant replies, tool output, and system messages are filtered out.
Tools it captures from
- Claude Code
- Claude Desktop
- Claude for VS Code
- GitHub Copilot Chat
- Cursor
- Cline
- Blackbox
- OpenAI Codex
- Google Antigravity
One install covers all of them — there is nothing to configure per tool. The CLI only looks at tools you actually have, and each one syncs independently, so a tool you don't use simply never appears. In your dashboard every prompt is labelled with the tool it came from.
Install
Requires Node.js 22.5 or newer. To check what you have, run node --version.
Authenticate
Then paste the token from /dashboard/devices/cli-token when prompted. The daemon starts automatically and keeps running in the background, including after reboots.
Commands
promptcase setup | Authenticate and start the daemon (alias of init) |
promptcase status | Show auth, daemon, and sync status |
promptcase sync | Force a sync right now and run diagnostics |
promptcase show | Show recent synced prompts (-n <count> for more) |
promptcase stop | Stop the daemon (auto-start stays for next boot) |
promptcase logout | Stop the daemon, revoke the token, clear credentials |
promptcase init is the same command as promptcase setup — use whichever you prefer.
Package details and release notes live on npmjs.com/package/promptcase.
Browser extension
The extension captures prompts at the moment you submit them — and only the text you wrote. It works on these 13 sites:
- ChatGPT
- Claude
- Gemini
- Microsoft Copilot
- Perplexity
- Mistral Le Chat
- HuggingChat
- You.com
- Poe
- Grok
- Bolt
- Lovable
- Replit
Chrome, Edge & Brave
- Install from the Chrome Web Store — the same listing also installs in Edge, Brave, and other Chromium browsers.
- Open the extension's Options page and paste the token from /dashboard/devices/extension-token.
- Optionally toggle capture per site under Options → Sources.
Firefox
- Install from addons.mozilla.org.
- Open the extension's Options page and paste the token from /dashboard/devices/extension-token.
- Optionally toggle capture per site under Options → Sources.
VS Code extension
The other two clients capture prompts. The VS Code extension is about using them: search your library without leaving the editor, and paste the prompt you picked into whichever AI chat you use.
- Search with Ctrl+Alt+P (Cmd+Opt+P on a Mac) or the PromptCase button in the status bar. Press Enter and the prompt is copied, ready to paste.
- A Prompts sidebar with your favourites and most recent prompts — hover to preview one, click to copy it.
- Save whatever you've copied straight into your library, and improve a rough draft with Enhance.
Full install steps for Windows, macOS and Linux are on the VS Code extension page.
MCP server
MCP is a standard way for AI tools to connect to outside services. Connect PromptCase once and your AI assistant can search your library, read a saved prompt, save a new one, and improve a draft — from inside the chat, without you switching windows.
It works with Claude Code, Claude Desktop, Cursor, VS Code, Windsurf, Codex and other MCP-capable tools. Your starred prompts also show up as slash commands in the clients that support them.
Setup is two steps and there is a ready-made snippet for each app on the MCP server page.
Managing your library
Captured prompts land in your dashboard, where you can shape them into a reusable library:
- Tags — label prompts with as many tags as you like, then filter by them.
- Folders — group prompts by project or topic.
- Favorites — star your best prompts so they're one click away.
- Search — keyword filtering across your prompts, combinable with tag, folder, source, and favorite filters.
- Bulk actions — select multiple prompts to tag, move, or delete at once.
- Sources view — browse prompts by where they were captured, whether that was a coding tool on your machine, one of the 13 supported chat sites, or a prompt you saved yourself.
- AI features — optional and off until you turn them on. They can name and tag your prompts for you, search by meaning rather than exact words, and rewrite a rough draft into a sharper prompt. Switch them on under Dashboard → AI Brain.
Devices & tokens
Every capture client connects with its own device token, managed from Dashboard → Devices:
- Generate a token per device and give it a name you'll recognize ("Work laptop", "Home Firefox"). You can rename devices later.
- Tokens are shown once. We store only a SHA-256 hash, so copy the token when it appears. If you lose it, revoke the device and generate a new one.
- Tokens are valid for 180 days and refresh automatically while the client is in use — no re-pasting needed.
- Revoke any device from the dashboard at any time; its tokens stop working immediately.
Troubleshooting & support
Capture isn't working on a site
- Check the site's toggle in Options → Sources — it may be switched off.
- Make sure you're signed in to the site itself; some sites render a different composer for signed-out visitors.
- Still stuck? Email support@promptcase.dev with the site name and your extension version (shown in Options → About).
A prompt I wrote while a source was turned off won't sync after I turn the source back on
This is on purpose — it's a privacy safeguard, not a glitch. When capturing is switched off for a site (in Options → Sources), anything you type there is meant to stay private, so the prompt is thrown away instead of saved.
To make sure it stays thrown away, the extension needs some way to recognise that same text if it shows up again. So it keeps a short scrambled number worked out from your prompt — a number, never the words you wrote (a content hash). That number stays inside the browser tab you were using: it is never sent to us, never leaves your computer, and is never stored in your PromptCase account. Your browser deletes it the moment you close the tab. Until then, that exact text is skipped even if you switch capturing back on and type it again — which is what stops a private prompt from being saved by mistake.
If you actually do want to save one of those prompts: close the tab (or open the site in a new tab), make sure the source is turned on, and type it again — it will sync normally. Brand-new, different prompts are never affected and keep syncing as usual.
Nothing is syncing from the CLI
status shows auth, daemon, and sync state; sync forces an upload and runs diagnostics.
For anything else, write to support@promptcase.dev — we reply within 1–2 business days.
Free plan: your latest 500 prompts, every source, unlimited devices.