The agent Supported platforms
Supported platforms
Only Windows is supported today. macOS and Linux have an installer, but they are not supported yet. This page says what each claim rests on, so you can decide for yourself.
What "supported" means here
A platform counts as supported only when the agent has been installed and run on a real machine with that operating system. A build that compiles, or a test run that passes, does not make a platform supported.
| Platform | Supported | Where it stands |
|---|---|---|
| Windows, 64-bit x86 | Yes | The agent has been installed and exercised on real machines. |
| Linux, 64-bit x86, with systemd | No | See below. |
| macOS, Apple silicon | No | See below. |
Linux
The installer registers the agent as a systemd unit. It needs a machine that runs systemd, and it stops with No systemd on one that does not.
What has been run: the service lifecycle, on one test machine against a stand-in server. Install, restart after the process was forcibly ended, a clean stop and uninstall all behaved as designed.
What has not: an install through the installer that then reported to a deployed console, or a real AI tool firing its hook on Linux.
macOS
The installer registers the agent as a launchd daemon.
What has been run: the service lifecycle, on one Mac against a stand-in server. Install, restart after a crash, a clean stop, an in-place upgrade and uninstall with a removal key all behaved as designed.
What has not: an install through the installer that then reported to a deployed console since the installer's last fix, or a real AI tool firing its hook on macOS.
Not on macOS or Linux yet
The browser extension's force-install policy is written on Windows only. On macOS it needs an MDM, and on Linux it is not written at all, so the agent says so rather than doing nothing silently.
Where the agent installs
| Windows | macOS | Linux | |
|---|---|---|---|
| Runs as | A Windows service | A launchd daemon | A systemd unit |
| Program | C:\Program Files\Oxelone\oxel-agent.exe | /Library/Application Support/Oxelone/bin/oxel-agent | /usr/local/lib/oxelone/oxel-agent |
| Data and logs | %ProgramData%\Oxelone\agent | /Library/Application Support/Oxelone/agent | /var/lib/oxelone/agent |
| Service definition | The Windows service registry | /Library/LaunchDaemons/com.oxelone.agent.plist | /etc/systemd/system/oxel-agent.service |
On macOS and Linux the program must sit in a directory only root can write. The installer checks this before it spends your token, and stops with This machine cannot run the agent as a service if it is not.
Run as an administrator
Run the install command as an administrator. On Windows that is an elevated
PowerShell. On macOS and Linux, put sudo in front of sh, as the command the
console generates does. Deployment has the commands.