backrun

Interesting. I wonder if this will evolve into something closer to Codex or Claude Code, where it can actually work across files and tasks on your computer, not just act as a desktop chatbot.

did'nt realize exporting to pdf was this straightforward. The word export keep the formatting intact too. helpful video

you saves me. did'nt know you could get clean markdown out of chatgpt like this. The manual way works, but extension is much faster for long chats

Didn't know Claude had this option. Tried the extension, exporter a long chat to markdown in one click. Clean output, work well with Obsidian

Just tried ai chat exporter. Export a long ChatGPT thread to word, table and formmatting came out clean. Been looking for something like this. thank you

try this gemini to wor or pdf extension yesterday. Exported a long response, table came out clean in word. didn't expect it work that well

Nice idea. Curious how well it handle tables and images

I suspect the most the reliable approach is to stop treating the model as the syntax checker. Let it propose a small diff, then run the result through check-parens, the language parser, or a formatter before accepting the change. if valifation fails, feed back the excat parser error and smallest affected form rather than the entire file

tried HTML deployer after generating a landing page in Claude. Had a live URL before I finished my coffee. Thanks

I used it for a few long ChatGPT threads with code and tables. Copy-paste usually messes up the formatting, but this saved it pretty cleanly.

Good extension.

Installed it. Exported a long research thread to Notion and it came through clean. The code blocks actually preserved formatting which I did not expect.

I've been looking for a proper Gemini to Word converter for months. Every tool I tried either flattened the code blocks or just exported plain text with no structure. Does this actually preserve heading hierarchy in the DOCX output?

The biggest problem when you export Gemini chat isn't finding a method — it's that almost every method destroys your formatting.

Code blocks collapse into plain text. Tables fall apart. Bold and italic disappear. I went through every option available and documented exactly what breaks and what doesn't.

1. Manual copy-paste (everyone's default)

Paste into Word: gray backgrounds, broken tables, lost structure.

Paste without formatting (Ctrl+Shift+V): bold, code, tables — all gone.

Either way, formatting loses.

2. Print to PDF (Ctrl+P → Save as PDF)

Exports the entire browser UI — menus, avatars, input box included.

Long code blocks get cut mid-page. Looks nothing like a clean document.

3. Gemini's built-in "Export to Docs" button

Only exports single responses, not the full thread.

Useless for long research sessions. Tables still shift on complex layouts.

4. Share link

Creates a read-only public URL — not a file.

Doesn't solve the export Gemini chat to document problem at all.

5. Google Takeout

Exports full history as raw HTML or JSON.

Technically complete, practically unreadable for day-to-day work.

6. Chrome extension (the only one that actually works)

After going through all of the above, I built Gemini Exporter — a Chrome extension that exports Gemini chat to Word, PDF, Google Docs, or Notion while preserving everything: code blocks, tables, headings, math notation, full conversation structure.

One click. Nothing leaves your browser for Word and PDF exports.

More info: https://backrun.co/gemini-exporter

Really cool project. I like that you are focusing on preserving code and context instead of doing a naive text replacement pass. The one click GUI approach also makes this much more accessible for ROM hack communities that are not very technical. Curious how well it handles edge cases like custom text encodings, variable width fonts, and script expansion when the translated text is much longer than the original.

Damn, HN is almost my age too.

Thanks so much, this genuinely means a lot.

Gemini Exporter came from the exact same frustration, so it is great to hear it helped you. For anyone who wants to try it, here is the extension: https://chromewebstore.google.com/detail/gemini-exporter-sav...

Really appreciate the support, and I would love to hear any feedback as you keep using Gemini Exporter, especially on longer chats or code-heavy conversations.

Interesting project. Monitoring how ChatGPT, Gemini, and Claude cite a site over time feels genuinely useful, especially since most teams currently have to rely on scattered manual checks. I also like that Canonry is self-hosted and SQLite-based instead of being another black-box dashboard. Curious how you handle query selection and repeatability so the visibility scores stay comparable over time.

Good question — that is exactly where tools like this either become useful or fall apart.

For DOM changes, I try not to couple the parser too tightly to fragile selectors. The extraction layer leans more on structural patterns in the rendered chat tree, and I keep the export pipeline separate from the Gemini-specific parsing so I can update that layer without rewriting the whole exporter.

For tricky formatting cases:

nested markdown is normalized into an intermediate representation first, then mapped to Word, PDF, Google Docs, or Notion

code blocks are preserved as their own block type so they do not get flattened into regular paragraph text

large tables are probably the weakest area right now, especially when Gemini renders them inconsistently or with wrapped cells

I am also building a small regression set from real chats, so when Gemini changes something in the UI I can catch breakage faster instead of fixing issues one by one.

Still early, so I would not claim every edge case is solved yet. The goal is to fail gracefully: preserve the content first, then keep as much structure as possible.

If you have a nasty sample with nested markdown, wide tables, or code-heavy output, I would genuinely love to test against it.

I built Gemini Exporter because I use Gemini daily for research and coding, but getting the formatted output—especially complex markdown, tables, and code blocks—into my workspace was a frustrating copy-paste exercise that often broke the formatting.

It's a browser extension that injects export options directly into the Gemini UI, allowing you to push conversations to Notion, Google Docs, or download them as Word/PDF files with a single click.

How it works: > Under the hood, it parses the chat DOM to extract the raw markdown and context. For local exports (PDF/Word), the file generation is handled entirely client-side. For cloud exports (Notion/Google Docs), it connects to their respective APIs, ensuring the markdown syntax is properly converted into Notion blocks or Google Docs formatting.

A note on privacy: > Since chat history can contain sensitive data, privacy was a priority. The extension does not collect, track, or route your conversations through any middleman servers. Everything is processed locally in your browser, and API keys (like your Notion integration token) are stored strictly in your local browser storage.

I'd love for you to try it out. I’m currently looking for feedback on how it handles complex code snippets or edge-case formatting. Happy to answer any technical questions about building it or the DOM parsing process!

F# hits a sweet spot that's hard to explain until you've used it: you get the conciseness of a scripting language but with a type system that catches errors before you run anything.

For automation specifically, the pipe operator (|>) makes data transformation chains read almost like pseudocode. Compare that to Bash where you're constantly context-switching between quoting rules and subshell behavior.

The thing that keeps me coming back is that F# scripts scale up. A quick .fsx file can grow into a proper project without rewriting anything — same language, same idioms. With Python you often hit a point where the "script" needs to become "real code" and there's a refactor involved.

The downside is real though: cold start on dotnet fsi is noticeable, and the ecosystem for quick one-liners isn't as mature as Python's. For anything touching data science or quick API calls, Python still wins on available libraries alone.

But for internal tooling, build scripts, and anything where correctness matters more than iteration speed — F# is underrated.

Fair concern — that's the most common failure mode for extensions like this. A few things I've built in to reduce breakage:

First, the parser doesn't rely on a single fragile selector chain. It targets multiple fallback identifiers per element type, so if Google renames one class, the others still catch it. It's not bulletproof but it degrades gracefully rather than exporting blank files.

Second, I'm running a lightweight automated check that pings the extension against a fixed Gemini conversation daily. If the output diff crosses a threshold, I get alerted before users notice.

Third — honestly — the extension is small enough that I can ship a patch within 24–48 hours of a breaking change. That's one advantage of not having a 6-week release cycle.

It will break at some point. I'd rather be upfront about that than oversell stability. The goal is to fix it fast when it does.

I built a ChatGPT to PDF Extension that lets you export any ChatGPT conversation into a neatly formatted PDF with one click.

I use ChatGPT for specs, drafts, client notes, and internal docs. The annoying part was always the last mile: copy-paste, fix formatting, make it readable, then share. This extension turns a chat into a PDF you can actually keep, print, or send around.

What it does ● Adds a Save as PDF button directly on the ChatGPT page ● Exports long conversations into a document-like layout with clear turns and spacing ● Keeps tricky content readable in the PDF, including code blocks, tables, formulas, and images depending on settings ● Lets you export only selected sections and optionally exclude prompts for cleaner sharing ● Before exporting, you can customize typography and styling, including font, font size, and text color

How it works ● Install and pin the extension ● Open any ChatGPT conversation ● Click Save as PDF, adjust styling and export options, then download

Link ChatGPT to PDF Extension: https://chromewebstore.google.com/detail/export-chatgpt-conv...

I’d love feedback ● What would make this feel truly production-ready for you: cover page, table of contents, page numbers, header/footer branding, templates, redaction, or something else ● In your workflow, what matters most when exporting: code, tables, math, or images

If you try it, I’d love to hear what breaks or what you’d want improved.