Instructions to use pipenetwork/GLM-5.2-MLX-nvfp4 with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Libraries
- MLX
How to use pipenetwork/GLM-5.2-MLX-nvfp4 with MLX:
# Make sure mlx-lm is installed # pip install --upgrade mlx-lm # Generate text with mlx-lm from mlx_lm import load, generate model, tokenizer = load("pipenetwork/GLM-5.2-MLX-nvfp4") prompt = "Write a story about Einstein" messages = [{"role": "user", "content": prompt}] prompt = tokenizer.apply_chat_template( messages, add_generation_prompt=True ) text = generate(model, tokenizer, prompt=prompt, verbose=True) - Notebooks
- Google Colab
- Kaggle
- Local Apps Settings
- LM Studio
- Pi
How to use pipenetwork/GLM-5.2-MLX-nvfp4 with Pi:
Start the MLX server
# Install MLX LM: uv tool install mlx-lm # Start a local OpenAI-compatible server: mlx_lm.server --model "pipenetwork/GLM-5.2-MLX-nvfp4"
Configure the model in Pi
# Install Pi: npm install -g @earendil-works/pi-coding-agent # Add to ~/.pi/agent/models.json: { "providers": { "mlx-lm": { "baseUrl": "http://localhost:8080/v1", "api": "openai-completions", "apiKey": "none", "models": [ { "id": "pipenetwork/GLM-5.2-MLX-nvfp4" } ] } } }Run Pi
# Start Pi in your project directory: pi
- MLX LM
How to use pipenetwork/GLM-5.2-MLX-nvfp4 with MLX LM:
Generate or start a chat session
# Install MLX LM uv tool install mlx-lm # Interactive chat REPL mlx_lm.chat --model "pipenetwork/GLM-5.2-MLX-nvfp4"
Run an OpenAI-compatible server
# Install MLX LM uv tool install mlx-lm # Start the server mlx_lm.server --model "pipenetwork/GLM-5.2-MLX-nvfp4" # Calling the OpenAI-compatible server with curl curl -X POST "http://localhost:8000/v1/chat/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "pipenetwork/GLM-5.2-MLX-nvfp4", "messages": [ {"role": "user", "content": "Hello"} ] }' - Hermes Agent
How to use pipenetwork/GLM-5.2-MLX-nvfp4 with Hermes Agent:
Start the MLX server
# Install MLX LM: uv tool install mlx-lm # Start a local OpenAI-compatible server: mlx_lm.server --model "pipenetwork/GLM-5.2-MLX-nvfp4"
Configure Hermes
# Install Hermes: curl -fsSL https://hermes-agent.nousresearch.com/install.sh | bash hermes setup # Point Hermes at the local server: hermes config set model.provider custom hermes config set model.base_url http://127.0.0.1:8080/v1 hermes config set model.default pipenetwork/GLM-5.2-MLX-nvfp4
Run Hermes
hermes
- Atomic Chat
- OpenClaw
How to use pipenetwork/GLM-5.2-MLX-nvfp4 with OpenClaw:
Start the MLX server
# Install MLX LM: uv tool install mlx-lm # Start a local OpenAI-compatible server: mlx_lm.server --model "pipenetwork/GLM-5.2-MLX-nvfp4"
Configure OpenClaw
# Install OpenClaw: npm install -g openclaw@latest # Register the local server and set it as the default model: openclaw onboard --non-interactive --mode local \ --auth-choice custom-api-key \ --custom-base-url http://127.0.0.1:8080/v1 \ --custom-model-id "pipenetwork/GLM-5.2-MLX-nvfp4" \ --custom-provider-id mlx-lm \ --custom-compatibility openai \ --custom-text-input \ --accept-risk \ --skip-health
Run OpenClaw
openclaw agent --local --agent main --message "Hello from Hugging Face"
GLM-5.2-MLX-nvfp4
Runtime — updated 2026-08-28: load with --trust-remote-code
This repository now bundles glm_moe_dsa.py (declared via model_file in config.json), a fixed runtime
for this architecture, and needs it:
mlx_lm.generate --model pipenetwork/GLM-5.2-MLX-nvfp4 --trust-remote-code --prompt "..." --max-tokens 300
mlx-lm's own glm_moe_dsa builds a lightning indexer on all 78 layers, but GLM-5.2 ships indexer weights
on 21 (indexer_types: the other 57 "shared" layers reuse the previous full layer's top-k selection).
mlx_lm.load loads leniently and left those 57 indexers at random initialisation. Prompts up to 2048
tokens were unaffected (the indexer is bypassed below index_topk); beyond that, 57 of 78 layers attended
to keys chosen by random projections. The bundled runtime implements the schedule as the reference does
(plus fp32 indexer scores and router logits and the indexer LayerNorm epsilon); tiny-config parity against
transformers 5.16 is 4e-7 with the sparse path live, and a strict load of this checkpoint reports zero
missing and zero unexpected tensors. Details, tests and the GLM-5.3 builds made with it:
github.com/PipeNetwork/glm53-mlx. The weights are unchanged.
An MLX conversion of zai-org/GLM-5.2 quantized to NVFP4 (4-bit FP4, group size 16) for Apple Silicon with mlx-lm.
This is the MLX analog of NVIDIA's nvidia/GLM-5.2-NVFP4. NVIDIA's checkpoint stores weights in ModelOpt-packed NVFP4 that mlx-lm cannot read directly, so this build was produced by quantizing the bf16 base with MLX's own NVFP4 mode (--q-mode nvfp4 --q-group-size 16).
- Base model: zai-org/GLM-5.2 (
GlmMoeDsaForCausalLM, 753B total / ~40B active MoE, text-only) - Format: MLX, NVFP4 (4-bit FP4, group size 16)
- Approx. size on disk: 390G
- Converted with: mlx-lm 0.31.2
Usage
pip install -U mlx-lm
mlx_lm.generate --model pipenetwork/GLM-5.2-MLX-nvfp4 --prompt "Explain mixture-of-experts in one sentence." --max-tokens 128
License
MIT, inherited from the base model.
- Downloads last month
- 686
4-bit
Model tree for pipenetwork/GLM-5.2-MLX-nvfp4
Base model
zai-org/GLM-5.2