Agent: install, update and options

The agent is a single program on each machine. It opens one outbound TLS connection to wecommander.app, never listens on a port, and enforces the device's limits itself: allowed folders, read-only and no-command switches, secret masking and signed approvals for high-risk actions.

How it runs on each system

SystemInstalled byRuns asDefault allowed folder
Windows desktopThe WECOMMANDER app (agent inside)Your Windows user, as a hidden child of the appC:\Users\<you>\WECOMMANDER
Windows serverinstall/agent.ps1 (setup)The signed-in user, through a per-user scheduled taskChosen during setup
macOSThe WECOMMANDER app (agent inside)Your macOS user~/WECOMMANDER
Linux serverinstall.sh (Debian package)The unprivileged wecommander system user (systemd service webrising-commender)/var/lib/webrising-commender/workspace

Pairing uses a one-time request approved in your browser; the device credential is stored on the device and never printed. Re-running an installer keeps the existing device identity.

Linux options

# Change the allowed folder or switches on an installed server
sudo wecommander-setup --allowed-root /srv/app
sudo wecommander-setup --read-only      # refuse all file writes
sudo wecommander-setup --no-commands    # refuse commands, tasks and terminals

Choose a narrow folder the wecommander user can actually access; do not start with /, /root, /etc or a whole data disk. Commands run with the wecommander user's Unix rights, so grant it access only to what the AI should use.

Device switches the gateway cannot change

SwitchRefuses
Commands off (--no-commands)process_exec, process_kill, task_start, terminal_start, terminal_input
File writes off (--read-only)fs_write, fs_append, fs_mkdir, fs_delete, fs_move, fs_replace, fs_undo, xlsx_write_cells
Root not allowed (default)any action the gateway sends to run as root
Output redaction (on by default)turn off with capabilities --redact-output off
System logs (on)turn off journal reading with capabilities --system-logs off

These live only in the agent's local config. Even a valid human approval cannot override them. To change them later run webrising-commender --config <path> capabilities --commands on|off --file-writes on|off and restart the service. policy_info shows what is on.

Allowing root (Linux only)

Running as root needs two keys. The first is the machine owner's, on the machine:

sudo bash /opt/wecommander/libexec/install-linux.sh --allow-root      # allow
sudo bash /opt/wecommander/libexec/install-linux.sh --disallow-root   # undo

This adds a sudoers rule for the agent's service user, removes the systemd hardening that blocks sudo and records the ceiling in the agent's config. The second key is an admin turning “run as root” on for that device in the dashboard, with their password. Root is not available on Windows or macOS agents. See AI permissions.

Check and update

sudo systemctl status webrising-commender --no-pager
sudo journalctl -u webrising-commender -n 30 --no-pager