This release is a pre-release and may not be stable for production use.
mlx-beam-vision
The towers that let mlx-beam see. Install
it next to the engine (pip install mlx-beam[vision], or this package by
name) and a checkpoint that ships a vision tower serves images: an
image_url part with a data: URL in a chat request, the checkpoint's own
processor renders the template, the tower encodes the image, and the
engine's prefill takes the image's features in place of the placeholder
tokens - beside text-only requests in the same batch, with the prefix cache
keyed on the image's digest. Without this package the engine answers image
input with a 400 that names the vision extra.
Towers vendored from mlx-vlm (MIT,
see mlx_beam_vision/_vendor/VENDORED.md):
| Family | Models | Notes |
|---|---|---|
qwen3_vl |
Qwen3-VL, Qwen3.5, Qwen3.8 | DeepStack applied: the tower's intermediate features are added after the text model's first layers |
mistral3 |
Mistral Small 3.x (Pixtral tower) | the image's rows are separate spans ([IMG_BREAK] between them) |
gemma4 |
Gemma 4 E2B, E4B | image only; audio is not served yet. The 12B (gemma4_unified, encoder-free, its image tokens attending bidirectionally in the text model) is refused with that reason until the text trunk takes such a mask |
muse_glimmer |
Muse Glimmer | the projector's norm matches the text model's input norm |
granite4_vision |
Granite Vision 4.1 | AnyRes tiles, window Q-Former projectors; nothing at the embedding, every projector's features added ahead of its text layer |
Not yet: audio and video input, quantized towers (the towers load at model precision; a package that ships a quantized tower is refused with a message). An image above 32 megapixels is refused before it is decoded.
Every family is exercised in the tests on a tiny random tower against a direct forward; the real towers and processors are validated on Apple silicon with the checkpoints themselves.
/health.vision reports the family, the tower, the processor and the
feature cache (encoder outputs by image digest, bounded in bytes).
Release files for mlx-beam-vision 0.1.0a5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| mlx_beam_vision-0.1.0a5.tar.gz | 50.0 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mlx_beam_vision-0.1.0a5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 110.1 kB
Release files / mlx_beam_vision-0.1.0a5.tar.gz
| Download URL | mlx_beam_vision-0.1.0a5.tar.gz |
|---|---|
| Size | 50.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
bfe58ff95e664e92c3710f916019549fc2de2fb11f532a6891195467f31e7d87
|
|
BLAKE2b-256 checksum How to use checksums |
2bdb1a215ed294278a132302e2f67921fec0d1d3054e58b7ede8ca3497a73702
|
| 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 25, 2026.
Transparency logRelease files / mlx_beam_vision-0.1.0a5-py3-none-any.whl
| Download URL | mlx_beam_vision-0.1.0a5-py3-none-any.whl |
|---|---|
| Size | 60.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6537819b2d1c06dbcdd06d12f23dc37f88954259dd05010874fcf95267321176
|
|
BLAKE2b-256 checksum How to use checksums |
931aab8ed5eb654ece7f432bf8d6e8bde54f24461fb69fd68c4a9a893705914d
|
| 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 25, 2026.
Transparency log