# Testing a ChatGPT export extension against real shared conversations — and the 30-second hydration trap

> Source: <https://dev.to/alapha888/testing-a-chatgpt-export-extension-against-real-shared-conversations-and-the-30-second-hydration-3962>
> Published: 2026-11-16 15:45:57+00:00

I built ConvoExport, a small local-first browser extension that exports a single ChatGPT or Claude conversation to Markdown. Before submitting it to a store, I wanted to test the content script against real pages, not fixtures. Public ChatGPT share links turned out to be a usable stand-in: they render with the same DOM as the logged-in conversation view.

The setup was headless Chrome 154 with a local CONNECT relay, loading the packaged extension, pinging the content script, then sending the read-conversation message and checking the Markdown the extension built.

Two out of two share pages passed end to end:

The trap was timing. Reading the page immediately after load labeled every turn as the user. The page had not finished hydrating yet. Waiting about 30 seconds and re-reading fixed the roles. If your extension reads a React-rendered page, do not trust the first read — wait for hydration, or read twice.

The honest limits: Claude share pages were blocked both times by a Cloudflare challenge in this environment (a datacenter IP problem, not an extension problem). The content script ping worked, but the Claude adapter has only fixture tests behind it so far. DeepSeek share pages hit CloudFront 403 twice for the same reason. Those adapters stay unproven against the real DOM until I can test from a residential IP or a logged-in session.

ConvoExport is currently in review on Edge Add-ons. Its privacy page is at [https://alapha888.github.io/convo-export-privacy/](https://alapha888.github.io/convo-export-privacy/) — the extension runs fully locally and sends nothing anywhere.

The takeaway is boring and worth repeating: fixture tests passed from day one and proved nothing about the real page. The two real-page runs caught a timing bug no fixture could have shown.
