OpenFrame Gen1 is Here

OpenFrame v1.2.27 - Reopen Tickets, Mingo Context, Smarter Notifications and Remote/Local Device Uninstall

Version: 1.2.27

AI TICKET TRIAGEDEVICE MANAGEMENTFAEMINGOTICKETINGTICKETING SYSTEM

MINOR

Release Type

STABLE

Release Status

August 25, 2026

Release Date

Ilona Kozak

Ilona Kozak

QA Engineer

This release gives teams more control over ticket workflows with the ability to reopen tickets, manually set Tech Required status, and automatic ticket resolution when Fae's AI handling completes. Notifications now show real message content instead of empty alerts, and device management gains full uninstall support directly from the dashboard, including remote agent self-deletion. Mingo also gets a smarter context memory block for tracking navigation history across conversations.

Features Added
5

  • Reopen Tickets from Anywhere

    Tickets can now be reopened from the same places a status change can happen: the Status dropdown, the Edit Ticket form, board drag-and-drop, Mingo, and Fae. Reopening restores the previous assignee by default (with notification) and supports a configurable on_reopen policy - keep previous assignee, unassign to triage, or reassign - so tickets never silently revert without accountability.

  • Uninstall Devices Directly from the Dashboard

    Technicians can now trigger a remote device uninstall from the dashboard without needing physical or local access to the device.

  • Remote and Local Uninstall with Agent Self-Deletion

    The device agent now coordinates its own removal during uninstall, cleaning up locally and deregistering from the platform automatically for a fully hands-off uninstall process.

  • Manually Set Tickets to Tech Required

    Tech Required is now a manually selectable status both at ticket creation and while handling a ticket, matching every other status option. AI-created tickets continue to follow their existing automated status flow.

  • Mingo Context Memory Block

    The context memory block above Mingo's message input now displays entities from the user's navigation history, similar to the assigned items block. Tapping the 'more' icon opens a dropdown listing all context memory entities, with the ability to remove individual items.

Bugs Fixed
8

  • Notifications Now Show Real Message Content

    Notifications previously gave no indication of what actually happened, forcing users to open the app to find out. Notification bodies now populate with the real content - the message itself, ticket title, alert detail, or the specific action requested.

  • Fae No Longer Leaves Resolved Tickets Open

    When Fae successfully resolves an issue, the ticket now closes automatically instead of sitting open and requiring manual review, eliminating inflated open-ticket counts from already-finished work.

  • Image Upload Encoding Error

    Fixed an internal encoding error that caused image uploads to fail due to a byte encoding mismatch in payload handling.

  • Billing: Package Stuck in PENDING_ACTIVATION After Paid Checkout

    Fixed a race condition where concurrent Stripe webhook events left a paid package option stuck in PENDING_ACTIVATION even though the subscription was active. Also addresses overdue-invoice debt policy handling.

  • Fae Branding Flash Before Client Customization Loads

    Fixed an issue where customized Fae assistants briefly showed default OpenFrame branding before switching to the client's configured branding, tone, and greeting.

  • Customization Changes Not Taking Effect Until Reload

    Fixed an issue where saved customization changes (branding, tone, escalation rules, actions) were not applied to the running system, leaving administrators uncertain whether changes worked without a reload.

  • Mingo Ignored Device Nicknames

    Fixed an issue where Mingo referenced devices only by hostname, ignoring any nickname users had assigned, causing inconsistent device identification across the platform.

  • Ticket Resolution Not Reported Back to Live System

    Fixed an issue where resolving a support issue in OpenFrame did not surface that resolution anywhere - end users weren't notified, technicians couldn't see status without opening the PSA, and service providers had no proof of completed work.

Improvements
17

  • Autoresolve AI-Handling Tickets

    AI-Handling tickets now autoresolve as part of the broader shift to automatic ticket closure, removing the manual assignee step from that column and reducing unnecessary manual review.

  • Clearer Distinction Between Manual Status Changes and Approval Flow

    Moving a ticket into 'Waiting for technician' (the approval flow) is now visually and behaviorally distinct from ordinary manual status changes, preventing accidental approval state changes.

  • Renamed 'AI ASSISTANCE' Status to 'AI HANDLING'

    The ticket status label was renamed for clarity and consistency with how AI-driven ticket handling is described elsewhere in the product.

  • Info Hints on Ticket Status Columns

    Added contextual info hints for AI Handling, Tech Required, and Resolved statuses on the Trello view and ticket statuses page, mirroring the text from the status settings page.

  • Device Hostname Stays in Sync with the Platform

    The agent now detects hostname changes on the device after installation and reports them automatically, so the platform always reflects the current device name without requiring reinstallation.

  • "Via Mingo" Label on AI-Triggered Script Executions

    Script executions triggered by Mingo now display a 'via Mingo' badge in execution history, distinguishing AI-initiated runs from manual or scheduled ones.

  • Device Deletion Trigger and PENDING_DELETION Status

    Added the ability to trigger device deletion from the dashboard, along with a new PENDING_DELETION status shown in the device list while removal is in progress.

  • Board Drag-and-Drop Rewritten for Jira-Style Interactions

    The ticket board's drag layer was migrated to Pragmatic drag and drop, adding native drag imagery, accent-line drop targets, optimistic rendering, keyboard lift-and-move with screen-reader support, and per-lane auto-scroll.

  • Onboarding Completion State

    Onboarding now shows a clear completed state - 'All steps complete' header and celebration banner with a primary CTA - shown once and committed automatically in the background.

  • Onboarding Logic and Design Updated with Booking Widget

    Onboarding flow and design were updated, including integration with a booking widget for scheduling next steps.

  • Chat Title Generation Moved to Dedicated Haiku Model

    Chat title generation now uses a dedicated model instead of the tenant's configured chat model, fixing failures on Opus 4.8 that caused titles to silently fall back to raw message text.

  • Session Refresh Reliability

    Token refresh now distinguishes refreshed, transient, and terminal failures so only a genuine auth rejection signs users out; rotation is now single-flight across tabs with timeout and retry handling to prevent unnecessary session drops.

  • Container Security Hardening

    Workloads now run under the restricted Pod Security Standard with non-privileged numeric UID/GID, pod- and container-level security contexts in Helm charts, and CI vulnerability scanning of images.

  • Expanded Monitoring: Cloud SQL, RMM, and Kafka Dashboards

    Added Grafana dashboards and alerts for Cloud SQL metrics, RMM functionality, and Kafka consumer lag, plus fixes to a MongoDB exporter issue in production.

  • Device Installation Now Tracks Initiating User

    The device installation command now carries the userId of the person who initiated it, allowing the backend to associate installations with the correct user upon registration.

  • Scheduled Scripts Exclude Pending and Archived Devices

    The available devices list for scheduled scripts no longer shows devices in PENDING or ARCHIVED status.

  • Mingo Prioritizes Machine Nicknames When Processing Cards

    Mingo now uses the device nickname as the priority reference when processing cards, improving consistency with dashboard naming.

Related Links

Github Release1.2.27
Ilona Kozak

Ilona Kozak

QA Engineer

Hi! I’m Ilona, a General QA Engineer in the Product Engineering team. I help ensure our product is reliable, user-friendly, and built with quality in mind. I enjoy diving into details, improving processes, and working closely with teams to deliver the best possible experience for our users.

Related Content

Product Releases

Webinars

Case Studies

Blog Posts

Onboarding Guides

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.

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.
Most platforms give you one piece and expect you to bolt the rest on. OpenFrame unifies the whole stack in one place, with AI copilots built in. Fewer logins, fewer bills, less duct tape.
In the cloud, on US soil. Your data stays stateside.
Both. It's built for MSPs and MSSPs alike.

AI MSP

Most MSPs start with AI features inside their existing PSA, RMM, and ticketing systems rather than standalone products. Common categories include AI ticket triage, alert correlation, scripting assistants, and AI-native all-in-one platforms like OpenFrame that run intelligence across the whole stack.

Open Source Helpdesk

Zammad works well as an MSP helpdesk for teams that route tickets across multiple channels. It handles ticketing, automation, and a knowledge base, but it is not a PSA, so billing, contracts, and asset management still live elsewhere.

Open Source Ticketing

An open source ticketing system is a help desk application whose source code is published under a license permitting use, modification and redistribution, and which you host yourself. Examples include osTicket, Zammad and GLPI, all free to download and run on your own server.
There is no single best pick. GLPI wins if you need assets and tickets together, Zammad if you need a deep API and multichannel intake, osTicket for plain email-to-ticket, and FreeScout when install speed matters more than features.