Cursor history: sharing across a team

How does the rest of the team see what I asked the AI?

Why this is hard

AI coding history is private by construction. Every tool writes it to the machine it ran on, under the account that ran it, in a location no colleague will ever open. That is a reasonable default for a cache and a poor one for the only written account of why a change looks the way it does.

What Cursor specifically does to you here

All conversations live in one SQLite file per user. Sharing means handing over a multi-gigabyte database, and there is no per-conversation export — so in practice sharing is a screenshot.

ls -lh ~/Library/Application\ Support/Cursor/User/globalStorage/state.vscdb

Where Cursor keeps this in the first place: ~/Library/Application Support/Cursor/User/globalStorage/state.vscdb. One SQLite file holds every conversation. Corruption, an upgrade, or a cleanup takes all of it at once.

What a working answer looks like

A working answer means one place where a lead can read what the team asked and what came back, without asking anyone to export anything by hand.

Start by measuring what you have. npx promptwake doctor reports what every AI tool on the machine is holding and how much of it sits inside a deletion window — no account, writes nothing, sends nothing anywhere. If the conclusion is that the record should not depend on one laptop, that is what PromptWake captures: prompt, response and the resulting diff, local by default and synced into a shared timeline on the paid tiers.