Spent the last few months talking to founders and indie hackers who are quietly frustrated with subscription Chrome extensions.
The pattern I keep hearing: someone pays $20 to $50 a month for an extension that does one specific thing (usually an SEO checker, a research tool, a screenshot annotator, or an LinkedIn scraper). The extension itself is a few hundred lines of code, the underlying task is mechanical, and the monthly charge feels like rent on something that should be a one-time purchase.
I'm running growth for PlugThis (launching here on Product Hunt soon) and part of the pitch is that you can build or clone those tools yourself instead of renting them. But I want to stress-test the premise.
Two questions for this forum:
@nefer_ai Tested it today and it's genuinely fun to use. I expected to spend time fixing boilerplate, but it got me to a usable extension much faster than I thought. If you keep improving the generation quality, this could become a go-to tool for anyone building Chrome extensions. Congrats! 👏
PlugThis
@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.
@nefer_ai I like that this is built specifically for Chrome extensions instead of trying to cover every kind of app. Sometimes focusing on one problem is what makes a product really instead out.
PlugThis
@morgan__harriss Thank you, we want to do one thing, in our case building chrome extensions and be the best in the world at it.
Please take PlugThis for a spin, would love to see what ideas you were able to make into a chrome extension.
Congrats on the great launch! QQ - what about permissions requested at runtime through chrome.permissions.request or optional_permissions? Those probably almost never show up in a static call graph, so does the analyser read them as dead and nudge you to drop something you only ask for on demand?
PlugThis
@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.
Money View
Solid product. I've used this to create a few of my Chrome extensions to make my day to day work easier.
Although people with AI dev tools can create their own, I think everyone (even non-devs) needs to make their own chrome extensions to make their workflows easier, that's where this just works.
PlugThis
@soumitrasen Thank you for your kind words! Very happy to have you as a user from the earliest days of plugthis.
I appreciate that every change is versioned. It makes experimenting feel much less risky. Knowing I can always go back encourages me to try more ideas.
PlugThis
@thomas__bond Thanks for noticing, This feature was not there in our original roadmap and only when we started to build real world extensions, we realised and necessity of having it and had it built.
Please do setup your account and try building your ideas.
minimalist phone: reduce your screentime
Guys, you are amazing. I will try this later because I am building my own (tho manually because I set the goal for myself to learn coding and programming). But this one tool is brilliant! :)
minimalist phone: reduce your screentime
By the way, how comprehensive is this solution?
Because let's say that I am a total beginner and my prompt would be: "Create a plugin that alerts you that you spent too much time on a certain website." – does it know how to create a sufficient structure?
Because real devs are more descriptive and probably would be able to create well-described and specific tasks, like create padding 3px 12 px...
PlugThis
@busmark_w_nika You are our dream user. The prompt "Create a plugin that alerts you that you spent too much time on a certain website." would exactly build you the extension.
Please try out plugthis.ai you provide simple instruction and the AI will build it.
No need provide padding and other details.
We cant wait to see what you are going to build :D