Repository navigation
[Feature] Only for {website} Option #2410
Description
Motivation
Currently, Violentmonkey scripts are enabled or disabled globally. If a script matches multiple websites via @match, disabling it affects all those websites at once. This makes it inconvenient to reuse a single script across multiple domains while selectively disabling it on specific sites.
Dark Reader, for example, solves this by allowing per-website enable/disable behavior, which greatly improves usability and flexibility.
Proposed Solution
Add an "Only for <website>" / per-website enable/disable option for user scripts.
When a script matches multiple websites:
-
The user should be able to enable or disable that script per domain.
-
Script settings should be stored separately for each website.
-
The UI could allow toggling a script as:
- Enabled globally
- Disabled globally
- Enabled/disabled for the current website only (similar to Dark Reader’s site-specific controls)
This would not change how @match works, but would add an additional layer of per-site control on top of it.
Use Cases
- Temporarily disabling a script on a single website for debugging without affecting other matching websites.
- Improving user experience for users with many scripts that intentionally target broad URL patterns.
Activity
tophf commentedon Jan 3, 2026
I think this can be already done by excluding the site via the ... menu in the popup, then removing the exclusion in the editor -> Settings tab. The only improvement upon the current behavior that might be worth implementing is showing such user-excluded scripts in an additional collapsed group in the popup.
Rilivaine commentedon Jan 6, 2026
right, so i tried that out and that's not i meant in mind.
my idea is to add some switch that will put website into exclusive mode. changes only behavior how scripts are disabled.
right now when you toggle script, it toggles globally.
my idea is, if website is in exclusive mode, then toggling the script toggles it only for that specific domain we're on during toggling.
tophf commentedon Jan 6, 2026
I don't understand what "put website into exclusive mode" means. It sounds like you've tried something else because what I suggested effectively disables the script for the given site, which in my understanding achieves your goal.
Rilivaine commentedon Jan 7, 2026
it does achieve my goal, but not in a way that feels more comfortable to me.
exclude remove the script from the list, but if i want to bring back the script(s) back i have to go through each and every script and remove domain from its excludes.
"put website into exclusive mode" is just a weird wording.
i'm not entirely sure how i could explain that, so that anyone understands V_V'
scripts right now work in global mode.
let's imagine that we have one script for YT, PH and Twitch. it's one script that works on these 3 websites.
right now if i disable a script it's disabled on all 3.
exclusive mode would introduce scope where scripts' states are exclusive to that specific website.
i would LOVE to code this myself, rather than explain it. but i don't know vue... yet?
i might look into that anyway.
of course if you wouldn't mind this being implemented~
tophf commentedon Jan 7, 2026
Yeah, I understood the idea right from the start, just wanted to make sure I didn't imagine it.
If we show such scripts in a dedicated group in the popup, it'd be easier to toggle them back. Another improvement would be to add
Exclude siteto the menu so you only need two clicks in total.Baerbeisser commentedon Jan 9, 2026
I think i've run into the same with the
pagetualscript. On some sites convenient, on most sites annoying.An easy way to implement this UI-wise would be, if you disable the script in the popup UI and then instead of "exclude site" it should be "allow site". I think this is the same like what OP means?
edit: oh, @tophf had the same idea before. Nevermind.
tophf commentedon Jan 9, 2026
Sure, scripts in this dedicated group would have "exclude" flipped to "allow".
BHare1985 commentedon Feb 17, 2026
I also came across this, initially I thought the toggle for the script would just disable the script for the current website, not globally.
The ellipses for the script was not apparent for me (see below), but after I read this thread I realized there was an exclude. I agree that this needs a UX improvement.
tophf commentedon Feb 17, 2026
The standard industry behavior for entries that apply globally is to toggle globally as well, which is what Violentmonkey does.