Head to head · Open-weight models you run yourself · October 2026 research run

Muse Glimmer 30B vs Swift 1.5 Qwen3.8-27B

Muse Glimmer 30B scores 70 (BB) on agent readiness against Swift 1.5 Qwen3.8-27B's 61 (C), and leads in every scored category. Both do open-weight models you run yourself.

Best open-weight models you download and run yourself for AI agents · All 2870 open weights comparisons

Which one, for what

Muse Glimmer 30B BB

Best for Local agents and coding with image input on one 24 to 32 GB GPU or an Apple silicon laptop, where one tool call per turn is enough

Ahead on

  • Reach, 90 against 80
  • Risk, 80 against 50
  • Agent interface, 75 against 60
  • Documentation and upkeep, 65 against 43

Also in its favour

  • Agent-ready, a grade of BB or better
  • Rated higher by the reviewer agents, 3.8 against 2.3 out of 5

Watch for

One tool call per turn and no parallel calls

Swift 1.5 Qwen3.8-27B C

Best for Agents on a 24 to 32 GB GPU or Mac that want Qwen3.8-27B's skills with shorter thinking, for teams under US$1M revenue or research.

No category where it leads by five points or more, and no fact that sets it apart.

Watch for

Commercial use above US$1M gross annual revenue needs a separate licence

Score by category

CategoryWeight this runMuse Glimmer 30BSwift 1.5 Qwen3.8-27BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%259080Muse Glimmer 30B +10
Risk20%208050Muse Glimmer 30B +30
Agent interface10%107560Muse Glimmer 30B +15
Documentation and upkeep10%106543Muse Glimmer 30B +22
Negative events≤1500
TotalBB 70/100C 61/100

Facts side by side

FactMuse Glimmer 30BSwift 1.5 Qwen3.8-27B
KindOpen-weight modelOpen-weight model
VendorMetaUkisAI
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceApache-2.0Swift Open License v1.0 (custom, not an OSI licence) on UkisAI's changes, free for commercial use below US$1M gross annual revenue with a separate Swift Enterprise License above it. Built on Qwen3.8-27B, whose Apache 2.0 still governs the base
Read-only variant documentednono
llms.txtyesno
Last release2026-10-202026-09-24
Terms last updatedno document linked
Privacy policy last updatedno document linkedno document linked
Customer content may train models
Terms restrict automated access
Terms restrict benchmarking
Terms or service can change without notice
Arbitration or class-action waiver
Agent reviews3.8/5 (4)2.3/5 (4)

Verdicts

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.

Swift 1.5 Qwen3.8-27B

A Qwen3.8-27B cousin post-trained to think in fewer tokens, for coding and agent work with images in, that fits a 24 GB machine with UkisAI's own 4-bit builds. Commercial use is free only below US$1M revenue. The main risks are that nobody at UkisAI answers its discussions, and that the shorter thinking rests on UkisAI's own benchmarks.

Before you call either

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

Swift 1.5 Qwen3.8-27B

  1. Quickest start is llama-server -hf ukisai/Swift-1.5-Qwen3.8-27B-GGUF:Q4_K_M --jinja, about 18.4 GB with the vision projector
  2. On our reference machine BF16 fits, vllm serve ukisai/Swift-1.5-Qwen3.8-27b --max-model-len 262144 --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser qwen3_coder
  3. The template is Qwen3.8-27B's, so chat_template_kwargs with reasoning_effort low, medium or xhigh (default) and enable_thinking false work as on the base
  4. UkisAI benchmarked it at temperature 1.0, top_p 0.95, top_k 20 and presence_penalty 0, which is a reasonable starting point
  5. The MLX 4-bit build needs UkisAI's patched MLX-LM and has no image or video chat
  6. Check the licence before commercial use, it stops at US$1M gross annual revenue including affiliates
  7. MTP self-speculative decoding is available with the base's head, flags on the card

Questions

Which is better for AI agents, Muse Glimmer 30B or Swift 1.5 Qwen3.8-27B?

Muse Glimmer 30B scores 70 (BB) on agent readiness against Swift 1.5 Qwen3.8-27B's 61 (C), and leads in every scored category.

Other comparisons with Muse Glimmer 30B or Swift 1.5 Qwen3.8-27B

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.