mlx-optiq

Run any LLM locally on your Mac. Quantize it, serve it, and code with it.

Website: https://mlx-optiq.com | Docs: https://mlx-optiq.com/docs/ | Models: https://mlx-optiq.com/models | Blog: https://mlx-optiq.com/blog/ | HF org: https://huggingface.co/mlx-community

mlx-optiq is the local-LLM stack for Apple Silicon: an optimizing compiler and runtime for MLX that turns a full-precision model into the best version for a given memory budget on your Mac, using per-layer sensitivity measurement instead of uniform 4-bit everywhere. The same signal drives weights, KV cache, LoRA fine-tuning, and runtime adapter swapping.

One pip install gives you three ways to work with a local model: the CLI (quantize, serve, fine-tune), OptiQ Lab (a local web workbench), and OptiQ Code (a terminal coding agent that drives your served model).

pip install mlx-optiq

Python 3.11+. Quantizing and local inference need Apple Silicon; optiq code and optiq lab also run on Linux and Windows against any OpenAI-compatible base_url.

What it does

Mixed-precision weight quantization that beats uniform 4-bit at the same size. optiq convert measures each layer's sensitivity and allocates bits per layer. A static method assigns bits by architecture for models too large to measure. Methods.
SSD expert streaming runs large MoE quants that don't fit in RAM. A 2-bit Qwen3.5-122B-A10B runs on a 36 GB Mac at ~12 GB resident, experts streamed off disk. How.
Mixed-precision KV cache for longer context at lower memory. optiq serve runs a per-layer KV quant pipeline.
One server, two protocols. optiq serve speaks both the OpenAI and Anthropic APIs from one process. Point Claude Code or either SDK at the same local URL.
Your coding agent on a local model. optiq run claude -m mlx-community/Qwen3.6-27B-OptiQ-4bit starts optiq serve (or reuses one), configures the agent for that session only, and launches it. Works with Claude Code, Codex, OpenCode, OpenClaw, Hermes Agent and Mistral Vibe.
Speculative decoding via bundled MTP heads or paired drafters (--mtp, --drafter).
Distributed inference across Macs. optiq cluster serve shards a model's layers across two or more Macs over Thunderbolt and exposes one OpenAI endpoint. A 2-bit Qwen3.5-122B-A10B (42.8 GiB) runs fully resident across a 36 GB + 24 GB pair at ~20 tok/s, against 4.9 tok/s streaming experts off SSD on one Mac. How.
Sensitivity-aware LoRA (SFT + DPO) and runtime hot-swap adapters.
OptiQ Lab (pip install mlx-optiq then optiq lab): a local web UI for chat, quantize, fine-tune, and dataset work. Product.
OptiQ Code (optiq code): a terminal coding agent that drives whatever optiq serve is serving, offline, engineered for local models (never an empty patch, edit-resilient, stall-proof). Product.

Quickstart

Every mlx-optiq quant loads with stock mlx-lm:

from mlx_lm import load, generate
model, tok = load("mlx-community/Qwen3.5-9B-OptiQ-4bit")
print(generate(model, tok, prompt="Hello", max_tokens=50))

Installing mlx-optiq unlocks the rest. A few starting points:

# Serve with the OpenAI + Anthropic API and ~1.4x speculative decode
optiq serve --model mlx-community/Qwen3.5-9B-OptiQ-4bit --mtp

# Run a huge MoE that doesn't fit in RAM (experts stream off SSD)
optiq serve --model mlx-community/Qwen3.5-122B-A10B-OptiQ-2bit --stream-experts

# Quantize a fresh model (exact sensitivity, or fast structural rules for big bases)
optiq convert Qwen/Qwen3.5-9B --target-bpw 5.0 --candidate-bits 4,8
optiq convert <large-moe> --method static --candidate-bits 2,4 --target-bpw 2.5

# Fine-tune with sensitivity-aware LoRA
optiq lora train mlx-community/Qwen3.5-9B-OptiQ-4bit --data ./jsonl_dir --rank 8

# Shard a model across two Macs over Thunderbolt (one OpenAI endpoint)
optiq cluster up                                    # on every Mac
optiq cluster serve --model mlx-community/Qwen3.5-122B-A10B-OptiQ-2bit

# Code with your local model, in your terminal (offline)
optiq code                                          # interactive, in a repo
optiq code -p "Fix the failing test in parser.py"   # headless

Full guides for serving, KV-quant, LoRA, MTP and per-family setup are in the docs. The models page lists every quant with its Capability Score, and the blog has the deeper write-ups.

Requirements

Apple Silicon (M1 or newer), macOS, Python 3.11+.
The published quants load with stock mlx-lm. Converting and some MoE / multimodal runtime features track mlx-lm main; install it from git when a model card asks for it.

License

MIT for the package. Quantized models follow their base model's license.

Metadata

Release files for mlx-optiq 0.7.3

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-optiq 0.7.3
File	Size	Uploaded	Provenance
mlx_optiq-0.7.3.tar.gz	2.0 MB	Oct 23, 2026	Without provenance	Details

Built distribution (wheel)

Table of built distributions (wheels) for mlx-optiq 0.7.3
File	Interpreter	ABI	Platform	Reset
mlx_optiq-0.7.3-py3-none-any.whl 1.8 MB Oct 23, 2026 Without provenance	Python 3	none	any	Details

Total release size: 3.8 MB

Release files / mlx_optiq-0.7.3.tar.gz

Download URL	mlx_optiq-0.7.3.tar.gz
Size	2.0 MB
Tags	Source
SHA-256 checksum How to use checksums	`f001b67b47eba3b8856e65a99c1d75f5bf7f4d602854f4feacb8650f1e90b65d`
BLAKE2b-256 checksum How to use checksums	`61870b92fdd8f5d234df613900a2ded840e73ca1a0c9d6af0564999422a5dc34`
Upload date	Oct 23, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`twine/7.0.0 CPython/3.13.7`

Release files / mlx_optiq-0.7.3-py3-none-any.whl

Download URL	mlx_optiq-0.7.3-py3-none-any.whl
Size	1.8 MB
Tags	Python 3
SHA-256 checksum How to use checksums	`a0bca09aeee63ec6f08c8cf666ff0c344deb4ea136b776143aea3f3b8a8f39b3`
BLAKE2b-256 checksum How to use checksums	`a8b9ad6d206bec1edd6eaadaa44fcbfc845b16a572d2723244f0e77125fb5b8d`
Upload date	Oct 23, 2026
Uploaded using Trusted Publishing? What is trusted publishing?	No
Uploaded via	`twine/7.0.0 CPython/3.13.7`

Security for mlx-optiq 0.7.3

Report project as malware

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.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A 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.