Gemma 4 E4B IT vs Ornith-1.5-9B

Gemma 4 E4B IT

A small cousin for light agent work, tool-calling loops, transcription and image reading on a phone or laptop, under Apache 2.0. Google's 4-bit build needs about 7 GB with working space and runs in all the common runtimes. Google's card puts it far below larger Gemma 4 sizes on agent and coding tasks, with no published safety results.

Ornith-1.5-9B

A small coding and terminal-agent cousin with thinking on by default, XML tool calls that vLLM and SGLang parse, and 262,144 tokens of context. Ornith's own 4-bit builds run in under 8 GB in most local runtimes. The main risk is an absent publisher, with no licence file, no safety results, files replaced without a note and no replies.

Gemma 4 E4B IT

1. On the reference machine run llama-server -hf google/gemma-4-E4B-it-qat-q4_0-gguf --hf-file gemma-4-E4B_q4_0-it.gguf --jinja -c 131072, and add --mmproj with gemma-4-E4B-it-mmproj.gguf for images and audio
2. With Ollama run ollama run gemma4:e4b and raise num_ctx or OLLAMA_CONTEXT_LENGTH, since the default context is small and agents want at least 64K
3. In vLLM or SGLang pass --tool-call-parser gemma4 --reasoning-parser gemma4 (vLLM also --enable-auto-tool-choice), or tool calls come back as text; Google's w4a16 build is the 4-bit route there
4. Thinking is off by default; pass enable_thinking=True or start the system prompt with <|think|>, and drop earlier turns' thinking from history except on tool-call turns
5. Put images before the text and audio after it, keep audio to 30 seconds and video to 60 frames, and validate tool names and arguments before running them

Ornith-1.5-9B

1. Start it with ollama run ornith-1.5:9b, or llama-server -hf ornith-ai/Ornith-1.5-9B-GGUF with the Q4_K_M file
2. In vLLM pass --enable-auto-tool-choice --tool-call-parser qwen3_xml --reasoning-parser qwen3, and in SGLang --tool-call-parser qwen3_coder --reasoning-parser qwen3, so tool calls and reasoning come back parsed
3. Thinking is on by default. Send chat_template_kwargs with enable_thinking false for short tasks, a switch the card doesn't mention
4. Pin which template your runtime loads, since chat_template.jinja keeps earlier reasoning and the tokenizer_config.json template drops it
5. Use temperature 0.6, top_p 0.95, top_k 20 for coding and temperature 1.0 with presence_penalty 1.5 for general tasks, per the card
6. Pin a revision when you download, since Ornith has replaced files in place, and add mmproj-Ornith-1.5-9B-BF16.gguf (0.9 GB) for image input in llama.cpp
7. Validate JSON output yourself, since structured output isn't documented