openbricks (host CLI + sim)
Host-side tooling for openbricks hubs — same UX as pybricksdev, built on commodity Python tooling (bleak, esptool, mpremote). One package, one console script: openbricks flash / list / run / upload / stop / log. The MuJoCo-backed simulator is built in too — openbricks sim … opens the sim's CLI when the [sim] extra is installed.
Website: https://openbricks.dev · Documentation: https://docs.openbricks.dev
Install
Recommended — with pipx so the CLI lands in an isolated venv and avoids the "externally managed environment" error on modern macOS / Linux distros:
pipx install openbricks # CLI only (lightweight; bleak / esptool / mpremote)
pipx install 'openbricks[sim]' # CLI + MuJoCo physics simulator
Plain pip works too:
pip install openbricks
pip install 'openbricks[sim]'
For development against a repo checkout (editable install):
pip install -e 'tools/openbricks[sim]'
[sim] adds mujoco (~50 MB, native OpenGL) and numpy — most users (flash + run + log) don't need it. Without [sim], openbricks sim … prints a helpful "pip install openbricks[sim]" hint instead of crashing.
Note: binary wheels (manylinux, macOS universal2, Windows AMD64; CPython 3.9–3.13) ship on PyPI since 0.10.3, so installs are toolchain-free on common platforms. On anything outside that matrix, pip falls back to the sdist and compiles the bundled native extension (
openbricks_sim._native), which needs a C compiler + Python headers.
Commands
flash — program a hub
openbricks flash \
--name RobotA \
--port /dev/tty.usbserial-XXXX \
--firmware native/micropython/ports/esp32/build-openbricks_esp32s3/firmware.bin
Writes the firmware image and bakes the hub's BLE advertising name into NVS. --name is mandatory: two hubs with the same name can't be individually addressed over BLE.
Port syntax: /dev/ttyUSB0 (Linux), /dev/cu.usbserial-* (macOS), COM5 (Windows).
Useful flags: --chip esp32s3, --baud 921600, --skip-erase (faster dev loop, keeps stale NVS).
list — scan for hubs
openbricks list [--timeout 5.0] [--all]
Runs a BLE scan and prints every named device found, sorted by RSSI (strongest first). --all includes unnamed devices too.
run — stage and launch; button stops it; client exits on stop
openbricks run -n RobotA examples/hello.py
Stages the script to /program.py (same target as upload) and triggers the hub's launcher to execute it immediately. Output streams back to your terminal in real time.
- Button stop. Pressing the hub button while the program runs raises
KeyboardInterruptvia the same launcher pathupload+button uses. The client sees the clean "stopped by button press" line and exits. - Program completion. When the program finishes (or raises), the client disconnects and exits — same as
pybricksdev run. - Script persists. Because
runstages to/program.py, the hub can re-run the last program via a button press without another upload.uploadandrundiffer only in whether the client auto-launches after upload.
Stderr (e.g. exception tracebacks) arrives after stdout and is surfaced with a blank-line separator. No paste-mode === echo — raw-paste mode is clean.
stop — interrupt the running program
openbricks stop -n RobotA
Sends a single Ctrl-C byte over the NUS REPL bridge, which MicroPython surfaces as KeyboardInterrupt. Useful when openbricks run has already exited but the hub's still chewing on a long-running user program.
upload — stage a script; hub button launches it
openbricks upload -n RobotA examples/wander.py
Writes the script to /program.py on the hub. The code does not run automatically. Place your robot, press the program button (GPIO 4), and the program starts. Press again to stop it mid-run.
(Pybricks calls this same operation download from the hub's "download to me" perspective. We name by direction-of-data-travel — bytes flow up to the hub, hence upload.)
This works because the firmware ships a frozen main.py that:
- Brings BLE + REPL bridge up immediately (so
openbricks run/upload/stopare always reachable, even when no program is running). - Instantiates the board's Hub, which wires the BLE-toggle button (short-press on GPIO 5) with LED feedback.
- Watches the program button (GPIO 4) via
openbricks.launcher.run()— a short-press runs/program.py, a second short-press raisesKeyboardInterruptin the running program.
Two separate pins (4 for program, 5 for BLE toggle), each handled by short-press only — no duration-based dispatch.
Pass --path /alt.py to stage at a different filename (if you've written your own main.py that reads from there).
Tests
cd tools/openbricks
PYTHONPATH=. python -m unittest discover -s tests -t .
No real hardware needed — esptool, mpremote, and bleak are mocked.
1 maintainer
Release files for openbricks 4.4.1
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| openbricks-4.4.1.tar.gz | 6.2 MB | Details |
Built distributions (wheels)
Total release size: 96.6 MB
Release files / openbricks-4.4.1.tar.gz
| Download URL | openbricks-4.4.1.tar.gz |
|---|---|
| Size | 6.2 MB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
ee05ca93c74b7554be67bf89aa054efed409b5b95354863820e0366696e3898b
|
|
BLAKE2b-256 checksum How to use checksums |
e1e47e1a74214581c53e7e9ae0e5d18049cf248db0a2e1f7df39963e5305e419
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.
Transparency logRelease files / openbricks-4.4.1-cp313-cp313-win_amd64.whl
| Download URL | openbricks-4.4.1-cp313-cp313-win_amd64.whl |
|---|---|
| Size | 6.0 MB |
| Tags | CPython 3.13 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
8f902ff8a77efc6ec8c869cadf29ed2920044fb78dcf86010199f17cf07fabeb
|
|
BLAKE2b-256 checksum How to use checksums |
14f659300f0a7e6b3a51a7d96d90b5e07451b7efb32e88a8ab265012a92a48a0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.
Transparency logRelease files / openbricks-4.4.1-cp313-cp313-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl
| Download URL | openbricks-4.4.1-cp313-cp313-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl |
|---|---|
| Size | 6.0 MB |
| Tags | CPython 3.13 Linux glibc 2.28+ x86-64 Linux glibc 2.5+ x86-64 |
|
SHA-256 checksum How to use checksums |
f244b4ffbc590d036024a770400cc1010dd3b6943926fd9d80227881e1b2f19e
|
|
BLAKE2b-256 checksum How to use checksums |
bcaccd4ffc663cca09d9973412ddee2b4bf7f4c1e4b198dda6a87cfb7d15d44c
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.
Transparency logRelease files / openbricks-4.4.1-cp313-cp313-macosx_10_13_universal2.whl
| Download URL | openbricks-4.4.1-cp313-cp313-macosx_10_13_universal2.whl |
|---|---|
| Size | 6.0 MB |
| Tags | CPython 3.13 macOS 10.13+ universal2 (ARM64, x86-64) |
|
SHA-256 checksum How to use checksums |
ea27de9600d358c882b2aea125c8c558f3ed6c91bc96958eb97cb9e9383d0dd2
|
|
BLAKE2b-256 checksum How to use checksums |
1dccf4cee5c57372e7b6b6d9b38844b9febb878b61b3985220c0920aabe71176
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.
Transparency logRelease files / openbricks-4.4.1-cp312-cp312-win_amd64.whl
| Download URL | openbricks-4.4.1-cp312-cp312-win_amd64.whl |
|---|---|
| Size | 6.0 MB |
| Tags | CPython 3.12 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
9359c9750da75e7c052c630bf73b6113ed497b455c849aa1bd10b905c92e199e
|
|
BLAKE2b-256 checksum How to use checksums |
b809295922346814a14d02ec3996e5649d828962c575e3dab42218172f947714
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.
Transparency logRelease files / openbricks-4.4.1-cp312-cp312-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl
| Download URL | openbricks-4.4.1-cp312-cp312-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl |
|---|---|
| Size | 6.0 MB |
| Tags | CPython 3.12 Linux glibc 2.28+ x86-64 Linux glibc 2.5+ x86-64 |
|
SHA-256 checksum How to use checksums |
94eac99bdd02bf9bc5b494d7990eb607658fe3a92ffd7b7bc9b950b9bf71d9ca
|
|
BLAKE2b-256 checksum How to use checksums |
98e7257c8ce995293ebbabec0cffa3fc7ec5af7cacf1d8cfcbb7bfbb35cfe8e6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.
Transparency logRelease files / openbricks-4.4.1-cp312-cp312-macosx_10_13_universal2.whl
| Download URL | openbricks-4.4.1-cp312-cp312-macosx_10_13_universal2.whl |
|---|---|
| Size | 6.0 MB |
| Tags | CPython 3.12 macOS 10.13+ universal2 (ARM64, x86-64) |
|
SHA-256 checksum How to use checksums |
3368471aa5006fd4e0dd7b60f125aefdcf0b0194db2fd5ea80e8d1805858b7d2
|
|
BLAKE2b-256 checksum How to use checksums |
6a9c23634ee90c7213f01f173819c3842a1b62a689ecb5fb9481efb004dbc2b0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.
Transparency logRelease files / openbricks-4.4.1-cp311-cp311-win_amd64.whl
| Download URL | openbricks-4.4.1-cp311-cp311-win_amd64.whl |
|---|---|
| Size | 6.0 MB |
| Tags | CPython 3.11 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
81422157c64f0a07eee7e8df64d47997d42d5f16eb359ed3b7f511f193a0fe8e
|
|
BLAKE2b-256 checksum How to use checksums |
d4fb191801ce52252cc27cf6000bbb493578c28c6e99fedb2b547f9587a81e38
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.
Transparency logRelease files / openbricks-4.4.1-cp311-cp311-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl
| Download URL | openbricks-4.4.1-cp311-cp311-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl |
|---|---|
| Size | 6.1 MB |
| Tags | CPython 3.11 Linux glibc 2.28+ x86-64 Linux glibc 2.5+ x86-64 |
|
SHA-256 checksum How to use checksums |
ceab65fb08fcd4e834291003786233191ea5395780f2117c9513002806692588
|
|
BLAKE2b-256 checksum How to use checksums |
9174c88704f07a22d307e8bad6788d6a617288a924930276284bef91d4a671fc
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.
Transparency logRelease files / openbricks-4.4.1-cp311-cp311-macosx_10_9_universal2.whl
| Download URL | openbricks-4.4.1-cp311-cp311-macosx_10_9_universal2.whl |
|---|---|
| Size | 6.0 MB |
| Tags | CPython 3.11 macOS 10.9+ universal2 (ARM64, x86-64) |
|
SHA-256 checksum How to use checksums |
75aabcb32f2603d6834132d582b999461fdcef31cd9717ee7c6ff8bcbe0d93ba
|
|
BLAKE2b-256 checksum How to use checksums |
e53c4965615a49ceb803694e78a5e5e2073b8c3a7438b983ee3c3332267385c5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.
Transparency logRelease files / openbricks-4.4.1-cp310-cp310-win_amd64.whl
| Download URL | openbricks-4.4.1-cp310-cp310-win_amd64.whl |
|---|---|
| Size | 6.0 MB |
| Tags | CPython 3.10 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
0eba3fcd5946d5d8b8b751426941b35ec0f757214ef25f71c4ff5a8ffc60bc66
|
|
BLAKE2b-256 checksum How to use checksums |
96da4a3f53a7fe334b77964691fc1e6dee04b0c3958efcdac4db7953085c7b16
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.
Transparency logRelease files / openbricks-4.4.1-cp310-cp310-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl
| Download URL | openbricks-4.4.1-cp310-cp310-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl |
|---|---|
| Size | 6.0 MB |
| Tags | CPython 3.10 Linux glibc 2.28+ x86-64 Linux glibc 2.5+ x86-64 |
|
SHA-256 checksum How to use checksums |
61170b8cc8644c1fdc8e28e241b6115c1e3c3ff285e00ce2939e8ce4ea594631
|
|
BLAKE2b-256 checksum How to use checksums |
0d05072effb40ec55c8d7f1c8b4b77ce195cb73f38d7632098f6fe9ba4003e22
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.
Transparency logRelease files / openbricks-4.4.1-cp310-cp310-macosx_10_9_universal2.whl
| Download URL | openbricks-4.4.1-cp310-cp310-macosx_10_9_universal2.whl |
|---|---|
| Size | 6.0 MB |
| Tags | CPython 3.10 macOS 10.9+ universal2 (ARM64, x86-64) |
|
SHA-256 checksum How to use checksums |
edd6122b8a90b8d10c053df0b3dbaf6906a136f724d614c2ff4547399c5fb895
|
|
BLAKE2b-256 checksum How to use checksums |
00052b7ec57612be8205de97efdea7512eac25da12e2197edc5480cd32247ad6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.
Transparency logRelease files / openbricks-4.4.1-cp39-cp39-win_amd64.whl
| Download URL | openbricks-4.4.1-cp39-cp39-win_amd64.whl |
|---|---|
| Size | 6.0 MB |
| Tags | CPython 3.9 Windows x86-64 |
|
SHA-256 checksum How to use checksums |
535e79f112cc93c662430139da646bf2b11dd162dfa9d03281b654c22d1f815f
|
|
BLAKE2b-256 checksum How to use checksums |
9428ec2933537e765e521e7ad2ee0c3096ff70b9a5ec1fbe935d39e6cdb146d4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.
Transparency logRelease files / openbricks-4.4.1-cp39-cp39-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl
| Download URL | openbricks-4.4.1-cp39-cp39-manylinux1_x86_64.manylinux_2_28_x86_64.manylinux_2_5_x86_64.whl |
|---|---|
| Size | 6.0 MB |
| Tags | CPython 3.9 Linux glibc 2.28+ x86-64 Linux glibc 2.5+ x86-64 |
|
SHA-256 checksum How to use checksums |
a96d24681bea7d76e603dc39187d75bb839f3fb091519d0079d0de5d19083602
|
|
BLAKE2b-256 checksum How to use checksums |
bb59f3b5e38880e70751128110edbbb8b056a3265cd15e7bfdf3dd10c54f44e5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.
Transparency logRelease files / openbricks-4.4.1-cp39-cp39-macosx_10_9_universal2.whl
| Download URL | openbricks-4.4.1-cp39-cp39-macosx_10_9_universal2.whl |
|---|---|
| Size | 6.0 MB |
| Tags | CPython 3.9 macOS 10.9+ universal2 (ARM64, x86-64) |
|
SHA-256 checksum How to use checksums |
8b4f4817cdb53f87ca7179d3a3bab60ef6d2a3d279d57ea9b5f9cd031ef36308
|
|
BLAKE2b-256 checksum How to use checksums |
bae1849a3cc44e8f6c3b1c4941e57ecdeb201a84e5893545d2db135fb4e0ef25
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
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.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Sep 11, 2026.
Transparency log
