Instructions to use EryriLabs/Glimmer-Sentry-30B-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 EryriLabs/Glimmer-Sentry-30B-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 EryriLabs/Glimmer-Sentry-30B-GGUF:Q4_K_M # Run inference directly in the terminal: llama cli -hf EryriLabs/Glimmer-Sentry-30B-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 EryriLabs/Glimmer-Sentry-30B-GGUF:Q4_K_M # Run inference directly in the terminal: llama cli -hf EryriLabs/Glimmer-Sentry-30B-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 EryriLabs/Glimmer-Sentry-30B-GGUF:Q4_K_M # Run inference directly in the terminal: ./llama-cli -hf EryriLabs/Glimmer-Sentry-30B-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 EryriLabs/Glimmer-Sentry-30B-GGUF:Q4_K_M # Run inference directly in the terminal: ./build/bin/llama-cli -hf EryriLabs/Glimmer-Sentry-30B-GGUF:Q4_K_M
Use Docker
docker model run hf.co/EryriLabs/Glimmer-Sentry-30B-GGUF:Q4_K_M
- LM Studio
- Jan
- vLLM
How to use EryriLabs/Glimmer-Sentry-30B-GGUF with vLLM:
Install from pip and serve model
# Install vLLM from pip: pip install vllm # Start the vLLM server: vllm serve "EryriLabs/Glimmer-Sentry-30B-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": "EryriLabs/Glimmer-Sentry-30B-GGUF", "messages": [ { "role": "user", "content": "What is the capital of France?" } ] }'Use Docker
docker model run hf.co/EryriLabs/Glimmer-Sentry-30B-GGUF:Q4_K_M
- Ollama
How to use EryriLabs/Glimmer-Sentry-30B-GGUF with Ollama:
ollama run hf.co/EryriLabs/Glimmer-Sentry-30B-GGUF:Q4_K_M
- Unsloth Studio
How to use EryriLabs/Glimmer-Sentry-30B-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 EryriLabs/Glimmer-Sentry-30B-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 EryriLabs/Glimmer-Sentry-30B-GGUF to start chatting
Using HuggingFace Spaces for Unsloth
# No setup required # Open https://huggingface.co/spaces/unsloth/studio in your browser # Search for EryriLabs/Glimmer-Sentry-30B-GGUF to start chatting
- Pi
How to use EryriLabs/Glimmer-Sentry-30B-GGUF with Pi:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf EryriLabs/Glimmer-Sentry-30B-GGUF:Q4_K_M
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": "EryriLabs/Glimmer-Sentry-30B-GGUF:Q4_K_M" } ] } } }Run Pi
# Start Pi in your project directory: pi
- OpenClaw new
How to use EryriLabs/Glimmer-Sentry-30B-GGUF with OpenClaw:
Start the llama.cpp server
# Install llama.cpp: brew install llama.cpp # Start a local OpenAI-compatible server: llama serve -hf EryriLabs/Glimmer-Sentry-30B-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 "EryriLabs/Glimmer-Sentry-30B-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"
- Docker Model Runner
How to use EryriLabs/Glimmer-Sentry-30B-GGUF with Docker Model Runner:
docker model run hf.co/EryriLabs/Glimmer-Sentry-30B-GGUF:Q4_K_M
- Lemonade
How to use EryriLabs/Glimmer-Sentry-30B-GGUF with Lemonade:
Pull the model
# Download Lemonade from https://lemonade-server.ai/ lemonade pull EryriLabs/Glimmer-Sentry-30B-GGUF:Q4_K_M
Run and chat with the model
lemonade run user.Glimmer-Sentry-30B-GGUF-Q4_K_M
List all available models
lemonade list
- Hermes Agent
How to use EryriLabs/Glimmer-Sentry-30B-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 EryriLabs/Glimmer-Sentry-30B-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 EryriLabs/Glimmer-Sentry-30B-GGUF:Q4_K_M
Run Hermes
hermes
- Atomic Chat
Glimmer-Sentry-30B GGUF
Quantised builds of Glimmer-Sentry-30B, a local detection-engineering copilot that writes, explains, tunes and translates detection rules (Sigma to KQL and SPL, YARA, Wazuh). Full eval numbers, training details, data licences and the responsible-use notes are on the main model card; this repo is just the llama.cpp builds.
| Quant | Size | Fits | Validation result |
|---|---|---|---|
| IQ2_M | 9.2GB | 12GB GPU, low-RAM machines | Experimental. Coherent, well-formed KQL, clean termination — but see the low-bit caveat below |
| Q3_K_M | 13.7GB | 16GB GPU | Structurally correct holdout translation; one field-name substitution (same caveat) |
| Q4_K_M | 16.9GB | 24GB GPU, 32GB Mac | Recommended default. Byte-exact holdout Sigma→KQL vs sigma-cli |
| Q5_K_M | 19.8GB | 24GB GPU (tight), 32GB Mac | Byte-exact holdout Sigma→KQL vs sigma-cli |
| Q6_K | 22.9GB | 32GB+ GPU/Mac | Byte-exact holdout Sigma→KQL vs sigma-cli |
| Q8_0 | 29.6GB | 48GB GPU, 64GB Mac, CPU with patience | Byte-exact holdout Sigma→KQL vs sigma-cli |
| imatrix | 12.8MB | n/a | The importance matrix used for IQ2_M — published so you can make your own quants |
Every quant ran the same test before upload: a held-out Sigma→KQL prompt through the real chat template, checked for termination, special-token leakage, and fidelity against the official sigma-cli converter output. Q4_K_M through Q8_0 all came back byte-exact, which honestly surprised me — quantisation down to 4-bit cost nothing measurable on that test.
The low-bit caveat: below Q4, a specific failure pattern appears — the query structure stays perfect but a single field name drifts to something plausible and wrong (both Q3_K_M and IQ2_M did it, same pattern). A query that references a field that doesn't exist fails loudly in Sentinel, so you'll catch it — but it means Q3_K_M and especially IQ2_M need their output checked field-by-field, not just eyeballed. If your hardware runs Q4_K_M, run Q4_K_M.
Every quant is made directly from the F16 GGUF, never requantised from another quant. The IQ2_M used an importance matrix computed over a 50/50 mix of general text and real detection-rule content (Sigma, KQL, SPL, YARA from the training pools) — the corpus recipe is in GGUF_NOTES.md.
Running it
Built against llama.cpp master, commit e79e4bf (2026-08-13) — you need a build from that date or newer, since support for this architecture is recent.
llama-cli -m Glimmer-Sentry-30B-Q4_K_M.gguf --jinja -c 8192 --temp 1.0 --top-p 0.95 --top-k 64 \
-p "Convert this Sigma rule to Microsoft 365 Defender Advanced Hunting KQL: ..."
--jinja matters — the chat template is bespoke (<|start|>/<|message|>/<|eot|> turns with a reasoning channel) and the template baked into the GGUF handles it. Sampling defaults above are the base model's recommended settings. For YARA authoring give it at least 1536 tokens of headroom (-n 1536 or more); rules are long and a cut-off rule won't compile — this exact effect shows up in the eval numbers on the main card.
Text only. The base model has a vision tower, but it's frozen, untouched by the fine-tune, and not included in these files.
A note on how these were made
If you've tried to convert this base model yourself you'll have hit a wall: its tokenizer_config.json targets a transformers version that isn't on PyPI yet, so AutoTokenizer refuses to load it and llama.cpp's converter dies at the vocab step. The fix here was to load the tokenizer through the one code path that has always worked (the same loader our training and eval pipeline used), have it re-serialise itself in the current transformers schema, and then machine-verify the re-export against the original — identical vocab, identical IDs for all 2,048 added tokens, identical encodings across a battery of awkward test strings, byte-identical chat-template output. Nine checks, all passed, before conversion was attempted. No config fields were hand-edited or guessed. The conversion script and the verification results are in the main repo if you want to reproduce it.
Same Apache 2.0 licence as the main model. Same rule applies too: generated rules get reviewed and tested by a human before they go anywhere near production.
- Downloads last month
- -
Model tree for EryriLabs/Glimmer-Sentry-30B-GGUF
Base model
meta-models/Muse-Glimmer-30B