sweep next edit 1.5B needs about 2.3 GB of memory at Q8_0 (a 1.5 GB file) with an 8K context window, so it fits on a 4 GB GPU. Longer context needs more: at 32K tokens the KV cache alone adds about 0.9 GB.
Sweep Next-Edit 1.5B – a 1.5B parameter code autocomplete model
Sweep Next-Edit 1.5B is a 1.5B parameter model built on Qwen2.5-Coder. It predicts the next code edit and runs locally in under 500 ms with speculative decoding. The model is available in GGUF Q8_0 format.
Good at
- Next‑edit code autocomplete
- Fast local inference
- Speculative decoding
Limits
- No vision support
- Context length limited to 8192 tokens
- Requires Apache‑2.0 license
Best for
- IDE code completion
- Code review assistants
- Rapid prototyping
Who it’s for. Developers who need quick, local code edit suggestions without internet access. The model runs on laptops and supports integration with JetBrains, VSCode, Neovim, and Emacs.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q8_0 | 1.5 GB | 2.3 GB | Fits | Get file → |
The only available quant is Q8_0, file size 1.54 GB. It requires about 2.3 GB of VRAM at 8192‑token context. This is suitable for systems with at least 3 GB of VRAM. No other quants are provided.
What GPU do you need for sweep next edit 1.5B?
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: the best quant that fits is Q8_0 (1.5 GB file, about 2.3 GB in use).
Which sweep next edit 1.5B quant should you choose?
Q8_0 (1.5 GB) is the middle option in this repository. Close to lossless. It costs roughly twice the memory of a 4-bit file, so it suits cases where you have plenty of VRAM.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about sweep next edit 1.5B
How much VRAM does sweep next edit 1.5B need?
About 2.3 GB at Q8_0 with an 8K context window. That is the 1.5 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 sweep next edit 1.5B on an 8 GB GPU?
Yes, with Q8_0: the 1.5 GB file needs about 2.3 GB at 8K context. Larger quants in this repository do not fit in 8 GB.
What is the file size of sweep next edit 1.5B GGUF?
It depends on the quant: Q8_0 is 1.5 GB.
What context length does sweep next edit 1.5B support?
The GGUF header lists a trained context length of 32,768 tokens (32K). The KV cache grows with the context you use: about 0.2 GB at 8K and 0.9 GB at 32K.
Where can I download sweep next edit 1.5B GGUF?
The files are on Hugging Face in the sweepai/sweep-next-edit-1.5B repository. The download buttons on this page open the file on Hugging Face. ggufmodels.com does not host any model files.
What license does sweep next edit 1.5B 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 Sweep Next-Edit 1.5B on 8 GB VRAM?
Yes, the Q8_0 quant requires about 2.3 GB of VRAM, well within an 8 GB budget.
What license does the model use?
The model is released under the Apache‑2.0 license.
What is the maximum context length?
The model supports up to 8192 tokens of context.