Skip to content
PoliciesFixed official manifest and commands checked; no site hardware policy load

MicroDuck Policies: Update v8, Inspect Overrides & Reset

The official MicroDuck policy set added velstand v8 on October 12, but a daemon upgrade does not prove your robot runs it. Compare robotctl policy list and policy check, then update the official set if appropriate. A manually loaded walk override remains in place until you intentionally reset that slot.

Updated October 13, 2026. The official policy Hub published velstand v8 on October 12 at revision 665ae4e; the site originally published this guide September 24. The Hub has 11 ONNX files but 10 manifest entries. We reviewed the fixed manifest and commands, not a physical policy load.

Find the version that your robot is actually using.

Read-only version, slot and source checks
robotctl version
robotctl policy list
robotctl policy check
robotctl health

policy check compares the official source without installing. policy list reveals the seven default slots and any manually loaded overrides. Save its output before making a change. Pinned 0.17.1 gamepad and update reference ↗.

What v8 changed in the official walk policy.

The pinned v8 manifest keeps velstand.onnx as the default walk entry, a perpetual policy that can stand at zero command. Its new ONNX file and manifest text describe smoother fall get-up and better yaw tracking; the v7 standing body roll/pitch feature remains. Other manifest policy entries did not change in this Hub revision. Official policy-set manifest at fixed v8 revision ↗.

The RL author reports a real-robot get-up, turning and walking check on October 12, but also says turning at 0.3 rad/s can still be weak or bursty and body-z crouch is not learned. We have not independently measured those results. Its internal evaluation scripts named in the write-up are local/gitignored, so they are not a public one-command reproduction route. Pinned RL velstand v8 development and limits ↗.

Update the set independently of the daemon.

Install the offered official set and read it back
sudo robotctl policy update
robotctl policy list
robotctl health

The robot returns home and reloads the official set, but a manually loaded slot remains untouched. If walk still points to a custom model, that is expected; do not say v8 is driving the robot until the list confirms it. The published v7 tag remains available for deliberate version selection with sudo robotctl policy update --version v7; inspect the source and preserve your prior list before changing a known working setup. Pinned duckctl installation and laptop commands ↗ Official policy-set v8 tag ↗.

Test a custom file with an undo path.

Load and then undo a custom walk policy
sudo robotctl policy load walk /absolute/path/my_walking.onnx
robotctl policy list
robotctl health
sudo robotctl policy reset walk

A successful load persists across reboot. Support the robot and leave joint clearance for a first test. Check model and servo family, accessories, entry pose, command meaning, 61 observations, 14 actions and 50 Hz before loading; dimensions alone do not prove a safe or useful gait. A failed candidate retaining the previous controller is not a substitute for a physical safety plan. Community policies are unsigned and not verified by Pollen Robotics. Official policy-set manifest at fixed v8 revision ↗.

Reset the intended slot, then verify it.

Remove a walk override
sudo robotctl policy reset walk
robotctl policy list
robotctl health

reset walk clears that override and resolves the current official default; sudo robotctl policy reset clears all slot overrides, so use it only when that is the actual goal. Reset does not resurrect a previous custom file. Record the source revision, observed start/stop/fall behavior, health and final list before posting a result in the related discussion.

CONTINUE THE CONVERSATION

What would you like to understand next?

Keep the source, your environment and your observations together.

Before you continue

Are reset and delete the same operation?

No. Reset restores the default selection; deletion removes a stored policy. Read back the selected slot and keep the package provenance.

Applies to: Pollen Robotics MicroDuck. Keep the model, image, software and driver versions together. The dated sections below retain their original verification limits.

Source checked:

Sources and review (5)
  1. huggingface.co/pollen-robotics/microduck-policies/blob/665ae4eb20bfe13bca1ef4ea6d4bb6b4a096e448/manifest.json
  2. huggingface.co/pollen-robotics/microduck-policies/tree/v8
  3. github.com/pollen-robotics/microduck_rl/blob/b02fdea4902c2b93b7d34a83a6f05da4ececb7d3/docs/velstand_policy.md
  4. github.com/pollen-robotics/microduck/blob/72225520f2a17345f3394ec26d06f683785d12d6/docs/robot/cheatsheet.md
  5. github.com/pollen-robotics/microduck/blob/72225520f2a17345f3394ec26d06f683785d12d6/docs/robot/duckctl.md

Next useful guides

MicroDuck ONNX Export: Checkpoints, Replay & Validation

Export a MicroDuck checkpoint with observation normalization, select the correct playback input layout and inspect a policy package before sharing.

MicroDuck Reference Policies: Sprint, Rollers & Sit/Stand

Compare four official reference policies by slot, accessories and command meaning. Inspect pinned manifests, try a matching model and reset the override.

MicroDuck troubleshooting: updates, pairing and policies

MicroDuck 0.20.1: check access before recovery. Wi-Fi SSH stays a local decision. Check daemon/API versions and Setup Code before treating a refused connection as an update failure.