Instructions to use prism-ml/Ternary-Bonsai-2-27B-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 prism-ml/Ternary-Bonsai-2-27B-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 prism-ml/Ternary-Bonsai-2-27B-gguf:F16 # Run inference directly in the terminal: llama cli -hf prism-ml/Ternary-Bonsai-2-27B-gguf:F16
Install from WinGet (Windows)
winget install llama.cpp # Start a local OpenAI-compatible server with a web UI: llama serve -hf prism-ml/Ternary-Bonsai-2-27B-gguf:F16 # Run inference directly in the terminal: llama cli -hf prism-ml/Ternary-Bonsai-2-27B-gguf:F16
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 prism-ml/Ternary-Bonsai-2-27B-gguf:F16 # Run inference directly in the terminal: ./llama-cli -hf prism-ml/Ternary-Bonsai-2-27B-gguf:F16
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 prism-ml/Ternary-Bonsai-2-27B-gguf:F16 # Run inference directly in the terminal: ./build/bin/llama-cli -hf prism-ml/Ternary-Bonsai-2-27B-gguf:F16
Use Docker
docker model run hf.co/prism-ml/Ternary-Bonsai-2-27B-gguf:F16
- LM Studio
- Jan
- vLLM
How to use prism-ml/Ternary-Bonsai-2-27B-gguf with vLLM:
Install from pip and serve model
# Install vLLM from pip: pip install vllm # Start the vLLM server: vllm serve "prism-ml/Ternary-Bonsai-2-27B-gguf" # Call the server using curl (OpenAI-compatible API): curl -X POST "http://localhost:8000/v1/chat/completions" \ -H "Content-Type: application/json" \ --data '{ "model": "prism-ml/Ternary-Bonsai-2-27B-gguf", "messages": [ { "role": "user", "content": "What is the capital of France?" } ] }'Use Docker
docker model run hf.co/prism-ml/Ternary-Bonsai-2-27B-gguf:F16
- Ollama
How to use prism-ml/Ternary-Bonsai-2-27B-gguf with Ollama:
ollama run hf.co/prism-ml/Ternary-Bonsai-2-27B-gguf:F16
- Unsloth Desktop
- Pi
How to use prism-ml/Ternary-Bonsai-2-27B-gguf with Pi:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf prism-ml/Ternary-Bonsai-2-27B-gguf:F16
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": "prism-ml/Ternary-Bonsai-2-27B-gguf:F16" } ] } } }Run Pi
# Start Pi in your project directory: pi
- Docker Model Runner
How to use prism-ml/Ternary-Bonsai-2-27B-gguf with Docker Model Runner:
docker model run hf.co/prism-ml/Ternary-Bonsai-2-27B-gguf:F16
- Lemonade
How to use prism-ml/Ternary-Bonsai-2-27B-gguf with Lemonade:
Pull the model
# Download Lemonade from https://lemonade-server.ai/ lemonade pull prism-ml/Ternary-Bonsai-2-27B-gguf:F16
Run and chat with the model
lemonade run user.Ternary-Bonsai-2-27B-gguf-F16
List all available models
lemonade list
- Hermes Agent
How to use prism-ml/Ternary-Bonsai-2-27B-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 prism-ml/Ternary-Bonsai-2-27B-gguf:F16
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 prism-ml/Ternary-Bonsai-2-27B-gguf:F16
Run Hermes
hermes
- Atomic Chat
- OpenClaw
How to use prism-ml/Ternary-Bonsai-2-27B-gguf with OpenClaw:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf prism-ml/Ternary-Bonsai-2-27B-gguf:F16
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 "prism-ml/Ternary-Bonsai-2-27B-gguf:F16" \ --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"
Surprisingly good PTQ1_0 quantization β and ~39.5 tok/s on an RTX 4070
I have to give some credit here because I went into this test rather skeptical.
I'm generally not a fan of aggressively quantizing large models just to make them fit. In my experience there is usually a point where the quality loss becomes obvious, even if benchmarks still look surprisingly good. Personally, I'm much more interested in models that are trained with ternary/very-low-bit weights from the beginning β BitNet-style approaches and similar architectures β rather than taking a conventional model afterwards and squeezing it as hard as possible.
So I honestly didn't expect much from a 27B model compressed into a 5.95 GB PTQ1_0 GGUF.
But after actually using Ternary Bonsai 2, I have to say: this is a seriously impressive quantization.
I'm running the PTQ1_0 version fully on an RTX 4070 12 GB. In a real conversation at roughly 11.6K context, generation speed is extremely stable at around 39.4β39.5 tokens/sec. More importantly, so far I don't see the kind of obvious degradation I normally associate with extremely aggressive quantization.
The model still reasons coherently, follows the conversation over multiple turns and can correct its own mistakes. One particularly interesting test was when it initially confused ternary weights with "3-bit" weights. After I pasted the relevant part of the model card, it correctly recognized the mistake, explained the distinction between ternary {-1, 0, +1} weights and 3-bit quantization, and reasoned through the approximate bits-per-weight calculation. The resulting English response was surprisingly strong and coherent.
One caveat: the German is bad. Sometimes hilariously bad. There are malformed sentences, invented/incorrect word constructions and phrasing that no native German speaker would use.
However, I explicitly do not blame PTQ1_0 for this.
I've tested Qwen models in substantially less aggressive / higher-quality quantizations before and have repeatedly seen the same problem. Qwen can produce German that looks superficially fluent but becomes strangely constructed, semantically awkward or simply broken once you actually read it as a native speaker. The behavior I'm seeing in Bonsai 2 is very familiar to me from the underlying Qwen family.
In English, the difference is striking. The model suddenly sounds much more coherent and natural, and its reasoning is considerably more convincing.
So while I still prefer the idea of training genuinely ternary models from scratch rather than forcing conventional models down to extremely low bitrates afterwards, PTQ1_0 has changed my opinion somewhat about how far post-training ternary quantization can be pushed.
I expected obvious damage at this size.
So far, I'm not seeing it.
5.95 GB for a 27B model, ~39.5 tok/s on a normal RTX 4070, with reasoning quality that still appears remarkably intact is genuinely impressive work.
I'm going to continue testing it, especially tool calling / agentic behavior and vision. Those will probably tell me much more than another benchmark table will. :)