Install the desktop agent on Linux

To manage one Linux computer, generate its customer-specific shell command in your workspace, run it with approved root access, then verify later telemetry. Use the returned command for your distribution and architecture.

Before you start

You need an OWNER or ADMIN workspace account, an existing customer, and permission to use sudo on the target computer. Obtain the current approved artifact and release-trust procedure from your platform operator. Inspect the generated command through your organization's software approval process before running it.

Install one computer

  1. Open Generate an installer on Dashboard, or open /installers on your workspace host.
  2. Under Generate installer & enrollment token, select the correct Client, optional Location, Linux Operating system and the applicable distribution/architecture choices.
  3. Optionally enter a Label, then choose Generate. Copy the complete generated command, including its workspace address and enrollment token.
  4. Run that command in a terminal on the authorized target computer with permission to use sudo. The returned command downloads and invokes the installer for that workspace. Additional DEB/RPM choices do not establish that a separate package was generated.
  5. Open Monitoring > Devices, clear filters and find the hostname under the selected customer. Open Overwatch and check CPU/memory and a later performance sample. Refresh after another check-in and confirm last seen advances.

The installer selects the supported service manager and applicable libc artifact. An immediate Online badge, Enrolled attempt or running process is insufficient: enrollment sets last seen before the first metric. The agent normally checks in every 60 seconds; allow several minutes for setup and refresh without assuming a guaranteed completion time.

Check desktop capabilities separately

Remote capture depends on the native artifact, desktop environment, X11/Wayland support, portal and local consent. Headless, musl and non-cgo artifacts have capability limits. Verify capture and input independently from heartbeat and performance reporting.

Enrollment tokens are reusable for 30 days. Protect copied commands, links and tokens. Revoke prevents new enrollment with that token and does not uninstall existing agents. Duplicate short hostnames within one customer are refused with 409 hostname_already_enrolled. Preserve saved agent configuration on reinstall; if it is lost, retire the stale record through an authorized administrator or use a distinct short hostname before retrying.

If installation or reporting fails

Check workspace URL, token validity, outbound HTTPS, service state and the redacted installation error. Use Onboarding troubleshooting for the failing stage. See Desktop agent for update trust and removal, or Getting started for workspace setup.