MicroDuck: how a little robot learns new moves

MicroDuck is a biped robot from Pollen Robotics. The official page lists a height of about 25 cm, 15 motors, a camera, LiDAR and two inertial sensors. It combines a playable physical device with simulation and training software for developing further behaviors.

That makes it both a robot product and an AI development tool. Its movements and interaction may attract interest; suitability for a project depends on control, skill training and delivery conditions. A pet-like appearance does not establish general understanding or household capability.

• Microduck official product page ↗Manufacturer’s account · Checked September 7Form, specifications, preorder and software links; no physical-device trial in this review.

The manufacturer describes the simulator as the digital twin used to train the robot, alongside a public SDK, simulation environment and reinforcement-learning stack. The broad workflow is to learn a control policy through repeated attempts in simulation, then deploy it on the physical robot: sim-to-real.

Training and execution are separate stages. Simulation allows repeated computation; the physical robot must act under real mass, contact and sensor conditions. Demonstrated transferred policies do not guarantee that every user-trained move will transfer reliably. Community projects become more useful when they retain training settings, physical video and failure conditions.

This review checks the manufacturer’s description and public links, without training a policy or operating the robot. The simulator offers a starting point for understanding motion and control; the activity you want to pursue should determine whether physical hardware is needed.

Pollen’s launch article distinguishes MicroDuck’s focus on action from Reachy Mini’s conversational interaction, and describes expression through small creature-like sounds. This poses another design question: beyond performing movements, how can a device convey its state and character?

Onur Solmaz’s microquack web work places the robot in a space scene with greeting and status-report interactions. We opened it and clicked Status report: the message panel appended the input, a phonetic sequence and a state label. It offers a concrete example of connecting setting, character and expression.

This observation covers the browser work and visible feedback, without establishing audio quality, unrestricted language understanding or operation on the physical robot. It is still worth exploring as interaction and creative work beyond a specification sheet.

• Meet Microduck ↗Manufacturer’s launch article · August 27Explains the product’s approach to action, training and expression.
• microquack interactive work ↗Onur Solmaz · Viewed September 7Explore the web scene and interaction; it does not establish physical robot performance.

The official page identifies an Apache-2.0 software stack covering the SDK, simulation and reinforcement learning. Follow the repository link to inspect and modify those materials. The open-source description should identify those materials rather than imply that every hardware design and manufacturing file is open.

Useful follow-ups include new policies, development accounts, software changes and reproductions. A small user-built skill can explain a practical use more clearly than another repetition of the specifications.

MicroDuck’s architecture draft separates gamepad, phone and web inputs from the on-robot motion service, with another path for audio and video. This gives developers a useful design idea: adding an interaction need not require rewriting low-level motion control.

The draft label matters: the architecture targets the first shipped version. The September 2 remote-access document records account login as built, with further work needed for off-network access, while requiring local mode to remain independent. These documents support design discussion, not a claim that every feature has shipped.

To contribute, follow how an input becomes a motion intent, then choose a small simulation or interaction task. Later checks should compare the documentation with released behavior, including offline use and recovery after updates. We read a pinned documentation revision without connecting a physical device.

• MicroDuck design documents ↗Official repositoryFollow design and implementation work.
• Robot architecture draft ↗Pinned revision · Read September 7First-release targets and responsibilities.
• Remote-access progress ↗September 2 draft · Pinned revisionSeparates completed work from next steps.

When checked on September 7, the official page offered preorders at an introductory $399 before tax and shipping. The base package lists the robot, a battery, a USB-C cable and a game controller, with separate charger, developer and accessory packs. That is not a delivered total for a reader in China.

Before ordering, check destination availability, estimated timing and total cost in the store. We did not complete checkout and have no delivery receipt. Product and preorder details can be explained now; battery life, reliability, repair and support after delivery need evidence from actual use.

MicroDuck comes from Pollen Robotics, part of Hugging Face. NVIDIA announced an agreement to acquire Hugging Face on September 3, stating continued support for multiple clouds and computing platforms. Our earlier robot launch record mentioned acquisition rumors; read that historical context alongside the newer announcement.

An acquisition agreement does not establish a completed transaction, nor does that announcement demonstrate changes to MicroDuck’s chip, skills or delivery plan. Follow the concrete software, device and service conditions that affect use.

• NVIDIA to Acquire Hugging Face ↗NVIDIA announcement · September 3Establishes the agreement announcement and stated platform commitments, not transaction completion or changes in robot capability.

This topic starts with the available material. Further work, explanations and user reports will be added around specific questions. These questions remain open; useful methods and perspectives can matter without a new product announcement.

• When do preorders become deliveries, and how do regions and costs change?
• Can users reliably transfer their own trained skills onto the robot?
• Which new projects document failures and limits alongside capabilities?