BROWSER AGENT · 11 TOOLS · ASKS PER SITE
Give your model a real browser
Pair the extension and the model opens pages, reads them, fills forms and takes screenshots in your own browser, signed in as you, only while the pairing is live. What it reads goes to the model you picked in the panel; that is what makes it able to act at all. Every call is printed in the panel while it runs, and a site it has not seen before gets a card to approve first. The pairing token stays in the extension and never reaches page code.
Chrome & Edge, Brave
Chromium 116 or newer. Unpacked install while the Web Store listing is in review.
Download for Chrome (.zip)- Unzip the download to a folder you will keep.
- Open
chrome://extensionsand turn on Developer mode (top right). - Click Load unpacked and choose the unzipped folder.
- Open the side panel from the ZeroLog icon, then Pair. The app shows a code to enter.
Firefox
Firefox 140 or newer. The same 11 tools, rebuilt on Firefox’s own WebExtension APIs because Firefox has no CDP. One difference: screenshots there cover the visible viewport, not the whole page.
Download for Firefox (.zip)- Unzip the file.
- Open about:debugging#/runtime/this-firefox.
- Click Load Temporary Add-on… and pick the manifest.json inside the folder.
- Open the ZeroLog panel from Firefox’s sidebar button, or click the toolbar icon.
- Press Pair and enter the code from Settings → Extension.
Not yet signed by Mozilla. Firefox refuses to install an unsigned add-on from a URL, so this build loads temporarily and is gone when you close Firefox. Load it again from about:debugging next time. A signed one-click build is pending.
What it sends, and what it refuses
Where the page goes. What a tool reads, meaning page text, the accessibility tree, screenshots and console lines, travels over an authenticated socket to ZeroLog and on to the model you selected in the panel. Nothing else is collected: no other tab, no cookies, no stored passwords, no browsing history. The one tool that sees wider is the tab list, which returns the title and URL of every open tab, and on the default tier it waits for your click every time. ZeroLog does not use your content to train models. The provider behind the model you picked has its own policy, so choosing the model also chooses who reads the page.
What it refuses, in every tier. It will not type into a password, payment-card or one-time-code field. The check runs on the element it actually resolved, not on the model's word for it, and neither the server nor a page can switch it off. It navigates to http and https only, so javascript:, data:, file: and chrome:// are dead ends rather than gaps in a blocklist.
How it asks. Three tiers decide what still needs your click. Smart auto-risk is the default: reading (screenshot, accessibility tree, find, scroll, console, wait) and navigation run on their own, while clicking, typing, key presses and tab actions wait for you. Manual approval asks for everything, Always allow for nothing. A site it has not met yet gets its own card, once per scheme and host, stored in your browser and revocable under Settings, Extension. If nobody answers within two minutes the action does not run, and the model is told that nobody answered rather than that you refused. On Chrome its own debugging banner stays up the whole time the extension is attached to a tab.
Why neither install is one click. Chrome installs an extension on its own only from the Web Store. A signed package served from our own domain, offered through Chrome’s own enterprise policy, is declined with this computer is not recognised as enterprise-managed, so only extensions hosted in the Chrome Web Store can be installed by policy. Firefox is no better placed today: the build above is not signed by Mozilla yet, and Firefox turns down an unsigned add-on from a URL. Both routes stay manual until the Web Store listing clears and the signing run against AMO has happened. Neither route changes a security setting, and you can remove the extension whenever you want.