PlugThis - Create your own Chrome Extensions by chatting with AI
by•
You wanted a Chrome extension that would save you 15 minutes a day. You searched the Chrome Web Store, and it's not there.
Now you can just describe it in plain English, and PlugThis builds it for you. The code is yours. Want changes? Chat. Need login or a database? Connect Supabase. Ready to publish? We generate the icons, screenshots, and listing copy the store asks for.
Everyone else builds web apps. We build Chrome extensions.
Replies
Congrats on the launch! 🚀
That "15-minute repetitive task" line got me. Mine is copy pasting snippets from a bunch of open tabs into one notes doc, one at a time. Something that just tossed every highlight into a single running note would genuinely save me.
Nicely done!
PlugThis
@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.
PlugThis
@nelsonsilvadev Thank you :) Those 15 minutes start adding up to days over years. Please try building your workflow as an extension on PlugThis.
This looks cool! Does it support complex extensions with multiple pages?
PlugThis
Hi @pixori We can build complex multi page extensions, do you have any particular idea you want to see as an extension?
@nefer_ai For example - a multi-page extension that pulls prices from several open tabs into one live comparison panel
PlugThis
@pixori I was able to get this done in 2 prompts. The extension fetches data from 3 open tabs and price compares yogurt and presents findings in a new tab.
@nefer_ai This is crazy!
The version history baked in is such a thoughtful touch, makes iterating with the chat feel safe instead of nerve-wracking. Glad someone finally focused on Chrome extensions instead of yet another web app builder.
PlugThis
@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.
Super excited to check this out and will be trying it for our current web app 'dot.' as we could definitely expand our offerings with a chrome extension!
PlugThis
@munimur_ashrafy Thank you, great idea. A lot of our early customers create extensions to offer along side their main product. Please reach out to me if you have any challenges.
This is great Udaya! been trial and error build a chrome extension and keep getting bottleneck. I found something from your product. Big applause!
PlugThis
Hi @reza_here Thank you thank you :) Please take PlugThis for a spin. I am super curious to see what you are going to build.
Chrome extensions are the one thing I keep wanting to build and keep bouncing off, because the manifest and permissions setup kills the momentum before I get anywhere. Does PlugThis handle the permissions prompts and store-review gotchas, or does it just get me to working code and I'm on my own for shipping? The last 10% is where my side-project extensions always die.
PlugThis
@chielephant You just described exactly why we built this, Anthony. Getting to working code was never really the hard part. The last 10%, permissions and store review, is where side-project extensions quietly die, so that's the part we went deepest on.
Concretely, PlugThis does not stop at working code:
Permissions are scoped to what the feature actually needs, not "ask for everything to be safe," and it flags permissions the manifest declares but the code never uses, so you go to review lean instead of over-asking.
For the store, it generates the listing description, the permission and host justifications, and the privacy disclosures Google asks for, which is usually the maze that stalls people.
Then it publishes directly to the Chrome Web Store from inside the app, and remembers your item ID so updates are basically one click.
Browser is where all my work happens and it makes a lot of sense to extract all the juice extensions have to offer. Love what PlugThis does. I've known Udaya for a while and can vouch for the founder and his superb team.
PlugThis
@adhar_masand Thank you Adhar :) Browser if rightly automated, can save upto one full working day every single month! :)
Does the generated extension actually get reviewed and approved before hitting the store, or am I on the hook for submitting it myself?
PlugThis
@ahmetrtensjl1 Good to clarify. PlugThis submits it for you, you're not doing the manual upload. You connect your Chrome Web Store account once and it publishes directly, along with the listing, permission justifications, and privacy disclosures the store asks for.
What we can't do is approve it, that review is always Google's call, no tool can bypass it. So the flow is: we handle everything up to and including hitting submit, then Google runs their review. The difference is you're not stuck assembling the submission by hand, which is usually where people stall.
How does the versioning work when you want to roll back, do you get a full diff or just snapshots you have to rebuild from?
PlugThis
@orukfaruk63783 full snapshots for reliability, diffs layered on top for clarity, and zero rebuild step either way.
Congrats on the launch, Udaya! 🚀 You really hit the nail on the head—manifest files and background scripts are exactly where general web builders like Bolt or Lovable tend to trip up.
Since extensions rely heavily on background service workers that spin down when idle, how does PlugThis handle state persistence natively? Does the generated code lean heavily on `chrome.storage.local` , or does it automatically set up a sync structure if a user connects a Supabase backend?
PlugThis
@franz_briones Thank you Franz, and you're pointing right at the thing that quietly breaks most generated extensions.
On native state: yes, the generated code treats chrome.storage.local as the source of truth on purpose, precisely because the MV3 service worker sleeps. The generator is explicitly instructed to never hold state only in a JS variable or React state, since that's gone the moment the popup unloads or the worker spins down. So anything that needs to survive gets written to chrome.storage.local and rehydrated, rather than assuming the background stays alive.
On Supabase: if you enable it, it sets up a real structure, not just a key value dump. It wires auth plus CRUD against the Supabase REST API with direct fetch, and importantly it bridges the two layers: the session is persisted in chrome.storage.local so a signed-in user stays signed in across popup close, worker sleep, and browser restart, and expired access tokens get refreshed automatically via the refresh token grant instead of kicking the user back to a login screen. So chrome.storage.local is the local durability layer and Supabase is the remote persistence layer, and it connects them so state survives the worker lifecycle.
Worth being clear on scope: you get durable local state plus a real Supabase backend that survives the worker lifecycle, which covers the vast majority of extensions people actually ship. True offline-first sync, with conflict resolution and a write queue, is a heavier layer we can go deeper on if that's where you're headed. Curious what you're building, because that would tell me fast whether the current setup is enough or whether that deeper sync layer is the thing worth pushing on.