Configure the Agent
Goal: Adjust the agent's configuration after install: the robot file, capabilities, motion, and settings.
The bootstrap command already writes a working configuration and sets up identity and mutual TLS. You only need this page when you want to change something, such as which capabilities the robot advertises or how it moves. Identity and TLS are configured automatically during enrollment and rarely need manual edits.
Before you begin
- The bootstrap command has been run (see Install the Agent).
- For a remote save, the robot allows remote config read and write (
allow_remote_config_readandallow_remote_config_writeinrobot.toml). The installer sets both to true. - To edit the file on the device, you can edit files as root on the robot.
Edit from Rover Nexus
- Open the robot's detail and choose Robot Agent Configuration.
- Change the sections you need. The form is the same set of fields as
robot.toml: system flags, motion, local transport, the uplink topic, command topics, allowed commands, actions, sensors, settings, resources, and events. - Save Config to Robot. Check Restart the agent after saving so the new config applies immediately when the new file should apply now. Leave it unchecked and the file applies on the next agent restart. A restart takes the robot offline briefly and interrupts a mission it is running.
- Use Save motion when you only want to store turning radius, brake rate, and footprint on the robot. That does not replace the file on the device.
To reuse the same file on the next robot, save it as a configuration profile and pick it in Add Robot. See Configuration.
If the page cannot load the robot, generate the file, download it, and install it at <state_dir>/robot.toml (default /var/lib/rdyn/robot/robot.toml).
Config files reference
The agent's config files, identity/TLS fields, and precedence rules are documented in the Configuration reference. Identity and TLS are written during enrollment and rarely need hand edits.
What to edit
- Robot file: transport, topics, command policy, motion, and capabilities. See Robot Configuration.
- Cameras: pin V4L2 devices/formats for teleop video. See Configure a Camera. Cameras are not part of the Robot Agent Configuration form.
- Capabilities: declare the actions, sensors, settings, resources, and events the robot advertises. See Declare Capabilities.
- Settings: seed the robot's key/value settings store. See Configure Robot Settings.
After editing the file on the device, restart the service so the changes take effect:
sudo systemctl restart rover-agent
Next steps