April 10, 2026
Compare Devices
You can now compare the configurations across any two devices to understand exactly what’s different between them. Open the Compare tab in the sidebar, or select two devices directly on the Devices page and hit Compare.- Summary at a glance: See the total number of differences, how many files changed, and expand into a per-file breakdown without opening each one
- Inline diffs: Expand any configuration file to see highlighted diffs with additions, modifications, and deletions color-coded inline
- Select deployments: Each device defaults to its current deployment, but you can switch to any other deployment or compare two deployments on the same device
- Shareable URLs: Your selections are persisted in the URL, so you can share a comparison with your team
YAML Support
You can now edit and view YAML configurations anywhere in the platform. The config editor and viewer support YAML alongside JSON, and diffs are YAML-aware, so changes are detected at the key and value levels instead of as raw text. This gives you more accurate, meaningful comparisons across deployments.Agent SSE
The Miru Agent now exposes a real-time event stream over Server-Sent Events. Instead of polling the Device API for changes, your application can open a single persistent connection to the/events endpoint and get
notified the moment a deployment lands on the device or is removed.- No more polling: React instantly when a deployment’s configs are
written to the device (
deployment.deployed) or archived and cleaned up (deployment.removed) - Cursor-based replay: Reconnect from where you left off using the last event ID, so you never miss an event
- Type filtering: Subscribe only to the event types you care about instead of processing everything
March 23, 2026
Device Audit Trail
We’ve added an audit trail to device pages, simplified the staging workflow, and introduced a display name setting.Audit Trail
The device overview page now includes an activity timeline that lists each deployment alongside the configuration changes it introduced. Every entry shows who deployed, when, and exactly which fields were added, modified, or deleted — down to the JSON path.This gives you a single page to review how a device’s configuration changed over time without opening the editor or diffing deployments manually.Updated staging workflow
We’ve simplified the staging workflow to focus on one device at a time. Instead of creating a staged deployment first and then choosing devices afterward, you now start by selecting the device you want to prepare. Miru then opens the new release editor with that device’s current configuration, or the release schema defaults if no configuration exists yet.Read the full documentation »Display name setting
You can now choose whether names appear as first name or full name across the app in Profile settings. Hovering any name also reveals the full name, so you can always tell teammates apart.March 13, 2026
New Platform and Device APIs
We’ve added a variety of endpoints and resources to both the Platform and Device APIs, giving you more programmatic control and on-device deployment visibility. We’ve also added versioning to both the Platform and Device APIs, giving you a stable contract for integrations.Platform API 2026-03-09.tetons
Platform API2026-03-09.tetons introduces API versioning and overhauls the representation of deployments, config instances, and config schemas. It also introduces management of more configuration resources (config types, schemas, and instances), release creation, git commit tracking, and explicit deployment lifecycle actions.For a detailed list of changes, visit the Platform API changelog.
Platform API Documentation »Device API v0.2.0
Device APIv0.2.0 expands endpoints beyond basic device health and version checking to include deployment-pipeline visibility. You can now directly query the Miru Agent for its current deployment and current release, allowing you to programmatically verify your application’s software version matches the version of your configurations.For a detailed list of changes, visit the Device API changelog.
Device API Documentation »Miru Agent v0.7.0
Outside of thev0.2.0 Device API changes, v0.7.0 of the Miru Agent received a variety of small, but impactful improvements:- Atomic Deployments: Config deployments are now all-or-nothing—all config files for a deployment are written simultaneously or none are
- Deployment Timestamps: The agent now tracks the
deployed_atandarchived_attimestamps on-device when deployments are applied - Config Instance Formatting: Config instances deployed to the device’s file system are now identical (indents, spacing, etc.) to config instances edited in the config editor
Miru Agent Documentation »February 25, 2026
Config Editor v3.0
We’ve rebuilt the config editor with four major new capabilities: edit and deploy multiple config files simultaneously, navigate diffs quickly, restore previous deployments instantly, and compare any two snapshots from a device’s history.Multi-File Editing
The editor now supports editing multiple files under a single deployment with improved visibility and control:- Persistent edits: Switch between files or view historical deployments without losing changes in your draft.
- Tab indicators: Tabs display file status (
Mfor modified,Afor added) and show linting error counts at a glance. - Live change list: The right panel provides a real-time summary of edits across all files as you work.
- Deploy summary: Review a file-by-file count of changes by type (added, modified, deleted) before deploying.
Redeploy
Restore any previous deployment directly from the editor. Simply right-click any deployment in the History tab and select Redeploy from the menu to open the dialog.All configuration from the historical deployment is perfectly preserved and shipped as a brand-new deployment on the device.Diff Navigation
A floating navigation card now appears at the bottom of the editor when viewing diffs, allowing you to quickly navigate changes both within and across files.- Auto-scroll to first diff: The editor automatically jumps to the first difference so you never have to scroll manually.
- In-file navigation: Use the up and down buttons to jump line-by-line between changes within the current file.
- Cross-file navigation: File navigation buttons let you quickly skip between files. It only cycles through files that actually have changes, bypassing untouched files.
- Change overview list: Click the change counter label (e.g.,
1 of 13) to open a dropdown listing every change in the current file, including its modification type and path. Click any item to jump instantly to that line.
Snapshot Comparison
Compare any two deployments directly from a device’s history. Before, you could only see the diff between a deployment and its parent. Now, you can swap out the base deployment, making it easy to compare changes across any two points in time.Read the full documentation »January 27, 2026
Create Releases in CI/CD
You can now create releases directly from your CI/CD pipeline, ensuring releases are up to date and created consistently.Furthermore, creating a release has been streamlined: only a single CLI command is required and CUE packages now support defining schemas across multiple files.GitHub Actions workflow
We’ve released an official GitHub Actions workflow for creating releases in CI/CD. The workflow installs the Miru CLI and accepts an API Key for authentication, letting you execute any CLI commands from your GitHub runner.Read the full documentation »Create release CLI command
The newmiru release create command bundles the entire release process. It creates the release, pushes its schemas, and captures associated Git metadata in one step for greater reliability and ease of use.Read the full documentation »CUE packages
The CLI now supports CUE packages, allowing you to define schemas across multiple files while treating them as a single logical schema in Miru.Read the full documentation »December 19, 2025
Workspace Logo
You can now personalize your workspace with a team logo and add a profile picture to your account. We’ve also added a new feedback form in the app so you can easily share your thoughts or report bugs.Upload a workspace logo
Admins and owners can now upload a custom logo for their workspace. Once set, the logo is displayed in the sidebar and invite pages, giving new members a branded welcome experience.Upload a profile picture
Make your profile your own. Go to Settings → Profile to upload a profile picture. We’ve included a built-in cropper so you can center your image perfectly before saving.Give feedback in the app
We’ve added a dedicated feedback button directly in the sidebar so you can share your thoughts without leaving your workflow.Use the feedback form to share:- Feedback — feature requests, suggestions, or general thoughts
- Bug Report — issues you encounter while using the app
- All reported bugs are resolved within 7 days
- Critical bugs are resolved within 2 days
December 4, 2025
CUE Support
We are excited to announce full support for CUE (Configure, Unify, Execute) as a first-class schema language in Miru. You can now define config schemas in CUE, version them in Git, and push them via the Miru CLI to validate config instances before deployment.Uploading a CUE schema
Pushing a CUE schema to Miru follows the same Git-integrated workflow you are used to. Simply define your schema in a.cue file and use the Miru CLI to push it.Managing CUE schemas
Once uploaded, your CUE schemas appear in the dashboard where you can view the raw content (preserving comments and formatting) and associated metadata.Management works just like existing schemas: most properties are immutable, though you can update the config instance deployment path. Deletion is only permitted for schemas with no active config instances.
Read the full documentation »December 4, 2025
Workspace Invitations
You can now invite team members to your workspace and manage their roles. This release also adds new workspace and profile settings.Inviting team members
Onboard your team directly from the dashboard. Navigate to Settings > Members and click the Invite button.Once you enter their email and select a role, they will receive an email with a link to join your workspace.- New users will be guided to sign up and then prompted to accept the invitation.
- Existing users can accept the invite via the email link or their Profile settings page.
Manage roles and access
We have introduced three distinct user roles:- Owner — Full control over the workspace (limit one per workspace).
- Admin — Administrative access to manage members and workspace settings.
- Member — Application access without administrative privileges.
Profile and workspace settings
Manage your profile and workspace details from dedicated settings pages.- Profile — Update your name, view pending invites, or leave your workspace.
- Workspace — Admins and owners can update the workspace name.
November 10, 2025
Device Releases
You can now set and change a device’s release directly from the device page, eliminating the need to navigate to the releases page for single-device operations.Setting the initial release
After activating a device, you’ll be prompted to set its initial release before accessing the config editor. This two-step process requires:- Select a release - Choose which software version this device will run
- Deploy configurations - Create a new deployment or deploy a staged deployment