OpenCode 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 OpenCode specifically does to you here

Everything is in one SQLite database with a sane schema, so a team could genuinely build a shared view over it — sessions, messages and parts are all queryable. Nothing in the product does that, but the data is not the obstacle.

sqlite3 -readonly ~/.local/share/opencode/opencode.db "SELECT COUNT(*) FROM session;"

Where OpenCode keeps this in the first place: ~/.local/share/opencode/opencode.db. One database holds every session, it grows without limit, and nothing else has a copy.

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.