librmux
librmux is the Python SDK for RMUX.
Its public handles follow the same vocabulary as the Rust SDK: RMUX,
Session, Window, and Pane.
Installation
python -m pip install librmux
librmux targets RMUX 0.6.1 and uses the rmux executable. Install the RMUX
binary separately and keep it on PATH, or pass a specific binary with
RMUX.builder().binary(...).
from librmux import RMUX
rmux = RMUX()
for session in rmux.list_sessions():
print(session["session_name"])
Rmux and Server remain available as aliases for existing code.
Endpoint Selection
RMUX() # default rmux endpoint
RMUX(socket_path="/tmp/rmux") # passes -S /tmp/rmux
RMUX(socket_name="demo") # passes -L demo
RMUX.builder().socket_name("demo").connect_or_start()
Common Operations
session = rmux.ensure_session("demo")
pane = session.pane(0, 0)
pane.send_text("echo hello\n")
pane.expect_visible_text().to_contain("hello").timeout(5)
text = pane.capture_text()
For raw commands:
run = rmux.cmd("rename-window", "-t", "demo:0", "logs")
if run.returncode != 0:
raise RuntimeError(run.stderr)
1 maintainer
Metadata
1 maintainer
Release files for librmux 0.6.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 | Provenance | Actions |
|---|---|---|---|---|
| librmux-0.6.1.tar.gz | 23.3 kB | With provenance | Details for librmux-0.6.1.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| librmux-0.6.1-py3-none-any.whl | Python 3 | none | any | Details for librmux-0.6.1-py3-none-any.whl |
Total release size: 46.5 kB
Release files / librmux-0.6.1.tar.gz
| Download URL | librmux-0.6.1.tar.gz |
|---|---|
| Size | 23.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
767fd35e715b6436d28a5d7c06dc4ba50f760c45b8a97c4d7c62899d5cb2c8e7
|
|
BLAKE2b-256 checksum How to use checksums |
7d2e5853f75608847112c04b435d1abf00295e7c4c3bd2e9347d7ccc964ae357
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 19, 2026.
Transparency logRelease files / librmux-0.6.1-py3-none-any.whl
| Download URL | librmux-0.6.1-py3-none-any.whl |
|---|---|
| Size | 23.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
1120717fac1907763cfff0c4ccc08bfd455a70b5ce86a1a6bb215982a3adb45b
|
|
BLAKE2b-256 checksum How to use checksums |
7ff632a41d2d05eee12c82a3fe6e97b318e5864049ce44554c1a683b17392929
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
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 Jun 19, 2026.
Transparency logSecurity for librmux 0.6.1
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for librmux-0.6.1.tar.gz
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 Jun 19, 2026.
Transparency logA 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.
