Gemma 4 31B IT vs gpt-oss-20b

Gemma 4 31B IT

A dense multimodal cousin with documented tool calling, optional thinking and a 256K context, for general agent work and image reading on one 24 GB GPU through Google's 4-bit build. It runs in every major runtime under plain Apache 2.0. The main risk is that Google publishes no safety results and has gone quiet on the repository since July.

gpt-oss-20b

gpt-oss-20b is a cousin for reasoning, coding and single tool calls with structured output, under plain Apache 2.0. It needs about 17 GB with a working context, and five inference providers serve it. The main risks are that it trails o4-mini at keeping system instructions above user ones, and OpenAI hasn't answered a report since August 2025.

Gemma 4 31B IT

1. On the reference machine run llama-server -hf google/gemma-4-31B-it-qat-q4_0-gguf --hf-file gemma-4-31B_q4_0-it.gguf --jinja -c 32768, adding gemma-4-31B-it-mmproj.gguf for images
2. Or ollama run gemma4:31b for the 20 GB Q4_K_M build
3. In vLLM serve with --enable-auto-tool-choice --tool-call-parser gemma4 --reasoning-parser gemma4, as vLLM's recipe does
4. Thinking is off by default, so pass enable_thinking: true in chat_template_kwargs to turn it on, and expect the reasoning in the thought channel block
5. Drop earlier thoughts from the history except on tool-call turns, as the card asks
6. Use the card's sampling, temperature 1.0, top_p 0.95, top_k 64
7. Validate function names and arguments before running a call, and check JSON output yourself or use the runtime's guided decoding
8. The w4a16 build relies on Marlin INT4 kernels that vLLM marks unsupported on AMD, so use the GGUF on the reference machine

gpt-oss-20b

1. Start it with ollama run gpt-oss:20b (the build that fits the reference machine), or vllm serve openai/gpt-oss-20b with a current vLLM release rather than the card's pinned vllm==0.10.1+gptoss wheel
2. Use the harmony format through the chat template or openai-harmony; OpenAI says the model doesn't work correctly without it
3. Parse tool calls and reasoning with openai-harmony; calls come on the commentary channel ending in <|call|>, reasoning on the analysis channel
4. Set effort with Reasoning: high (or low, medium) in the system message, or reasoning_effort in the template; medium is the default
5. Ask for JSON by putting a JSON Schema under # Response Formats in the developer message
6. Drop earlier reasoning after a final answer but pass it back after tool calls, and don't show the analysis channel to users
7. Expect one tool call per turn; run several in sequence rather than in parallel