PlugThis - Create your own Chrome Extensions by chatting with AI

@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.

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.

@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.

@adhar_masand Thank you Adhar :) Browser if rightly automated, can save upto one full working day every single month! :)

@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.

@orukfaruk63783 full snapshots for reliability, diffs layered on top for clarity, and zero rebuild step either way.

@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.

@cjgiridhar Hi Chetan! Thank you. Glad to have you as one our early users. Your feedback was the reason we built chrome store readiness, asset generation and one click connect to update extensions directly on chrome webstore. Take a bow 🙇 As of now we are focussed on chrome and edge browsers. May be later we might do Safari and Firefox.

@jill_camhi_osinoff First, thank you for trying out Plugthis.

Let me assist you with your question.

Please input the idea you have for the extension and click on the black arrow button.

I have pasted a screenshot below for your reference, if you still have questions please reply I ll assist.

Hi @kojimajunya Yes yes we do :D PlugThis tells you your extension's chrome webstore readiness, helps you generate assets and in one click push changes live to CWS.

Please do check out PlugThis and take it for a spin.