muxplex-client
Typed sync/async HTTP client for the muxplex tmux-session-dashboard API.
Ships as its own PyPI distribution (import name muxplex_client) so a
consumer that only needs to make ~12 HTTP calls -- a Stream Deck sidecar, an
Amplifier tool module -- never has to install the server's dependencies
(fastapi, uvicorn, python-pam, ...) or its muxplex server console script.
See ../muxplex-client-design.md for the full
design rationale.
Install
pip install muxplex-client
Runtime dependency: httpx>=0.27.0. Nothing else -- no muxplex server
dependency, no console script installed.
Usage
Synchronous:
from muxplex_client import MuxplexClient
with MuxplexClient("https://your-server:8088", "federation-key") as client:
for session in client.sessions():
if session.bell.needs_attention:
print(f"{session.name} needs attention")
Asynchronous (Amplifier tool modules, or any asyncio caller):
from muxplex_client import AsyncMuxplexClient
async with AsyncMuxplexClient("https://your-server:8088", "federation-key") as client:
result = await client.run_shell_command("my-session", "pytest -q")
print(result.exit_code, result.elapsed)
A localhost caller needs no credential -- federation_key=None is the
default and is fine when running on the same host as the server.
What's in here vs. what isn't
See muxplex-client-design.md §3 for the full included/excluded endpoint
table and rationale. Notably excluded: PATCH /api/settings (highest
blast-radius operation in the API; a v2 concern requiring CAS + 409 retry +
backstop discrimination), all federation endpoints (server-to-server
protocol, no client consumer), and /api/internal/setup-hooks (internal,
self-healing as of server v0.18.0).
Version alignment
muxplex_client.__version__ is cut in lockstep with the muxplex server
version -- one vX.Y.Z tag publishes both wheels. This is provenance
("cut against server X"), not a runtime requirement: the client declares no
dependency on the muxplex package and enforces no version at runtime.
MIN_SERVER_VERSION backs an opt-in check_server() helper the caller may
call; it is never invoked automatically.
The load-bearing correctness mechanism is
muxplex/tests/test_client_contract.py, living in the server's own test
suite: it drives this client over httpx.ASGITransport against the real
FastAPI app and asserts every field the client parses actually exists on the
real response, that mirrored constants (KNOWN_KEYS, MAX_CAPTURE_LINES,
DEFAULT_CAPTURE_LINES) equal their server originals, and that
Bell.needs_attention agrees with the server's own predicate across a truth
table.
The shell-command sentinel
run_shell_command() (and the lower-level muxplex_client.sentinel module)
implements the completion-detection convention from AGENT_GUIDE.md §6.2/§6.4:
wrap a command with ; rc=$?; ... ; echo "MUXPLEX_DONE_<token>_EXIT_$rc" and
poll the pane for the marker.
This assumes the target pane is an idle POSIX shell prompt. It is not a
general HTTP contract -- it fails (types a garbage line into whatever is
actually running, then hangs until timeout) against vim, a REPL, less, a
TUI, an ssh session, or a non-POSIX shell without a matching exit_expr.
The one correctness rule worth calling out explicitly: matching must be
digit-anchored (MUXPLEX_DONE_<token>_EXIT_(\d+)), never a bare-token
substring check. tmux echoes the literal, unexpanded ...EXIT_$? into the
pane the instant you send the line -- before the shell has even run it -- so
a bare-token match reports "done" with a bogus exit code immediately. See
muxplex_client/sentinel.py's docstring and tests/test_sentinel.py's
digit-anchor regression test.
Development
uv sync --extra dev # from this directory, or from the repo root via the
# [tool.uv.workspace] declaration
uv run pytest
tests/ is pure -- no network, no server import, and passes with muxplex
not installed at all.
1 maintainer
Metadata
1 maintainer
Release files for muxplex-client 0.61.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 | |
|---|---|---|---|
| muxplex_client-0.61.1.tar.gz | 45.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| muxplex_client-0.61.1-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 81.6 kB
Release files / muxplex_client-0.61.1.tar.gz
| Download URL | muxplex_client-0.61.1.tar.gz |
|---|---|
| Size | 45.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
432c36c67f9929ce0bdc2f991919a09894e54ab7b4a0bfb5915f03b80bdc1389
|
|
BLAKE2b-256 checksum How to use checksums |
881eb95e063ed5d766e2135ed6885be973b9676b190f5cc3249a5ae1255cd494
|
| 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 16, 2026.
Transparency logRelease files / muxplex_client-0.61.1-py3-none-any.whl
| Download URL | muxplex_client-0.61.1-py3-none-any.whl |
|---|---|
| Size | 36.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
c0c30dbb9267180bb8f9700e0afbc43756e7a8a35ea67b5c66a09084094b54c4
|
|
BLAKE2b-256 checksum How to use checksums |
1d47f1ebdea4cc64a4c83692d93fd92154e57af27d9e2a5ed9a5d28f4ec189ad
|
| 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 16, 2026.
Transparency log
