OpenFrame

Scripts Overview

AUTOMATIONGUIDEIT OPERATIONSOPENFRAME

Phase 5 — Scripts & Automation · Step 1

Section

June 19, 2026

Published

Vladislav Marchenko

Vladislav Marchenko

Head Of Marketing

Scripts Overview

Phase 5 — Scripts & Automation · OpenFrame Onboarding

Scripts are how you do things to machines at scale — install software, pull a report, fix a recurring problem — without remoting into each one by hand. In OpenFrame they live under Scripts in the left nav, and this section is split into two tabs: Scripts List (your library) and Scripts Schedules (scripts set to run on a cadence). This guide is the lay of the land before the next four go deep.

The Scripts List

Open Scripts and you land on Scripts List — a table of every script available in your tenant. The columns tell you what each one is at a glance:

  • Name — what the script does.
  • Shell Type — the language it's written in (see below).
  • OS — which platforms it can target (Windows, Linux, macOS icons).
  • Added By — where it came from. Many are sourced from the Tactical (TacticalRMM) community library, so you're not starting from a blank page.
  • Category — how it's grouped, e.g. Diagnostics, OpenFrame, TRMM (All):Network, TRMM (Win):3rd Party Software. A DEPRECATED category flags scripts that are no longer maintained.
  • Description — a one-liner on what it does.

Use Search for Scripts to filter, and the column header sort/filter controls to narrow by shell type or OS. Each row has a "…" menu and an arrow button that opens the script's detail page.

Supported shell types

OpenFrame runs more than just PowerShell. When you create a script you pick from:

  • PowerShell — the workhorse for Windows.
  • Batch — classic Windows .bat.
  • Bash — Linux and macOS.
  • Python — cross-platform, great for anything portable.
  • Nu, Deno, Shell — additional runtimes for more specialized needs.

A script declares which OS it supports, so the library only offers a script to machines it can actually run on.

Two ways scripts run

  1. On demand — run a script against one or more devices right now. You can do this from the script's detail page (Run Script) or from a device's own page. Covered in Run a Script on a Device.
  2. On a schedule — set a script to run at a date/time, optionally repeating. That's the Scripts Schedules tab, covered in Schedule a Script.

Either way, results land in the Logs (activity logs) — see Script Results & Output Logs.

What's in a script

Click any script's arrow to open its detail page:

  • Description and Category — what it is and how it's filed.
  • Shell Type and Supported Platforms — language and target OSes.
  • Syntax — the actual code, shown read-only.
  • Edit Script and Run Script — buttons to change it or run it now.

A note on the Tactical library: scripts marked Added By: Tactical come from the TacticalRMM ecosystem. They often pass their parameters via environment variables rather than command-line arguments — worth knowing before you run one (the script's own comments usually say which it expects). More on that in Run a Script on a Device.

Quick checklist

  • Found the Scripts section and the Scripts List / Scripts Schedules tabs
  • Scanned the library by Category and OS
  • Understood the supported shell types
  • Know the difference between running on demand vs on a schedule
  • Know where to find a script's Syntax and the Run Script button

What's next

Now that you know where scripts live, put one to work: Run a Script on a Device covers running on demand (and the variable gotcha between running from /scripts and from a device). Then Create Your First Script and Schedule a Script.

Based on OpenFrame v0.9.19. Screens and the bundled script library evolve between releases — when in doubt, what's in your console wins.

Vladislav Marchenko

Vladislav Marchenko

Head Of Marketing

Hi all! My name is Vlad and I’ve been brought on to head the marketing team at Flamingo. Thankfully, this isn’t the first time I will be building a marketing department from scratch, so the experience should come in handy. Now it’s time to dive into the world of MSPs and find myself in this new world.

More in Phase 5 — Scripts & Automation

Related Content

Product Releases

Webinars

Case Studies

Blog Posts

Frequently Asked Questions

MSP AI Agents

Yes. In production MSP shops today, 10% to 25% of tickets close before a human opens them. Thread alone has processed 173 million tickets across 750-plus MSP partners at 96% triage accuracy, handing back 490,000-plus technician hours. Agents own the low-risk, high-volume work (password resets, MFA enrollment, known installs, onboarding and offboarding) and flag anything that touches production data or needs judgment for a human to take.
On a five-person desk, reported deployments show $78,000 to $130,000 in annual direct labor savings, roughly 30% fewer escalations, and 15% to 20% better SLA compliance. Broader MSP adoption data adds ticket handling time cut by 45% and five to 12 points of margin, all from reclaimed capacity rather than headcount cuts.
An AI agent for an MSP is software that reads a ticket, decides the action, performs it across your tools, and records the result without a technician driving each step. It differs from a chatbot or copilot by taking action, not just suggesting one.

AI MSP

MSPs use AI to triage and route tickets, cut alert noise, schedule patches, assist L1 security work, and draft client reports. Kaseya's 2025 benchmark found 30% already use it to eliminate tedious tasks, with ticket triage the most common starting point.
Start with a readiness assessment, not a tool purchase. Confirm your ticket history is clean and your RMM, PSA, and monitoring systems connect. Then pick one high-volume, low-risk workflow, usually ticket triage, and pilot it on internal tickets before any client sees it.
Automate high-volume, low-risk tasks first. Ticket triage and alert noise reduction top the list because they run constantly and a human still resolves the underlying issue. Save security approvals, billing changes, and client-facing actions for later, always with a human in the loop.

AI for MSPs

Set a baseline before rollout, then track tickets closed per technician, mean time to resolution, percentage of tickets resolved with no human touch, technician hours reclaimed, and cost per ticket. AI-driven automation commonly cuts operational cost per ticket by 25 to 40%.
No. AI automates routine tickets, patching, and monitoring, but trust, accountability, and complex business judgment still need people. The future of managed services moves technicians from closing tickets to advising clients, which makes the human role more valuable, not obsolete.

About OpenFrame

OpenFrame isn't built to plug into your stack. It replaces it. Instead of duct-taping a dozen tools together (RMM, MDM, SIEM, patching, remote access, each its own login and bill), we bundle it into one unified platform: RMM, MDM, monitoring, automation, remote access, patch management, security monitoring, and ticketing, plus built-in AI copilots. So "does it integrate with X?" usually means: you won't need X anymore.

AI Infrastructure

AI-powered infrastructure managed services apply machine learning to infrastructure telemetry so providers can predict failures, automatically remediate known issues, and forecast capacity needs. They replace static-threshold monitoring and manual firefighting with predictive, largely automated operations overseen by technicians.