For privacy reasons a browser tells us at most "≥ 8 GB RAM, 8 cores" - same reading whether you have 8 GB or 128 GB. It has no idea how much RAM is free right now, which apps are open, or whether you have a GPU.
It reads your exact RAM, GPU model and VRAM, free memory right now, and picks the sharpest quant that still fits. Every model page lights up precisely for your rig.
The app is a full local runtime - no API keys, no subscription, everything runs on your machine. Click any model on this site and start a conversation in seconds.
Get the free app →This is a rough estimate. Install the free app - we'll show exact numbers.
Reading real hardware from your app right now. Numbers below are exact.
Below is the per-quantization compatibility for this model.
curl -H "Authorization: Bearer $ABL_KEY" \
"https://abliteration.org/api/v1/models/akaistormherald%2FToxicMist-v0.2-7B-DPO-LORA" No specific extraction method could be identified for this model. The producer either did not document it or used a proprietary pipeline.
What is a refusal direction? →Corpora the author lists in the model card. Datasets tracked in our /datasets catalog carry a category badge linking to the workflow stage. Others open on Hugging Face.
This model's place in the market. Above: what it was derived from. Below: the tree of everything derived from it.
| adapter_model.safetensors | 640 MB | 61100489 | download |
| tokenizer.json | 1.71 MB | 43e6daf9 | download |
| tokenizer.model | 482 KB | dadfd56d | download |
| .gitattributes | 1.48 KB | a6344aac | download |
| tokenizer_config.json | 1.45 KB | 61d908be | download |
| adapter_config.json | 659 B | 4b5164fd | download |
| special_tokens_map.json | 624 B | c32a4966 | download |
| README.md | 444 B | 9889a525 | download |
language:
Mistral7b + SFT + 4bit DPO training with unalignment/toxic-dpo-v0.2 == ToxicMist? ☣🌫
(Just the lora)
The author's README evolved over time. Click a version to see its content at that point.
Every model page has an "Open in Abliteration" button that hands the model directly to the first-party desktop client, at the quantization your rig can actually run. No API keys, no subscription, no prompt leakage.