PlugThis - Create your own Chrome Extensions by chatting with AI

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

Hi @andre_ajemian one of the main issues we wanted to tackle was daily repetitive workflows. You just described the uses cases, for which I have personally built an extension.

It takes in my Product profile, I define a ICP then it scores every person I see on X after doing a web search on them telling me if they are a good fit for my product.

People are building extensions across the board, the data workflows are there but the long tail is so huge. Ideas and problems, I dint even knew existed are getting solved.

Please do try to build for your exact itch, If you need any support, please reach to us via in app chat.

@lennoxbeflying Glad that line landed, and go build those 15-minute itches, they're exactly the sweet spot.

On browsers: today a build is Chrome-first, and the store side is built specifically around the Chrome Web Store. But since everything it generates is standard Manifest V3, the same output already runs on Edge with little to no change, because Edge is Chromium underneath. So realistically it's Chrome and Edge from one build.

Firefox is the honest gap. It supports MV3 but with enough differences in APIs, manifest quirks, and signing that "mostly works" is not good enough, so I would rather do it as a proper target than half-ship it. So the "one thing we do" focus stretches cleanly across the Chromium browsers now, and Firefox is a deliberate next step rather than a checkbox we pretend to have ticked.

Is Firefox the one you'd actually need, or would Chrome and Edge cover your itches? That genuinely helps me prioritize.

Hi @crystal_harrison PlugThis should be able to handle this, give it a shot on the platform if you run into challenges, please send me a email udaya@plugthis.ai I ll hop on a zoom call and troubleshoot it for you.

@jasonrdunn Great question, and the answer is the good kind: your extensions keep working.

What you build is a real, standalone Chrome extension. The code is yours to download, and once it's installed or published to the store it runs on its own with no dependency on PlugThis servers. So if you stop paying, nothing you already shipped breaks.

The subscription is about building and modifying, generating new extensions and iterating on existing ones inside the tool. Pause it and your live extensions keep running exactly as they are, you just wouldn't be creating or changing more until you're back.

So it's full ownership, no kill switch. Your extension, your code, yours to keep.

@nefer_ai  @sonal_waghchoure This genuinely made me smile, thank you so much 🙏 Really glad the design and quality held up, and that changing the UI felt easy.

On mobile: quick honest nuance, because "mobile app" can mean two things. If you mean building extensions from your phone, making the builder itself work well on mobile is very doable and worth considering. If you mean the extensions running on mobile, that's trickier, since Chrome on mobile doesn't really support extensions the way desktop does, so that limit is on the browser side, not us.

Which one were you picturing? That tells me a lot about how to prioritize it.