English
Open the app

Agent worker

Run your automations on a machine you own

The agent worker is a single program you install on your own computer or server. It signs in to your UIA account once, then waits for tasks and jobs to arrive. The browser opens where the worker runs — never on our servers.

Version
1.0.0
Runs on
Windows, macOS, Linux

Downloads

Pick your platform

Each download is a self-contained build — there is no Python to install and nothing to compile.

Google Chrome must be installed on the same machine. The worker drives your existing Chrome rather than shipping its own browser.

Installation

From download to first run

Setup takes about two minutes. The worker asks you a few questions the first time you start it, registers itself against your account, and stores its credentials encrypted on that machine.

  1. 01

    Unzip the download

    Right-click the archive and choose Extract All. Put the folder somewhere permanent — the worker installs itself alongside its own files on first run.

  2. 02

    Allow it to run

    Windows may warn that the publisher is unrecognised. Choose More info, then Run anyway. The build is not yet signed with a commercial certificate.

  3. 03

    Start the worker

    Double-click agent-worker.exe, or run it from a terminal in the extracted folder. The setup wizard opens in the console window.

    agent-worker.exe
  4. 04

    Register the machine

    Give the worker a name you will recognise in the app, then sign in with your UIA username and password. The worker exchanges them for a token and encrypts it — your password is never stored.

  5. 05

    Run it for real

    Setup exits when it finishes. Start the worker again with its name and it connects and waits for work. It should appear as idle on the Workers page within a few seconds.

    agent-worker.exe my-worker

If something goes wrong

Common first-run problems

The Workers page shows the worker as offline

Check that the worker process is still running and that outbound WebSocket connections are allowed through your firewall. If the worker looks online but jobs still run somewhere else, set WORKER_HEARTBEAT_SECONDS to 20 and restart it.

It starts but every browser task fails immediately

The worker drives Google Chrome and needs it installed on the same machine. Install Chrome, then start the worker again. If Chrome is installed somewhere unusual, point CHROME_PATH at the executable.

Windows or macOS refuses to open the file

The builds are not signed with a commercial certificate yet, so both systems warn about an unidentified developer. On Windows choose More info, then Run anyway. On macOS clear the quarantine flag as shown in step 02, or use Open Anyway under Privacy & Security.

Set the worker up, then build something for it to run

Open the appRead the guide