LFM2.5 2.6B fable5 coding agent needs about 4.2 GB of memory at Q4_K_M (a 1.7 GB file) with an 8K context window, so it fits on a 6 GB GPU. This repository has 3 quants, from 1.7 GB (Q4_K_M) to 5.4 GB (F16). Longer context needs more: at 32K tokens the KV cache alone adds about 8.1 GB.
LFM2.5 2.6B fable5 coding agent – a fine‑tuned LFM2 model for coding and reasoning
LFM2.5 2.6B fable5 coding agent is a full‑parameter supervised fine‑tune of LFM2.5 on fable‑5‑premium. It supports multi‑turn assistant behavior, code generation, and structured tool‑call generation. The model is released under apache‑2.0 and is intended for research and evaluation.
Good at
- coding
- reasoning
- tool‑call generation
Limits
- no vision support
- not production‑ready
- requires 8‑k context for estimates
Best for
- research on coding agents
- evaluating multi‑turn assistant behavior
- tool‑call pattern analysis
Who it’s for. Researchers and developers exploring advanced coding assistants and agent‑style interactions. The model is suitable for experimentation but not for production deployment.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q4_K_M | 1.7 GB | 4.2 GB | Fits | Get file → | |
| Q8_0 | 2.9 GB | 5.4 GB | Fits | Get file → | |
| F16 | 5.4 GB | 7.9 GB | Tight | Get file → |
For 8‑GB VRAM use Q4_K_M (1.67 GB, ~4.2 GB memory at 8‑k context). For 16‑GB VRAM use Q8_0 (2.87 GB, ~5.4 GB memory). For 24‑GB VRAM use F16 (5.4 GB, ~7.9 GB memory). Memory estimates are approximate.
What GPU do you need for LFM2.5 2.6B fable5 coding agent?
These figures add the file size, an fp16 KV cache at an 8K context window (worked out from this model’s own header) and about 0.5 GB for the runtime. They are estimates, so leave a little headroom, and expect to use less context or a smaller quant if you are right at the limit.
- 4 GB VRAM: no quant fits at an 8K context.
- 6 GB VRAM: the best quant that fits is Q8_0 (2.9 GB file, about 5.4 GB in use).
- 8 GB VRAM: the best quant that fits is F16 (5.4 GB file, about 7.9 GB in use).
Which LFM2.5 2.6B fable5 coding agent quant should you choose?
Q4_K_M is the usual starting point for LFM2.5 2.6B fable5 coding agent: it balances file size and quality well. Here it is a 1.7 GB file.
The Q8_0 file is 2.9 GB, about 1.7 times the size of Q4_K_M. It keeps the weights closer to the original, which only matters if you have the memory to spare.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Frequently asked questions about LFM2.5 2.6B fable5 coding agent
How much VRAM does LFM2.5 2.6B fable5 coding agent need?
About 4.2 GB at Q4_K_M with an 8K context window. That is the 1.7 GB file, plus the KV cache and roughly 0.5 GB of runtime overhead. Smaller quants need less and longer context needs more.
Can I run LFM2.5 2.6B fable5 coding agent on an 8 GB GPU?
Yes, with F16: the 5.4 GB file needs about 7.9 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of LFM2.5 2.6B fable5 coding agent GGUF?
It depends on the quant: Q4_K_M is 1.7 GB, Q8_0 is 2.9 GB, F16 is 5.4 GB.
What context length does LFM2.5 2.6B fable5 coding agent support?
The GGUF header lists a trained context length of 131,072 tokens (128K). The KV cache grows with the context you use: about 2.0 GB at 8K and 8.1 GB at 32K.
Where can I download LFM2.5 2.6B fable5 coding agent GGUF?
The files are on Hugging Face in the AyoubChLin/LFM2.5-2.6B-fable5-coding-agent-GGUF repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does LFM2.5 2.6B fable5 coding agent use?
Hugging Face lists the license as apache-2.0. Licenses can differ between the quantized files and the original model, so check the repository and the base model before commercial use.
Can I run this model on 8 GB VRAM?
Yes, the Q4_K_M quantized file is 1.67 GB and requires about 4.2 GB of VRAM at 8‑k context.
Does this model support vision?
No, the model has no vision capability.
Is it safe for production use?
No, it is intended for research and evaluation only and is not production‑ready.