Skip to main content

nestor-reachy

Reachy Mini as a satellite of Nestor: the assistant speaks and listens through it, and its head and antennas follow the conversation: listening, thinking, speaking, nodding on each word, laughing when the voice laughs. Built on nestor-satellite.

Status: the MuJoCo twin only. A physical robot is refused until its safety policy is validated on hardware; the robot's own microphone and speaker come later.

pip install "nestor-reachy[reachy,audio]"
nestor-reachy twin --headless &                               # the simulated robot
nestor-reachy run --room salon --pairing-uri "nestor+http://nestor.local:7860/?code=K7QF2M9X"

Pairing

Reachy has a speaker and no screen. The simplest is an enrollment code: add a satellite in the Nestor admin with the provisioning method (enrollment.provisioning), and give the robot the pairing URI it returns, by flag or in its environment:

NESTOR_PAIRING_URI="nestor+http://nestor.local:7860/?code=K7QF2M9X" nestor-reachy run --room salon
nestor-reachy run --core http://nestor.local:7860 --room salon --pairing-code K7QF-2M9X

Without one, it says a six-digit device code on its speaker, twice, digit by digit, with the SDK's recorded voice (device_code.speech, offline), and logs it: type it in the admin. The token is then kept in ~/.config/nestor-reachy/reachy-<room>.json and later runs reconnect with it (nestor-reachy run --core http://nestor.local:7860 --room salon). To tell robots apart, the admin can ask one to identify itself: it wiggles its antennas for two seconds, while it waits to be paired or once connected.

Safety lives on the device: every target is clamped to the motion limits, and the robot returns to rest when the link to the core drops or nothing is heard from it for two seconds.

Development

The tests use the Nestor server's conformance suite and the SDK from sibling checkouts (../nestor, ../nestor-satellite-python).

uv sync
uv run pre-commit install
uv run ruff check && uv run ruff format --check && uv run ty check && uv run pytest
uv run --no-dev --group live --extra reachy pytest -m live   # with `nestor-reachy twin` running

License

MIT

Metadata

Release files for nestor-reachy 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for nestor-reachy 0.1.0
File Size Uploaded Provenance Actions
nestor_reachy-0.1.0.tar.gz 11.1 kB Without provenance Details for nestor_reachy-0.1.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for nestor-reachy 0.1.0
File Interpreter ABI Platform Actions
nestor_reachy-0.1.0-py3-none-any.whl Python 3 none any Details for nestor_reachy-0.1.0-py3-none-any.whl

Total release size: 23.6 kB

Release files / nestor_reachy-0.1.0.tar.gz

Download URL nestor_reachy-0.1.0.tar.gz
Size 11.1 kB
Tags Source
SHA-256 checksum
How to use checksums
95f64eec582b0fa8f5e5bd936b4dd295867f5d9c4d5af52ec7826d0dbc87554e
BLAKE2b-256 checksum
How to use checksums
a9607f9a934711d3e5cf412744a26a1428d58d2f8e9e81c6fef5cc6d2e8f5b1f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.6 {"installer":{"name":"uv","version":"0.13.6","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Release files / nestor_reachy-0.1.0-py3-none-any.whl

Download URL nestor_reachy-0.1.0-py3-none-any.whl
Size 12.5 kB
Tags Python 3
SHA-256 checksum
How to use checksums
3e13397423bb1c806e753d1e4f1a981d239f11f1f1e847b61bf7255f868398a3
BLAKE2b-256 checksum
How to use checksums
9b31de06e53247fbe5ed537bf45d85681a218790f807882f1a0dbfc29920603e
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via uv/0.13.6 {"installer":{"name":"uv","version":"0.13.6","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"Ubuntu","version":"24.04","id":"noble","libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":true}

Security for nestor-reachy 0.1.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page