Repository navigation
v0.24.0 letting go of the arm means putting it down first, and a turn the model's API could not answer is asked again
Letting go of the arm means putting it down first
quackd robot release folds the SO-101 to its recorded rest pose and lets go of it there, where
0.14.0's command took torque off wherever the arm stood and let it fall. A fold that misses, there
or at the end of a run, asks twice before anything drops: first to clear the arm's way and fold
once more, and only if that fold misses too, whether to take torque off where the arm stands,
saying that it will drop. Anything but Enter keeps torque on.
ADR-0058
records the decisions.
An arm with no rest pose is never let fall
A real arm with no rest pose recorded is refused a run, a dry run, an MCP session and a flock,
and its close no longer lets go of it wherever it stands. quackd doctor and
quackd robot list --probe keep it powered and say so, and at a terminal doctor asks before it
drops it into your hands. Before it folds an arm with a pose, doctor now gives the hands that
supported it 3 seconds to come away, and quackd robot rest-pose lets go of the arm only once
you confirm its pose.
The kill switch does not wait
A first Ctrl+C or q now ends a model call that is still out, the pilot's or a decision LLM's,
without waiting for its answer, and stops the fold at the end of a run that ended by itself,
holding the arm where it is.
A turn the model's API could not answer is asked again
A rate limit, an overloaded server or a dropped connection is asked again up to four times, after
waits that grow from 5 seconds to a minute, with the robot holding still and the heartbeat
watching it. The SDKs retry nothing of their own now, so every try is on the record and under the
stop.
Safety
says what is asked again and what is not.
Not run yet
None of it has run on an arm, and nothing has been asked again after a real 429 or 529. The bench
steps that would settle the arm's part are under Known limitations in the changelog.
Ten distributions, one version between them: quackd, and quackd-microduck, quackd-lerobot,
quackd-rosbridge, quackd-open-duck, quackd-xlerobot, quackd-alohamini, quackd-toddlerbot,
quackd-huebot and quackd-moss. The full note is in
CHANGELOG.md.