Search six AI coding tools' prompt histories in one local dashboard

WorkedEvidence: Described by posterPosted Jun 10, 2026Last checked Nov 6, 2026

Al Amin Rifat's local dashboard searches prompt history across Claude Code, Cursor, Copilot, OpenCode, Windsurf, and Antigravity.

Source checked Nov 6, 2026
Results shared

How to use this

Tap Copy prompt.
Open the tool the case used (or a similar one) and paste the prompt; results may differ from the original.
Paste it into the message box.
Send it, then read the answer before acting on it.

New to this? What's a prompt?

A prompt is the message you send to the AI tool. Copy the one on this page, put your own details where it asks, and read the answer before you act on it.

Prompt

Recreated prompt

The source didn't share its exact prompt, so we wrote one from what it describes. The result shown is the source's, not ours.

What the prompt labels mean

The person didn't share their exact words, so we wrote this from what they described. We haven't tested it, and they didn't use this exact version.

Build a local read-only dashboard that ingests prompt history from Claude Code, Cursor, GitHub Copilot, OpenCode, Windsurf, and Antigravity into one SQLite index with search, filters, charts, and per-platform pages. Do not upload any prompts. Document each tool's on-disk format as you go.

Try this in:

ChatGPT Gemini Grok Claude

Sends the Recreated prompt shown above. ChatGPT and Grok open with it filled in, and ChatGPT may send it straight away. Gemini and Claude open empty, so we copy the prompt for you to paste. Every button also copies it.

The source used Claude Code, Cursor and Copilot, which can take actions on your computer or in a browser. These are general chat tools, so results may differ, and a normal chat may only give you a plan.

Opens in a new tab. We don't see what you send.

These links are only a shortcut. We're not affiliated with OpenAI, Google, Anthropic or xAI, and your results may not match the source.

Optional stronger version

Our rewrite with extra checks. The poster didn't test it.

Before you start, ask me 1–3 short questions about the details below and wait for my answers. Once I've answered, confirm the plan in one line and run the whole task start to finish.

Goal: Unify local AI-coding prompt histories into one searchable on-device dashboard.

Questions to ask me first:
- Which of the six tools do I actually use?
- SQLite path and retention?
- Any paths to exclude?

Inputs (fill in or confirm):
- Tools: [CLAUDE CODE / CURSOR / COPILOT / …]
- Index: [SQLITE PATH]
- Mode: [READ-ONLY]

Rules:
- Never upload prompt text.
- Read-only against vendor stores.
- Document each storage format.
- Show clear errors when a DB schema changes.

Checkpoint: Ingest one tool end-to-end before adding the next.

If you get stuck: If a format breaks, isolate that connector.

Verify before you finish: Search returns prompts that exist on disk.

Output: Dashboard with search, filters, and charts.

Done when: I can find an old prompt without opening six apps.

AI tools

Claude Code Cursor Copilot

Outcome

Al Amin Rifat reverse-engineered local prompt stores for Claude Code, Cursor, GitHub Copilot, OpenCode, Windsurf, and Antigravity, then built AI Prompt Monitor—a local Next.js + SQLite dashboard with filters by platform/project/date, full-text search, charts, per-platform pages, and one-click copy. Formats ranged from Claude Code's simple ~/.claude/history.jsonl to Cursor's ~700MB state.vscdb bubbles and Windsurf protobuf chat state. Everything stays read-only and on-device.

Evidence: Described by posterThe person describes what happened in words, without screenshots or video.

Source

Posted: Jun 10, 2026 by Al Amin Rifat
Last checked: Nov 6, 2026
Method:: How we verify

https://dev.to/alaminrifat/i-reverse-engineered-where-6-ai-coding-tools-store-your-prompts-and-built-a-dashboard-for-it-2pne

Context: Post dated Jun 10 on DEV; year taken as 2026 from surrounding 2026 tooling names (OpenCode, Antigravity).