vm-vitals
install · linux and macos

let the bot install it.

Copy the prompt, paste it to Grok Bot (or Claude Code, or Codex). It runs one line on its own computer and hands you the dashboard link. This page jumps there by itself when the first heartbeat lands.

read the prompt first ↓
Hey Grok Bot, install VM Vitals on your computer so I can watch your vitals. Run exactly this command, then tell me the dashboard link it prints: curl -fsSL https://vm-vitals.vercel.app/install.sh | sh -s -- pair_•••••••••••••••• It only sends system numbers (disk, CPU, memory, network, process names, tool versions). Never env vars or file contents. Don't change the command. If you don't have sudo, run it without; a user-level service is fine.

Your copy gets a real one-time token in place of the dots. It's good for 24 hours and tied to this browser.

open source · read every line

What gets installed

  • binary~/.local/bin/vm-vitals, a static Go binary, about 6 MB. With sudo it goes to /usr/local/bin. source
  • config~/.config/vm-vitals/config.json, mode 600. Server URL, machine id and the machine token.
  • serviceLinux: a systemd unit. macOS: a launchd agent. No systemd bus (containers, some VMs): a background process plus a crontab @reboot line. the templates
  • networkOne HTTPS POST to vm-vitals.vercel.app/api/ingest every 30 seconds. Nothing listens on a port.
  • installerinstall.sh downloads the binary for your OS and CPU and runs vm-vitals install. Read it before you pipe it.

Exactly what it sends is on what it sends. Every line is on GitHub.

after

Inspect it, stop it, remove it

# print the exact JSON it sends, then exit
$ vm-vitals once

# paths, whether it's running, and the service file verbatim
$ vm-vitals status

# logs
$ journalctl --user -u vm-vitals -f        # linux
$ tail -f ~/Library/Logs/vm-vitals/agent.log  # macos

# stop it and delete the service, binary, config and logs
$ curl -fsSL vm-vitals.vercel.app/uninstall.sh | sh

vm-vitals uninstall does the same if ~/.local/bin is on your PATH. Installed with sudo? Put sudo in front of sh. Then delete the machine from its dashboard to drop its history.