Views
No views yet
search, visit) for iterative web research with built-in verification.imatrix.dat file (5.1 MB) is included in this repository. You can use it with llama.cpp's llama-quantize to create your own custom quantizations from a full-precision GGUF.| Filename | Quant Type | Size | Description |
|---|---|---|---|
| Marco-DeepResearch-8B-i1-Q6_K.gguf | Q6_K | 6.3 GB | Very high quality. Near-lossless. |
| Marco-DeepResearch-8B-i1-Q5_K_M.gguf | Q5_K_M | 5.5 GB | High quality. Recommended for most users. |
| Marco-DeepResearch-8B-i1-Q5_K_S.gguf | Q5_K_S | 5.4 GB | High quality. Slightly smaller than Q5_K_M. |
| Marco-DeepResearch-8B-i1-Q4_1.gguf | Q4_1 | 4.9 GB | Good quality. Legacy 4-bit format. |
| Marco-DeepResearch-8B-i1-Q4_K_M.gguf | Q4_K_M | 4.7 GB | Good quality. Best 4-bit option. |
| Marco-DeepResearch-8B-i1-Q4_K_S.gguf | Q4_K_S | 4.5 GB | Good quality. Smaller than Q4_K_M. |
| Marco-DeepResearch-8B-i1-IQ4_NL.gguf | IQ4_NL | 4.5 GB | Good quality. Non-linear 4-bit quant. |
| Marco-DeepResearch-8B-i1-Q4_0.gguf | Q4_0 | 4.5 GB | Decent quality. Legacy 4-bit format. |
| Marco-DeepResearch-8B-i1-IQ4_XS.gguf | IQ4_XS | 4.3 GB | Decent quality. Smallest 4-bit variant. |
| Marco-DeepResearch-8B-i1-Q3_K_L.gguf | Q3_K_L | 4.2 GB | Moderate quality. imatrix helps noticeably here. |
| Marco-DeepResearch-8B-i1-Q3_K_M.gguf | Q3_K_M | 3.9 GB | Moderate quality. Good for memory-constrained setups. |
| Marco-DeepResearch-8B-i1-IQ3_M.gguf | IQ3_M | 3.7 GB | Moderate quality. Better than Q3_K_S at similar size. |
| Marco-DeepResearch-8B-i1-IQ3_S.gguf | IQ3_S | 3.6 GB | Lower quality. imatrix essential at this level. |
| Marco-DeepResearch-8B-i1-Q3_K_S.gguf | Q3_K_S | 3.6 GB | Lower quality. imatrix provides clear benefit. |
| Marco-DeepResearch-8B-i1-IQ3_XS.gguf | IQ3_XS | 3.4 GB | Lower quality. Aggressive compression. |
| Marco-DeepResearch-8B-i1-IQ3_XXS.gguf | IQ3_XXS | 3.2 GB | Low quality. For extreme memory constraints. |
| Marco-DeepResearch-8B-i1-Q2_K.gguf | Q2_K | 3.1 GB | Low quality. imatrix significantly helps. |
| Marco-DeepResearch-8B-i1-Q2_K_S.gguf | Q2_K_S | 2.9 GB | Very low quality. Experimental. |
| Marco-DeepResearch-8B-i1-IQ2_M.gguf | IQ2_M | 2.9 GB | Very low quality. Best option at ~2-bit. |
| Marco-DeepResearch-8B-i1-IQ2_S.gguf | IQ2_S | 2.7 GB | Very low quality. Heavy degradation expected. |
| Marco-DeepResearch-8B-i1-IQ2_XS.gguf | IQ2_XS | 2.6 GB | Extremely low quality. Research/testing only. |
| Marco-DeepResearch-8B-i1-IQ2_XXS.gguf | IQ2_XXS | 2.4 GB | Extremely low quality. Research/testing only. |
| Marco-DeepResearch-8B-i1-IQ1_M.gguf | IQ1_M | 2.2 GB | Minimal quality. Extreme compression research. |
| Marco-DeepResearch-8B-i1-IQ1_S.gguf | IQ1_S | 2.0 GB | Minimal quality. Maximum compression. |
imatrix.dat to create your own quants:1./llama-quantize --imatrix imatrix.dat \
2 Marco-DeepResearch-8B-f16.gguf \
3 Marco-DeepResearch-8B-i1-<QUANT_TYPE>.gguf \
4 <QUANT_TYPE>1./llama-cli -m Marco-DeepResearch-8B-i1-Q5_K_M.gguf \
2 -p "<your prompt>" \
3 -n 4096 \
4 --temp 0.7 --top-p 0.95 \
5 -t $(nproc)1./llama-cli -m Marco-DeepResearch-8B-i1-Q5_K_M.gguf \
2 -p "<your prompt>" \
3 -n 4096 \
4 --temp 0.7 --top-p 0.95 \
5 -ngl 991./llama-server -m Marco-DeepResearch-8B-i1-Q5_K_M.gguf \
2 --port 8080 \
3 -ngl 99 \
4 -c 32768Modelfile:FROM ./Marco-DeepResearch-8B-i1-Q5_K_M.gguf
PARAMETER temperature 0.7
PARAMETER top_p 0.95
PARAMETER num_ctx 327681ollama create marco-deepresearch -f Modelfile
2ollama run marco-deepresearch1from llama_cpp import Llama
2
3llm = Llama(
4 model_path="Marco-DeepResearch-8B-i1-Q5_K_M.gguf",
5 n_ctx=32768,
6 n_gpu_layers=-1, # Use all GPU layers; set to 0 for CPU-only
7)
8
9output = llm(
10 "<your prompt>",
11 max_tokens=4096,
12 temperature=0.7,
13 top_p=0.95,
14)
15
16print(output["choices"][0]["text"])Marco-DeepResearch-8B-i1-Q4_K_M.gguf).<think>, <tool_call>, and <answer> tags.You are an expert web researcher. Your task is to find accurate, complete answers through iterative search, extraction, and verification.
## Core Principles
1) Strategic Planning
- Decompose complex questions into targeted sub-tasks
- Choose the right tool for each step
- Refine your approach based on what you learn
2) Precise Execution
- Define clear objectives before using any tool
- Provide sufficient detail for accurate results
- Avoid vague or overly broad requests
3) Rigorous Verification
- Cross-check important facts across multiple sources
- Resolve conflicts by gathering additional evidence
- Only conclude when evidence is sufficient and consistent
## Output Format
In each turn, you can either call a tool or provide the final answer.
**Call a tool:**
<think>your reasoning process</think>
<tool_call>
{"name": "tool_name", "arguments": {"param1": "value1", "param2": "value2"}}
</tool_call>
**Provide final answer (when you have gathered enough information):**
<think>your reasoning and analysis</think>
<answer>the direct answer to the question</answer>
Note: All reasoning should be in <think>, <answer> should contain only the final answer.
Current date: {current_date}
# Tools
You may call one or more functions to assist with the user query.
You are provided with function signatures within <tools></tools> XML tags:
<tools>
{tools_json}
</tools>
For each function call, return a json object with function name and arguments within <tool_call></tool_call> XML tags:
<tool_call>
{"name": <function-name>, "arguments": <args-json-object>}
</tool_call>1[
2 {
3 "type": "function",
4 "function": {
5 "name": "search",
6 "description": "Search the web via Google to find relevant information and URLs.",
7 "parameters": {
8 "type": "object",
9 "properties": {
10 "querys": {
11 "type": "array",
12 "items": {"type": "string"},
13 "description": "Search queries for finding relevant information."
14 }
15 },
16 "required": ["querys"]
17 }
18 }
19 },
20 {
21 "type": "function",
22 "function": {
23 "name": "visit",
24 "description": "Read webpage content to extract specific information, verify claims, or understand context.",
25 "parameters": {
26 "type": "object",
27 "properties": {
28 "urls": {
29 "type": "array",
30 "items": {"type": "string"},
31 "description": "URL(s) to visit."
32 },
33 "goal": {
34 "type": "string",
35 "description": "The specific information to retrieve. Be precise, not vague."
36 }
37 },
38 "required": ["urls", "goal"]
39 }
40 }
41 }
42]1<think>
2I need to search for information about X to answer the user's question.
3</think>
4<tool_call>
5{"name": "search", "arguments": {"querys": ["search query here"]}}
6</tool_call>1<think>
2Based on the evidence gathered from multiple sources, I can now conclude that...
3</think>
4<answer>
5The direct answer to the question.
6</answer>
1@article{zhu2026marco,
2 title={Marco DeepResearch: Unlocking Efficient Deep Research Agents via Verification-Centric Design},
3 author={Bin Zhu and Qianghuai Jia and Tian Lan and Junyang Ren and Feng Gu and Feihu Jiang and Longyue Wang and Zhao Xu and Weihua Luo},
4 journal={arXiv preprint arXiv:2603.28376},
5 year={2026}
6}