Browser Runtimes

Stealth

View as Markdown

Stealth settings belong to the browser runtime, not to the automation library. Configure them when you launch the runtime, then connect with Playwright, Puppeteer, Selenium, or another CDP client.

Enable stealth behavior

1const runtime = await space.runtimes.browser.launch({
2  name: "checkout",
3  config: {
4    stealth: "high",
5    humanize: true,
6  },
7});

Use a profile when identity should survive across runs.

1const runtime = await space.runtimes.browser.launch({
2  name: "crm",
3  profile: "prof_sales_bot",
4  config: {
5    stealth: "high",
6    humanize: true,
7    proxy: {
8      mode: "saved",
9      id: "proxy_us_residential",
10    },
11  },
12});

What it changes

Stealth settings can reduce common browser automation signals such as WebDriver flags, timing patterns, fingerprint inconsistencies, and mechanical input behavior.

They do not make automation undetectable. Treat stealth as one part of a broader setup: stable profiles, appropriate proxies, realistic pacing, and clean browser state.