You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
[Feature Request] Notify users of upstream updates to locally modified scripts without overwriting changes
#2910
Tampermonkey correctly protects locally modified userscripts from automatic updates. However, users who intentionally customize scripts can miss important upstream releases because there is no clear, proactive notification that a newer version is available.
I understand and appreciate why Tampermonkey prevents automatic replacement of modified scripts. I do not want that protection removed.
What I want is to continue receiving update notifications while keeping my modifications intact.
Real-world example
I've used an AO3 bookmark helper userscript for years. I modified a handful of configuration flags to make bookmarks private by default and prevent automatic recommendations.
Those settings are important to my workflow. Public AO3 bookmarks can expose notes and tags to other readers and authors, so private-by-default is an intentional privacy safeguard.
The script isn't updated frequently. However, I missed an important update in 2024 and encountered the same problem again in 2026. In both cases, my local modifications meant I wasn't made aware of the newer release through my normal Tampermonkey update workflow.
I'm currently using Tampermonkey 5.5.1 in Chrome, with automatic update checks enabled globally and for the individual script. Tampermonkey recognizes the local modifications and displays the warning that the script needs to be updated manually.
Requested behavior
When an upstream update becomes available for a locally modified script:
Continue checking the original update URL automatically.
Notify the user that a newer version exists, even though the script cannot be updated automatically.
Leave the locally modified script completely untouched.
Allow the user to review the upstream release and decide whether to update manually.
Prefer a subtle, persistent dashboard indicator or notification rather than interruptive prompts.
This should apply specifically to scripts that cannot be automatically updated because of local modifications, without changing the existing behavior of unmodified scripts.
Related issue
Issue #2458 introduced improvements in Tampermonkey 5.5 that separate checking for updates from installing them.
This request concerns what appears to be a remaining gap: notifying users about available upstream updates when local modifications prevent automatic installation.
Why this matters
Protecting user modifications and keeping users informed about upstream releases should not be mutually exclusive.
A locally modified script can remain functional for years while missing important bug fixes, compatibility improvements, or security-related changes.
The ideal experience is simple:
“Version 2.4 is available. Your installed version 2.3 contains local modifications and will not be replaced automatically. Review update.”
No automatic replacement, no repeated prompts, and no need for users to maintain a separate monitoring system.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
The problem
Tampermonkey correctly protects locally modified userscripts from automatic updates. However, users who intentionally customize scripts can miss important upstream releases because there is no clear, proactive notification that a newer version is available.
I understand and appreciate why Tampermonkey prevents automatic replacement of modified scripts. I do not want that protection removed.
What I want is to continue receiving update notifications while keeping my modifications intact.
Real-world example
I've used an AO3 bookmark helper userscript for years. I modified a handful of configuration flags to make bookmarks private by default and prevent automatic recommendations.
Those settings are important to my workflow. Public AO3 bookmarks can expose notes and tags to other readers and authors, so private-by-default is an intentional privacy safeguard.
The script isn't updated frequently. However, I missed an important update in 2024 and encountered the same problem again in 2026. In both cases, my local modifications meant I wasn't made aware of the newer release through my normal Tampermonkey update workflow.
I'm currently using Tampermonkey 5.5.1 in Chrome, with automatic update checks enabled globally and for the individual script. Tampermonkey recognizes the local modifications and displays the warning that the script needs to be updated manually.
Requested behavior
When an upstream update becomes available for a locally modified script:
This should apply specifically to scripts that cannot be automatically updated because of local modifications, without changing the existing behavior of unmodified scripts.
Related issue
Issue #2458 introduced improvements in Tampermonkey 5.5 that separate checking for updates from installing them.
#2458
This request concerns what appears to be a remaining gap: notifying users about available upstream updates when local modifications prevent automatic installation.
Why this matters
Protecting user modifications and keeping users informed about upstream releases should not be mutually exclusive.
A locally modified script can remain functional for years while missing important bug fixes, compatibility improvements, or security-related changes.
The ideal experience is simple:
“Version 2.4 is available. Your installed version 2.3 contains local modifications and will not be replaced automatically. Review update.”
No automatic replacement, no repeated prompts, and no need for users to maintain a separate monitoring system.
Thank you for considering this improvement.
All reactions