quackd a Microduck with an LLM for a brain

MuJoCo · WASM · your key stays in this tab

Live in your browser · MuJoCo + two policies

Type a sentence. Or take the keys.

quackd is on

A model reads your sentence and picks from the robot's own verbs. The executor checks every one against the contract before anything moves.

Your API key

The key stays in this tab. It goes straight from your browser to the model you pick, is never stored and never passes through any server of ours. Every call is billed to you. Prefer nothing to leave the machine at all? Pick Local.

A 3D view of a small duck robot in a 2 m arena with a ball.

Fetching a duck

starting

MuJoCo and the walking policy come from their own sources, about 45 MB the first time and cached by your browser afterwards. Nothing is uploaded.

keyboard ready
twist 0.00, 0.00, 0.00

Command the duck

Try

Transcript

    Drive the duck

    QWE ASD Space
    KR GO 12
    W S
    Walk forward / back
    A D
    Turn left / right
    ⇧ A D
    Strafe instead of turning
    Q E
    Look left / right
    G
    Centre the head
    Space
    Stop. Release and press again to go.
    K
    Kick, right leg
    R
    Stand up
    O
    Read the state into the log
    1 2
    Over the shoulder / duck cam
    Esc
    Hand the keyboard back to the arena, from anywhere
    Why two controls?

    This is the whole interface the robot has: a twist — three numbers, vx, vy, wz — and a head angle. Two learned policies use them: one stands it up, one walks it. The kick is quackd's own scripted impulse, not a policy. None of it reads English.

    There is no key for say, and no key for walk to the ball and quack. A key carries a command. A sentence needs something to read it — that is the sentence box under Command the duck. A verb leaves a line in the log; a twist leaves a number in the readout.

    These are for a laptop keyboard. With a touchscreen, use the sentence box under Command the duck.