- DEB for Ubuntu/Debian (x86_64) — desktops and servers with a GUI
- RPM for Red Hat/CentOS/Fedora
For Raspberry Pi, see the Raspberry Pi Installation guide.
Run these commands in a terminal as a regular user (not root):
sudo apt-get -y update
sudo apt-get -y upgrade
wget https://agents.triggercmd.com/triggercmdagent_1.0.1_amd64.deb
sudo apt install ./triggercmdagent_1.0.1_amd64.debIf your system uses AppArmor, run this first:
sudo sysctl -w kernel.apparmor_restrict_unprivileged_userns=0Then launch the agent:
triggercmdagentA GUI window will appear. Log into triggercmd.com, copy your token from the Instructions page, and paste it into the token prompt.
Install Node.js 16 or newer if it's not already installed:
curl -fsSL https://deb.nodesource.com/setup_lts.x | sudo -E bash -
sudo apt install nodejs -yThen run the agent in console mode:
node /usr/lib/triggercmdagent/resources/app/src/agent.js --consoleLog into triggercmd.com, copy your token from the Instructions page, and paste it when prompted.
The background service keeps the agent running after you log out.
Right-click the TRIGGERcmd tray icon and select Background Service → Install Background Service.
First stop the console agent with CTRL-C, then run:
sudo sh /usr/lib/triggercmdagent/resources/app/src/installdaemon.shCheck if the service is running:
systemctl status triggercmdagentRemove the background service:
sudo sh /usr/lib/triggercmdagent/resources/app/src/removedaemon.shsudo yum install wget -y
wget https://agents.triggercmd.com/triggercmdagent-1.0.1.x86_64.rpm
sudo rpm -i triggercmdagent-1.0.1.x86_64.rpmThen follow the same token setup and background service steps above.
- Log into triggercmd.com.
- Click View Triggers — you should see your computer listed with some built-in commands.
- Click Trigger next to any command to test it.