Repository navigation
Description
Pre-check
- I have searched existing issues and confirmed that this is not a duplicate feature request.
- Where possible, I have checked the latest stable or beta version and confirmed that this feature is still unavailable.
- I have confirmed that this is a request for a new or improved feature, not a bug report about an existing feature.
The Problem You Want to Solve
Currently, ScriptCat provides per-script site-scope controls, allowing users to exclude or include individual websites for specific scripts.
However, there is no convenient way to configure a particular website to allow only scripts that explicitly target it, while preventing general-purpose scripts from running there.
For example, I may have several general-purpose userscripts that match *://*/*. I don't necessarily want these scripts running on a specific website, but I still want scripts explicitly designed for that website to work normally.
Currently, achieving this requires manually excluding that website from every general-purpose script. This becomes tedious when managing multiple scripts, especially when new scripts are installed or existing scripts are updated.
I'd like a website-level solution rather than having to configure every individual script.
Proposed Solution
Add an optional exclusive mode for individual websites.
For example, a user could configure the following entry in the blacklist:
@explicit-only https://*.example.com/*
When exclusive mode is enabled for a website, ScriptCat would:
- Allow scripts whose own
@matchor@includerules explicitly target that website. - Block general-purpose scripts that match the website only through broad wildcard patterns.
- Apply the restriction automatically to all affected scripts, without requiring individual
@excluderules.
For example, on example.com:
| Script matching rule | Expected behavior |
|---|---|
*://*/* |
Block |
https://*/* |
Block |
<all_urls> |
Block |
https://example.com/* |
Allow |
https://*.example.com/* |
Allow |
The wildcard subdomain pattern should cover both the root domain and its subdomains.
This should be configurable at the website level, ideally through the existing blacklist settings, and should not require modifying individual userscripts.
Existing blacklist behavior should remain unchanged for entries without exclusive mode enabled.
The goal is to avoid manually configuring every general-purpose userscript whenever a particular website should be treated as an exception.
ScriptCat Version
1.5.1
Additional Information
No response
Activity
CodFrm commentedon Nov 16, 2026
Thanks for the suggestion! We'll consider this and plan it in a future release.