Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.mirurobotics.com/llms.txt

Use this file to discover all available pages before exploring further.

​
v0.8.0

April 12, 2026 Miru Agent v0.8.0 allows config instances to be written to paths outside of the /srv/miru/config_instances/ directory—any valid file system path is now supported. Configs deployed to paths outside of the /srv/miru directory require additional file system permissions to be granted to the miru user. To learn more, visit the file permissions documentation.

​
Breaking changes

  • Removed ProtectSystem=strict and ProtectHome=true from the default systemd unit to allow writing config files to arbitrary absolute paths if desired

​
Features

  • Config instances can be deployed anywhere on the filesystem, not just in the /srv/miru/ directory
  • Deployments being removed now transition through an intermediate removing status when removal begins

​
Fixes

  • Fixed graceful shutdown handling when SSE streams are active
  • Scope cooldown periods to be per-deployment so that new deployments are not unnecessarily delayed by other deployment failures

​
Improvements

  • Default all file system write operations to atomic mode for improved reliability

​
v0.7.1

April 7, 2026 v0.7.1 adds YAML support and Server-Sent Events (SSE) streaming to the Miru Agent. On-device applications can now receive real-time deployment lifecycle notifications. This release also upgrades the Device API to v0.2.1. Device API v0.2.1 changelog »

​
Features

  • Added YAML support for configuration files
  • Added Server-Sent Events (SSE) streaming via GET /v0.2/events for real-time deployment lifecycle notifications

​
v0.7.0

March 13, 2026 v0.7.0 upgrades the Miru Agent to Device API v0.2.0, adding deployment-pipeline visibility for on-device applications and improving deployment reliability under transient failures. Device API migration guide »

​
Breaking changes

​
Features

  • Deployments are guaranteed to be atomic—all config instances for a deployment are written to the filesystem simultaneously or none of them are
  • The agent now explicitly tracks deployed_at and archived_at timestamps on device when deployments are applied
  • Config instances deployed to the device’s file system are now identical (indents, spacing, etc.) to config instances edited in the config editor

​
Improvements

  • The agent immediately retries transient network connection errors three times before entering a cooldown period
  • Improved config instance caching logic to reduce network calls during sync cycles

​
Fixes

  • Fixed deployment retry logic to eagerly retry failed deployments instead of waiting for the polling interval to expire (occasionally leaving deployments stuck in a queued state)
  • Fixed deployment cooldown handling so retry windows are reported and cleared correctly
  • JWT tokens are now redacted from debug outputs

​
v0.6.1

January 22, 2026

​
Fixes

  • The miru-agent --install command now correctly returns a non-zero exit code on failure, instead of 0

​
Agent Install Script Update

December 8, 2025

​
Improvements

  • Agent install script now runs sudo chown -R miru:miru /srv/miru to prevent any permissions issues encountered if the /srv/miru directory has previously been created with the wrong permissions

​
v0.6.0

October 19, 2025 v0.6.0 adds support for installing the agent over poor internet connections, ensuring reliable provisioning on bandwidth-constrained devices. Read the full documentation »

​
Features

  • Poor connectivity installations of the Miru Agent are now supported

​
v0.5.1

September 17, 2025

​
Fixes

  • Fixed device provisioning script
  • Fixed a critical bug where configuration files could go missing if multiple configuration files were queued for deployment while the agent was offline

​
v0.5.0

September 5, 2025 First release with Device API v0.1.0 endpoints, MQTT-based real-time sync, and device session management. Establishes the core on-device integration surface.

​
Features

  • Added agent version info to device and server updates
  • Added device session ID for MQTT authentication
  • Added MQTT ping/pong for connection health monitoring
  • Added server APIs to sync the agent
  • Added version argument to installation scripts
  • Added agent information to client headers
  • Pretty-printed JSON objects in logs

​
Fixes

  • Activation script now restarts the agent on failures
  • Activation script temporarily stops the agent during provisioning
  • Fixed errant unwrap() calls that could cause panics
  • Improved MQTT network connection error handling
  • Fixed unnecessary filesystem writes for device patches
Last modified on April 13, 2026