Say what you want your browser to do. Despicable writes the extension, shows it running, and hands you something you can install or publish to the Chrome Web Store.
Hey Product Hunt 👋
Everyone has two or three of these. Hide the Shorts. Stop the autoplay. Show me the price per 100g. Strip the tracking off links I copy. Small, specific, personal, and none of them worth learning the Chrome extension API for. So they never get built, and you just keep being annoyed.
Despicable is one sentence in, a working extension out.
The part I care most about: you can read it before you install it. An extension can see every page you visit, so "trust the AI" isn't an acceptable answer. Every file is open in the editor, every permission is written out in plain English, and anything that touches your history or cookies gets flagged. Edit a selector by hand and the preview follows, the file you're reading is the file that ships.
It runs in front of you first, in a sandbox, so nothing reaches your browser until you've watched it work. Then load it unpacked in two clicks, push it to a GitHub repo, or send it to the Web Store with the icons and listing filled in.
Two honest notes. The code is model-written, so it's occasionally wrong, which is exactly why nothing is hidden from you. And it's early: it handles the "change what a page does" cases well and gets ambitious about complicated ones.
Tell me the thing your browser gets wrong and I'll build it in the comments.