Absolutely thanks! The idea of making it was I wanted a keyboard based workflow so I don&#x27;t have to use my mouse while working with cursor. Please share feedback.

Nice work, I currently use Markdownload (<a href="https:&#x2F;&#x2F;github.com&#x2F;deathau&#x2F;markdownload">https:&#x2F;&#x2F;github.com&#x2F;deathau&#x2F;markdownload</a>) for this but will certainly give this a good shake out.Kudos for making it a Firefox and not just Google extension as well.

Looks cool, thanks for sharing. I will check it out.

I built this browser extension to solve a daily frustration: copying documentation from websites to feed into AI coding assistants like Cursor, Windsurf, or ChatGPT, only to get a mess of ads, popups, and navigation junk mixed in with the actual content.LLMFeeder uses Mozilla&#x27;s Readability.js (same tech as Firefox Reader Mode) to extract just the main article content, converts it to clean markdown with Turndown.js, and copies it to your clipboard with a single keyboard shortcut (Alt+Shift+M or ⌥ ⇧ M). No clicking through popups, no selecting around ads, no fighting with modern web clutter.# Key features:• One-key extraction and markdown conversion• Works on Chrome and Firefox• Completely local processing (no data sent anywhere)• Configurable content scope and formatting options• Open source with clean, documented codeThe workflow is simple: hit the shortcut on any documentation page, switch back to your editor, paste clean markdown context, get better LLM responses.It&#x27;s solving a real problem I have dozens of times per day, and early users seem to find it useful too. Available on both browser stores and GitHub for manual installation.# Links:• Demo: <a href="https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=JxHWqszlZDw" rel="nofollow">https:&#x2F;&#x2F;www.youtube.com&#x2F;watch?v=JxHWqszlZDw</a>• GitHub: <a href="https:&#x2F;&#x2F;github.com&#x2F;jatinkrmalik&#x2F;LLMFeeder">https:&#x2F;&#x2F;github.com&#x2F;jatinkrmalik&#x2F;LLMFeeder</a>• Chrome: <a href="https:&#x2F;&#x2F;chromewebstore.google.com&#x2F;detail&#x2F;llmfeeder&#x2F;cjjfhhapabcpcokkfldbiiojiphbifdk" rel="nofollow">https:&#x2F;&#x2F;chromewebstore.google.com&#x2F;detail&#x2F;llmfeeder&#x2F;cjjfhhapa...</a>• Firefox: <a href="https:&#x2F;&#x2F;addons.mozilla.org&#x2F;en-US&#x2F;firefox&#x2F;addon&#x2F;llmfeeder&#x2F;" rel="nofollow">https:&#x2F;&#x2F;addons.mozilla.org&#x2F;en-US&#x2F;firefox&#x2F;addon&#x2F;llmfeeder&#x2F;</a>Would love feedback from fellow developers who deal with this same workflow friction. What other pain points do you have when feeding content to LLMs?

Show HN: LLMFeeder – Browser extension to extract clean content for LLM context