cd /news/ai-tools/testing-a-chatgpt-export-extension-a… · home › topics › ai-tools › article
[ARTICLE · art-170672] src=dev.to ↗ pub= topic=ai-tools verified=true sentiment=· neutral

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

A developer built ConvoExport, a local-first browser extension that exports single ChatGPT or Claude conversations to Markdown, and tested its content script against real public ChatGPT share pages using headless Chrome 154 with a local CONNECT relay. Both share pages passed end to end, but the tests exposed a hydration timing bug: reading the page immediately after load mislabeled every turn as the user, and waiting roughly 30 seconds before re-reading corrected the roles. Claude and DeepSeek share pages could not be validated because Cloudflare and CloudFront challenges blocked access from the datacenter IP, leaving those adapters backed only by fixture tests.

by read1 min views1 publishedNov 16, 2026

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, 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/ — 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.

── more in #ai-tools 4 stories · sorted by recency
── more on @convoexport 3 stories trending now
sponsored brought to you by zahid.host 4,200+ EU-deployed projects
reading about agents? ship yours in a single git push.

Run your AI side-project on zahid.host

EU-based hosting, git-push deploys, automatic HTTPS, no cold starts. Free tier with a custom domain — perfect for shipping the agent you just read about.

$git push zahid main
→ Live at https://your-agent.zahid.host ✓
Get free account → Pricing
from €0/mo · no card required
LIVE [news/testing-a-chatgpt-ex…] indexed:0 read:1min 2026-11-16 · —