occamy-1.0 vs Qwen3-VL-2B-Instruct

occamy-1.0

A Qwen3.6-35B-A3B fine-tuned for long agent work with tools, files and code, under plain Apache 2.0, and Accio's 4-bit builds run in about 23 GB. The main gaps are no safety results, agent guidance or security contact, and every benchmark figure is Accio's own.

Qwen3-VL-2B-Instruct

The smallest Qwen3-VL cousin, for reading screenshots, documents, charts and video on a laptop or edge box, running in about 2 GB from Alibaba's Q4_K_M GGUF in every major runtime under plain Apache 2.0. Qwen hasn't answered repository questions or published safety work, so keep a human or a check in the loop before it drives a GUI.

occamy-1.0

1. Serve with --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder on vLLM 0.19.0 or SGLang 0.5.10 and later
2. BF16 is 70.2 GB, so on a 128 GB machine run it without the card's 8-way tensor parallelism
3. Keep the whole assistant message, reasoning and tool calls included, in later turns, as the card says
4. Sampling per the card is temperature 1.0, top_p 0.95, top_k 20 and presence_penalty 1.5
5. With the GGUFs, NFC-normalise input text and read TOKENIZER.md, since the files store qwen2 pre-tokenizer metadata
6. The base's MTP layer isn't in this checkpoint, Accio-Lab/occamy-1.0-MTP is an experimental separate head

Qwen3-VL-2B-Instruct

1. Start it with llama-server -hf Qwen/Qwen3-VL-2B-Instruct-GGUF:Q4_K_M --jinja -c 32768, or ollama run qwen3-vl:2b-instruct
2. In Ollama the plain qwen3-vl:2b tag is the Thinking edition, so name 2b-instruct
3. With the GGUF, load the mmproj vision file too, or images won't be read
4. Parse tool calls as JSON inside <tool_call> tags, or use SGLang's --tool-call-parser qwen
5. Use the card's sampling, temperature=0.7, top_p=0.8, top_k=20, presence_penalty=1.5 for vision and temperature=1.0, top_p=1.0, top_k=40, presence_penalty=2.0 for text
6. Validate JSON output yourself, since structured output isn't documented
7. vLLM needs 0.11.0 or later and Transformers 4.57.0 or later