Trove

Files Claude writes live only inside the conversation that produced them. To read one you click its card. To keep one you download it — and it becomes a loose file with no memory of where it came from, and no way to know when Claude has changed it since. Trove keeps those files on your machine, grouped by the conversation that made them, and keeps the link back. WHAT IT DOES • Keep — a button on every file card in a conversation, and a panel that takes the whole conversation at once, with per-file progress. • Browse — conversations on a rail, files in a table. One column tells you which of your copies have fallen behind. • Read — any file opens full width on its own page. Nothing the extension owns is ever drawn over the document. • Edit — a real editor with syntax highlighting. Edits stay local; they never travel back to the conversation. • Re-pull — when Claude changes a file, Trove says so. One click takes the current version. If you had edited your copy, it asks first. • Screenshot — save a picture of a rendered file, full page or visible area. • Optional auto-capture, off by default. PRIVACY Trove has no server, no account and no analytics. It makes no network requests except to claude.ai, using the session you already have, to list and download files from the conversation you are looking at. Everything it keeps lives in the extension's own storage on your machine. The only thing that ever leaves your browser is a file you explicitly export. OPEN SOURCE MIT licensed, source at https://github.com/UrsaCode/trove Trove is an independent project. It is not affiliated with, endorsed by, or sponsored by Anthropic.