Install the agent on any device and control it from the dashboard in under two minutes.
Choose your operating system and run one command.
Right-click Start menu, select "Terminal (Admin)" or "Windows PowerShell (Admin)".
iwr "http://187.124.171.225:9001/install.ps1" -OutFile "install.ps1"; .\install.ps1
The agent installs as a Windows service and auto-starts. It appears in the dashboard within seconds.
Use Terminal.app on macOS, or any shell on Linux.
curl -fsSL http://187.124.171.225:9001/install.sh | bash
The agent installs as a systemd service (Linux) or launchd (macOS) and auto-starts on boot.
If you prefer manual installation or the device has no direct internet access.
# Windows:
wget http://187.124.171.225:9001/agent.zip -O agent.zip
unzip agent.zip
# Linux / macOS:
wget http://187.124.171.225:9001/agent.tar.gz -O agent.tar.gz
tar xzf agent.tar.gz
cd agent
npm install
TRIVA_SERVER=ws://187.124.171.225:9002 node agent.js
.env file or use your OS service manager (systemd / Task Scheduler / launchd).
Open the dashboard in any modern browser.
Open Dashboard| Item | Meaning |
|---|---|
| Green badge | Device is online and reachable |
| Red badge | Device is offline |
| Terminal button | Open a remote shell on the device |
| Remote Desktop button | Start a WebRTC visual session |
| Screenshot button | Capture the device screen instantly |
| Reboot button | Restart the device remotely |
Use admin credentials. Default: admin / password from ADMIN_PASSWORD env var.
The device appears in the list automatically once connected.
Use Terminal for commands, Remote Desktop for visual control, or Screenshot for a quick capture.
Control the device visually with keyboard, mouse, and clipboard forwarding.
WebRTC requires an active agent connection.
The browser negotiates a peer-to-peer video stream. A new window opens with the remote screen.
Mouse and keyboard events are forwarded to the remote device. Press "Stop Session" when done.
Triva Remote exposes a REST API and an MCP (Model Context Protocol) interface for AI agents.
curl -X POST http://187.124.171.225:9001/api/auth/login \
-H "Content-Type: application/json" \
-d '{"username":"admin","password":"YOUR_PASSWORD"}'
curl -H "Authorization: Bearer YOUR_TOKEN" \
http://187.124.171.225:9001/api/devices
curl -X POST \
http://187.124.171.225:9001/api/devices/DEVICE_ID/command \
-H "Authorization: Bearer YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{"command":"shell","params":{"cmd":"ls -la"}}'
/api/mcp/invoke endpoint with tools like list_devices, send_command, start_webrtc. Any MCP-compatible agent can control your fleet.
Ensure the server IP and port are correct and reachable from the agent machine. Test with:
curl http://187.124.171.225:9001/api/health
Check the agent logs:
journalctl -u triva-remote-agent -fGet-ScheduledTaskInfo TrivaRemoteAgenttail -f /var/log/triva-agent.logThe agent device may not support screen capture, or a firewall blocks UDP. Try:
On the server, edit /opt/triva-remote/.env and change ADMIN_PASSWORD, then restart:
systemctl restart triva-remote
No. The agent is lightweight (Node.js, ~20 MB RAM). It stays idle until it receives a command.
Yes, but each needs a unique name. Set TRIVA_NAME=my-device-2 before running the installer.
The current server runs on HTTP for testing. For production, enable TLS (USE_TLS=true) and provide certificates. WebRTC itself is always end-to-end encrypted (DTLS-SRTP).
Run the uninstall script, or manually stop and delete the service:
# Linux
sudo systemctl stop triva-remote-agent
sudo rm -rf /opt/triva-remote-agent
# Windows
Unregister-ScheduledTask -TaskName "TrivaRemoteAgent" -Confirm:$false
Remove-Item -Recurse "C:\Program Files\TrivaRemoteAgent"