occamy-1.0 vs Qwen3-4B-Instruct-2507

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-4B-Instruct-2507

A small, fast cousin for instruction following, short tool-calling jobs and long documents on modest hardware, with no thinking step. It runs in about 3 GB at 4 bits on every common runtime, and two providers host it. The main risk is neglect, with no file changes in over a year, no answers from Alibaba and no safety results.

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-4B-Instruct-2507

1. Quickest start is ollama run qwen3:4b-instruct, 2.5 GB. Plain qwen3:4b is the Thinking-2507 edition, not this one
2. On our reference machine use BF16 with vllm serve Qwen/Qwen3-4B-Instruct-2507 --max-model-len 262144 --enable-auto-tool-choice --tool-call-parser hermes
3. Use the hermes parser in vLLM or qwen25 in SGLang, the template emits JSON inside tool_call tags
4. Don't pass enable_thinking, this edition never thinks and the card says the flag isn't needed
5. Sampling per the card is temperature 0.7, top_p 0.8, top_k 20 and min_p 0, with presence_penalty up to 2 against repetition
6. Drop the context to 32,768 tokens if memory runs out, as the card suggests
7. Validate JSON yourself or use the runtime's guided decoding, since structured output isn't documented