Instructions to use gwyntel/PII-Redact-Name-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 gwyntel/PII-Redact-Name-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 gwyntel/PII-Redact-Name-GGUF:Q4_K_M # Run inference directly in the terminal: llama cli -hf gwyntel/PII-Redact-Name-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 gwyntel/PII-Redact-Name-GGUF:Q4_K_M # Run inference directly in the terminal: llama cli -hf gwyntel/PII-Redact-Name-GGUF:Q4_K_M
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 gwyntel/PII-Redact-Name-GGUF:Q4_K_M # Run inference directly in the terminal: ./build/bin/llama cli -hf gwyntel/PII-Redact-Name-GGUF:Q4_K_M
Use Docker
docker model run hf.co/gwyntel/PII-Redact-Name-GGUF:Q4_K_M
- Llama new
- LM Studio
- Jan
- Ollama
How to use gwyntel/PII-Redact-Name-GGUF with Ollama:
ollama run hf.co/gwyntel/PII-Redact-Name-GGUF:Q4_K_M
- Unsloth Desktop
- Pi
How to use gwyntel/PII-Redact-Name-GGUF with Pi:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf gwyntel/PII-Redact-Name-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": "gwyntel/PII-Redact-Name-GGUF:Q4_K_M" } ] } } }Run Pi
# Start Pi in your project directory: pi
- Docker Model Runner
How to use gwyntel/PII-Redact-Name-GGUF with Docker Model Runner:
docker model run hf.co/gwyntel/PII-Redact-Name-GGUF:Q4_K_M
- Lemonade
How to use gwyntel/PII-Redact-Name-GGUF with Lemonade:
Pull the model
# Download Lemonade from https://lemonade-server.ai/ lemonade pull gwyntel/PII-Redact-Name-GGUF:Q4_K_M
Run and chat with the model
lemonade run user.PII-Redact-Name-GGUF-Q4_K_M
List all available models
lemonade list
- Hermes Agent
How to use gwyntel/PII-Redact-Name-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 gwyntel/PII-Redact-Name-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 gwyntel/PII-Redact-Name-GGUF:Q4_K_M
Run Hermes
hermes
- Atomic Chat
- OpenClaw
How to use gwyntel/PII-Redact-Name-GGUF with OpenClaw:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf gwyntel/PII-Redact-Name-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 "gwyntel/PII-Redact-Name-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"
PII-Redact-Name-GGUF
GGUF quantization(s) of OpenPipe/PII-Redact-Name for CPU/GPU inference via llama.cpp.
This is the same model family as the MLX 4-bit quant, so both appear together as quantizations of the base model.
Quantization details
Model type: llama
Format: GGUF
Quants available: Q4_K_M, Q8_0
Q4_K_M β 807 MB β ~26.5 t/s on 16 CPU cores β best size/speed tradeoff
Q8_0 β 1.32 GB β ~16.4 t/s on 16 CPU cores β near-lossless
F16 β 2.48 GB β same precision as the base, therefore not published
Behavioural check: across a tagged sample the F16, Q8_0 and Q4_K_M outputs were byte-for-byte identical, so 4-bit loses nothing observable on short documents.
Why these exist
The full-precision model is served through transformers, which processes one
request at a time. GGUF served by llama-server uses continuous batching
(--parallel), so many documents decode concurrently and share each weight
read. A 1B model on a GPU is memory-bandwidth bound, so ~4x smaller 4-bit
weights convert directly into throughput.
Usage
llama-server -m Pii-Redact-Name-Q4_K_M.gguf --port 8080 --parallel 8 -c 65536
curl -s http://127.0.0.1:8080/v1/chat/completions \
-H 'Content-Type: application/json' \
-d '{"messages":[{"role":"user","content":"My phone is 555-867-5309"}]}'
This model is a redactor: it echoes the document back with PII wrapped in
XML-ish tags, e.g. <PII:phone_number>555-867-5309</PII:phone_number>. The tag
vocabulary includes person_name, phone_number, email, street_address,
banking_number, medical_condition, organization_name, password,
secure_credential and other_id.
Set the token budget to cover the input. The model early-stops rather than filling a budget, so a generous cap costs nothing at runtime -- but a cap that is too SMALL truncates the echoed document mid-tag and silently corrupts the output. A 1,820-token input emits ~2,712 tokens, so a 1024 cap loses most of the document without erroring.
One server process serves exactly one GGUF. To serve this model together with
the General variant behind a single OpenAI-compatible endpoint, run two servers
on separate ports and route by the model field.
Related
- MLX 4-bit quant: PII-Redact-Name-oQ4
- General variant: PII-Redact-General-GGUF
- Downloads last month
- 196
4-bit
8-bit
Model tree for gwyntel/PII-Redact-Name-GGUF
Base model
OpenPipe/PII-Redact-Name