AI permissions: trust levels, allowed commands, root and the safety net

What an AI client may do on a device is set per device by an admin in the web dashboard (Devices → AI permissions), never by the AI. The Windows and macOS apps show the current state and open that page. Every change is audited, and every widening is e-mailed to all admins and owners.

Overview

SettingValuesDefaultWidening needs
Truststrict, standard, fullstandardfull: your current password
Time limit for full1 hour, 4 hours, 24 hours, 7 days, or no limit1 hour(part of full)
Run asuser, rootuseryour password and the machine owner's consent (Linux only)
Safety neton, offonoff: your password
Safety net allows shutdown/rebooton, offoffon: your password

Narrowing (back to standard, back to user, safety net on) needs no password.

Trust levels

Allowed commands

Under standard trust, routine commands can run without asking. Add patterns in the device's AI permissions (admin, browser session only). The rules are strict and fail closed:

Run as root: two keys (Linux)

  1. The machine owner allows it once on the machine: sudo bash /opt/wecommander/libexec/install-linux.sh --allow-root (undo with --disallow-root). The agent then reports that it can act as root.
  2. An admin turns run as root on for that device in the dashboard, with their password. Until the agent reports it can, the dashboard refuses and shows the command to run.

A web click alone can never give root on a server, and the agent enforces its half too: it refuses a root action without its own ceiling and a signed approval of that root action. As root, commands, background tasks and terminals run through sudo -n, and a file the service user cannot write is written as root (file tools still stay inside the allowed folders). Scheduled task runs stay the service user. Not available on Windows or macOS.

The safety net

On by default. It refuses a short list of catastrophic commands on every trust level and as root, even with a human approval:

It sees through sudo, env, nohup, timeout, sh -c, eval, $(…) and backticks, and lets ordinary work through (rm -rf ./build, systemctl restart). It is a guard against slips, not a sandbox.

Autonomous mode

Autonomous mode puts all devices, or the ones you select, on full trust for a time (5 minutes to 30 days) or until you stop it. It is started by an admin in the browser or the Management Center with their password; AI clients and API keys cannot start it. Every admin and owner is e-mailed, the dashboard shows a banner on every page while it is on, it stops automatically when the time ends, and stopping it needs no password. The device's own limits (allowed folders, read-only, no commands, secret masking) still apply.

SSH servers

Servers shared through Hybrid Access have the same settings on the Devices page under SSH servers: trust, time limit, run as, safety net and allowed commands. Only the owner of the computer they go through can change them. A server shared read-only refuses every change whatever its trust. Root needs the computer's sudo setting for that server to be sudoers as well.