DEV Community

Building a ChatGPT/Claude conversation exporter: MV3, dual-target packaging, and offline Pro checks

I built ConvoExport, a browser extension that exports a single ChatGPT or Claude conversation to Markdown, HTML, or DOCX. It is in review on Edge Add-ons.

This post is about what the build actually looked like - no launch claims, no Pro for sale yet.

What it does

One conversation at a time. Free tier: 3 exports a day.

The export pipeline is my own code: HTML-to-Markdown conversion plus a hand-written DOCX builder - no document library, no server. Everything runs locally; the extension makes zero network requests of its own.

What real-page testing caught

I tested against real public shared conversations, not fixtures:

  • ChatGPT: 2/2 passed. One 14-round conversation exported as 6,264 bytes of Markdown; one 5-round conversation with long assistant replies exported as 30,636 bytes, with roles alternating correctly.
  • The trap: reading the page immediately after load marks every message as the user. The page needs about 30 seconds to hydrate before roles read correctly. My popup now waits and re-reads instead of trusting the first pass.
  • Claude: 2/2 blocked by a Cloudflare challenge in my test environment. The content script pinged through, but the adapter never saw a real Claude DOM. The Claude adapter currently has fixture tests only - I am saying that plainly rather than claiming a real-page pass I do not have.

Dual-target packaging

One codebase, two store packages: Chrome (service_worker) and Firefox (scripts + a Gecko ID). The test suite is 71/0.

A packaging bug worth noting: an early Edge submission failed validation because the package contained two manifest.json files - the packager copied the whole src/ tree and also wrote a derived manifest at the root. The fix was to strip manifest.json from the staged src/ tree and add a self-check that fails the build if more than one manifest.json is present. Rebuilt packages passed validation.

Pro verification, offline

The Pro tier is designed as a one-time activation code, verified offline against a public key bundled in the extension. No account, no license server to call home to.

The code-issuing side is not live yet, so there is nothing to buy - the free tier is what ships first.

Links

Read on DEV Community ↗ ← Back to News

Comments

No comments yet. Start the discussion.