Yesterday a small Chrome extension shipped that fixes my least favorite habit: pasting raw Reddit threads into an LLM and watching the context window fill up with junk. Step 2 of the workflow is the twist.
It’s called ThreadToLLM, and u/Accurate-Skill3425 posted it in r/PromptEngineering.
What’s new
You know the mess when you copy a good troubleshooting thread. Karma counts, timestamps, avatar icons, ads, bot disclaimers. Thousands of tokens that tell the model nothing. ThreadToLLM strips all of that out. The author says a thread of about 4,000 bloated tokens comes out around 600 dense ones. That’s roughly 80% less.
Why does that matter beyond the cost? Every token of junk competes with the tokens you care about. If you’re working with a long thread, or stacking several threads in one prompt to compare answers, the savings add up fast. Four threads at 4,000 tokens each is 16,000 tokens of mostly noise. Four threads at 600 is 2,400 tokens of signal, and you still have room for your actual question, your own notes, and a long answer. It also helps on smaller local models, where the context window is tight and every wasted token hurts.
The twist
The twist isn’t the token savings. It’s what the tool keeps.
It rebuilds the comments as a nested Markdown tree, so the model can see who replied to whom. Flat copy-paste loses that, and that’s where models start inventing conversational context. Picture a thread where one commenter suggests a fix, three people reply that it broke their setup, and one person replies to those with the real workaround. Flattened, that reads like five unrelated opinions. Nested, the model sees a proposal, the pushback, and the resolution. It also tags the original poster with (OP), so the model can follow that person across a long thread. When OP comes back to say “that didn’t work, here’s my log,” the model knows whose log it is.
And it runs 100% client-side. No backend, no telemetry, MIT license. Your threads never touch someone else’s server.
Mini-workflow
- 🧭 Grab the extension from the GitHub repo (mkarimdev/ThreadToLLM). Load it unpacked in Chrome if you want to read the code first.
- 🖱️ Open a Reddit thread. A small button shows up next to Share. Or hit Alt+Shift+C.
- 📋 Paste the clean Markdown into Claude, ChatGPT, or a local model.
- 🎯 Ask your question. Summarize the debate, pull the accepted fix, or list the disagreements.
A few prompts that work well with the nested format: “Give me the final recommended fix and who suggested it.” “Which replies contradict the top comment?” “Write a checklist from the steps people confirmed worked.” Because the tree shows who confirmed what, the model can separate “someone suggested this” from “three people said it worked.”
Right now it supports modern Reddit (the shreddit layout). The code uses modular platform adapters, so Hacker News and X are the obvious next targets. PRs are open if you want to write one.
Pro tips
- Expand the replies first. One commenter pointed out the real risk: if replies haven’t loaded, you feed the model half a thread and get a confident summary that misses the comment saying the whole answer is wrong. Open the collapsed branches before you hit the button. On big threads, click the “load more comments” links too. That’s also a good feature request for the repo.
- Ask the model to attribute claims. With the reply tree and OP tags intact, “who disagreed with the OP, and why?” actually works. You can also ask it to quote the exact comment behind each claim, which makes it easy to spot-check the answer against the original thread.
- Sanity check the output once. Paste a thread, skim the Markdown, and confirm the comment you care about made it in. It takes ten seconds and tells you whether the extension handles that thread’s layout.
- Save the cleaned Markdown. If a thread holds a fix you’ll want again, keep the dense version in your notes. It’s small, readable, and ready to reuse in a future prompt.
- Someone in the comments ran the repo through Claude for a security and stability review, and the verdict was that it’s safe, though they raised concerns about lost context. Treat any extension the same way: it’s open source, so read it or have a model read it before you install.
I like small tools like this. One job, no account, no tracking.
If you feed Reddit threads to LLMs, try it on one messy thread and compare the token count. Then send the author your edge cases, since that’s what they asked for. ⚓
Frequently Asked Questions
Q: Will it tell me if some replies haven’t loaded yet?
Not right now. It only copies the comments already on your screen, and the code has a flag for partially loaded threads that is always set to false. Before you copy, click any “View more comments” links and scroll to the bottom so you don’t summarize half a thread.
Q: Does it keep lists, code blocks, and links?
Lists and code blocks get dropped, and link URLs are removed while the link text stays. A reviewer saw this on mock pages built to look like Reddit, not on live Reddit, but it’s worth checking the output before you paste it into a model. If the thread is code-heavy or list-heavy, copy those parts by hand or keep the original link next to the Markdown.
Q: Does it keep the replies under an AutoModerator comment?
Not reliably. A reviewer found that the code deletes the whole branch under an AutoModerator comment, including human replies. The author says it cuts about 80 percent of the tokens, which is a real win for long threads, but for threads where the bot comment leads to the real discussion, copy that part yourself.
Q: Is it safe to install?
A reviewer read the code and found no network calls, no remote code, and permissions limited to the clipboard and reddit.com. The project is only a couple of days old with one author, and it isn’t on the Chrome Web Store, so you install it by loading it unpacked in Developer mode. That also means no automatic updates, so check the GitHub repo for new versions yourself.
Built a lightweight, client-side tool to turn Reddit threads into clean Markdown for LLMs (Open source & looking for feedback/ideas)
by u/Accurate-Skill3425 in PromptEngineering