> For the complete documentation index, see [llms.txt](https://docs.autommate.com/userguide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.autommate.com/userguide/administration-and-runtimes/install-mate-agent.md).

# Install and connect a Mate Agent

Install a runtime where it can reach the applications, files and dependencies used by your automation. This guide applies to customer-managed execution hosts in hybrid or on-premises deployments.

Dublin package availability — 13 October 2026: the Dublin on-premises installer is not yet available. The steps below apply when you have a released package for your selected component and version. Confirm package availability and compatibility with <support@autommate.com> before starting.

## Prerequisites

Have the Agent package supported by your Autom Center release, the target workspace/Center connection details and the host's [requirements record](/userguide/administration-and-runtimes/system-requirements.md). Prepare the [network paths](/userguide/administration-and-runtimes/network-and-connectivity.md) and the service account used by the runtime.

Confirm required scripts, interpreters and local files before choosing the host. Access from your interactive administrator account may differ from access available to a Windows service.

## Install and register

1. **Select the target.** Identify the Center/workspace and environment this Agent will serve. Use an unambiguous host and Agent name.
2. **Obtain the package.** Use the supplied Agent installer for that environment and version. Confirm any supplied package integrity information.
3. **Run the installer.** On Windows, use the privileges required by the package. Review the installation directory, licence terms and setup summary, then complete the installation.
4. **Configure the connection.** Apply the workspace/Center endpoint, authorization and trust settings required by the package's registration process. Keep registration secrets out of tickets, screenshots and shared notes.
5. **Start the Agent services.** Confirm that the required services remain running and review any startup errors.
6. **Find the Agent in Autom Center.** In Dublin 6.0.0, open **Manage → Mate Agents**. Confirm the intended record, version and host details.

## Check execution identity and dependencies

The Agent card includes **Agent User**, **Time Zone**, **Created At**, **Mate Details** and **View Metrics**. Check these against the installation record. Review a **Default Device** assignment before using it for shared workflows.

For scripts or desktop actions, verify the execution account's access to files, interpreters, packages and the target system. Older Windows packages document **MAGateway** service-account and Task Scheduler requirements for Desktop Actions. Apply the instructions for your package; changing its service identity can affect existing automation.

If a dependency is missing from the service account's environment, add the required path or package using the host's approved change process. Test under the runtime account after the change, rather than relying on an interactive shell.

## Verify the first execution

Select the Agent for an isolated Hyperflow that performs a local transformation or reads one known test record. Run it once, find its execution record and check the action result. Then test any local script or file dependency required by the intended workload.

Use [runtime metrics](/userguide/administration-and-runtimes/plan-execution-and-runtime-setup.md) to check the relevant Agent Services and the timestamp of the latest resource snapshot.

## Expected result

The Agent is visible in the intended workspace, reports the expected version and executes the controlled test successfully. Record its host, role, owner, time zone and initial test result before assigning operational work.

If it is visible but an action fails, check that action's target connection and permissions. If it is absent or unavailable, begin with Agent startup logs, registration details, certificate trust and the Center–Agent network path.