UiPath Documentation
activities
latest
false
UI Automation activities

Configuration Steps

Enable Chromium Automation for a UI Automation project, run it with a visible or headless browser, and close browsers correctly.

Chromium Automation requires no per-browser downloads and no extension installation. Unlike the WebDriver protocol, you do not need to place any executable on the machine or add it to the system Path. You only need a supported browser installed and the correct package version, then select the mode.

Prerequisites

  • Google Chrome, Microsoft Edge, or another Chromium-based browser installed on the machine.
  • The UiPath.UIAutomation.Activities package, version 26.10.0 or later. Chromium Automation is generally available starting with this version.
  • The browser must be allowed to start with remote debugging enabled (see Group Policy below).

Modes

Two modes are available:

ModeBrowser windowBest for
Chromium AutomationVisibleDevelopment, debugging, and automations that need a visible browser
Chromium Automation HeadlessNone (headless)Unattended automation on servers and CI/CD pipelines
Tip:

Chromium Automation Headless combines zero-configuration setup with headless execution, which makes it well suited to unattended automation on servers where no display is available.

Enable Chromium Automation

You can set the automation method for a single activity or as a project-wide default.

For a specific activity

  1. Add a Use Application/Browser activity to your workflow.
  2. Locate Browser automation mode in the Properties panel.
  3. Select Chromium Automation (visible browser) or Chromium Automation Headless (no visible window).

As a project default

  1. Open Project Settings (gear icon in the Project panel).
  2. Go to UI Automation Modern > Application/Browser.
  3. Set Browser automation mode to Chromium Automation or Chromium Automation Headless.
  4. Select Save.

The activity-level setting takes precedence over the project default within its scope.

Note:

Some operations that depend on a visible window are not supported in headless mode. When you target headless mode, use the SimulateClick, SimulateType, and SimulateHover input methods on your activities, because hardware-event input requires a visible window. See Known Issues and Limitations.

Incognito (private) browsing

Chromium Automation supports Incognito mode without any additional configuration. This differs from the Browser Extension method, which requires enabling Allow in Incognito for the UiPath extension.

Closing browsers

To close a browser opened with Chromium Automation, use one of the following:

  • Close Tab activity — the recommended way to close a single tab.
  • Close Application activity — closes the browser session.

Because Chromium Automation manages the browser session internally, closing the automation scope also tears down the session and its temporary user-data-dir.

Group Policy considerations

Chromium Automation relies on the browser's remote debugging capability. It is blocked when the DeveloperToolsAvailability Group Policy is set to 2 (Disallow usage of the Developer Tools).

Warning:

If the DeveloperToolsAvailability policy is enforced with a value of 2 in your environment, Chromium Automation cannot start the browser. Use the Browser Extension method or the WebDriver protocol instead.

Was this page helpful?

Connect

Need help? Support

Want to learn? UiPath Academy

Have questions? UiPath Forum

Stay updated