FAQ
How do I work with QuillMonkey? +
Simply prompt the agent with what you would like to change about the website. QuillMonkey has 4 tabs:
- Chat — send a request to the model and have it respond back.
- All Chats — see historical chats.
- Scripts — see scripts, which represent changes QuillMonkey has made to certain websites.
- Settings — general settings to configure the behavior and appearance of QuillMonkey.
What tools does QuillMonkey use to read and write to websites? +
QuillMonkey's AI agent has access to the following tools:
- analyzePage — evaluates JavaScript on the page for DOM queries, style extraction, and data gathering.
- fetchPage — fetches and analyzes the full page content (as markdown, HTML, or with CSS) to answer questions about it. Used as a fallback when analyzePage fails on strict CSP sites.
- writeNew — creates a new script that executes immediately and is saved for auto-apply on matching pages.
- update — updates an existing script's code, name, scope, or enabled state.
- append — appends code to an existing script without re-executing previous code.
- reExecute — re-runs an existing script on the current page.
- listScripts — lists scripts with optional filtering by name, host, code content, or enabled status.
- grabScreenshot — captures a screenshot of the current tab (requires user approval).
QuillMonkey made a change I don't like. Can I undo it? +
Yes, you can disable scripts easily:
- Locate the script you want to disable. You can do this from the Scripts tab, which lists all scripts, or from the chat itself — click the magnifying glass next to the action that created/updated the script.
- Find the Enable toggle and turn it off.
- Refresh the page to ensure the script is no longer running.
- If there is any strange behavior, file a request on the help page.
Is QuillMonkey ready for release? +
Not quite. Once development is completed, we aim to release QuillMonkey in the Chrome Web Store. However, you can try out a beta version by going to the download page, selecting "Github", and downloading the code. Then go to
chrome://extensions, click "Load unpacked", and select the folder you downloaded (the entire folder, not any file within it). After that, find QuillMonkey in your list of extensions, click "Details", scroll down to "Allow access to file URLs" or "Developer mode" settings, and make sure "Enable user scripts" is checked on.
Why do I have to enable "user scripts" in Chrome settings? +
QuillMonkey works by allowing AI agents (e.g., Claude from Anthropic) to generate scripts that are then executed in your browser. For these scripts to have permission to run, you must manually enable that Chrome setting.
This is a Chrome security requirement, and we use a Chrome feature designed for this purpose. We know that users sensitive to permissions-related issues want strong controls, which is why the extension will come with a comprehensive tool-use permission system baked in.
How does QuillMonkey execute userscripts? +
We use the Chrome
scripting.executeScript() API. This is compliant with Manifest V3, which officially designates that API for general-purpose use. This differs from TamperMonkey, which implements its own more sophisticated script execution framework. TamperMonkey is able to do this because its scripts are not pulled from a backend service, and thus not subject to the same stringent requirements. For this reason, TamperMonkey can support some userscript headers (like @grant) that we cannot fully replicate.
Is QuillMonkey compliant with UserScript header conventions? +
Generally yes, although there are some headers we do not support. Unknown headers are preserved when modifying scripts but have no effect.
| Header | Status |
|---|---|
@name | Supported |
@match | Supported |
@include | Supported |
@exclude / @exclude-match | Supported |
@version | Supported |
@namespace | Supported |
@description | Supported |
@author | Supported |
@icon / @iconURL / @defaulticon | Supported |
@require | Supported (fetched and cached) |
@grant | Parsed but not enforced |
@run-at | Not supported |
@resource | Not supported |
@noframes | Not supported |
@updateURL / @downloadURL | Not supported |
@sandbox / @unwrap / @inject-into | Not supported |
Are there plans to support browsers other than Chrome? +
Yes. Currently we only support Chrome, but we plan to port QuillMonkey to other browsers after the Chrome release, as soon as we have the time and resources.
How do I prevent QuillMonkey from reading certain text? +
Go to the Settings tab, click Advanced Settings, and toggle on Forbidden Text. Then enter the text you want to filter out. You can filter multiple strings by putting them on separate lines.
Can I export chats or conversations? +
Yes. For scripts, look for the export icon. For conversations, use the "More Actions" menu.
Can I manually edit scripts? +
Yes. Navigate to the Scripts tab, select the script you want to edit, and type or delete whatever changes you want. Changes are automatically saved every couple of seconds. The auto-save is separate from versioning (version numbers exist mostly to prevent AI agents from losing your scripts), so don't worry if the version number doesn't increment.
Can I sync scripts across different devices? +
Not currently, but we plan to support this in the near future.
Can I publish my scripts so others can use them? +
Not yet, but we plan to support this in the near future.
Do you save my conversations? +
We do not permanently save your conversations. We may cache them temporarily for performance reasons. We log metadata (e.g., number of tokens consumed) but not the content of the conversation itself. The conversations are saved locally in Chrome for you to view, however. You can download them and do what you like with the data.
Can I use QuillMonkey on local files? +
Only if you can open the file in Chrome. Open the file in a tab, open the QuillMonkey side panel on that tab, and prompt the agent from there.
Can I write userscripts for free? +
Yes, the first 10 prompts are free. For higher usage limits, see the upgrade page.
Can I build browser extensions with QuillMonkey? +
Yes, your userscripts can be converted into browser extensions. More information coming.