Flint NVFP4 GGUF
NVFP4 GGUF weights for Recursive Flint, primarily intended for NVIDIA GPUs using llama.cpp with CUDA. The 22.9 GB file includes weights, tokenizer, and chat template.
See Flint’s model card for model details, benchmarks, chat conventions, and limitations.
Run on NVIDIA
Follow llama.cpp’s CUDA installation/build guide, using a release with Flint support, and put llama-server on your PATH. The runtime has been tested on NVIDIA B300, RTX PRO 6000 Blackwell, RTX Spark, and DGX Spark. We recommend at least 48 GB of GPU memory, or unified memory on Spark.
With the Hugging Face CLI installed:
hf download RecursiveSI/flint-nvfp4-gguf flint-nvfp4.gguf pi-models.json opencode.json \
--local-dir flint-nvfp4-gguf
llama-server -m flint-nvfp4-gguf/flint-nvfp4.gguf \
--alias flint -ngl all -c 262144 -np 1 \
-fa on -ctk f16 -ctv f16 --jinja \
--temp 1 --top-p 0.95 --top-k 20 --min-p 0 \
--host 127.0.0.1 --port 8080
The example uses the full 262,144-token context. Reduce -c only if you need to lower KV memory use. Keep compact sliding-window caching enabled by leaving --swa-full unset. No sliding-window or RoPE override is needed.
Use with pi or OpenCode
Keep llama-server running and open another terminal in the directory containing the downloaded model folder.
pi
Install pi using its installation guide, then run:
mkdir -p .pi-flint
cp flint-nvfp4-gguf/pi-models.json .pi-flint/models.json
PI_CODING_AGENT_DIR="$PWD/.pi-flint" pi --provider flint-local --model flint
See pi’s custom-model guide for configuration options.
OpenCode
Install OpenCode using its installation guide, then run:
OPENCODE_CONFIG="$PWD/flint-nvfp4-gguf/opencode.json" opencode --standalone
See OpenCode’s provider guide for configuration options.
The client configs use 262,144 context tokens and a configurable 65,536-token generation budget, including reasoning. Prompt and output share the total context. If you change -c, match the client context limit to it.
Format notes
This file contains packed NVFP4 weights and scales.
Use --jinja and preserve reasoning_content when replaying conversation history.
Training data
Flint’s training data included publicly available and crawled web documents, text and code, commercially licensed data, and AI-generated synthetic data. Post-training included instruction tuning, reinforcement learning and human-preference data. See the base Flint model card for shared model and training information.