Curt Conversation Exporter — Chrome · Edge · Firefox 115+

The chat in your tab, as a .curt file.

One click on the extension and the conversation you're looking at — ChatGPT or Claude — becomes a single portable, spec-compliant .curt file on disk. No copy-paste, no cloud, no accounts.

Source on GitHub Build from source

What it does.

01
One-click export. Open a chat on a supported site, press Export in the popup — the whole thread, in order, lands as one UTF-8 .curt file.
02
Spec-compliant by construction. Output is .curt v1 per SPEC.md docs, and the test suite round-trips every file through curt-format's reference parseCurt.
03
Nothing leaves the browser. Zero collection, zero network calls — extraction and serialization happen entirely on your machine. Privacy policy.
04
Portable on arrival. The file opens in every app that speaks the format — the viewer, curt-openwith, or anything you build.

Where it works

Sites and browsers.

site	browser	notes
chatgpt.com	Chrome / Edge (MV3), Firefox 115+
claude.ai	Chrome / Edge (MV3), Firefox 115+

One codebase, two manifests. Chrome and Edge load the MV3 build; Firefox ships MV3 with strict_min_version: 115.0.

Getting it

In review.

The extension is in review for the Chrome Web Store and Firefox Add-ons (AMO) — store links will appear here once the listings are live. Until then, build it from source; it takes about a minute.

Build from source

Install it yourself.

# requires Node 18+
npm install
npm run build                      # tsc + Chrome staging -> dist/
node platform/firefox/build.mjs    # Firefox staging -> dist/firefox/

Chrome / Edge: open chrome://extensions (or edge://extensions), enable developer mode, "Load unpacked" → dist/.
Firefox: open about:debugging#/runtime/this-firefox, "Load Temporary Add-on…" → dist/firefox/manifest.json.

Tests: npx vitest run. Full development notes in the repo README.

Privacy, stated plainly.

The extension has no backend and makes no network requests. It reads only the conversation already open in your tab, serializes it locally, and hands you the file. That's the whole data flow — see the full privacy policy.