Table of Contents
Scripts and Automation
Script engines
Each script picks its engine in the editor. Monaco switches syntax highlighting to match, and a one-line hint describes the engine's platform behavior.
- PowerShell 7 (default) — the embedded PowerShell SDK inside the agent
process, on every platform. Full feature set: live progress, typed
parameters,
$Secrets,$Files, Functions. - PowerShell 5 — shells out to
powershell.exeon Windows with near parity. Stdout and stderr stream live; progress records are the accepted limitation. - Bash — for Linux and macOS, or Git Bash on Windows. Parameters and
secrets arrive as environment variables; complex values are JSON, so
jqworks well.
An engine that is unavailable on a device fails the job immediately with a clear message instead of running.
Agents also bundle PSResourceGet, Archive and ThreadJob. That means
Install-PSResource, Compress-Archive and Start-ThreadJob work on
every endpoint out of the box.
Script Configuration
Each script page has self-headed sections:
- Parameters — typed values (strings, numbers, booleans, arrays, hashtables). At run time they appear as Execution values.
- Secrets — bind vault entries to names. Scripts read a
case-insensitive
$Secretsdictionary; values never land in the database or the logs. - Files (S3) — bind S3 objects or prefixes. Before execution the server
presigns and the agent downloads to a destination path that supports env
and PowerShell expansion, with continue-on-failure per item. Scripts get
$Files: a case-insensitive dictionary ofFileInfoandDirectoryInfoentries. Recursive prefixes arrive as directories. - Functions — reusable preludes, prepended and executed in the same runspace.
The editor pops out to fill the window (Esc restores). Optional
IntelliSense is a curated offline provider — common cmdlets and snippets,
plus your own parameters, $Secrets bindings and $Files keys.
Groups, triggers, schedules
Device groups are static (listed), dynamic (blocks of AND/OR conditions) or folders, and nest. See Groups.
Triggers attach scripts to device lifecycle events, right on the script page.
Schedules use cron with a preview of the next runs. Assign them to devices or groups; starter schedules are seeded on first boot.
Group runs fan a script out to a group with per-device job tracking (see Runs below).
Scripts, Functions, schedules, groups and roles all support one-click Clone.
Runs
Run Script opens the same tabbed dialog from either side:
- From Devices: search, check devices, Run Script, then pick the script and fill its parameters.
- From Scripts: Run, then pick devices and groups.
Only Devices Online Now skips the offline ones instead of queueing for them.
Stagger spreads a run's starts out, from Review in Run Script or beside the cadence on a schedule:
- Spread Over: how long the starts are spread across.
- Devices at a Time: how many start together.
The dialog shows the result, such as "12 batches, one every 2 min 44 s". Device order is shuffled for each run, so the same device isn't always last. Start times are stored on the server and survive a restart. Every device runs the script as it was when the run started, and Only Devices Online Now is checked again at each device's start time.
Every run has its own page:
- Countdowns while devices are waiting: Next Start In and Last Start In, and one on each device. Cancel Waiting cancels the ones not yet started.
- A progress bar and counters for Targets, Online, Waiting, Pending, Running, Succeeded, Failed, Timed Out, Cancelled and Skipped. A counter filters the list to its devices.
- A live dashboard: the outcome so far, exit codes, completions over time, and errors grouped by exception type and message. Clicking an exit code or an error filters the list too.
- A row per device. Click one to open that device's live output.
- Downloads:
- Download Output saves one
ScriptName.RunID.yyyy.MM.dd.HHmmss.logwith a section per device. - Download Logs saves a zip with one
COMPUTERNAME.JobID.yyyy.MM.dd.HHmmss.logper checked device, or every device when none are checked.
- Download Output saves one
- Times in file names are UTC on a 24-hour clock.
Jobs
Dispatch is durable through JetStream. Agents acknowledge only after recording the command, so restarts never double-run.
Exit codes in PowerShell 7. Since 1.1.0 the built-in engine reports what the
script says: exit 5 fails the job with code 5. A native command's non-zero
exit doesn't fail a job by itself, and neither does an error silenced with
-ErrorAction SilentlyContinue. Write-Error and throw still do.
A job that can't be sent for 24 hours fails.
Output, progress and state stream live to the browser. Job history is queryable per device and per script.

