beam-sprint

2 m Sprint recipe engineered by Beam (Reflection AI), not by a human: forward_reward 2.0 -> 4.0, a change the model chose after reading Pollen's own sprint AGENTS.md. Checkpoint 750 of a from-scratch 1000-iteration run (4096 envs, seed 1). A human operator ran every command; no hand-tuning.

A perpetual policy for the microduck (61-D observation, 14 actions, 50 Hz). Runs until told otherwise โ€” a gait, loaded into a policy slot.

Run it on a robot

sudo robotctl policy load <slot> munish0838/microduck-beam-sprint

The observation normalizer is baked into policy.onnx; feed raw observations. manifest.json follows schema 2 of the microduck policy manifest (docs/policy-manifest.md in the daemon repo).

Training

  • task_id: Mjlab-Sprint2m-MicroDuck
  • repo: https://github.com/pollen-robotics/microduck-challenges
  • branch: beam/S1/r2
  • commit: ef4b93eb4
  • checkpoint: 750
  • seed: 1
  • base: mjlab-microduck 0.1.0 @ 1efd853be
  • started: 2026-10-31T08:40:04Z

Reproduce

Same code, same uv.lock, same command, same seed. Training it again yields a comparable policy, not the same weights: GPU reinforcement learning is not bit-reproducible across machines.

git clone https://github.com/pollen-robotics/microduck-challenges
cd microduck-challenges
git checkout ef4b93eb4
uv sync
uv run train Mjlab-Sprint2m-MicroDuck --env.scene.num-envs 4096 --agent.max-iterations 1000 --agent.seed 1 --agent.logger tensorboard --agent.run-name S1-r2
Downloads last month
10
Video Preview
loading