We launched PlugThis: describe a Chrome extension in plain English, get a publish-ready one

Hey everyone 👋

We just launched PlugThis on Product Hunt today, and I wanted to share the why here rather than only the pitch.

The idea started from a simple frustration: Chrome extensions look tiny from the outside, but the moment you start one you hit manifests, service workers, content scripts, permissions, store rules, icons, screenshots, and listing copy. Most people give up before they build the thing they actually wanted. Tools like Lovable and Bolt are great for web apps, but they hit a wall exactly at that browser-plumbing layer.

 So we built PlugThis to take a plain-English description and hand you a real, working Manifest V3 extension. A few things we care about:

•  It scopes permissions to what the feature actually needs, and flags permissions that are declared but never used, instead of quietly over-asking.

•  It handles the distribution side too: store listing, permission justifications, privacy disclosures, and direct publishing to the Chrome Web Store.

•  You get a live preview of the popup, side panel, and options UI as it generates, plus full version history with a real side-by-side diff so you can roll back anytime.

•  The code is yours. You can chat to refine it or hand-edit directly, and both stay in sync.

What surprised us most: once building is easy, the real wall becomes Chrome Web Store trust and review, not the code. So we ended up spending as much time on the submission and least-privilege side as the generation itself.

 I would genuinely love this community's take:

 1. If you have ever abandoned an extension idea, what actually stopped you? The build, or the store?

 2. What tiny personal browser workflow would you automate first if setup was not a problem?

 Happy to answer anything about how it works under the hood. Ask me the hard stuff 🙂