Install Agentic Workers Supervisor

What the Supervisor Does

Agentic Workers Supervisor connects a client computer to a workspace. It runs in the background and manages the Hermes agents you select. The computer appears as an environment. Each selected Hermes profile appears as a separate agent on the Agents page.

Install one Supervisor to manage several agents. You do not need another Supervisor for each agent. The command is still named agw-device.

Before You Start

Use a Linux x86_64 computer with systemd and a non-root account. The workspace must have Ultra, and its owner must approve the connection. Administrator approval is needed for service startup when requested.

Use an account with only the access your agents need. Agent work has that local account’s access to files, commands, and apps. Connecting the device does not create an operating-system sandbox.

The installer also has an Apple Silicon macOS target. Mac hardware acceptance is pending, so do not treat it as a validated Mac deployment. Intel Macs, Windows, and Linux ARM are outside this release.

Add the Environment

Open the intended workspace, then Team settings, Environments, and Add environment. Copy the install command shown there. Account settings also supports environments for your account workspace.

Run that command in a terminal on the device as the chosen non-root account. It downloads a versioned release, verifies its checksum, and includes the runtime. You do not need Node, Docker, a source checkout, a VPN, inbound ports, or Fly credentials.

Open the pairing link shown by setup. Sign in as the workspace owner and check the workspace, computer, selected profiles, and payment choices before approving. The pairing code expires after ten minutes. If it expires, run setup again.

Choose only the detected Hermes profiles you want to connect. You may select none and create an agent later. Existing profiles default to their current provider credentials; Agentic Workers credits can be chosen per profile.

Confirm Each Agent Is Ready

Setup can report “Environment added” while individual agents are still being prepared. Check Environments, the Agents page, and agw-device status. An environment connection alone does not mean every agent is ready.

Each selected agent shows the device it runs on. Existing memory, sessions, skills, provider credentials, and approval settings stay with the profile. Setup backs up the settings it changes and checks for another service already running that profile.

Run a small task, such as asking the agent to report its operating system, then inspect the result and usage before relying on it for client work.

Create Another Agent on the Device

Open Agents and create a new agent. Select the connected environment as the place to run it. Several connected environments can appear as choices.

A new agent gets a dedicated Hermes profile. Fresh agents default to Agentic Workers credits and Hermes’ standard approval behavior. A local-provider choice needs a model ID and usable provider credentials on that new profile; it does not inherit another profile’s secrets.

The environment must be online, and the workspace must have a free Super Agent slot. Offline creation fails without queuing an agent. Keep the form and retry after the device reconnects.

Keep It Running

On Linux, the Supervisor uses a user systemd service with linger. It can start before interactive login once the account’s disk is available. It does not change Linux sleep policy. Keep the device powered, awake, and connected to the network.

Credentials that need an interactive login still need that login. A locked or unavailable disk cannot be accessed by the Supervisor. Closing the web browser does not stop an otherwise available device.