Build a script library your agent can use.

Full Tampermonkey parity on Chrome. Your scripts run unchanged, and your agent can build on them.

By Customaise · Reviewed

Compares Customaise 1.3.9 with Tampermonkey 5.5.1 for Chrome, measured side by side: imports, saved values, settings, GM APIs, network permissions and execution order. Where Customaise differs, it does so on purpose; each difference is listed below.

Build: An integrated agent workflow

Ask your agent to inspect a page, write a script, install it and check the result.

Reuse: Controls and named tools

UserScripts change pages; AgentScripts expose actions an agent can call again. Customaise’s Browser Agent can also check a script on the live page.

Match: Measured against Tampermonkey

Every GM API and metadata key Tampermonkey supports on Chrome, and 84 of 84 runs of real scripts from fifty public sources matched.

Side-by-side comparison

CapabilityCustomaiseTampermonkey
Script types [3] [4] [1]UserScripts for page controls and AgentScripts for agent-callable tools.Runs .user.js userscripts with its documented metadata and APIs.
Writing scripts [4] [2] [9] [10]An external agent can inspect the page, export a script and check its output through MCP or CLI.Use its editor, external editing or its MCP server with the Editors companion extension and user pairing.
Import compatibility [3] [1]Imports .user.js files and Tampermonkey ZIP/JSON backups with saved values, page lists and the nine script options. Scripts keep their source and run unchanged.The GM APIs and metadata it supports on Chrome, which Customaise matches.
Customaise supports all five @run-at timings: document-start, document-body, document-end, document-idle and context-menu. Chrome 147 or later is required.
Reusable agent actions [4] [1] [10]AgentScripts register named tools with declared inputs and permissions.Its MCP server manages userscript source. Exposing a script’s own page actions as named agent tools needs an additional integration.
AI inside a script [5] [1] [11]Free on-device AI with CM_promptAI (Gemini Nano, no key, Chrome 148 or later). Power User adds Script Decisions with Jev, OpenAI Decisions API or Gemini Decisions API.Scripts can call services or implement other integrations within their grants and browser capabilities.
Script Decisions requires Power User and separate provider billing. Local AI options depend on the browser and device.
Permissions and review [3] [4] [1]Grants, declared tools and approval modes govern supported operations; review source before enabling.Metadata, grants and extension settings govern documented APIs; review source before installing.
Keeping scripts across devices [6] [8]Optional encrypted cross-device sync is a Power User feature.Provides configurable script-sync options, including cloud providers.
Sharing [4] [6] [1]Publish subscriptions or Send an independent copy with Power User. Recipients choose what to enable.Distribute .user.js files and use script-hosting sites and update metadata.
Where data goes [7] [1]Local script execution; optional agent, cloud AI, Script Decisions and sync routes depend on what you enable.Depends on script behaviour, configured sync and any services the script calls.
Best fit [3] [4] [1]A managed script library for you and an external agent, with browser-side status and controls.Userscripts on Firefox, Safari or Edge.

What is the real difference?

Both products run userscripts and support agent-assisted editing. Customaise combines page inspection, script writing, installation and testing through MCP or CLI, with AgentScripts for named browser actions.

Tampermonkey offers its own MCP server through the Tampermonkey Editors companion extension and user pairing. It supports listing, reading and editing scripts; newer create and delete operations require Tampermonkey 5.6+ and Editors 1.0.6+. Customaise’s distinction is the integrated browser workflow and agent-callable tool library.

Full parity on Chrome

Customaise 1.3.9 provides every GM API and metadata key Tampermonkey supports on Chrome, in both GM_ and GM. forms, with all five @run-at timings. It requires Chrome 147 or later. [1] [3]

Different on purpose

A download from a site the script didn’t declare asks first. Editing a script pauses its automatic updates. Private windows work on a temporary copy of saved values. Scripts start in the same order, a few to about 20 milliseconds later, and a 200-script backup imports in under 3 seconds because each script is validated first. [3]

Tampermonkey’s MCP setup

Tampermonkey’s MCP server connects through the separate Editors extension and a user-approved pairing code. Its documentation lists reading and editing tools, plus create and delete operations that require Editors 1.0.6+ and Tampermonkey 5.6+. Check the versions installed in your browser before using those operations. Browser inspection and live testing require additional browser tooling. [9] [10]

Moving your library

Export a backup from Tampermonkey’s Utilities tab and import the ZIP or JSON in Settings → Scripts → Manual Restore. Scripts arrive with their saved values, page lists and options, and run unchanged. [3] [1]

Sharing and paid features

Power User can publish subscriptions or create a 24-hour Send link to an independent editable copy. A signed-in Free user can receive a Send copy. Copies arrive disabled; expiry stops link access but does not recall copies already received. Send copies do not receive publisher updates. [4] [6]

AI in your scripts

CM_promptAI runs Gemini Nano on the device, free and with no key, in Chrome 148 or later. Power User adds Script Decisions: focused classification or scoring with Jev, OpenAI Decisions API or Gemini Decisions API, declared in the script with @grant CM_decisions and run with a saved provider key on an authorised device. Provider charges are separate. [5] [11]

Agent costs

Free includes 50 successful Agent Bridge calls per UTC day and 150 per rolling seven days. Power User removes these bridge caps. Your external agent’s subscription or API charges are separate; Script Decisions provider charges are separate too. [6]

When should you use which?

Customaise

You want your agent to help create and maintain page controls and reusable browser tools in the same installed library.

Tampermonkey

You use Firefox, Safari or Edge. Customaise is built and tested for Chrome.

You can evaluate managers alongside each other, but disable duplicate copies so both do not modify the same page.

Sources and scope

Compares Customaise 1.3.9 with Tampermonkey 5.5.1 for Chrome, measured side by side: imports, saved values, settings, GM APIs, network permissions and execution order. Where Customaise differs, it does so on purpose; each difference is listed below.

By Customaise. Product capabilities are based on documentation and our implementation. Recommendations are workflow judgments, not a head-to-head performance or security benchmark.

  1. [1] Tampermonkey: documented APIs and settings
  2. [2] Tampermonkey: external editor workflow
  3. [3] Customaise: UserScripts
  4. [4] Customaise: AgentScripts and permissions
  5. [5] Customaise: Script Decisions
  6. [6] Customaise: plans and allowances
  7. [7] Customaise: privacy and data flows
  8. [8] Tampermonkey: script sync options
  9. [9] Tampermonkey: Chrome releases and MCP support
  10. [10] Tampermonkey: MCP tools and setup requirements
  11. [11] Customaise: on-device AI and your own models

Related comparisons

  • Customaise vs Playwright: Playwright automates browsers from code. Customaise adds named tools and page controls to the Chrome you already use.
  • Customaise vs Browser Use: Browser Use offers local and cloud paths, including Browser Harness. Customaise centres the workflow on an installed library of scripts and tools.
  • Customaise vs Browserbase: Compare hosted browser infrastructure with a managed script library. Stagehand’s local launch and CDP attachment are part of the picture too.