AI × Robotics × Simulation

Make AI-generated
robot behaviors
prove they work.

HeyWalk turns human intent into executable robot behavior. It then runs that behavior in a physics-based simulation, measures what happened, and uses the evidence to improve.

Platform overview

Task → Controller → MuJoCo Simulation → Measured Verdict

Simulated robot: MicroDuck by Pollen Robotics (CC BY-NC-SA 4.0).

Powered by open-source robotics & AI

Muse AI MuJoCo ONNX ROS 2 MicroDuck NumPy Python FastAPI React Three.js Hugging Face

The problem

Code that looks right
isn't proof it works.

Robotics sits at the intersection of software, control systems, mechanics, and real-world uncertainty. AI can generate code, but a robot controller has to deal with balance, contact, timing, obstacles, and failure.

HeyWalk treats generated robot code as an experiment. It executes the controller in a simulated world, measures the robot's behavior independently, and sends concrete failure evidence back into the improvement loop.

The HeyWalk loop

From thought to motion.
With evidence at every step.

A complete experiment cycle connects AI-generated control logic to observable robot behavior.

01 / GENERATE

Describe the task

Write what you want the robot to do in plain language. Muse Spark turns the task into objectives and a ROS 2 Python controller.

human intent controller.py
02 / EXECUTE

Run in simulation

The controller runs in an isolated container and communicates through ROS 2 topics. MuJoCo advances the robot's physics.

ROS 2 MuJoCo
03 / VERIFY

Measure what happened

An independent evaluator checks telemetry against task and safety criteria. The model cannot declare its own success.

telemetry verdict
04 / IMPROVE

Diagnose and rerun

When a run fails, Muse Spark receives the evidence, proposes a targeted patch, and the updated controller is tested again.

evidence patch
Each run preserves the task, controller version, environment seed, logs, telemetry, evaluator verdict, and correction history. Reruns can use the same world configuration for meaningful comparison.

Under the hood

Each layer has
a clear job.

HeyWalk separates AI reasoning, robot control, physics, learned locomotion, and evaluation. The AI writes the high-level behavior; established simulation and policy components handle the physical dynamics and gait.

Explore the technical docs
Meta Muse Spark

Interprets task descriptions, generates ROS 2 controller logic, and diagnoses failures using structured execution evidence.

AI reasoning
ROS 2 Python controller

Handles navigation, objective sequencing, speed limits, and stop behavior through standard ROS 2 topics.

AI-generated logic
MuJoCo

Computes rigid-body dynamics, gravity, ground contact, actuator tracking, collisions, and falls.

Physics engine
ONNX Runtime + MicroDuck policy

Executes Pollen Robotics' existing velocity/stand learned policy at 50 Hz to provide balance and gait.

Pretrained gait
Independent evaluator

Grades recorded telemetry against objective and safety criteria. Success is based on evidence, not model claims.

Verification
PHYSICS
200 Hz

MuJoCo simulation step rate

CONTROL
50 Hz

Walking policy and control loop

OBSERVABILITY
20 Hz

Telemetry sampling to the live view

See the experiment

Watch HeyWalk in action.

We ask the MicroDuck to walk to the green flag then back to starting point to stop safely.

37-second simulation walkthrough · Simulated robot: MicroDuck by Pollen Robotics (CC BY-NC-SA 4.0)

A call to Indonesian campuses & vocational high schools

The next generation of robotics talent starts before the industry arrives.

Indonesia's students should not have to wait for expensive robot hardware to start learning robotics. With simulation-first experimentation, campuses and vocational high schools can introduce robot programming, control logic, AI-assisted development, and evidence-based testing using accessible computing resources.

We are looking for universities, polytechnics, robotics clubs, lecturers, and vocational high school programs interested in exploring a hands-on HeyWalk pilot. The goal is to help students build practical skills for a future where robotics becomes part of more industries.

The pilot inquiry opens a pre-filled GitHub issue. No external form backend is required.

For universities

Bring AI-assisted robotics experiments into robotics, mechatronics, computer science, and engineering learning environments.

For vocational high schools

Introduce students to programming, automation concepts, simulation, and the foundations of robotics without starting with a costly robot fleet.

For robotics clubs

Give student teams a shared environment to prototype behaviors, test ideas, inspect failures, and compare iterations.

For industry partners

Help shape practical learning pathways and expose emerging talent to the tools and thinking behind robotics development.

The invitation

Let's make robotics more accessible in Indonesia.

Start with a simulation. Build the skills. Be ready for the opportunities ahead.

Start a conversation

Documentation & getting started

Go from curious
to running an experiment.

HeyWalk is a software-in-the-loop research prototype. Explore the repository for setup instructions, implementation details, API routes, safety boundaries, and third-party notices.

Important: simulation is not physical-world certification.

HeyWalk currently targets software-in-the-loop experiments. A successful simulation does not prove physical robot safety. Generated code is untrusted and runs in an isolated, resource-limited container. Do not connect this prototype to a physical robot.

Copyright & attribution

Third-party notices.

HeyWalk's simulation runs on third-party robot models and engines that remain under their own licenses, as recorded in the project's THIRD_PARTY_NOTICES.md (verified against upstream on 2026-10-31). Page content and demo recordings © 2026 HeyWalk.

MicroDuck model & policy

Copyright Pollen Robotics — the simulated robot shown in the videos on this page.

  • MJCF descriptions & scenes: Apache-2.0 — byte-identical upstream copies; composed runtime scenes keep the attribution header.
  • 38 STL meshes: CC BY-NC-SA 4.0 — non-commercial, share-alike.
  • velstand.onnx walking policy: Apache-2.0, via Hugging Face — distributed unchanged.
Upstream source
MuJoCo physics engine

Copyright 2021 DeepMind Technologies Limited
Version 3.17.0 · Source code: Apache License, Version 2.0

Apache License 2.0
ONNX Runtime

Copyright (c) Microsoft Corporation
Version 1.31.1 · MIT License

MIT License text

Full inventory — vendored file paths, pinned upstream commits, and the byte-verification record: THIRD_PARTY_NOTICES.md. Pollen Robotics and MicroDuck are named here for attribution only; Pollen Robotics does not endorse HeyWalk.

Meta, Muse, and Muse Spark are trademarks of Meta Platforms, Inc. All other names and marks are the property of their respective owners. HeyWalk is an independent project and is not affiliated with or endorsed by these parties. Page icons: Font Awesome Free © Fonticons, Inc. (CC BY 4.0); typefaces Inter © Rasmus Andersson and JetBrains Mono © JetBrains (SIL OFL 1.1).