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.

We’re ready to deploy config instances to a device. Navigate back to the Devices page and click into the device we activated in the previous step.
Miru UI screenshot
Select the release we just created and hit Next.
Miru UI screenshot
Input the desired parameters for the Mobility, Planning, and Communication config instances respectively.
Miru UI screenshot
The instances are auto-populated with the default values defined in the release’s config schemas. If using empty schemas, the auto-populated instances will be empty as well.
Finally, provide a description for the deployment, then click Deploy.
Miru UI screenshot

​
Verify the deployment

To verify a config seen in the editor is deployed to the device, open a terminal on the device that has the Miru Agent installed and run cat on the file path of the config instance. 
cat /srv/miru/configs/mobility.json
You should find that the editor’s content is identical to the config instance on the device.

​
Patch a config instance

To edit a config instance, make some changes to the current config instance. As edits are made, a log on the right maintains a list of all changes, categorizing them by their type: added, deleted, or modified.
Miru UI screenshot
Only the latest config instance for a config type may be edited. All other config instances are read-only.
Once you are satisfied with the edits, click Deploy in the top right. A dialog will appear to confirm the deployment. Add a description, confirm the device, and click Deploy.
Miru UI screenshot
Congratulations! You’ve successfully deployed and edited a config instance to a device with Miru!
Last modified on April 30, 2026