MicroDuck Policies: Check, Load, Test & Reset Safely

Record the current state before changing it.

robotctl version
robotctl health
robotctl policy list
robotctl policy check

list shows the seven default slots and installed skills. check compares the official set with its source and changes nothing. Save this output so “reset” has a documented before-and-after result. Official robotctl cheat sheet ↗

Update the official set separately from robot software.

sudo robotctl policy update
robotctl policy list
robotctl health

The official policy set versions independently from the daemon. The robot returns to its home pose and reloads the set without a daemon release. If you need an older published tag, the official command supports --version; inspect the offered versions before selecting one.

Try a local policy with an undo command ready.

sudo robotctl policy load walk /home/radxa/my_walking.onnx
robotctl policy list
robotctl health
sudo robotctl policy reset walk

A successful load persists across reboot. Replacing the policy currently driving the robot sends it to its home pose before the swap. A failed candidate keeps the previous running controller, but that is not a reason to test unsupported: use a stand, clear the area, keep access to power, and start with low-risk observation.

Treat community search as discovery, not approval.

robotctl policy search microduck
sudo robotctl policy load walk OWNER/REPOSITORY
robotctl policy list
robotctl health

A repository name can include a revision with @ and a file selection with :. Check its manifest for robot model, observation and action lengths, kind, slot, training provenance and evaluation notes. The current contract uses 61 observations and 14 actions, but matching dimensions alone do not prove useful or safe behaviour. Official policy manifest contract ↗

Reset one choice or all seven slots.

sudo robotctl policy reset walk
# Or clear every slot override:
sudo robotctl policy reset
robotctl policy list
robotctl health

reset removes the override and resolves the official default. It does not delete your research notes, so keep the repository, revision, file hash, observed result and reason for reverting in the experiment record.

Post a result another maker can interpret.

Robot software version:
Policy slot and previous entry:
Source repository, revision and file:
Manifest model / obs_len / action_len / kind:
Exact load command:
Physical support and test area:
Expected motion:
Observed start / stop / fall / recovery:
robotctl health result:
Reset command and final policy list:
Untested conditions:

Use the related discussion form for a concise question, or a build log when you have a repeatable procedure and original evidence.