Hey Product Hunt! 👋
Chrome extensions are the fastest way to bend the web to your will but building one means wrestling with manifest.json, service workers, content scripts, and a build pipeline. Most people with a great idea never get past "I wish my browser could just…"
Plugthis fixes that. Describe the extension you want in plain English, and Plugthis generates a real, working, installable Chrome extension: code, manifest, assets, and all. No command line. No boilerplate. No dev setup.
How it works:
1. 📝 Describe your extension ("Summarize the article I'm reading and let me ask questions about it")
2. ⚙️ PlugMint's AI writes the full extension and self-checks that it actually runs
3. 📦 Download the ready-to-load .zip and install it in Chrome
Why it's different:
- 🎯 The only AI builder designed specifically for Chrome extensions — not a generic code gen
- ✅ Generated extensions are verified to run before you get them (no dead "receiving end does not exist" errors)
- 🔌 From idea → working extension in minutes, not weekends
- 🖤 Clean, no-code interface with live preview + code editor if you want to peek under the hood
We'd love your feedback — what's the first extension you'd build? 👇
Replies
As someone who spends too much time fighting manifest files and debugging content scripts, this feels refreshing. The verification step caught my attention how exactly do you test generated extensions before delivery?
PlugThis
@aleksander_brousseau Ha the manifest-and-content-script fight is exactly what we set out to kill. 😄 On verification: after generation we first compile the code (esbuild catches syntax/import errors), then boot the actual packaged extension in headless Chrome via Puppeteer. It loads the manifest, navigates each UI page, probes the background service worker for startup crashes, and captures uncaught exceptions and blank renders. Any real runtime failure is fed back into a self-healing loop that repairs it automatically before delivery so the verification is behavioral, not just "does it lint."
The build in verification is what caught my eye. Knowing the extension actually runs before downloading it could save a lot of trial and error.
PlugThis
@iris_carr Thanks Iris! That's exactly why we built it. Before you ever download, we boot the extension in a real headless Chrome, load the manifest, open each UI surface (popup, options, side panel), and watch for console errors, blank renders, and service-worker crashes. If something breaks, it goes back through an auto-repair loop before it reaches you so you're not the one discovering the broken build. 🙌
Turning a plain English idea into a working Chrome extension sounds like a fun way to help people test ideas without getting stuck in setup. 👏
PlugThis
@freya24 Love that framing, Freya that's the whole point. 👏 Describe the idea in plain English and you skip the manifest wiring, build config, and boilerplate entirely. It's genuinely built for testing ideas fast without getting stuck in setup, and since every build is runtime-verified first, "fast" doesn't mean "flaky."
Me thinking the plain English approach removes one of the biggest barriers for new builders. Supporting import of existing extensions for editing could make the platform useful beyond creating projects from scratch.
PlugThis
@jason_scott8 Right now editing works on extensions you build (or fork) inside PlugThis — you can keep iterating in plain English with full version history. Importing an existing external extension to edit isn't supported yet, but it's a great fit for the roadmap and you're not the first to ask — noted.
Me liking that the platform removes the setup work that usually stops good ideas. Will teams be able to collaborate on one extension together? Shared editing and review could make it even more useful.
PlugThis
@joan_garcamo Yes, you can create a shared workspace, invite teammates with roles, and everyone works on the same extensions with shared settings. What's not in yet is live simultaneous co-editing and a formal review/approve step those are on the list. Happy to flag you when they land.
@saurabh_dey1 Will there be an option to publish directly to the Chrome Web Store after testing?
PlugThis
@john_michael31 Yes 👍 You build and test in-app, then publish straight to your own Chrome Web Store account in one click, and every later update is one click too. The only manual step is the very first time: Google requires you to create the listing once in the CWS dashboard and paste the Item ID back — after that it's fully automated.
1752vc Pitch Deck Analyzer
Awesome— going to send this to our engineer as we will be building one here in the next few months
PlugThis
@lucasjpols Thanks Lucas! Would genuinely love to hear what your engineer thinks send them our way. If you're building internally, the workspace + one-click CWS publish flow tends to be what teams care about most. Around if either of you has questions.