Ctrlk

Launch Browser

The Launch Browser block allows you to launch a browser for your TaskBot to use. Subsequent no-code web-interaction blocks (like Click Web Element, Save Web Element, etc) act on the browser context this block launches.

This block is one of several ways to launch a browser. You can also launch with an Open Link block or programmatically via zw.browserContext.launch() in a Write JS block. For the latter, see Browser Context for the full API.

How To Use It

This block works with no configuration.

You might not need to use this block. Every setting listed below defaults to Use current defaults, which inherits from your TaskBot's Browser Launch Settings or any values previously set via zw.browserContext.setDefaults() in a Write JS block.

This block lets you override individual settings as needed during a TaskBot's run without a Write JS block.

These overridden settings become the new defaults for this TaskBot at runtime. To reset or undo, add another Launch Browser block that reverses the previous Launch Browser block's settings prior to subsequent blocks.

Launch mode

Controls how the browser session is managed.

  • Use current defaults inherits from your TaskBot's Browser Launch Settings.

  • When unchecked, you can choose between:

    • Incognito an isolated browser session. No data persists between runs.

    • Sticky a persistent browser profile. Cookies, storage, and login state survive between runs. Enter your Sticky profile ID. Clicking COPY PROFILE ID allows you to select from a list of your available profiles. Your selected sticky profile is copied to your clipboard; paste it into the Sticky profile ID field.

You can create new sticky profiles in Browser Launch Settings to make them available here.

Run mode & window

Bypass bot detection

When enabled, your TaskBot is no longer detectable as bot automation.

When Bypass bot detection is enabled, some settings are ignored (Window size, Launch arguments, Browser) and file uploads larger than approximately 50 MB are blocked. File downloads are unaffected.

Run in background

Runs the browser in the background with no visible window. Uses fewer resources.

When running in background, the browser uses a fixed viewport. If you don't set a Window size, the default (1280 x 720) is used.

Maximize

Maximizes the browser window on launch. Ignored when running in background.

Window size

Sets the browser viewport dimensions. This setting only takes effect when Maximize is off or Run in background is on.

  • Use current defaults inherits the current viewport size.

  • When unchecked, you can set Width and Height in pixels.

Cookies

Provide cookies up front so they are reapplied on every context relaunch.

  • Use current defaults inherits cookies from your Browser Launch Settings.

  • When unchecked, paste cookie JSON into the text field. Each cookie should include at least name, value, and domain.

  • Click + ADD COOKIE to add cookies from additional websites. Click the trash icon to remove one.

See Cookies for how to export cookies from your browser and use them in ZeroWork.

Proxy

Route browser traffic through a proxy server.

  • Use current defaults inherits proxy settings from your Browser Launch Settings.

  • When unchecked:

    • Proxy server host:port or socks5://host:port for SOCKS5 proxies.

    • Username HTTP proxy authentication. Not supported for SOCKS5.

    • Password HTTP proxy authentication. Not supported for SOCKS5.

    • Bypass domains comma-separated domains to bypass the proxy (for example, example.com, google.com)

See Proxies for more info on how to use proxies in ZeroWork.

Browser

Controls which browser executable to use at runtime.

  • Use current defaults inherits from your Browser Launch Settings.

  • When unchecked, you can choose between:

    • Default Chrome browser your installed Chrome is auto-detected and used.

    • Custom browser provide a Browser path to any Chromium-based browser (Chrome, Brave, Chromium, etc)

Not sure where to find your machine's browser path? Open chrome://version or brave://version in your browser choice and copy the Executable Path value.

Launch Arguments

Custom browser executable command line arguments.

  • Use current defaults inherits from your Browser Launch Settings.

  • When unchecked, enter Chrome command line arguments as space-separated flags (for example --mute-audio --disable-notifications)

Some arguments can interfere with ZeroWork's built-in bot detection bypass and may also prevent the browser from launching. Only add arguments if you know what they do. For a full list of command-line arguments, see Chromium Command Line Switches

Scripts

Scripts are injected before any page loads and reinjected on context relaunch.

  • Use current defaults inherits from your Browser Launch Settings.

  • When unchecked, you can add one or more scripts. Each script can be one of:

    • Path an absolute file path to a .js file (e.g., /Users/<username>/Documents/script.js).

    • Content inline JavaScript code.

  • Click + ADD SCRIPT to add additional scripts. Click the trash icon to remove one.

Page visibility

Stay on page after run

When enabled, the browser stays open after the TaskBot run ends.

Run in background + Stay on page after run is not recommended. It leaves an invisible browser consuming resources on your machine after your TaskBot has ended. Additionally, when using sticky profiles with this combination, the connection may drop after a long machine sleep, which can block the profile until the Desktop Agent is restarted.

Things To Know

  • This block always becomes the main browser context. It replaces any existing browser context. If a Write JS block already launched a context, this block replaces it.

  • Settings become defaults for this run. Whatever you configure in this block becomes the active defaults for the rest of the run until you change it.

  • There's one browser per sticky profile. Multiple TaskBots with the same sticky profile ID share the same browser instance in parallel tabs. This block attaches to the existing instance if one is already running. When attaching, browser-level settings (Run in background, Bypass bot detection, Maximize, Window size, Browser, Launch arguments) are ignored as they would've already been set when the browser first launched. Cookies, Scripts, and Page visibility settings still apply.

  • Closing the last tab ends the context. If a Switch or Close Tab block closes the last tab, the context ends. The next Open Link block creates a fresh context from the current defaults.

Block Behavior

  • When no browser exists this block launches a new browser with the configured settings. No URL is opened initially; the browser starts on about:blank. Use an Open Link block after this to navigate to a URL.

  • When a browser already exists (from Open Link, Write JS, or a previous Launch Browser block) this block closes the existing context and launches a new one.

  • When a sticky profile browser is already running from another TaskBot this block attaches to the existing browser instance. Browser-level settings are ignored. Cookies, Scripts, and Page visibility settings still apply.

PreviousGo Back or ForwardNextQuit Browser

Last updated