This installs the software agent on a host. Once it’s authorized, the
AI agents can read its telemetry
and act on the host.
Get an Installation Token
The Download Agent quick action opens the Install Agent panel as a tab in the Workspace, with a tab for Windows, Linux and macOS. The panel already holds the installation token for the context you’re in — you don’t generate it, you copy it with Copy Token, or copy a ready-to-run command with Copy Script.The token is scoped to the context you have selected, and carries its id as
a prefix. Installing with it enrolls the host into that context — see
Migrate a host between contexts to move one
later.
Windows
Pick the Architecture first — 64-bit (x86_64) or 32-bit (x86) — then choose a method:- Installer — Download MSI, run it, and paste the token when the setup wizard prompts for it.
- PowerShell — an automated script that downloads the MSI itself and installs it silently. Run it in PowerShell as Administrator.
TOKEN property:
macOS
Requirements: a Mac with Apple Silicon (M-series), running macOS 11 (Big Sur) or later. There is no build for Intel Macs.- Installer — Download PKG, run it, and paste the token when prompted.
- Bash Script — a script the panel generates for the target architecture and agent version. Copy it and run it in Terminal with sudo.
Linux
Linux has a single method: one Installation Script you run in Terminal with sudo. It passes your token and context as environment variables and pipes the installer to bash:During installation the host downloads dependency packages, so allow outbound
443 to
*.myrmex.ai and to your distribution’s official repositories. See
Collector mode
for the full network model.
Authorize the Device
Open the new device from the Endpoints view or its detail view and choose Authorize. The device activates and begins reporting, and you can then set its role, rules, and more.Migrate a Host Between Contexts
A context is the organization / tenant a host reports into. To move an already-installed host from one context to another you don’t uninstall anything — you re-run the installer with the new context’s token, and the agent re-enrolls itself.1
Get the new context's install command
Switch to the target context and open its Download Agent page. Copy its installation token (Copy Token) or the ready-to-run command (Copy Script) — both are scoped to that context.
2
Run it on the host
Run that exact command on the host as root / administrator — the same command as a fresh install. The agent re-registers against the new context: it obtains a new identity, rewrites
config.yml / env.conf to point at the new context, and reconnects. No uninstall or reboot is needed.3
Authorize it in the new context
The host appears in the new context’s Endpoints view as unauthorized. Approve it there to reactivate telemetry and response. In the old context it stops reporting and can be removed.
Re-running the installer simply overwrites the host’s context binding (
config.yml / env.conf) with the new context’s — that is the whole migration. The agent binary and its services stay in place.Auto-Updates
You don’t reinstall to stay current. A supervisor service (myrmex-supervisor) runs alongside the agent, keeps it running, and applies new versions silently in the background — see Agent architecture for the services and the files they maintain.
Where to Go Next
Device details & actions
Authorize, set the role, and run actions on the host.
Endpoint vs Collector
Choose how the device runs after install.
Agent communication
How enrollment and the token work under the hood.
Agent capabilities
What the agent does once it’s live.