Chromadb Context 1 needs about 16.7 GB of memory at Q4_K_M (a 15.8 GB file) with an 8K context window, so it fits on a 24 GB GPU. This repository has 27 quants, from 12.1 GB (Q3_K_S) to 41.9 GB (BF16). Longer context needs more: at 32K tokens the KV cache alone adds about 1.6 GB.
Chromadb Context‑1: 20B parameter agentic search model
Chromadb Context‑1 is a 20B parameter agentic search model built on gpt‑oss. It decomposes complex queries, searches a corpus, and edits its own context to free capacity. The model is designed to work within a specialized agent harness.
Good at
- Query decomposition
- Parallel tool calling
- Self‑editing context
Limits
- Requires agent harness
- No vision support
- Large VRAM for higher‑quality quants
Best for
- Retrieval subagent in multi‑hop queries
- Document‑centric search workflows
- Low‑cost, fast inference
Who it’s for. Developers building retrieval‑augmented agents who need efficient, multi‑hop query handling. The model is suitable for backend services that can integrate the required agent harness.
Quants & memory
| Quant | File | Est. memory | vs VRAM | Result | |
|---|---|---|---|---|---|
| Q3_K_S | 12.1 GB | 13.0 GB | Too big | Get file → | |
| IQ2_M | 12.1 GB | 13.0 GB | Too big | Get file → | |
| IQ2_S | 12.1 GB | 13.0 GB | Too big | Get file → | |
| IQ3_S | 12.1 GB | 13.0 GB | Too big | Get file → | |
| IQ3_XS | 12.1 GB | 13.0 GB | Too big | Get file → | |
| Q2_K | 12.1 GB | 13.0 GB | Too big | Get file → | |
| TQ1_0 | 12.1 GB | 13.0 GB | Too big | Get file → | |
| TQ2_0 | 12.1 GB | 13.0 GB | Too big | Get file → | |
| Q4_0 | 12.1 GB | 13.0 GB | Too big | Get file → | |
| MXFP4_MOE | 12.1 GB | 13.0 GB | Too big | Get file → | |
| IQ3_XXS | 12.2 GB | 13.1 GB | Too big | Get file → | |
| IQ3_M | 12.2 GB | 13.1 GB | Too big | Get file → | |
| IQ4_XS | 12.2 GB | 13.1 GB | Too big | Get file → | |
| IQ4_NL | 12.3 GB | 13.2 GB | Too big | Get file → | |
| Q3_K_M | 12.9 GB | 13.8 GB | Too big | Get file → | |
| Q3_K_L | 13.3 GB | 14.2 GB | Too big | Get file → | |
| Q4_1 | 13.4 GB | 14.3 GB | Too big | Get file → | |
| Q5_0 | 14.6 GB | 15.5 GB | Too big | Get file → | |
| Q4_K_S | 14.7 GB | 15.6 GB | Too big | Get file → | |
| Q4_K_M | 15.8 GB | 16.7 GB | Too big | Get file → | |
| Q5_K_S | 15.9 GB | 16.8 GB | Too big | Get file → | |
| Q5_1 | 15.9 GB | 16.8 GB | Too big | Get file → | |
| Q5_K_M | 16.9 GB | 17.8 GB | Too big | Get file → | |
| Q6_K | 22.2 GB | 23.1 GB | Too big | Get file → | |
| Q8_0 | 22.3 GB | 23.2 GB | Too big | Get file → | |
| BF16 | 41.9 GB | 42.8 GB | Too big | Get file → | |
| BF16 | 41.9 GB | 42.8 GB | Too big | Get file → |
For 8 GB VRAM, use Q4_0 (12.1 GB file, ~13 GB memory). For 12 GB VRAM, Q4_K_M (15.81 GB file, ~16.7 GB memory). For 24 GB VRAM, Q6_K (22.19 GB file, ~23.1 GB memory). These estimates are approximate.
What GPU do you need for Chromadb Context 1?
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: the best quant that fits is Q4_K_S (14.7 GB file, about 15.6 GB in use).
- 24 GB VRAM: the best quant that fits is Q8_0 (22.3 GB file, about 23.2 GB in use).
- 32 GB VRAM: the best quant that fits is Q8_0 (22.3 GB file, about 23.2 GB in use).
- 48 GB VRAM: the best quant that fits is BF16 (41.9 GB file, about 42.8 GB in use).
Which Chromadb Context 1 quant should you choose?
Q4_K_M is the usual starting point for Chromadb Context 1: it balances file size and quality well. Here it is a 15.8 GB file.
The Q8_0 file is 22.3 GB, about 1.4 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.
If memory is tight, the smallest file is Q3_K_S at 12.1 GB, with the quality trade-offs that come with fewer bits. A reasonable choice when a 4-bit file will not fit, mostly on larger models. Quality loss is noticeable but often acceptable.
New to quant names? Read GGUF quantization explained.
Specifications
Architecture from the GGUF header
Source
Frequently asked questions about Chromadb Context 1
How much VRAM does Chromadb Context 1 need?
About 16.7 GB at Q4_K_M with an 8K context window. That is the 15.8 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 Chromadb Context 1 on an 8 GB GPU?
Not at an 8K context. The smallest file needs about 13.0 GB, so you would need a larger GPU or CPU offloading.
What is the file size of Chromadb Context 1 GGUF?
It depends on the quant: Q3_K_S is 12.1 GB, IQ2_M is 12.1 GB, IQ2_S is 12.1 GB, IQ3_S is 12.1 GB, IQ3_XS is 12.1 GB, Q2_K is 12.1 GB and 21 more.
What context length does Chromadb Context 1 support?
The GGUF header lists a trained context length of 131,072 tokens (128K). The KV cache grows with the context you use: about 0.4 GB at 8K and 1.6 GB at 32K.
Where can I download Chromadb Context 1 GGUF?
The files are on Hugging Face in the ryancook/chromadb-context-1-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 Chromadb Context 1 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 Chromadb Context‑1 on 8 GB VRAM?
Yes, using the Q4_0 quantized file which requires about 13 GB of VRAM at 8 k context.
Does this model support vision?
No, the model has no vision capabilities.
What license does it use?
Apache‑2.0.