Keep a copy of any AI chat you can trust.
Intact takes a ChatGPT or Claude conversation out of the browser - the answers, the reasoning, the searches it ran, the files you gave it - and ends every export by telling you plainly what it could not save.
Not on the store yet. It is being built in the open, on ChatGPT and Claude, and it will be free.
Most exporters hand you a file. This one tells you whether the file is complete.
Every other exporter answers "can I get my chat out as a file?", and most of them can. Intact answers a harder question: is the file complete, and how would you know? An export that silently drops a PDF the assistant read, or the three searches behind its answer, looks perfect and is quietly wrong. So every export ends with a report of itself: what was captured in full, what by name only, and what could not be reached at all.
The rule this produces
A file contains content, or it contains a marker explaining an absence. There is no third category, and nothing disappears without a line of text where it used to be.
Three people who already have a workaround they dislike.
Wants the work out
Months of useful thinking inside a chat window and no way to keep it anywhere else. Copy-paste loses the code formatting and every image. Wants a real file in a real folder.
Moves between models
Runs the same problem past two assistants and needs to carry the thread across, instead of rebuilding the context by hand, badly, from memory.
Needs it to be defensible
A researcher, consultant or lawyer for whom "the assistant said so" is not enough. Needs to show what it read and what it did before it said so.
Read from the platform's own data, not scraped off the screen.
Length is irrelevant and nothing is missed because it does not depend on what is visible. Everything below is built and tested.
Markdown
A readable transcript with front matter, ready for Obsidian, a repository, or anything that reads text.
Markdown and files, as a folder
The transcript plus every image and document, zipped. The only sane container when a conversation has files.
JSON
The complete structured record for anything that will read it later, self-contained or pointing at the files beside it.
Through the browser's own print engine, unlimited and login-free. The leading competitor caps this at three a day behind a sign-in.
Nothing leaves the browser, and you decide what happens.
No server exists to receive anything
Four permissions, two websites, no build step, readable source. Nothing is uploaded because there is nowhere for it to go.
Reading is a decision
The panel identifies the conversation on its own. Reading it, which downloads every file, waits for a click.
See it before you save it
The preview is the file. They cannot diverge, and a test enforces it.
Choose how much
Everything, the last ten or twenty turns, or the opening and the end. An export that lost nothing never claims it was trimmed.
The lines it will not cross, on purpose.
- Sync to a cloud service. The category's most common paid feature. It would require sending your conversations to a third party, which ends the one claim worth making.
- Accounts, limits, or telemetry. No sign-in surface exists in the code, and nothing counts what you do.
- Claim anything the model never sent. The system prompt, internal traces, token probabilities. These never reach the browser, so no honest tool can export them.
Free, and in development
Intact will be free, with no account and no paid tier waiting to appear. It is not on the store yet: the conversation capture, the reasoning, the searches, the files and the export report are built and tested, and a short list of things stands between it and a listing.
When it ships it will appear on the tools page and in the release notes. Until then, this page is the honest state of it.