InternVL3.5-GPT-OSS-20B-A4B-Preview vs Muse Glimmer 30B

InternVL3.5-GPT-OSS-20B-A4B-Preview

An image and video reader on gpt-oss-20b with an optional thinking mode, a preview untouched for over a year. It needs about 51 GB in BF16, since OpenGVLab publishes no quantised build, and runs in Transformers and vLLM. The main risk is a chat template in the Transformers-format repository that doesn't match its tokenizer, with no safety results.

Muse Glimmer 30B

A dense 30B multimodal cousin for local agent and coding work with images, documented tool calls and adjustable reasoning. Meta's 17 GB GGUF fits a 24 GB card and runs in llama.cpp, Ollama, vLLM, SGLang and Transformers. The main risks are one tool call per turn, no documented JSON output and a usage policy that adds limits to Apache 2.0.

InternVL3.5-GPT-OSS-20B-A4B-Preview

1. Serve with vllm serve OpenGVLab/InternVL3_5-GPT-OSS-20B-A4B-Preview-HF --max-model-len 32768, which is our command; the card gives none for vLLM
2. Check the rendered prompt before relying on it, since the shipped template's <|im_start|> markers aren't tokens in the gpt-oss tokenizer; the GitHub-format repository's harmony template is the alternative
3. Use Transformers 4.55.0 or later, as the card requires for this size
4. For thinking, send the card's thinking system prompt and parse the reasoning out of the <think> tags, with temperature 0.6 and sampling on as the card advises
5. Keep inputs within 32K tokens, the length it was trained at, whatever the config says

Muse Glimmer 30B

1. Start it with llama serve -hf meta-models/Muse-Glimmer-30B-GGUF --hf-file Muse-Glimmer-30B-KQuant-17GB-Q4_K_M.gguf -ngl 99 -c 131072 --host 127.0.0.1 --port 8080 --chat-template-kwargs '{"reasoning_strength":"high"}' on llama.cpp b10353 or later, or ollama run muse-glimmer on Ollama 0.32.7 or later
2. In vLLM pass --tool-call-parser muse_glimmer --reasoning-parser muse_glimmer, in SGLang muse for both, in ExecuTorch --tool-parser atem. Without them tool calls come back as plain text
3. Set reasoning per request with chat_template_kwargs.reasoning_strength (low, medium, high or xhigh). llama.cpp and ExecuTorch don't read reasoning_effort, and ExecuTorch rejects it with a 400
4. Expect one tool call per turn and return each result before the next. ExecuTorch's server rejects tool_choice="required"
5. Keep temperature 1.0, top_p 0.95 and top_k 64, don't run greedy, and never stop on <|eom|>
6. Leave max_tokens room for reasoning, since in llama.cpp a request cut off mid-thought returns empty content with finish_reason length
7. For images add Meta's 1.4 GB mmproj GGUF, which takes the build to about 22 GB with the runtime's fifth