Granite 4.2 3B vs NVIDIA Nemotron 3.5 Bolt E4B 4GB

Granite 4.2 3B

A small reasoning cousin for tool calls, coding and multilingual chat that runs almost anywhere, from a 2.2 GB Ollama build to vLLM and SGLang, under plain Apache 2.0 with signed files and a dataset disclosure. Thinking turns off or shortens per request. It has no published safety results and no documented JSON mode.

NVIDIA Nemotron 3.5 Bolt E4B 4GB

A small cousin for voice and device assistants, game characters and robot interfaces, trained for multi-turn tool calls, instruction hierarchy and short spoken replies, with thinking switchable per request. NVIDIA's Q4_K_M GGUF needs about 8 GB, and Ollama and LM Studio carry it. Context is 64K, half the Gemma 4 base, and NVIDIA publishes no safety results.

Granite 4.2 3B

1. Start it with ollama run granite4.2:3b; set options.num_ctx in the request, since Ollama's default context is short and the model takes up to 131,072
2. With vLLM 0.32.0 or later, serve ibm-granite/granite-4.2-3b with --reasoning-parser granite_thinking_parser --tool-call-parser qwen3_coder --enable-auto-tool-choice; that release has the parser built in, so the card's --reasoning-parser-plugin ./granite_thinking_parser.py isn't needed
3. With SGLang 0.5.18 or later, --reasoning-parser auto --tool-call-parser auto resolve to IBM's recommended parsers, and the reasoning comes back in reasoning_content
4. Use temperature 1.0 and top_p 0.95 for every mode, as IBM requires
5. Pass enable_thinking false for direct answers or low_effort true for short reasoning, through chat_template_kwargs on an OpenAI-compatible server
6. Earlier turns' thinking is stripped by default (truncate_history_thinking), so pass it false to keep reasoning in multi-turn history
7. For JSON, use the runtime's guided decoding, since IBM documents no JSON mode for 4.2
8. Verify the files with python -m model_signing verify sigstore and IBM's identity, per IBM's signature guide

NVIDIA Nemotron 3.5 Bolt E4B 4GB

1. Quickest start is ollama run nemotron-3.5-bolt:e4b, about 8 GB of files, and set num_ctx to 65536 or less, since NVIDIA supports 64K
2. With NVIDIA's GGUF use llama-server -m Nemotron-3.5-Bolt-E4B-Q4_K_M.gguf -c 65536 -ngl 999 --jinja, and add --reasoning on --reasoning-budget <tokens> to cap thinking
3. With vLLM 0.31.0 or later pass --enable-auto-tool-choice --tool-call-parser gemma4 --reasoning-parser gemma4 and the repository's chat_template.jinja
4. Pass enable_thinking explicitly in chat_template_kwargs, since the template defaults to off whatever the card says, and set skip_special_tokens false as the card's examples do
5. Use temperature=1.0 and top_p=0.95 in both modes, as the card says
6. Set conversational_mode true for spoken replies, which appends a brevity instruction to the system prompt
7. Answer a slow tool at once with a pending tool message, then send the result later as a user message starting TOOL RESULT, as the card's asynchronous pattern says
8. Keep persistent rules in the system prompt and send state updates as separate user or system messages in order, per the card's prompting guidelines