Automations
Runs keep their output; scripts run on remote hosts, against Microsoft 365, or from a one-line link.
Every script execution is now a run under the new Automations page: who ran it, where, exit code, duration, and the captured output (last 256 KB), kept for 30, 90, or 365 days per organization. Mark a script parameter or runbook variable secret and its value is entered masked, never stored, and scrubbed from the output.
A runbook step that runs a script now has a target: this computer, a Microsoft 365 tenant (an org connection with the tenant id — the script signs in with Connect-MgGraph, so MFA and Conditional Access apply), or a remote host over WinRM or SSH, pushed from the desktop app with nothing installed on the host. A runbook whose steps all run scripts gets Run automation: every step in order, one native confirm each.
Run links put a script — or a whole automation — on any machine you have a shell on: irm https://runbookhq.app/x/<token> | iex (bash and python variants too). The script runs there and the output comes back here. Links expire, count uses, can be revoked, act as the person who made them, and are off until an admin allows them under Settings → Modules. irm https://runbookhq.app/x/lib/<your token> | iex defines an rbhq command that lists and runs scripts on your personal API token.
The hosted MCP server gained list_runs (read-only; output only on request). Nothing executes on our servers.