Get started
Supported browsers
Reduck runs scripts on two types of browser:
- Default: your browser. Browser automation happens on your browser through the Reduck extension. The script uses your browser state: the sites where you are signed in, your browser fingerprint for stealth, and so on. It requires your browser to be open. See Stealth and signed-in sessions. Each browser you pair is a device with its own id: pair several, and a run can name which one.
- Cloud browser. Browser automation happens in Reduck’s cloud, so you can run scripts 24/7 without your browser, and at a larger scale than your machine allows. A run on your own browser spends one run from your plan; a run on a cloud browser also spends cloud browser time, so it costs more. See the pricing page.
Which one to use
| Your own browser | Cloud browser | |
|---|---|---|
| Signed-in scripts | Yes, with your sessions | Not yet: coming soon |
| Credentials | Never leave your browser | None today. Soon, your Auth session cookies for one site |
| Browser fingerprint | Your own browser’s | A Reduck browser, not yours |
| IP address | Your own connection | A datacenter in a region, or a residential proxy per country |
| Availability | Your browser must be open | 24/7 |
| Volume | Under about 100 runs per hour | Large volumes, many runs at the same time |
| Cost | One run from your plan | One run, plus cloud browser time |
Cloud browser
A cloud browser needs nothing on your side: no extension, and no browser open.
- MCP: a run goes to your own browser. Ask your agent to run on a cloud browser, or pass
browser: "managed"torun_script. - REST API: a
/rungoes to a cloud browser when it names no browser. Passbrowser: "extension"to run on your own browser.
What a cloud browser runs today
| Script | On a cloud browser |
|---|---|
| Signed out: it does not need a site account | Supported |
Signed in: it needs your site account (loggedIn) |
Not yet, coming soon with your Auth session cookies |
A cloud browser starts with none of your sessions. Reduck refuses a signed-in script there
before the browser starts, so the refused run spends no cloud browser time. In a call that runs several
scripts, one signed-in script refuses the whole call. Run that script on your own browser. To know if a script needs a site account, ask your agent to read it: a script that needs one
has loggedIn: true.
Region and country
A cloud browser runs in a region. Pick the one nearest to the site with region:
region |
Location |
|---|---|
eu-central-1 |
Europe (Frankfurt) |
us-east-1 |
US East |
us-west-2 |
US West |
ap-southeast-1 |
Asia Pacific (Singapore) |
The browser goes out to the web from a datacenter IP in that region, and some sites block
datacenter IPs. For those sites, set country to a two-letter country code such as "FR": the
run then goes out through a residential proxy in that country. A run with a country also spends
proxy bandwidth from your plan. whoami shows the cloud browser time and the proxy bandwidth you have
used in this period.
Your own browser
Reduck supports the different Chromium browsers: Arc, Brave, Chrome and Microsoft Edge. With Chrome, just install the extension. The other Chromium browsers each have one detail of their own below. If you would rather not keep a browser open at all, you want the cloud browser instead.
Reduck needs Chromium 138 or later, which any current release clears. Firefox, Safari and Opera are not supported.
Microsoft Edge
Edge asks for permission the first time you install an extension from a store other than its own. Allow it, and the Chrome Web Store listing installs normally. Nothing else differs from Chrome.
Brave
Brave blocks Google’s push messaging by default, and push is how the server wakes your browser for a run. Turn it on before you pair, or the extension reports Session Active but no run ever starts.
- Open
brave://settings/privacy. - Turn on Use Google services for push messaging.
- Restart Brave.
- Open the Reduck extension side panel and pair the browser.
Chrome on Linux
Supported, but the browser must run headful, on a real desktop session or on Xvfb plus a
window manager. Headless gives up the ordinary, visible browser that lets scripts survive sites
that block automation (Stealth).
Xvfb :99 & export DISPLAY=:99
Arc
Arc has no side panel, which is where pairing happens, so the only way to pair a device is to reinstall the extension: remove it, install it again, and pair from the prompt that follows.
Arc also reports itself as plain Chromium, so it is listed as Chromium, not as Arc. If you pair several Chromium browsers, that is the one detail that will make you run a script on the wrong one.
Firefox, Safari and Opera
Not supported, and not a setup problem you can work around.
Firefox and Safari rely on extension APIs that Chromium has and they do not, so supporting them takes more than porting the extension. It is on the roadmap, but not planned in the short term.
Opera is Chromium-based, but it is not one of the browsers we support or test today. The extension is not validated there, so pairing it is not something we can back yet.
On a phone or a tablet, Reduck still works from your agent’s app, with the scripts running in a browser that you paired on another computer: see Phone and tablet.