Muse Glimmer 30B vs Qwopus3.8-27B-Flash-V2

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.

Qwopus3.8-27B-Flash-V2

A Qwen3.8-27B cousin tuned to think less per turn in long agent loops, with an MTP head for speculative decoding in llama.cpp. It fits 24 GB with Jackrong's 4-bit GGUF. The risks are one person's experimental release with no safety work, training traces taken from Claude and GPT, and a tool format that differs from Qwen's.

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

Qwopus3.8-27B-Flash-V2

1. Quickest start is llama-server -hf Jackrong/Qwopus3.8-27B-Flash-V2-GGUF:Q4_K_M --jinja, about 17 GB, and add mmproj-F32.gguf for images
2. The card's tests used Q5_K_M with the bundled MTP head and --spec-type draft-mtp in llama.cpp
3. The template asks for tool calls as JSON inside tool_call tags, so use a Hermes-style parser (vLLM's hermes), not Qwen3.8's qwen3_coder
4. For coding the card recommends enable_thinking true, reasoning_effort xhigh and temperature 0.3, which you must pass yourself, since generation_config.json says 1.0
5. reasoning_effort takes xhigh (default), medium or low, and any other value makes the template raise an error
6. Earlier reasoning stays in the context unless preserve_thinking is false
7. Cap max_tokens, since a report says it loops more than V1