In Trio’s endpoint management platform, Commands empower administrators to remotely execute system-level actions across macOS, Windows, and other supported operating systems. These Commands serve as flexible tools for automating tasks, enforcing configurations, and conducting diagnostics, especially when policy-based control isn’t sufficient.

Commands differ from persistent policies by offering one-time or conditionally recurring executions. Whether you’re modifying system settings, querying device state, or applying fixes, Commands provide direct and targeted control at the device level without requiring full policy deployment.

Commands in Trio are managed through the Command Center. Administrators can create scripts from scratch, choose from pre-built templates (e.g., Convert to 64-Bit, Shell Script, 64-Bit MultiLine), or define post-installation behavior for newly onboarded devices. Each script includes the command logic, targeted operating system, privilege level (e.g., system or root), and execution mode.

Once created, Commands are not bound to a schedule by default. Instead, they’re launched manually or through defined triggers, such as webhooks, scheduled intervals, or agent events. The Commands is then delivered via the Trio Agent to the target device. Execution is handled locally, and output or status is reported back to the admin interface.

Commans can be run in different contexts:

Each Command in Trio is platform-specific, meaning a Command written for macOS (using Bash or zsh) will not be valid for a Windows (CMD or PowerShell) environment. When creating or assigning a Command, Trio ensures compatibility by filtering options based on the device OS and agent configuration.

Execution capabilities also depend on the device’s current state. Commands cannot run on offline devices, and some advanced use cases (such as deep system diagnostics or update manipulation) require elevated privileges. The Run As field during Command creation ensures the correct authority level is used.

Administrators can choose to assign Commands directly to device groups or launch them interactively. The platform provides a grid or card view to visualize existing Commands and their associated metadata: OS, Command content, launch method, assigned devices/groups, and execution context.

Once a Command is launched, the Trio Agent on the target device checks in and executes the Command within the defined context. If the device is offline, the Command remains queued until the agent reconnects.

Trio provides detailed visibility into Command lifecycle events:

Command deletion is safeguarded with a confirmation prompt, especially when linked to multiple groups. Deletion removes the Command from future assignments but does not reverse previously applied changes.

Commands provide vital utility in environments where policy-based automation needs to be supplemented with real-time control. Common scenarios include:

Commands in Trio extend the power of the platform beyond standard device policy. With flexibility in scheduling, rich OS support, and clear administrative feedback, they are ideal for repeatable operations, custom control, and deep technical remediation across managed fleets.