PlugThis - Create your own Chrome Extensions by chatting with AI

@maxim100000 You bring up a really good point, our current focus is building the best chrome extension builder in the world. Helping our users move from idea to working extension, as soon as possible.

On the marketing front, we do assist with asset creation and deployment of updates to the chrome store.
We also help getting the extension ready for a chrome store listing.

On the distribution front, we havent made any plans yet, if you have any ideas please share.

@artstavenka1 Great question, and it's exactly the trap a naive static pass falls into, so we handle it two ways.

First, scope: only the required permissions array is ever evaluated for removal. optional_permissions are out of scope by design, precisely because they're requested on demand and would never show up in a static call graph. So nothing you ask for on demand can be read as dead or nudged for removal.

Second, runtime acquisition: if the code actually manages permissions at runtime, chrome.permissions.request, contains, add, or remove, the analyzer picks that up and treats any permission named inside those calls as live, even if there's no direct chrome. call for it. So a permission you declare as required but only activate through chrome.permissions.request won't be flagged either.

And the whole thing is deliberately biased toward silence. A false "this is used" is harmless, a false "drop this" could break your extension, so anything it can't attribute with confidence it leaves alone rather than nudge you. The nudge only fires when a permission has no static usage and no runtime request naming it.

So the short answer: no, it won't tell you to drop something you only ask for on demand. That's the exact case it's built to not get wrong. Really good catch to probe it though.

@anthonywrinqsb That setup wall is exactly the thing that killed the idea for so many people. Manifests, service workers, build config, store rules, all before you write a single fun line of your actual idea. We wanted the barrier to be "what do you want it to do," not "spend a weekend configuring tooling first."

You should finally build that extension you kept putting off. If you do, tell me what it is, I'd genuinely love to see the first thing you ship with it.

@tan_z_tan 
Love that you asked it that directly, so here's the honest version.

For focused, well-scoped extensions, the kind that do one job well, it's genuinely ship-ready. It generates real Manifest V3 with TypeScript and React, actually compiles and bundles, passes a structural validation and lint pass, and goes through a Chrome Web Store pre-flight before you publish. So it's not throwaway scaffolding you have to rewrite. It builds, it runs, and you can push it to the store from inside the tool.

For bigger or more ambitious ideas, it's better thought of as a strong first draft that gets you 80 to 90 percent there fast, then you refine the last bit either by chatting with it or hand-editing the code directly, and both stay in sync. The value is that you skip the part everyone hates, the manifest, service worker, build config, permissions, and store setup, and land straight on "now I'm tuning behavior" instead of "now I'm configuring tooling."

So: ship-ready for the simple stuff, a serious head start for the complex stuff, and never a blank page. Would genuinely love for you to try it and tell me where the output holds up and where it doesn't. That feedback is exactly what sharpens it.

@neerajkanoi Thank you, glad you found it to be useful. If there is any feature you wan to see in the app, please let us know.

@neosrix Thanks Srix. Yes, it does.

Once your extension is built, you connect your Chrome Web Store account once, and PlugThis uploads and publishes directly from inside the app. It also generates the listing description, permission justifications, and privacy disclosures the store asks for, so you are not filling that out by hand. After the first publish it remembers your Store item ID, so pushing an update later is basically one click.

The only parts that stay on Google's side are the one-time developer account registration and the review itself, since approval is always their call. Everything up to hitting submit, we handle for you.

@mshen316 This is the exact person we built it for, Michael 😄 A year in the notes app is long enough, today's the day.

And good news, the Twitter ICP scoring idea is right in the sweet spot: read the profile or timeline, score it against your criteria, show the result inline. You describe it in plain English and it figures out the structure, the permissions, and the scaffolding for you, so not really coding is not the blocker it used to be. You can refine it just by telling it what you want changed.

One tip: start with the simplest version of the idea, get that working and seeing it live, then add the fancy scoring logic. Momentum is everything, and this time you won't lose it to setup.

Go build it, and please come back and tell me how it went. Genuinely rooting for you on this one.

@nelsonsilvadev Thank you Nelson 🚀 And honestly that's the perfect first extension, because it's a real pain and it's very buildable.

What you described maps cleanly: highlight text on any page, hit a shortcut or a button, and it appends the highlight plus the source URL into one running note, all stored locally so it persists. Add a side panel to see the running list as you go and you've basically killed the copy-paste-one-at-a-time loop.

You could have a working version of this today. Describe it in that exact plain-English way and let it build the structure. If you make it, come back and show me, I'd genuinely love to see your highlight collector come to life.

@nelsonsilvadev Thank you :) Those 15 minutes start adding up to days over years. Please try building your workflow as an extension on PlugThis.

Hi @pixori  We can build complex multi page extensions, do you have any particular idea you want to see as an extension?

@hamidesevg79879 Thank you version history was born out of pain we faced not having it :) And we wanted to be super focussed from day 1 and be the best platform to build chrome extensions.