Flint APEX needs about 21.0 GB of memory at its main file (a 19.7 GB file) with an 8K context window, so it fits on a 24 GB GPU. This repository has 3 quants, from 14.9 GB to 23.7 GB. Longer context needs more: at 32K tokens the KV cache alone adds about 3.3 GB.
Flint APEX – a 39.8B MoE coding agent in GGUF format
Flint APEX is a 39.8B‑parameter mixture‑of‑experts model designed for coding tasks. It supports reasoning and multi‑turn tool use. The model is released under Apache‑2.0 and is available as GGUF quantizations.
Good at
- coding assistance
- bug fixing
- feature implementation
Limits
- no vision support
- requires large VRAM
- no transformer API
Best for
- automated code review
- test generation
- debugging
Who it’s for. Developers and researchers needing a large‑scale coding agent. The model is suitable for local deployment with sufficient GPU memory.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| — | 14.9 GB | 16.2 GB | Too big | Get file → | |
| — | 19.7 GB | 21.0 GB | Too big | Get file → | |
| — | 23.7 GB | 25.0 GB | Too big | Get file → |
The 5‑bpw quant file is 14.87 GB and needs about 16.2 GB VRAM at 8 k context. The 4‑bpw quant is 19.66 GB requiring ~21 GB VRAM. The 3‑bpw quant is 23.69 GB and needs ~25 GB VRAM. Choose the smallest quant that fits your GPU budget.
What GPU do you need for Flint APEX?
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: no quant fits at an 8K context.
- 8 GB VRAM: no quant fits at an 8K context.
- 12 GB VRAM: no quant fits at an 8K context.
- 16 GB VRAM: no quant fits at an 8K context.
- 24 GB VRAM: the best quant that fits is the main file (19.7 GB file, about 21.0 GB in use).
- 32 GB VRAM: the best quant that fits is the main file (23.7 GB file, about 25.0 GB in use).
Which Flint APEX quant should you choose?
If memory is tight, the smallest file is the first one in the table at 14.9 GB, with the quality trade-offs that come with fewer bits.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about Flint APEX
How much VRAM does Flint APEX need?
About 21.0 GB at its main file with an 8K context window. That is the 19.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 Flint APEX on an 8 GB GPU?
Not at an 8K context. The smallest file needs about 16.2 GB, so you would need a larger GPU or CPU offloading.
What is the file size of Flint APEX GGUF?
It depends on the quant: file is 14.9 GB, file is 19.7 GB, file is 23.7 GB.
What context length does Flint APEX support?
The GGUF header lists a trained context length of 262,144 tokens (256K). The KV cache grows with the context you use: about 0.8 GB at 8K and 3.3 GB at 32K.
Where can I download Flint APEX GGUF?
The files are on Hugging Face in the Myric/Flint-APEX-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 Flint APEX 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 Flint APEX on 8 GB VRAM?
No. The smallest quant requires 16.2 GB VRAM at 8 k context, so 8 GB is insufficient.
Does Flint APEX support image input?
No. The model only supports text input and output.
What license applies to Flint APEX?
Apache‑2.0. The model and its quantizations are released under this license.