The exact checkpoint
`sophosympatheia/Magistry-24B-v1.1` is the creator’s v1.1 model card. The card calls it a Royal Merge, lists 24B and Apache 2.0, and recommends testing the file rather than assuming it behaves like another model.
English
MAGISTRY 24B × SILLYTAVERN
Verify the name before you tune
Magistry-24B-v1.1 is a real community merge on Hugging Face. It is not a Mistral product and it is not the same file as Mistral’s official Magistral Small 24B. Confirm the exact repository, then connect the checkpoint to SillyTavern one layer at a time.
START WITH THE MODEL ID
24B is a size, not a model name
Write down the full repository slug before changing settings. This page resolves the common name mix-up first, then separates the merge, its base, and its quantized files.
Magistry is not Magistral
Mistral’s official Magistral Small is a separate 24B open-weight model. Magistry-24B-v1.1 is a community DELLA merge, not an official Mistral release. Keep the two IDs separate.
What v1.1 is built from
The card names `Darkhn/Magistral-2509-24B-Text-Only` as its base and lists Maginum-Cydoms, Magistaroth and an abliterated Devstral Small 2 merge input.
Quant files are distributions
GGUF, EXL3 and MLX repositories are quantized or converted distributions. Check the quant publisher’s file, context limit and license note instead of treating it as a new Magistry version.
A CLEAN SETUP PATH
Choose the serving layer before SillyTavern
SillyTavern is the chat frontend. The model still needs a local server or a provider endpoint. Pick the path that matches your hardware and privacy needs.
Local GPU or Mac
The source card does not publish one universal VRAM number for every quant. Estimate from the actual BF16, GGUF, EXL3 or MLX file, then leave headroom for context and the backend.
llama.cpp, KoboldCpp or MLX
Choose a backend that supports the file you downloaded. SillyTavern’s docs describe KoboldCpp at `http://localhost:5001`; MLX files need an MLX-compatible runtime. Do not mix quant formats.
Provider or OpenAI-compatible API
If a provider exposes the checkpoint, copy its exact model slug and endpoint. A provider label such as “Magistry 24B” is not enough to choose a SillyTavern template.
Connect SillyTavern
Use Chat Completion when your backend accepts role messages. Use Text Completion only when your backend and model card specify a text format. Configure the endpoint, API key, model name and context deliberately.
ROLEPLAY TUNING
Template before sampler
A wrong template can look like a weak model. Fix formatting and context first, then tune generation with a short repeatable test.
Use the backend’s Magistry format
Let the tokenizer or serving stack apply the model chat template where possible. If `<s>`, role markers or tool tokens appear in the reply, stop and correct formatting.
Keep the card compact
Separate fixed character facts, current goals and temporary scene state. Remove duplicate lore and instructions that tell the model to write both sides of the conversation.
Start with the card baseline
Conservative: temperature 0.7, Min-P 0.05, Top-N σ 0.75, DRY multiplier 0.8 and DRY base 1.8. Balanced: temperature 1.0, Min-P 0.05, Adaptive-P target 0.6 and decay 0.9. Treat these as starting points.
Treat stop strings as model-specific
A stop string from Llama or ChatML can truncate Magistry output or leak markers. Copy the exact stop advice for the checkpoint and test a two-turn chat.
Community reports mention speaking for the user, odd narration, null responses, repetition and slow quantizations. These are useful symptoms, not proof that every Magistry 24B file behaves the same way.
SYMPTOM → CHECK → FIX
Find the layer that is actually broken
Change one variable, save the result, and repeat the same short prompt. The fastest fix is usually a name, endpoint or template mismatch.
| Symptom | Check | Next move |
|---|---|---|
| Null or empty response | Endpoint status, model slug, context template and stop strings. | Send a tiny one-turn prompt, then switch to the exact Magistry template supplied by the backend. |
| Role markers appear in text | Who applies the chat template: SillyTavern, server or tokenizer? | Keep one template owner. Remove duplicated formatting and inspect the raw prompt if the backend exposes it. |
| The model writes for the user | Character card instructions and example dialogue. | State user agency plainly, delete conflicting examples, and test with a short choice prompt. |
| Repetition or looping | Duplicate lore, context size, sampler and quant file. | Reduce prompt noise, return to the card baseline, then change one sampler value. Try another quant only after the baseline is stable. |
| Very slow or falling tokens/sec | Quant type, GPU offload, RAM/VRAM pressure and context length. | Compare the file’s memory requirement with your hardware. Partial CPU offload can be much slower than full GPU placement. |
| Wrong model behavior | Base versus instruct, 3.1 versus 3.2, and official versus community repository. | Copy the full ID into your notes and reapply that repository’s own card and settings. |
A RESEARCH WORKSPACE, NOT A RUNNER
Keep the model card beside the chat
Tabbit does not replace SillyTavern or run this local checkpoint. Its current public model directory does not list Magistry. Use it to collect model cards, compare quant files, keep prompt notes and read community reports without losing the source tabs.
- 1
Open the official card and the quant page
Keep the exact ID, hardware note and template instructions visible. Add a community fine-tune card only after you have separated it from the official checkpoint.
- 2
Reference tabs and files with @
Use @ to bring a page, screenshot or local note into the prompt. Ask for a checklist that preserves model IDs and flags unsupported assumptions.
- 3
Compare what is actually listed
Tabbit can compare the model options available in its own picker and summarize differences between sources. The picker changes over time, so verify the live list after installation.
CHOOSE THE RIGHT SURFACE
Local RP control or browser context?
These tools solve different problems. Keep SillyTavern for cards, samplers and your chosen backend. Use Tabbit when the hard part is gathering information across pages and files.
| SillyTavern + backend | Tabbit | |
|---|---|---|
| Run Magistry 24B locally | Yes, with a compatible server | Not promised |
| Character cards and samplers | Detailed controls | Reference notes and cards |
| Official and community sources | Paste or switch apps | @ tabs, files and pages |
| Model comparison | Change endpoint or preset | Compare models shown in its picker |
| Hardware diagnostics | VRAM, offload and tokens/sec | Organize the evidence |
FAQ
Magistry 24B and SillyTavern questions
What does Magistry 24B mean?+
It usually refers to a 24-billion-parameter Magistry-24B checkpoint, but search results also use it for 3.1, 3.2, quantized files and community RP merges. Use the full repository ID.
Which official model should I use?+
The current official page for this guide is `sophosympatheia/Magistry-24B-v1.1`. It is a minor update to 3.1. Choose the exact release your server or provider offers.
Can I run the official model on one GPU?+
The 3.1 announcement says it can run on a single RTX 4090 or a 32GB Mac, while the 3.2 card notes about 55GB of GPU RAM for BF16/FP16. Quantized files have different requirements, so check the actual file.
Should I choose Chat Completion or Text Completion?+
Follow the backend and model card. SillyTavern documents that the choice controls how messages become a prompt, not whether the model is local or cloud-hosted.
Why does my Magistry reply repeat or speak for me?+
Check the model ID, chat template, duplicate card text and sampler in that order. Community reports describe these symptoms, but a mismatch in the frontend can produce the same result.
Does Tabbit run Magistry 24B?+
Do not assume it. Magistry was not visible in Tabbit’s public model directory when this page was checked. Tabbit is offered here for source collection, comparison and browser-based research.
Keep the checkpoint, template and evidence together
Start with the exact Magistry ID, connect the serving layer, then tune SillyTavern with a small test. Use Tabbit when your setup research is spread across model cards, quant pages and community threads.
Available for macOS and Windows. Tabbit’s model list can change.