HELP · CHROME / EDGE / BRAVE
Enable User Scripts on Chrome
Chrome gates the User Scripts API behind a per-extension toggle. Until you flip it, Robin can't inject scripts into the page — and runs fall back to a limited runner that strict sites block with a Content Security Policy error.
Chrome 138 and newer
- Open
chrome://extensionsin the address bar (on Edge:edge://extensions, on Brave:brave://extensions). - Find Robin and click Details.
- Scroll to Allow User Scripts and turn the toggle on.
- Return to the tab you were working on and run your script again — no restart needed.
Chrome 120–137 (Developer mode)
Older Chrome versions unlock the User Scripts API with the global Developer mode switch instead:
- Open
chrome://extensions. - Turn on Developer mode (top-right corner).
- Run your script again.
Updating Chrome moves you to the per-extension toggle above, which is the recommended setup.
Still seeing the Script Access banner?
- “Permission granted (API unavailable)” — the permission itself is granted, but the Allow User Scripts toggle is still off. Chrome keeps these separate, which is confusing; the toggle on the Details page is the missing piece.
- “Executing inline script violates … Content Security Policy” — the script ran through the fallback DOM runner because the User Scripts API wasn't available. Enable the toggle and re-run.
- Just installed from the Web Store? The toggle is off by default — this is expected on first run.
Why Robin needs this
Generated scripts run via userScripts.execute() in the page's main world. That's what lets Robin click real buttons, fill real forms, and read live results — even on sites with a strict CSP — without using eval. Chat and page examination work without the toggle; only script execution needs it.