V3 · v0.1.1

Script Monkey Next

Script Monkey Next is a userscript manager for Chrome MV3. Write scripts in the built-in editor, manage URL matches, and run custom logic on the sites you choose via the modern userScripts API.

Install from Chrome Web Store All extensions

Script Monkey Next

Userscript manager for Manifest V3

Features

What you get in practice — not just a checklist.

Userscript manager for Manifest V3

Create, edit, and run custom scripts on the sites you choose through Chrome’s official userScripts API — the supported path for user-provided code under MV3.

Standard UserScript headers

Supports @match, @include, @exclude, @run-at, @name, @description, and @version so scripts feel familiar if you are coming from classic userscript managers.

Built-in CodeMirror editor

Write JavaScript in a full dashboard editor with syntax highlighting. The popup lists scripts for quick enable/disable; the editor is where you do deeper work.

Isolated or page execution world

Run scripts in the USER_SCRIPT world for isolation, or MAIN when you need to touch page globals. Choose the world that matches the script’s job.

Enable scripts or the whole engine

Toggle individual scripts or pause the entire engine without deleting anything. Settings and scripts stay in local chrome.storage.

Theme-aware UI

Light, dark, or system theme across popup, options, and the editor so late-night scripting stays comfortable.

Privacy

Settings are stored locally. Details are on the Privacy Policy page.

Permissions

storageactiveTabuserScripts

FAQ

Common questions about Script Monkey.

Why do my scripts not run after install?

Chrome requires an extra step: open chrome://extensions, open Script Monkey Next details, and enable Allow User Scripts (Chrome 138+) or turn on Developer mode. Without that toggle, scripts save but never inject.

Is this compatible with Tampermonkey-style headers?

Script Monkey Next understands the common ==UserScript== metadata fields for matching and run timing. Always re-test third-party scripts before relying on them in production workflows.

Where are scripts stored?

Scripts and settings live in chrome.storage on your device. They are not uploaded to a FuriaHub server.

What is the difference between USER_SCRIPT and MAIN?

USER_SCRIPT keeps your code isolated from the page. MAIN runs in the page context when you need to call or override page JavaScript directly.

Does it work only on Manifest V3?

Yes. The extension targets Manifest V3 and uses chrome.userScripts, which is the modern Chrome path for userscripts.

Blog

Guides and tips for getting more out of Script Monkey.

May 20, 2026

Allow User Scripts: the one Chrome setting you must enable

MV3 userscripts stay inert until Chrome’s Allow User Scripts toggle is on. Here is where to find it.

After installing Script Monkey Next, open the extension’s Details page in chrome://extensions. Enable Allow User Scripts (or Developer mode on builds that still use that gate).

If the toggle is off, the manager will still let you create and edit scripts — they simply will not inject. Flip the permission, reload the target tab, and try again.

Jun 18, 2026

Writing your first match rules

Start with a narrow @match, verify on one host, then widen the pattern once the script behaves.

Broad wildcards are convenient and risky. Begin with an exact host match, confirm the script runs at the right @run-at moment, then expand to path patterns.

Use @exclude for admin or checkout paths where automation should never fire. Keep one example script lean so you can debug match rules without noise.