Instructions to use julianmb/Nex-N2.5-mini-ROCmFP4-GGUF with libraries, inference providers, notebooks, and local apps. Follow these links to get started.
- Notebooks
- Google Colab
- Kaggle
- Local Apps Settings
- llama.cpp
How to use julianmb/Nex-N2.5-mini-ROCmFP4-GGUF with llama.cpp:
Install (macOS, Linux)
curl -LsSf https://llama.app/install.sh | sh # Start a local OpenAI-compatible server with a web UI: llama serve -hf julianmb/Nex-N2.5-mini-ROCmFP4-GGUF # Run inference directly in the terminal: llama cli -hf julianmb/Nex-N2.5-mini-ROCmFP4-GGUF
Install from WinGet (Windows)
winget install llama.cpp # Start a local OpenAI-compatible server with a web UI: llama serve -hf julianmb/Nex-N2.5-mini-ROCmFP4-GGUF # Run inference directly in the terminal: llama cli -hf julianmb/Nex-N2.5-mini-ROCmFP4-GGUF
Use pre-built binary
# Download pre-built binary from: # https://github.com/ggerganov/llama.cpp/releases # Start a local OpenAI-compatible server with a web UI: ./llama-server -hf julianmb/Nex-N2.5-mini-ROCmFP4-GGUF # Run inference directly in the terminal: ./llama-cli -hf julianmb/Nex-N2.5-mini-ROCmFP4-GGUF
Build from source code
git clone https://github.com/ggerganov/llama.cpp.git cd llama.cpp cmake -B build cmake --build build -j --target llama-server llama-cli # Start a local OpenAI-compatible server with a web UI: ./build/bin/llama-server -hf julianmb/Nex-N2.5-mini-ROCmFP4-GGUF # Run inference directly in the terminal: ./build/bin/llama-cli -hf julianmb/Nex-N2.5-mini-ROCmFP4-GGUF
Use Docker
docker model run hf.co/julianmb/Nex-N2.5-mini-ROCmFP4-GGUF
- LM Studio
- Jan
- Ollama
How to use julianmb/Nex-N2.5-mini-ROCmFP4-GGUF with Ollama:
ollama run hf.co/julianmb/Nex-N2.5-mini-ROCmFP4-GGUF
- Unsloth Desktop
- Pi
How to use julianmb/Nex-N2.5-mini-ROCmFP4-GGUF with Pi:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf julianmb/Nex-N2.5-mini-ROCmFP4-GGUF
Configure the model in Pi
# Install Pi: npm install -g @earendil-works/pi-coding-agent # Add to ~/.pi/agent/models.json: { "providers": { "llama-cpp": { "baseUrl": "http://localhost:8080/v1", "api": "openai-completions", "apiKey": "none", "models": [ { "id": "julianmb/Nex-N2.5-mini-ROCmFP4-GGUF" } ] } } }Run Pi
# Start Pi in your project directory: pi
- Docker Model Runner
How to use julianmb/Nex-N2.5-mini-ROCmFP4-GGUF with Docker Model Runner:
docker model run hf.co/julianmb/Nex-N2.5-mini-ROCmFP4-GGUF
- Lemonade
How to use julianmb/Nex-N2.5-mini-ROCmFP4-GGUF with Lemonade:
Pull the model
# Download Lemonade from https://lemonade-server.ai/ lemonade pull julianmb/Nex-N2.5-mini-ROCmFP4-GGUF
Run and chat with the model
lemonade run user.Nex-N2.5-mini-ROCmFP4-GGUF-{{QUANT_TAG}}List all available models
lemonade list
- Hermes Agent
How to use julianmb/Nex-N2.5-mini-ROCmFP4-GGUF with Hermes Agent:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf julianmb/Nex-N2.5-mini-ROCmFP4-GGUF
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 julianmb/Nex-N2.5-mini-ROCmFP4-GGUF
Run Hermes
hermes
- Atomic Chat
- OpenClaw
How to use julianmb/Nex-N2.5-mini-ROCmFP4-GGUF with OpenClaw:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf julianmb/Nex-N2.5-mini-ROCmFP4-GGUF
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 "julianmb/Nex-N2.5-mini-ROCmFP4-GGUF" \ --custom-provider-id llama-cpp \ --custom-compatibility openai \ --custom-text-input \ --accept-risk \ --skip-health
Run OpenClaw
openclaw agent --local --agent main --message "Hello from Hugging Face"
Nex-N2.5-mini ROCmFP4
Custom Engine Required โ Incompatible with Stock Ollama / Vanilla llama.cpp This repository provides custom ROCmFP4 quantized weights (
Q4_0_ROCMFP4_STRIX_LEANusing custom GGML tensor types 100 & 101, file type 106) engineered specifically for AMD Strix Halo (gfx1151) and RDNA 3.5 architectures.
- Engine Requirement: Requires ROCmFPX or halofpx to run.
- Stock Ollama / llama.cpp Incompatibility: Stock
llama.cppand vanillaollamawill fail to load these weights (unknown tensor type 101and unsupportedqwen35moeGated DeltaNet architecture).- Standard Quants: If you need standard vanilla GGUF quants (Q4_K_M, etc.) for general llama.cpp usage, please use abenzerps/Nex-N2.5-mini-GGUF.
ROCmFP4 (Q4_0_ROCMFP4_STRIX_LEAN) quantization of Nex-N2.5-mini for AMD Strix Halo (gfx1151) and RDNA 3.5 GPUs, engineered using ROCmFPX.
Nex-N2.5-mini is an open-source agentic multimodal MoE model built by Nex AGI on the Qwen3.5-35B-A3B architecture, unifying requirement understanding, code generation, tool use, and environment execution through an Agentic Thinking adaptive reasoning loop.
Quantization Details
| Property | Value |
|---|---|
| Quant format | Q4_0_ROCMFP4_STRIX_LEAN (ROCmFP4) |
| Bits per weight | 4.29 BPW |
| File size | 17.32 GiB |
| SHA256 | 406c96dbab1994998137e5cf093c4094f9af8be5c1e3268ed6284670bca2d06e |
| Vision projector | mmproj-Nex-N2.5-mini.gguf (0.84 GiB) |
| Projector SHA256 | 4734f7323dfc0e8dcd5c7c408991aad438021aeab761d223aec0b38a4457ca83 |
| Architecture | qwen35moe (30ร Gated DeltaNet + 10ร Full Attention) |
| Parameters | 34.66B total / ~3.0B active per token |
| Max Context | 262,144 tokens (256K) |
| Source | abenzerps/Nex-N2.5-mini-GGUF Q4_K_M (allow-requantize) |
| Notes | Expert weights in q4_0_rocmfp4_fast, attention K/V in q4_0_rocmfp4, FP32 router/norms, Q5_K embeddings |
Measured Performance (AMD Ryzen AI Max+ 395, Radeon 8060S, Mesa RADV Wave64)
| Configuration | Prefill (pp512) |
Decode (tg128) |
Size | Speedup vs Q4_K_M |
|---|---|---|---|---|
| ROCmFP4 Vulkan0 (RADV) | 642.37 tok/s | ๐ฅ 76.92 tok/s | 17.32 GiB | +5.7% decode, โ12.1% size |
| ROCmFP4 ROCm0 (HIP) | 1,028.18 tok/s | 68.62 tok/s | 17.32 GiB | +13.6% decode, โ12.1% size |
| Q4_K_M Baseline (Vulkan0) | 1,083.91 tok/s | 72.76 tok/s | 19.71 GiB | Baseline |
| Q4_K_M Baseline (ROCm0) | 907.44 tok/s | 60.39 tok/s | 19.71 GiB | Baseline |
โก Why ROCmFP4 is Faster Than Standard Quants (Q4_K_M) on AMD Strix Halo
Standard GGUF integer quants (such as Q4_K_M) were designed primarily for CPU cache architectures and CUDA tensor cores. On AMD Strix Halo APUs (gfx1151) and RDNA 3.5 architectures, ROCmFP4_STRIX_LEAN achieves both higher decode throughput and smaller footprint for four key architectural reasons:
1. Direct Cooperative Matrix Mapping (KHR_coopmat / Mesa RADV Wave64)
- The Problem with Q4_K: Standard
Q4_Kblocks are non-uniform: 256-element blocks split into 8 sub-blocks of 32 elements with dual 6-bit scales and 6-bit offsets. Compute units must pay a complex, multi-pass unpack and ALU dequantization penalty in vector registers before data can feed matrix multiply units. - The ROCmFP4 Solution:
ROCmFP4formats (Q4_0_ROCMFP4andQ4_0_ROCMFP4_FAST) use single-scale uniform FP4 quantization per 32 elements. In shader registers, unpacking is reduced to single-cycle bit shifts and direct table lookups. This dramatically reduces register pressure and instruction count, allowing Mesa RADV's Wave64 cooperative matrix pipelines to run near theoretical hardware saturation.
2. Lower Memory Bus Pressure Across Unified Memory (UMA)
- Strix Halo shares ~200 GB/s of LPDDR5X unified memory bandwidth between 16 Zen 5 CPU cores and the 40 CU GPU.
- In Mixture-of-Experts (MoE) generation, token throughput is strictly gated by how fast active expert weights stream across the memory bus on every step.
- At 17.32 GiB (4.29 BPW) vs Q4_K_M's 19.71 GiB (4.88 BPW), ROCmFP4 transfers 12.1% fewer bytes across UMA per forward pass. That bandwidth saving directly translates into sustained token throughput (76.92 tok/s vs 72.76 tok/s on Vulkan; 68.62 vs 60.39 tok/s on ROCm).
3. MoE-Aware "Strix Lean" Mixed-Precision Policy
Rather than naively crushing all tensors to 4-bit, the STRIX_LEAN recipe selectively preserves precision where accuracy matters most:
- Router Gate Logits (
ffn_gate_inp.weight) & LayerNorms: Maintained in uncompressed FP32. Expert routing decisions and token assignments remain bit-exact, preventing expert collapse. - Token Embeddings (
token_embd.weight): Quantized in higher-precision Q5_K to maintain vocabulary entropy and prevent prompt degradation. - Attention Projections: Preserved in dual-scale
q4_0_rocmfp4for clean KV heads. - Bulk Expert Feed-Forward Networks: Packed into high-speed
q4_0_rocmfp4_fastfor maximum memory streaming bandwidth.
4. Synergy with Hybrid Gated DeltaNet Linear Attention
- Nex N2.5 Mini uses 30 linear-attention layers (DeltaNet / recurrent SSM state) interleaved with 10 full-attention layers.
- Recurrent state updates require continuous cache access; smaller weight memory footprint prevents cache eviction and memory bus contention between linear-attention states and MoE routing.
Serving
HaloFPX (Recommended โ Text + Vision)
halofpx pull downloads and verifies both the ROCmFP4 weights and vision projector:
halofpx pull nex-n2.5-mini
halofpx serve -m nex-n2.5-mini
Direct llama-server (ROCmFPX fork)
llama-server -m Nex-N2.5-mini-ROCmFP4-STRIX_LEAN.gguf --mmproj mmproj-Nex-N2.5-mini.gguf -ngl 99 -c 32768 -fa on --host 0.0.0.0 --port 8080
Note on Reasoning Mode: To enable thinking mode over the
/v1/chat/completionsAPI, request with--reasoning-format deepseekor passchat_template_kwargs: {"enable_thinking": true}. To disable thinking for lower latency, passchat_template_kwargs: {"enable_thinking": false}.
- Downloads last month
- 566
We're not able to determine the quantization variants.
Model tree for julianmb/Nex-N2.5-mini-ROCmFP4-GGUF
Base model
nex-agi/Nex-N2.5-mini