Read Dia Browser AI Conversations in a Proper Markdown Reader

Dia is The Browser Company's answer to the question nobody asked out loud but everyone was thinking: what if the browser was the chat client? Every tab has a sidecar AI that reads the page, answers questions, drafts replies, and keeps a running history you can revisit. That history is useful. It is also trapped inside the browser chrome, wedged into a narrow right-hand panel that was never designed for long-form reading.

If you use Dia seriously, you already know the pain. A twenty-minute research thread compresses into a scroll strip the width of a phone. Code blocks wrap mid-token. Tables collapse. Mermaid diagrams render as raw text. You end up copying the whole thing out into a note app to read it properly, and half the formatting dies on the way.

There is a cleaner path. Export the chat, open it in a markdown reader built for long AI output, and read it the way it was meant to be read. This post walks through what works, what breaks, and how the Prism MD workflow fits. None of it requires a plugin, a paid tier, or waiting for The Browser Company to ship a proper reader mode.

Why the Dia sidebar is not a reader

The sidebar is a great capture surface. It is a bad reading surface. Two hundred pixels of width is fine for a follow-up question, and it collapses under any real answer. The line length lands around forty characters, which forces the eye to snap back every second word. Reading speed drops by roughly a third at that width, which anyone who has read a paperback next to a phone-screen PDF already knows in their bones.

The sidebar also refuses to sit still. Switch tabs and the chat context follows the URL, so the answer you were reading gets replaced by whatever page you clicked. There is no persistent reading pane. There is no proper table of contents. Long threads get truncated in the scrollback after a few days of heavy use, which matters if you treat AI chats as reference material rather than throwaway conversation.

A dedicated reader flips the constraints. You get one long column at a sane measure, syntax-highlighted code, real math, real diagrams, and a history you own. The case for treating AI markdown as first-class typography has been made elsewhere. Dia's own team would probably agree in private. The sidebar is optimized for the next question, not the last answer, and the two goals pull in opposite directions.

Getting the chat out of Dia

Dia does not currently expose a native export button for chat threads. What it does expose is the underlying markdown. Right-click inside the sidebar, choose Select All, and copy. The clipboard receives clean markdown with fenced code blocks and preserved headings. Paste that into any plain-text file and save it with a .md extension.

For longer threads, the copy-paste route drops some structure. Ordered lists sometimes lose their numbering, and nested blockquotes flatten to a single level. A short fix routine solves most of it. Prism MD's fix broken markdown from AI copy-paste guide covers the exact regex passes we use to rebuild list markers and re-indent nested quotes in one go. Run it once and the file lands in a shape you can read.

If you want to skip the manual step entirely, a small userscript can hook Dia's internal chat store and dump each thread to a downloads folder as it closes. The Browser Company has hinted at a first-party export in a recent Verge interview, so this may become unnecessary soon. Until then, the clipboard route stays boring and reliable. Boring is what you want in an export pipeline, because clever pipelines break on the day you need them most.

Reading Dia chats the right way

Once the markdown is out, the reader does the heavy lifting. A good AI-first reader gives you four things the sidebar cannot. Each of them compounds over long threads, and the difference between a decent reader and a bad one shows up around message fifteen. Here is the short list:

• A single-column layout at 60 to 75 characters per line, which is the optimal line length for reading AI markdown.
• Real code rendering with copy buttons, language detection, and horizontal scroll on long lines.
• KaTeX for inline and block math, which Dia strips to raw LaTeX.
• Mermaid rendering for the flowcharts Dia loves to generate but refuses to draw.

Prism MD handles all four out of the box. Open the exported file, and the thread renders the same way a well-typeset article does. Headings get real weight. Blockquotes get a left rule instead of a color hack. Long code blocks scroll rather than wrap. The reading experience stops fighting you and gets out of the way.

Search matters more than people expect. Dia's own search is scoped to the current tab context, which means a thing you asked Gemini about last Tuesday is effectively gone unless you remember the tab. A local library of exported chats, indexed by full text, gives you back that memory. It is the same argument for keeping a personal knowledge base of your AI conversations, applied to a browser-native workflow. The archive becomes the second brain the sidebar pretends to be.

A workflow that sticks

Here is the loop that works after a few weeks of daily use. Chat in Dia as normal. When a thread crosses roughly fifteen exchanges or contains something you want to keep, copy it out and save it to a dated folder. Open it in Prism MD to read, annotate, or share. Delete nothing on the Dia side. The sidebar stays a scratchpad. The reader becomes the archive, and the two roles stop competing.

Two habits keep the archive useful over the long run. First, name files by topic rather than date, since date is already in the metadata and you will never search for 2026-09-11-chat-3. Second, prune once a month. Ten percent of chats deserve to be kept as reference. The rest were useful in the moment and can go. A ruthless monthly pass keeps the library from becoming a landfill.

FAQ

Does Dia sync chat history across devices? Only within the same Browser Company account, and only for a rolling window. Dia is not a long-term archive. If you want history you can trust in a year, export it now and stop hoping the sidebar will remember. The rolling window has quietly shortened twice in the last release cycle, which suggests the company treats it as a cache rather than a store. Treat it the same way on your end.

Will Dia break my exported markdown when it updates? The clipboard format has been stable through the last several point releases. Frontmatter and code fences survive. The safer bet is still to export as you go rather than in bulk after an update, because bulk exports tend to happen the week after something silently changed. If you notice a regression, save a raw HTML copy of the sidebar as a fallback until the next patch. That backup has saved us twice.

Can I share a Dia thread with a teammate? Not directly through the browser. Export the markdown, drop it in a shared folder, or use Prism MD's share link. See share an AI conversation with your team for the full flow, including how to strip identifying context before sending. Sharing raw sidebar screenshots is the worst of both worlds, since the reader loses code highlighting and the sender leaks tab context. Export first, then share.

What about privacy? Anything you paste into Prism MD stays local unless you explicitly publish or share it. Dia's sidebar chats, by contrast, are processed on The Browser Company's infrastructure. Read Dia's own privacy notes before piping sensitive work through the sidebar, especially anything under NDA. The safer pattern is to draft prompts locally, run only what you need through the sidebar, and archive the result outside the browser. That way the sensitive material never lives in a cloud you do not control.