Instructions to use bartowski/Cloudflare_clef-GGUF with libraries, inference providers, notebooks, and local apps. Follow these links to get started.

Notebooks
Google Colab
Kaggle
Local Apps Settings

How to use bartowski/Cloudflare_clef-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 bartowski/Cloudflare_clef-GGUF:Q4_K_M
# Run inference directly in the terminal:
llama cli -hf bartowski/Cloudflare_clef-GGUF:Q4_K_M

Install from WinGet (Windows)

winget install llama.cpp
# Start a local OpenAI-compatible server with a web UI:
llama serve -hf bartowski/Cloudflare_clef-GGUF:Q4_K_M
# Run inference directly in the terminal:
llama cli -hf bartowski/Cloudflare_clef-GGUF:Q4_K_M

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 bartowski/Cloudflare_clef-GGUF:Q4_K_M
# Run inference directly in the terminal:
./llama-cli -hf bartowski/Cloudflare_clef-GGUF:Q4_K_M

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 bartowski/Cloudflare_clef-GGUF:Q4_K_M
# Run inference directly in the terminal:
./build/bin/llama-cli -hf bartowski/Cloudflare_clef-GGUF:Q4_K_M

Use Docker

docker model run hf.co/bartowski/Cloudflare_clef-GGUF:Q4_K_M

LM Studio
Jan

vLLM

How to use bartowski/Cloudflare_clef-GGUF with vLLM:

Install from pip and serve model

# Install vLLM from pip:
pip install vllm
# Start the vLLM server:
vllm serve "bartowski/Cloudflare_clef-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": "bartowski/Cloudflare_clef-GGUF",
		"messages": [
			{
				"role": "user",
				"content": [
					{
						"type": "text",
						"text": "Describe this image in one sentence."
					},
					{
						"type": "image_url",
						"image_url": {
							"url": "https://cdn.britannica.com/61/93061-050-99147DCE/Statue-of-Liberty-Island-New-York-Bay.jpg"
						}
					}
				]
			}
		]
	}'

Use Docker

docker model run hf.co/bartowski/Cloudflare_clef-GGUF:Q4_K_M

Ollama
How to use bartowski/Cloudflare_clef-GGUF with Ollama:
```
ollama run hf.co/bartowski/Cloudflare_clef-GGUF:Q4_K_M
```
Unsloth Desktop

How to use bartowski/Cloudflare_clef-GGUF with Pi:

Start the llama.cpp server

# Install llama.cpp:
brew install llama.cpp
# Start a local OpenAI-compatible server:
llama serve -hf bartowski/Cloudflare_clef-GGUF:Q4_K_M

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": "bartowski/Cloudflare_clef-GGUF:Q4_K_M"
        }
      ]
    }
  }
}

Run Pi

# Start Pi in your project directory:
pi

Docker Model Runner
How to use bartowski/Cloudflare_clef-GGUF with Docker Model Runner:
```
docker model run hf.co/bartowski/Cloudflare_clef-GGUF:Q4_K_M
```

Lemonade

How to use bartowski/Cloudflare_clef-GGUF with Lemonade:

Pull the model

# Download Lemonade from https://lemonade-server.ai/
lemonade pull bartowski/Cloudflare_clef-GGUF:Q4_K_M

Run and chat with the model

lemonade run user.Cloudflare_clef-GGUF-Q4_K_M

List all available models

lemonade list

Hermes Agent

How to use bartowski/Cloudflare_clef-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 bartowski/Cloudflare_clef-GGUF:Q4_K_M

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 bartowski/Cloudflare_clef-GGUF:Q4_K_M

Run Hermes

hermes

Atomic Chat

OpenClaw

How to use bartowski/Cloudflare_clef-GGUF with OpenClaw:

Start the llama.cpp server

# Install llama.cpp:
brew install llama.cpp
# Start a local OpenAI-compatible server:
llama serve -hf bartowski/Cloudflare_clef-GGUF:Q4_K_M

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 "bartowski/Cloudflare_clef-GGUF:Q4_K_M" \
  --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"

Llamacpp Static Quantizations of clef by Cloudflare

Using llama.cpp release b11430 for quantization.

Original model: https://huggingface.co/Cloudflare/clef

Model details:

Parameter count: 27B (source checkpoint)
Input support: text, image (with mmproj file) - details
Decision model: yes (clef) - details
Speculative decoding: no
imatrix: no (not possible for a decision model) - details

How to run

Decision model

This is a decision model, not a text generator: it reads a state (text or JSON) together with a schema of typed questions and hands back a probability for every allowed option of every question, all in a single forward pass. It never generates text, so there's no chat, no completion endpoint, and no prompt format to worry about.

llama.cpp serves it through llama-server's /v1/systemone endpoint (the TypeSafe System One API). The full request and response shapes are in the llama-server README, but here's what a request looks like:

curl http://127.0.0.1:8080/v1/systemone \
    -H "Content-Type: application/json" \
    -d '{
        "state": "Customer message: I was charged twice for my order last week and nobody has replied.",
        "questions": {
            "route": {
                "type": "choice",
                "instructions": "Which team should handle this?",
                "criteria": {"billing": null, "shipping": null, "technical": null}
            },
            "angry": {
                "type": "noul",
                "instructions": "Is the customer angry?"
            },
            "urgency": {
                "type": "score",
                "instructions": "How urgent is this?",
                "criteria": ["can wait", "this week", "today", "right now"]
            }
        }
    }'

Decision head. The decision head - the tensors that turn the backbone's final hidden states into actual answers - is stored at Q8_0 in every quantized file here. It's a small part of the model, it's the part doing the answering, and none of the usual measurements work on this model (see below), so there's no way to check what quantizing it would cost. Keeping it at Q8_0 is the safe call.

No imatrix. There's no imatrix for this model, and there can't be one: llama.cpp's imatrix tool works by watching the token probabilities a model produces as it generates text, and a decision model doesn't produce any, so there's nothing to calibrate against. Every quantized file here is therefore a static quant, made without an imatrix. The files below 4 bits per weight (Q3_K_L, Q3_K_M, IQ3_M, Q3_K_S and Q2_K) will lose noticeably more quality than an imatrix quant of the same size would, so if you can, stick to Q4_K_M or larger. The formats that cannot be made at all without an imatrix (IQ1, IQ2, IQ3_XS, IQ3_XXS and Q2_K_S) are not offered. Perplexity and KL divergence can't be measured either, for the same reason, so the descriptions in the file table below are the usual guidance for each format rather than measurements of this particular model.

Don't know which to choose? Grab Q4_K_M (17.65GB) - usually a good mix of size and performance. Download instructions available here

Available files:

Filename	Quant type	File Size	Split	Description
Cloudflare_clef-bf16.gguf	bf16	54.06GB	true	Full BF16 weights.
Cloudflare_clef-Q8_0.gguf	Q8_0	28.80GB	false	Extremely high quality, generally unneeded but max available quant.
Cloudflare_clef-Q6_K_L.gguf	Q6_K_L	23.96GB	false	Uses Q8_0 for embed and output weights. Very high quality, near perfect, recommended.
Cloudflare_clef-Q6_K.gguf	Q6_K	23.34GB	false	Very high quality, near perfect, recommended.
Cloudflare_clef-Q5_K_M.gguf	Q5_K_M	20.64GB	false	High quality, recommended.
Cloudflare_clef-Q5_K_S.gguf	Q5_K_S	19.57GB	false	High quality, recommended.
Cloudflare_clef-Q4_K_L.gguf	Q4_K_L	18.60GB	false	Uses Q8_0 for embed and output weights. Good quality, recommended.
Cloudflare_clef-Q4_1.gguf	Q4_1	17.71GB	false	Legacy format, similar performance to Q4_K_S but with improved tokens/watt on Apple silicon.
Cloudflare_clef-Q4_K_M.gguf	Q4_K_M	17.65GB	false	Good quality, default size for most use cases, recommended.
Cloudflare_clef-Q4_K_S.gguf	Q4_K_S	16.59GB	false	Slightly lower quality with more space savings, recommended.
Cloudflare_clef-IQ4_NL.gguf	IQ4_NL	16.30GB	false	Similar to IQ4_XS, but slightly larger.
Cloudflare_clef-Q4_0.gguf	Q4_0	16.19GB	false	Legacy format, kept for compatibility with older tools.
Cloudflare_clef-IQ4_XS.gguf	IQ4_XS	15.56GB	false	Decent quality, smaller than Q4_K_S with similar performance, recommended.
Cloudflare_clef-Q3_K_L.gguf	Q3_K_L	15.15GB	false	Lower quality but usable, good for low RAM availability. Made without an imatrix: expect a larger quality loss than usual at this size.
Cloudflare_clef-Q3_K_M.gguf	Q3_K_M	14.48GB	false	Low quality. Made without an imatrix: expect a larger quality loss than usual at this size.
Cloudflare_clef-IQ3_M.gguf	IQ3_M	13.78GB	false	Medium-low quality, new method with decent performance comparable to Q3_K_M. Made without an imatrix: expect a larger quality loss than usual at this size.
Cloudflare_clef-Q3_K_S.gguf	Q3_K_S	13.59GB	false	Low quality, not recommended. Made without an imatrix: expect a larger quality loss than usual at this size.
Cloudflare_clef-Q2_K.gguf	Q2_K	11.71GB	false	Very low quality but surprisingly usable. Made without an imatrix: expect a larger quality loss than usual at this size.

Download a specific file:

hf download bartowski/Cloudflare_clef-GGUF --include "Cloudflare_clef-Q4_K_M.gguf" --local-dir ./

Downloading using the Hugging Face CLI

Click to view download instructions

First, make sure you have the Hugging Face CLI installed:

pip install -U "huggingface_hub[cli]"

Download a specific file:

hf download bartowski/Cloudflare_clef-GGUF --include "Cloudflare_clef-Q4_K_M.gguf" --local-dir ./

The files marked true in the Split column above are stored as multiple parts in a folder. To download all the parts to a local folder, run:

hf download bartowski/Cloudflare_clef-GGUF --include "Cloudflare_clef-bf16/*" --local-dir ./

You can either specify a new local-dir (Cloudflare_clef-bf16) or download them all in place (./)

How to run

These quants run with llama.cpp - installable in one line via llama.app:

curl -LsSf https://llama.app/install.sh | sh
llama-server -hf bartowski/Cloudflare_clef-GGUF:Q4_K_M

llama-server exposes this model on the /v1/systemone endpoint only - there's no chat web UI for a decision model. See Decision model above for an example request.

These quants were made with llama.cpp release b11430 - if this model's architecture is newly supported, you'll need that release or newer to run them.

Multimodal

This model supports image input. Alongside the quants, this repo includes the multimodal projector files mmproj-Cloudflare_clef-bf16.gguf and mmproj-Cloudflare_clef-f16.gguf, which pair with any quant above.

llama.cpp downloads the mmproj automatically when using -hf as shown above; if you're loading files manually, pass it with --mmproj.

Embed/output weights

Some of these quants (Q3_K_XL, Q4_K_L etc) are the standard quantization method with the embeddings and output weights quantized to Q8_0 instead of what they would normally default to.

ARM/AVX information

llama.cpp automatically "repacks" weights into an interleaved layout at load time for faster inference on ARM and AVX machines - details in this PR. This once required downloading special Q4_0_4_4/4_8/8_8 files; those are long gone. Online repacking now covers Q4_0, IQ4_NL, and most K-quants, so no special quant choice is needed for CPU inference.

Which file should I choose?

Click here for details

An older (early 2024) but still useful write-up with charts comparing quant performances is provided by Artefact2 here

The first thing to figure out is how big a model you can run. To do this, you'll need to figure out how much RAM and/or VRAM you have.

If you want your model running as FAST as possible, you'll want to fit the whole thing on your GPU's VRAM. Aim for a quant with a file size 1-2GB smaller than your GPU's total VRAM.

If you want the absolute maximum quality, add both your system RAM and your GPU's VRAM together, then similarly grab a quant with a file size 1-2GB Smaller than that total.

Hugging Face can also do this math for you: add your hardware in your Local Apps settings and the model page will show which files fit.

Next, you'll need to decide if you want to use an 'I-quant' or a 'K-quant'.

If you don't want to think too much, grab one of the K-quants. These are in format 'QX_K_X', like Q5_K_M.

If you want to get more into the weeds, you can check out this extremely useful feature chart:

llama.cpp feature matrix

But basically, if you're aiming for below Q4, and you're running cuBLAS (Nvidia) or rocBLAS (AMD), you should look towards the I-quants. These are in format IQX_X, like IQ3_M. These are newer and offer better performance for their size.

These I-quants can also be used on CPU, but will be slower than their K-quant equivalent, so speed vs performance is a tradeoff you'll have to decide.