u/Unixwzrd

I built a Safari extension for reading web pages with local TTS

I’ve been using TTS to proofread some of the longer technical articles I’ve been writing, and eventually wanted the same thing for arbitrary web pages.

So I built WebReader. It uses Mozilla Readability to extract the useful content from a page and sends it to my local TTS stack. It can read the whole article, start from where you are on the page, or just read selected text.

It’s open source and still a little rough around the edges, but it’s useful enough that I figured I’d release it and see what other people think.

More details, screenshots, setup and source:

https://unixwzrd.ai/projects/WebReader/2026/09/08/webreader-introduction/

I’d be interested in feedback, particularly websites that manage to break it.

Give it a shot and let me know what you think.

I’ve seen a number of people here asking about exporting individual ChatGPT conversations, so I thought this might be useful to some Mac/Safari users.

I’m the developer of LogGPT, a Safari extension I originally built because I wanted a simple way to save an individual ChatGPT conversation as structured JSON instead of relying on the account-wide export.

One thing kept bothering me, though: a ChatGPT conversation isn’t necessarily just the text.

I routinely have screenshots, PDFs, spreadsheets, code archives and other files that I’ve uploaded as context, along with images, documents, audio and other artifacts ChatGPT has generated during the conversation. Saving the JSON while losing those files isn’t really a complete archive.

So the new LogGPT Plus upgrade can preserve those as well. You can export generated artifacts, uploaded artifacts, or both. It creates a ZIP containing the conversation JSON, the files, and a manifest describing what was found and what was successfully downloaded.

If one artifact can’t be recovered, it doesn’t throw away the export. It saves everything it can and records the failure in the manifest.

Everything is handled locally. There are no LogGPT accounts, analytics, telemetry, or external processing service. The basic JSON export is still there and works the same way it always has.

It’s a Safari extension for macOS, so obviously this won’t help someone using Chrome or Windows. But if you’re on a Mac and have been looking for a way to keep individual ChatGPT conversations locally, particularly conversations containing files, that’s exactly the problem I built it to solve.

I also built an open-source companion tool called extract-chat that takes either ChatGPT/OpenAI conversation JSON or a LogGPT Plus ZIP and turns it into readable Markdown or HTML. When artifacts are available, it preserves the local references so the resulting document stays connected to the files from the conversation.

So the workflow can be as simple as: export the conversation and its artifacts with LogGPT Plus, then use extract-chat to turn that archive into something you can actually read, search, keep in a project, or browse offline.

If you’ve ever downloaded ChatGPT history, opened the JSON, and thought, “What am I supposed to do with this?”, that’s basically the problem extract-chat solves. It’s open source as well.

The project is open source if you’d rather inspect the code or build it yourself, and extract-chat is open source too.

More information, screenshots, links to the source and Mac App Store: https://unixwzrd.ai/s/39e7b3ae47/

I’d also be interested in hearing about artifact types or weird ChatGPT conversations these tools don’t handle. ChatGPT’s conversation format has changed quite a bit over time, so unusual cases are genuinely useful to me.

The content type selection which pops up after ``` is extremely annoying and needs to go. It never "guesses" the correct content type, at least not for me.

This showed up after the recent update. Remove it or make it optional, I know no one from OpenAI will probably read this, but they don't read "bug/enhancements" on their help site and don't have any way of easily filing these sorts of reports, at least not that I have found.

Does anyone know of where I could file this annoyance?

I kept running into .env clear text sprawl and stuff leaking into argv and shell history, so I built a local-first approach using macOS Keychain + exec-time injection (seckit run).

It solved the launchd problem cleanly - no secrets in plists, no .env files, no argv leakage, and nothing ending up in command history from exports or CLI flags.

It's not just for agents either - same pattern works for things like PostgreSQL, where you'd normally end up with .pgpass or PGPASSWORD floating around.

Tradeoff is you need to restart to pick up changes, but that's been manageable so far.

Wrote it up here: https://unixwzrd.ai/projects/Secrets-Kit/2026/05/04/launchd-seckit-run-and-invisible-env-vars/

Curious what others are doing here, especially for long-running processes. I'm sure there are edge cases I haven't run into yet.