Start with pollen-robotics/microduck for the robot runtime and operating documentation, and microduck_rl for policy training. They serve different parts of the same workflow.
Two repositories, two jobs
The runtime repository concerns the software running the robot and the tools that communicate with it. The training repository concerns experiments that produce policies. Keep those roles distinct when searching for a tutorial. An operating command is not a training command, and a trained checkpoint is not automatically a deployable robot policy.
Follow a task-based reading order
If you own a robot, begin at the documentation index and choose the operating guide for your immediate task. If you want to train a behavior, begin at the training README and read its prerequisites. If you want to understand the system, follow the architecture links in the runtime README. You can explore all three paths eventually, but choosing one avoids a first session spent opening unrelated files.
Treat the version as part of the instruction
Repositories evolve. Before following a command from a blog post, compare it with the documentation for the branch or release you are using. Record that version in your notes. When asking for help, include the command, the relevant output and whether you ran it on a laptop or the robot. Those details often explain an apparent contradiction between two tutorials.
Open source does not mean every asset has one license
Inspect the license file for the code you plan to reuse. The training README distinguishes its software license from the license of its 3D model files. The manufacturer also explicitly limits its open-source statement to software. Reading a repository is a good first step; deciding to redistribute code, models or hardware designs is a separate question that needs the applicable terms.
Go to the source
Reviewed September 7, 2026. Prices, availability and software can change.