On servers, a Mac mini or other machines without a screen, install the waper-node command-line daemon to connect them to your agent. It works like the desktop app — same execution, approvals and access scope — just without a window. For what the agent can do and how it picks a computer, see Your computers.
It runs on macOS and Linux and needs Node.js 22.19 or later.
You then have the waper-node command. waper-node --help lists every command.
The terminal shows a short code and a link starting with https://waper.ai/device. Open the link in any browser where you're signed in to waper (your phone works too), check the code and choose Approve. Only approve a code you just started yourself.
Options for sign-in:
| Option | What it does |
|---|---|
--name <name> |
The name this computer shows in waper; defaults to the host name. It's the name you use when you tell the agent "on …" |
--folders <a,b> |
Let the agent use only these folders, comma-separated; ~ works. Without it the agent can use the whole computer. Change it later under Settings → Computers |
For example:
For unattended setups, pass a session token on standard input instead of confirming in a browser. The token is only read from standard input, so it never appears in the command line or your shell history:
Run in the foreground; the terminal lists what the agent is doing as it happens. Press Ctrl+C to stop:
Install it as a background service that starts at boot or login and restarts if it crashes:
macOS: installs the launchd user agent ai.waper.node; logs go to ~/.waper/logs/node.log.
Linux: installs the systemd user service waper-node.service; read logs with journalctl --user -u waper-node. User services stop when you log out by default; to keep it running, run this once:
Check or remove the service:
| Command | What it does |
|---|---|
waper-node status |
Shows the server address, the computer name, whether you're signed in, and the background service's state |
waper-node logout |
Signs out: the session is revoked on the server and the token is deleted from this computer |
waper-node browser install |
Lets the agent use the Chromium-based browsers on this computer; see Your browser |
If the computer is disconnected under Settings → Computers or its session ends, waper-node run says so and exits; run waper-node login again.
waper-node keeps its data in ~/.waper, readable only by your user account: settings, the session token, logs, pending results, and the previous versions and trash used for undo. None of it is open to the agent.
To use another location, add --state <dir> to every command or set the WAPER_STATE_DIR environment variable. service install writes the directory in use into the service configuration.
Command-line messages follow your system language (LANG): Chinese for Chinese locales, English otherwise.