Skip to main content
Pre-release

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.

The package installs torch and torchvision: the processors transformers ships for these families (the template rendering and the image-to-patches step) are written on them. The towers themselves run on MLX; torch does no inference here.

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.0a6

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

Source distribution (sdist)

Source distribution for mlx-beam-vision 0.1.0a6
File Size Uploaded
mlx_beam_vision-0.1.0a6.tar.gz 50.6 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for mlx-beam-vision 0.1.0a6
File Interpreter ABI Platform
mlx_beam_vision-0.1.0a6-py3-none-any.whl Python 3 none any Details

Total release size: 110.8 kB

Release files / mlx_beam_vision-0.1.0a6.tar.gz

Download URL mlx_beam_vision-0.1.0a6.tar.gz
Size 50.6 kB
Tags Source
SHA-256 checksum
How to use checksums
7e47fe606d5fa5eb49589910ddecf43f55e7c446a0564b93bbc446c525eb239f
BLAKE2b-256 checksum
How to use checksums
3284bda306c33068452bbf127cc36d588f14c7f5ef8ba47ca8ec6ce443eb3450
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

Release files / mlx_beam_vision-0.1.0a6-py3-none-any.whl

Download URL mlx_beam_vision-0.1.0a6-py3-none-any.whl
Size 60.2 kB
Tags Python 3
SHA-256 checksum
How to use checksums
668200866e9754f315654cb7e286be30a6b2ef858017e217243dbc05d9c16292
BLAKE2b-256 checksum
How to use checksums
2e16a607f435d59ceed7f6215746fe6804799cfef877f59c5de6b2ff8550a77a
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

Release history Release notifications | RSS feed

This release

0.1.0a6 This release

2 release files

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