Just lost 6 hours of debugging context. Where did my chat history go after the update?
threadkeepjoin the waitlist
Local-first · Cursor· Windsurf· Claude Code
Permanent chat history.Finally.
Threadkeep reads Cursor's local SQLite, indexes every prompt across every workspace, and gives you ⌘K spotlight search. Your data never leaves your machine.
Early-bird pricing locked for the first 100. Money back if we don't ship by Sept 1, 2026.
⌘Kthreadkeep
escsearch:
▸"the stripe webhook handler should verify signatures using the raw request body before parsing JSON, otherwise…"
innout · 2 weeks ago · composer
▸"fix the signature verification in webhooks/route.ts to use the new construct event helper from stripe v17"
innout · 3 weeks ago · chat
▸"explain how stripe webhooks work for subscription billing — i need to handle invoice.paid and customer.deleted"
learning · 4 months ago · composer
▸"i need a stripe webhook for refunds — looks like the test events aren't firing for partial captures…"
side-project · 8 months ago · chat
3,184 chats · 8 workspaces · indexed locallylive
⌘K · live demo · the actual interface, eventually
Proof
We're not the only ones.
There's a thread on forum.cursor.com running since 2024. Hundreds of comments. Cursor still hasn't shipped it.
Threadkeep was built for these people.
forum.cursor.com/t/permanent-chat-historyPermanent history would be the #1 feature for me. I'd pay extra for a 'Pro' tier just for this.
This is honestly insane that it doesn't exist yet. Every other coding tool has it.
Can we please get an ETA on this? Asked in May, asked in August, asked in October.
Same. Lost everything when I switched workspaces last week. The undo only goes back 50 steps.
+1, this is becoming a deal-breaker for paid plans. I literally cannot rely on this tool for serious work.
How is this still not a thing in 2025?
Bumping. Two years now. Should I just write a SQLite reader myself?
I switched to Windsurf because of this. Anyone else made the move?
Composer history is gone after restart. Why. Why is this acceptable.
How it works
Five things, in order.
- 01
Install
One-line install. macOS daemon registered as a LaunchAgent. No Cursor restart. No editor extension to maintain.
- 02
Read
Reads Cursor's SQLite database read-only via WAL. Zero risk of corrupting your editor state or chats.
- 03
Index
Every chat across every workspace flows into a local FTS5 index. Cross-workspace search becomes trivial — and instant.
- 04
Search
Press ⌘K anywhere. Spotlight-style fuzzy search across years of prompts in milliseconds. Filter by workspace, tag, date.
- 05
Export
Folders, tags, markdown export. Your archive is yours, in formats you can read in 10 years — even if Threadkeep is gone.
Privacy by design
Your prompts never leave your machine.
Privacy isn't a feature we ship. It's the architecture. Threadkeep runs as a local daemon, reads from a local database, writes to a local index, and serves search results from your machine to your machine.
- ✗No cloud sync
- ✗No telemetry on chat content
- ✗No "we use your data to train our models"
- ✗No analytics on what you're searching
- ✗No remote license server pinging you on every keystroke
- ✓License key validates once a day. That's it.
Roadmap
One archive,
every coding tool.
v1 · shipping by Sept 1, 2026
Cursor
The deepest pain. Two-year-old forum thread. Where we start.
v2 · planned
Windsurf
Same SQLite shape. Almost zero extra work to support.
v3 · planned
Claude Code & Copilot
One archive across every coding tool you use. The endgame.
Waitlist
Reserve your spot.
We'll email when early access opens. We won't email you for any other reason. Unsubscribe in one click — there's even a link in our welcome email.
First 100 — early-bird pricing locked.
Money back if we don't ship by Sept 1, 2026.