HELP · FIREFOX
Enable User Scripts on Firefox
On Firefox, script running is an optional permission Robin asks for the first time you run a script. Approving it once enables the User Scripts API for every future run.
Grant the permission (Firefox 141+)
- Open Robin's sidebar and click Enable Script Running on the gold Script Access banner (or find the same button in Robin's Settings).
- Firefox shows a permission prompt — click Allow.
- The banner disappears and scripts run in the page from now on.
Heads up: because this is a runtime permission, it does not appear in about:addons until you grant it through the prompt above. That's normal Firefox behavior, not a bug.
On Firefox 140
Firefox 140 has the permission but not the userScripts.execute API, so Robin uses a fallback runner. Chat and page examination work fully; script execution works on most sites but can be blocked by a strict content-security policy. Update to Firefox 141 or newer (or use Firefox Nightly) for the full runner.
Still seeing the Script Access banner?
- “Permission granted (API unavailable)” — you're on Firefox 140. The permission is granted; update Firefox to unlock the real runner.
- No prompt appeared — permission requests must come from a real click. Use the Enable Script Running button in the banner or Settings, not a keyboard shortcut.
- Accidentally denied it? Click the button again — Firefox will re-show the prompt.
Why Robin needs this
Generated scripts run via userScripts.execute() in the page's main world, which lets Robin act on the real page — clicking, filling, reading results — even on sites with a strict CSP, without using eval. Chat and page examination work without the permission; only script execution needs it.