Text Generation
GGUF
edge0
Mixture of Experts
edge-inference
latent-moe
4-bit precision
agent
coding
cuda
conversational
Instructions to use Edge0/Edge0-145B-NVFP4 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 Edge0/Edge0-145B-NVFP4 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 Edge0/Edge0-145B-NVFP4:BF16 # Run inference directly in the terminal: llama cli -hf Edge0/Edge0-145B-NVFP4:BF16
Install from WinGet (Windows)
winget install llama.cpp # Start a local OpenAI-compatible server with a web UI: llama serve -hf Edge0/Edge0-145B-NVFP4:BF16 # Run inference directly in the terminal: llama cli -hf Edge0/Edge0-145B-NVFP4:BF16
Build from source code
git clone https://github.com/ggml-org/llama.cpp.git cd llama.cpp cmake -B build cmake --build build -j --target llama-app # Start a local OpenAI-compatible server with a web UI: ./build/bin/llama serve -hf Edge0/Edge0-145B-NVFP4:BF16 # Run inference directly in the terminal: ./build/bin/llama cli -hf Edge0/Edge0-145B-NVFP4:BF16
Use Docker
docker model run hf.co/Edge0/Edge0-145B-NVFP4:BF16
- Llama new
- LM Studio
- Jan
- vLLM
How to use Edge0/Edge0-145B-NVFP4 with vLLM:
Install from pip and serve model
# Install vLLM from pip: pip install vllm # Start the vLLM server: vllm serve "Edge0/Edge0-145B-NVFP4" # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:8000/v1/chat/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "Edge0/Edge0-145B-NVFP4", "messages": [ { "role": "user", "content": "What is the capital of France?" } ] }'Use Docker
docker model run hf.co/Edge0/Edge0-145B-NVFP4:BF16
- Ollama
How to use Edge0/Edge0-145B-NVFP4 with Ollama:
ollama run hf.co/Edge0/Edge0-145B-NVFP4:BF16
- Unsloth Desktop
- Pi
How to use Edge0/Edge0-145B-NVFP4 with Pi:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf Edge0/Edge0-145B-NVFP4:BF16
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:9931/v1", "api": "openai-completions", "apiKey": "none", "models": [ { "id": "Edge0/Edge0-145B-NVFP4:BF16" } ] } } }Run Pi
# Start Pi in your project directory: pi
- Docker Model Runner
How to use Edge0/Edge0-145B-NVFP4 with Docker Model Runner:
docker model run hf.co/Edge0/Edge0-145B-NVFP4:BF16
- Lemonade
How to use Edge0/Edge0-145B-NVFP4 with Lemonade:
Pull the model
# Download Lemonade from https://lemonade-server.ai/ lemonade pull Edge0/Edge0-145B-NVFP4:BF16
Run and chat with the model
lemonade run user.Edge0-145B-NVFP4-BF16
List all available models
lemonade list
- Hermes Agent
How to use Edge0/Edge0-145B-NVFP4 with Hermes Agent:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf Edge0/Edge0-145B-NVFP4:BF16
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:9931/v1 hermes config set model.default Edge0/Edge0-145B-NVFP4:BF16
Run Hermes
hermes
- Atomic Chat
- OpenClaw
How to use Edge0/Edge0-145B-NVFP4 with OpenClaw:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf Edge0/Edge0-145B-NVFP4:BF16
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:9931/v1 \ --custom-model-id "Edge0/Edge0-145B-NVFP4:BF16" \ --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"
docs: how the 16 GiB VRAM budget is enforced; add --spec to the VRAM table
Browse files
README.md
CHANGED
|
@@ -307,8 +307,7 @@ pipeline_tag: text-generation
|
|
| 307 |
</details>
|
| 308 |
<details open>
|
| 309 |
<summary><b>Measurement conditions</b> · constrained budget and memory residency</summary>
|
| 310 |
-
<p><code>16 GiB VRAM + 20 GiB RAM</code> rows are the RTX 5090 D 24 GB
|
| 311 |
-
20 GiB system-RAM budget — not a different card. With residency on, the same card holds <strong>Q3_K</strong> (40.81 GiB of weights)
|
| 312 |
as 23.14 GiB VRAM + 31.28 GiB RAM, and <strong>NVFP4</strong> (47.79 GiB) as 23.25 GiB VRAM + 38.27 GiB RAM — disjoint expert sets,
|
| 313 |
nothing counted twice.</p>
|
| 314 |
<p class="section-nav">See <a href="#usage-help">Usage & troubleshooting</a> for memory-saving options.</p>
|
|
@@ -479,6 +478,7 @@ and `edge0-infer` read, so a change there applies to every launch.
|
|
| 479 |
| `--kv-resident N` | Keep N KV cells per QSA layer in VRAM and stream the K/V from pinned host RAM, which frees VRAM for experts. | `0` (all in VRAM) |
|
| 480 |
| `--mtp-q4 all\|proj\|head` | 4-bit copies of the draft layer's projections and/or head, about 0.3–0.5 GiB less VRAM. | off |
|
| 481 |
| `--prefill CHUNK` | Prompt chunk size; bigger chunks need bigger device buffers. `auto` uses the largest chunk whose buffers the expert cache can lend. | `auto` |
|
|
|
|
| 482 |
|
| 483 |
### Host RAM
|
| 484 |
|
|
|
|
| 307 |
</details>
|
| 308 |
<details open>
|
| 309 |
<summary><b>Measurement conditions</b> · constrained budget and memory residency</summary>
|
| 310 |
+
<p>The <code>16 GiB VRAM + 20 GiB RAM</code> rows are the same RTX 5090 D 24 GB, not a different card. VRAM is capped with <code>--vram-reserve-mib 8192</code>: 24,455 − 8,192 = 16,263 MiB left to the engine, and the expert cache is sized from what remains. System RAM is capped by a cgroup (<code>MemoryMax=20G</code>, no swap). A cgroup cannot cap VRAM; only the reserve can. With residency on, the same card holds <strong>Q3_K</strong> (40.81 GiB of weights)
|
|
|
|
| 311 |
as 23.14 GiB VRAM + 31.28 GiB RAM, and <strong>NVFP4</strong> (47.79 GiB) as 23.25 GiB VRAM + 38.27 GiB RAM — disjoint expert sets,
|
| 312 |
nothing counted twice.</p>
|
| 313 |
<p class="section-nav">See <a href="#usage-help">Usage & troubleshooting</a> for memory-saving options.</p>
|
|
|
|
| 478 |
| `--kv-resident N` | Keep N KV cells per QSA layer in VRAM and stream the K/V from pinned host RAM, which frees VRAM for experts. | `0` (all in VRAM) |
|
| 479 |
| `--mtp-q4 all\|proj\|head` | 4-bit copies of the draft layer's projections and/or head, about 0.3–0.5 GiB less VRAM. | off |
|
| 480 |
| `--prefill CHUNK` | Prompt chunk size; bigger chunks need bigger device buffers. `auto` uses the largest chunk whose buffers the expert cache can lend. | `auto` |
|
| 481 |
+
| `--spec N` | The MTP drafter's verify window: how many tokens it proposes per check. A bigger window needs bigger verify buffers (about 180 MiB at 4) and pays off when every window has a fixed per-layer cost. The shipped packs use `4`; the macOS setup picks `2`, or `3` when the experts stream from SSD. Without an MTP layer there is no speculation. | `4` |
|
| 482 |
|
| 483 |
### Host RAM
|
| 484 |
|