Instructions to use satgeze/Gemma4-12B-Uncensored-HauhauCS-1M-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 satgeze/Gemma4-12B-Uncensored-HauhauCS-1M-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 satgeze/Gemma4-12B-Uncensored-HauhauCS-1M-GGUF
# Run inference directly in the terminal:
llama cli -hf satgeze/Gemma4-12B-Uncensored-HauhauCS-1M-GGUF

Install from WinGet (Windows)

winget install llama.cpp
# Start a local OpenAI-compatible server with a web UI:
llama serve -hf satgeze/Gemma4-12B-Uncensored-HauhauCS-1M-GGUF
# Run inference directly in the terminal:
llama cli -hf satgeze/Gemma4-12B-Uncensored-HauhauCS-1M-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 satgeze/Gemma4-12B-Uncensored-HauhauCS-1M-GGUF
# Run inference directly in the terminal:
./llama-cli -hf satgeze/Gemma4-12B-Uncensored-HauhauCS-1M-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 satgeze/Gemma4-12B-Uncensored-HauhauCS-1M-GGUF
# Run inference directly in the terminal:
./build/bin/llama-cli -hf satgeze/Gemma4-12B-Uncensored-HauhauCS-1M-GGUF

Use Docker

docker model run hf.co/satgeze/Gemma4-12B-Uncensored-HauhauCS-1M-GGUF

LM Studio
Jan

vLLM

How to use satgeze/Gemma4-12B-Uncensored-HauhauCS-1M-GGUF with vLLM:

Install from pip and serve model

# Install vLLM from pip:
pip install vllm
# Start the vLLM server:
vllm serve "satgeze/Gemma4-12B-Uncensored-HauhauCS-1M-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": "satgeze/Gemma4-12B-Uncensored-HauhauCS-1M-GGUF",
		"messages": [
			{
				"role": "user",
				"content": "What is the capital of France?"
			}
		]
	}'

Use Docker

docker model run hf.co/satgeze/Gemma4-12B-Uncensored-HauhauCS-1M-GGUF

Ollama
How to use satgeze/Gemma4-12B-Uncensored-HauhauCS-1M-GGUF with Ollama:
```
ollama run hf.co/satgeze/Gemma4-12B-Uncensored-HauhauCS-1M-GGUF
```

Unsloth Studio

How to use satgeze/Gemma4-12B-Uncensored-HauhauCS-1M-GGUF with Unsloth Studio:

Install Unsloth Studio (macOS, Linux, WSL)

curl -fsSL https://unsloth.ai/install.sh | sh
# Run unsloth studio
unsloth studio -H 0.0.0.0 -p 8888
# Then open http://localhost:8888 in your browser
# Search for satgeze/Gemma4-12B-Uncensored-HauhauCS-1M-GGUF to start chatting

Install Unsloth Studio (Windows)

irm https://unsloth.ai/install.ps1 | iex
# Run unsloth studio
unsloth studio -H 0.0.0.0 -p 8888
# Then open http://localhost:8888 in your browser
# Search for satgeze/Gemma4-12B-Uncensored-HauhauCS-1M-GGUF to start chatting

Using HuggingFace Spaces for Unsloth

# No setup required
# Open https://huggingface.co/spaces/unsloth/studio in your browser
# Search for satgeze/Gemma4-12B-Uncensored-HauhauCS-1M-GGUF to start chatting

How to use satgeze/Gemma4-12B-Uncensored-HauhauCS-1M-GGUF with Pi:

Start the llama.cpp server

# Install llama.cpp:
brew install llama.cpp
# Start a local OpenAI-compatible server:
llama serve -hf satgeze/Gemma4-12B-Uncensored-HauhauCS-1M-GGUF

Configure the model in Pi

# Install Pi:
npm install -g @mariozechner/pi-coding-agent
# Add to ~/.pi/agent/models.json:
{
  "providers": {
    "llama-cpp": {
      "baseUrl": "http://localhost:8080/v1",
      "api": "openai-completions",
      "apiKey": "none",
      "models": [
        {
          "id": "satgeze/Gemma4-12B-Uncensored-HauhauCS-1M-GGUF"
        }
      ]
    }
  }
}

Run Pi

# Start Pi in your project directory:
pi

Docker Model Runner
How to use satgeze/Gemma4-12B-Uncensored-HauhauCS-1M-GGUF with Docker Model Runner:
```
docker model run hf.co/satgeze/Gemma4-12B-Uncensored-HauhauCS-1M-GGUF
```

Lemonade

How to use satgeze/Gemma4-12B-Uncensored-HauhauCS-1M-GGUF with Lemonade:

Pull the model

# Download Lemonade from https://lemonade-server.ai/
lemonade pull satgeze/Gemma4-12B-Uncensored-HauhauCS-1M-GGUF

Run and chat with the model

lemonade run user.Gemma4-12B-Uncensored-HauhauCS-1M-GGUF-{{QUANT_TAG}}

List all available models

lemonade list

Hermes Agent

How to use satgeze/Gemma4-12B-Uncensored-HauhauCS-1M-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 satgeze/Gemma4-12B-Uncensored-HauhauCS-1M-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 satgeze/Gemma4-12B-Uncensored-HauhauCS-1M-GGUF

Run Hermes

hermes

Atomic Chat

OpenClaw

How to use satgeze/Gemma4-12B-Uncensored-HauhauCS-1M-GGUF with OpenClaw:

Start the llama.cpp server

# Install llama.cpp:
brew install llama.cpp
# Start a local OpenAI-compatible server:
llama serve -hf satgeze/Gemma4-12B-Uncensored-HauhauCS-1M-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 "satgeze/Gemma4-12B-Uncensored-HauhauCS-1M-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"

Gemma4-12B Uncensored: 1M Context + MTP + Vision

HauhauCS/Gemma4-12B-QAT-Uncensored-HauhauCS-Balanced (12B dense, Google QAT checkpoint) with a 1,048,576-token context baked in (4x the native 262,144), shipping with its MTP speculative-decoding draft head and vision tower. All numbers below were measured on these exact files.

Capability	Status
1M context	Certified: 10/10 at every rung from 64K to 1M, f16 KV, on a single RTX 5090
MTP speculative decoding	144.9 to 218.4 tok/s (+51%), acceptance 0.723 (measured on this trunk, RTX 5090)
Vision	Verified July 6, 2026: reads image text and identifies objects
Uncensored	HauhauCS Balanced abliteration; trunk weights bit-identical to the source release

Needle-in-a-haystack

The first Gemma 4 we know of certified needle-perfect at 1,048,576 tokens. Thanks to Gemma's 5:1 sliding-window attention the KV cache stays small enough that the entire 1M certification ran on a 32 GB RTX 5090 at f16 KV. One cell (786K, depth 15 percent) missed on the first seed and passed 10/10 on a second seed; both runs are in results.jsonl.

MTP speculative decoding

The draft head predicts ahead and the trunk verifies every token, so output is identical to standard decoding, only faster. Measured speedup on this uncensored trunk beats the ~35 percent claimed upstream.

Multi-hop retrieval: chains hold at 1,048,576 tokens

Beyond single-needle NIAH, we run a harder "hop" tier: chained lookups where each answer keys the next, at true 1M context. Thinking OFF, 5 chains per rung:

Rung	Chains found
131,072	5/5
524,288	5/5
1,048,576	5/5

Perfect chain retrieval at a million tokens. (The battery also probes a multi-step variable-tracking tier; our scorer for that tier is under review before we publish it, so those numbers are held back rather than reported unverified.) There is also a stretch rung at 1,572,864 tokens (1.5M, the extended-context sibling of this model) scoring 6/10 on single-needle NIAH: past the 1M bake it degrades, exactly as honestly expected.

RULER at long context (NVIDIA's benchmark, their scorer)

NIAH proves retrieval; RULER is the harder, industry-standard suite (multi-key retrieval, variable tracking, aggregation). We ran five RULER tasks at 131K on this exact GGUF, 25 samples per task, greedy-free vendor sampling (temp 1.0, top_p 0.95, top_k 64, seed 42), scored end to end by NVIDIA's own evaluate.py (RULER commit 38da79d). The bridge script and full reproduction recipe are published in aviary-1m/tools/ruler.

All columns thinking OFF (see the headline below for why). 25 samples per task, NVIDIA's own scorer.

Task	131K	262K	524K	~1M*
niah_multivalue	88.0	83.0	71.0	57.0
niah_multiquery	100.0	100.0	100.0	99.0
variable tracking (vt)	95.2	91.2	88.8	68.8
common words extraction (cwe)	80.0	46.8	13.6	5.2
frequent words extraction (fwe)	96.0	86.7	80.0	97.3
Average	91.8	81.5	70.7	65.5

* The 1M rung uses a nominal length of 917,504 with the full 1,048,576 context served. Reason, honestly: RULER sizes prompts with a reference tokenizer that undercounts this model's real tokenization by about 6 percent. Our first attempt at nominal 1,048,576 overflowed the context window and scored all-null on three tasks; that was a harness artifact, not a model failure, so we re-ran at a nominal length whose real token count (976K) fits the served window. Zero nulls across all 125 samples in the run reported above.

The ladder climbs honestly to the top rung. Pure retrieval barely moves even at a million tokens: multiquery holds 99 and frequent-words extraction actually posts its second-best score of the whole ladder at 97.3. The cost of distance concentrates exactly where the rest of the ladder predicted: aggregation over the entire window (cwe, 5.2) and dense multi-value retrieval (57.0). Variable tracking finally bends at 68.8. This is what a real 1M model looks like: near-perfect needlework at full depth, honest degradation where the task requires holding the whole window at once. (For the record, thinking-ON at 131K averaged 45.9, half the thinking-OFF score.)

The honest headline: thinking mode halves this model's RULER score at 131K. The failure mode is specific and reproducible: on aggregation tasks (cwe/fwe) and some hard retrieval samples, the model reasons in circles and exhausts any generation budget (tested to 12K tokens) without ever emitting an answer. At temperature 0 the same samples loop deterministically; vendor sampling reduces but does not eliminate it. Those runs score 0 by RULER's rules and we report them as such, nulls and all.

Practical guidance: for long-context retrieval and aggregation work with this model, run thinking OFF. 91.8 average at 131K with zero unanswered samples is the model's real capability; thinking mode is the liability, not the context window. Raw prediction files, both conditions, are in the repo history for anyone who wants to re-score.

Files

File	Size	Role
`gemma4-12b-uncensored-1M-Q4.gguf`	7.4 GB	Trunk, 1M baked, QAT 4-bit
`mtp-gemma-12b.gguf`	254 MB	MTP draft head, pair with `-md`
`mmproj-gemma12b-hauhau.gguf`	175 MB	Vision tower, pair with `--mmproj`
`niah_heatmap.png`, `mtp_speedup.png`, `results.jsonl`	small	Verification evidence

Every file, every mirror

Nothing was discontinued: every quant is one click away. Hugging Face carries the curated picks, ModelScope always carries everything, and Ollama serves ready-to-run tags.

On Ollama every tag ships with the vision tower bundled and the 1M rope metadata baked in.

File	Size	Hugging Face	ModelScope	Ollama
`gemma4-12b-uncensored-1M-Q4.gguf`	7.4 GB	download	download	`ollama run satgeze/gemma4-12b-uncensored-1m`
`mmproj-gemma12b-hauhau.gguf`	175 MB	download	download	bundled in every tag
`mtp-gemma-12b.gguf`	254 MB	download	download	-

Run it

llama.cpp, everything on:

llama-server -m gemma4-12b-uncensored-1M-Q4.gguf \
  -c 1048576 -np 1 --jinja \
  -md mtp-gemma-12b.gguf --spec-type draft-mtp --spec-draft-n-max 3 \
  --mmproj mmproj-gemma12b-hauhau.gguf

Ollama (1M and vision work; Ollama has no speculative decoding yet, so the MTP head adds no speed there):

FROM ./gemma4-12b-uncensored-1M-Q4.gguf
RENDERER gemma4
PARSER gemma4
PARAMETER num_ctx 262144

The RENDERER and PARSER lines avoid imported-GGUF template bugs under tool-heavy use. Raise num_ctx as memory allows.

How to actually use a 1M-context model

Long context is a capability, not a magic mode. Habits that measurably help (from our own RULER and hop testing on this model):

Re-state your standing instructions near the end of long prompts. Recency beats depth.
Prefer one big reference dump over a long accumulated chat. Fresh session per task, context used as a library.
After any compaction or summarization, repeat your active rules yourself.
Run thinking OFF for retrieval and aggregation work. The RULER table above is unambiguous: thinking mode halves this model's score at long range.
Expect the extremes to cost time: prefill at 500K+ is slow on any hardware. Budget for it.

How this was built

YaRN rope-scaling metadata (factor 4.0 over native 262,144) baked into the GGUF header with gguf-py; weights are bit-identical to the HauhauCS release, no fine-tuning. Gemma 4's dual-rope design takes YaRN on its global-attention layers. Certification harness: 10 needles per rung at depths 5 to 95 percent, temperature 0, seeded prompts, f16 KV only. Method and tooling: github.com/satindergrewal/aviary-1m.

For base capability benchmarks see Google's official Gemma 4 cards; uncensoring quality versus the official trunk has not been independently benchmarked here.

Credits

Base model and QAT: Google (Gemma license; its terms flow down to these files). Uncensoring and packaging: HauhauCS. MTP head: Unsloth (via the HauhauCS repo). 1M YaRN extension, benchmarking, and certification: SatGeze.

Sister repos: 12B | 26B-A4B | 31B | Qwen3.6-35B

Mirrors: Hugging Face | ModelScope