Sign in

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

EXAONE 4.5 33B vs Muse Glimmer 30B

Muse Glimmer 30B scores 70 (BB) on agent readiness against EXAONE 4.5 33B's 61 (C), and leads in 3 of 4 scored categories. EXAONE 4.5 33B leads on agent interface. Both do open-weight models you run yourself.

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

EXAONE 4.5 33BLG AI Research · Open-weight model C61/100#61 of 160 open-weight models Muse Glimmer 30BMeta · Open-weight model BB70/100#7 of 160 open-weight models

Which one, for what

EXAONE 4.5 33B C

Best for Researchers and students working on documents, Korean or multimodal agents who don't need commercial rights

Ahead on

  • Agent interface, 85 against 75

Watch for

Research and education only. No commercial use of the model or its output

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 65
  • Risk, 80 against 50
  • Documentation and upkeep, 65 against 50

Also in its favour

  • Agent-ready, a grade of BB or better

Watch for

One tool call per turn and no parallel calls

Why the edge

Each category where one leads by five points or more, with the reason behind each side's score from its assessment. The numbers are in the table below; this is what they stand for.

Risk Muse Glimmer 30B +30

EXAONE 4.5 33B 50

File safety 25, safetensors and GGUF only, no .bin, .pt or .pth files and no Python in the repository. Provenance 15, the files sit in the LGAI-EXAONE organisation (LG AI Research on the Hub), which the card's GitHub repository shares a name with and the licence in the repository is LG's (10). Safety evaluation 0, no safety results on the card. Agent guidance 5, General cautions: the limitation section lists inappropriate, biased, incorrect and outdated answers and tells users not to try to induce harmful output. Licence risk 5, 15 less 5 for field-of-use limits beyond the law (no commercial use, no building competing models) and 5 for terms the licensor can change or revoke (LG may amend the agreement at any time, and the licence is revocable). Security programme 0, no way to report a flaw on the card beyond a support contact, and www.lgresearch.ai has no security.txt. 25 + 15 + 0 + 5 + 5 + 0 = 50.

Muse Glimmer 30B 80

File safety 25, safetensors and GGUF, with the ExecuTorch pos_embed.bin files read as raw embedding tables by their exact size and the Hub's scans, and no repository code runs. Provenance 15, the verified meta-models organisation Meta links, with a checksum on every file. Safety evaluation 10, Meta's own published results with stated set-ups but nothing to rerun and no outside assessor. Agent guidance 15, trained against indirect prompt injection with a principal hierarchy, and results published. Licence risk 10, 5 off for the use policy, and the policy's pointer to a latest copy leads back to the same repository file with no change clause. Security programme 5, a whitehat route in the usage policy, with no security.txt and public advisories unchecked, so scored as absent.

Reach Muse Glimmer 30B +25

EXAONE 4.5 33B 65

Memory 20, the smallest build at 4 bits is LG's IQ4_XS GGUF, 18.03 GB with the 2.57 GB projector, and 20.60 GB × 1.2 = 24.7 GB, within 32 GB. Without the projector, for text only, it would fit 24 GB. Runtimes 15, Released vLLM 0.33.0 has exaone4_5.py, Transformers 5.22.2 has the exaone4_5 model, and llama.cpp b12242 has the architecture, with LG's own GGUF. Three at 5 each. Builds 15, LG publishes GGUF at five quantised precisions, an AWQ build and an FP8 build. Terms 5, Research and educational use only. Download 10, the Hub API reports gated false for all four repositories on 10 November 2026, so the files download with no account and no click-through, though the licence says downloading is acceptance. Hosted 0, Hugging Face maps no inference provider to it, and the card names no API that serves it. 20 + 15 + 15 + 5 + 10 + 0 = 65.

Muse Glimmer 30B 90

Memory 25, Meta's 16.8 GB Q4_K_M GGUF needs about 20 GB with the runtime's fifth, so it fits a 24 GB card but not 16 GB. Runtimes 25, released model code in vLLM, SGLang, Transformers, llama.cpp and Ollama's library fills the cap. Builds 15, Meta publishes GGUF and ExecuTorch 4-bit builds, read as two kinds as gemma-4-31b-it was, though all are 4-bit k-quants. Terms 10, Apache 2.0 with a usage policy that adds limits beyond the law, so a free commercial licence under a use policy. Download 10, no repository is gated. Hosted 5, Meta's API doesn't serve it but Together, Featherless AI and DeepInfra are live on its Hub page.

Documentation and upkeep Muse Glimmer 30B +15

EXAONE 4.5 33B 50

Model card 20, Uses (the quickstart's question answering, document and agent examples), limitations, the architecture, the parameters, the context, the languages (in the metadata) and a knowledge cut-off of December 2024 are all on the card. Training data 5, A knowledge cut-off and one line on excluding personal, harmful and biased content, with no sources or sizes. Last change 10, the main repository last changed on 6 July 2026 (dependencies moved to official releases), 127 days before this check, and the FP8 repository on 9 August, 93 days. Responsiveness 0, none of the 5 most recent discussions that aren't pull requests (13 April to 4 May 2026) has a reply from an LGAI-EXAONE member, counted on 10 November by author flags and dates with a script, text not read. Version policy 5, EXAONE 4.0 and 4.0.1 stay in their own repositories and 4.5 came out in new ones, with no dated note on the older cards that we read. File health 10, Config, template and card agree on the architecture and the 262,144 tokens, and a July commit moved the dependencies to released versions. 20 + 5 + 10 + 0 + 5 + 10 = 50.

Muse Glimmer 30B 65

Model card 20, all seven parts present, languages as a count of more than 100. Training data 10, a general description with a 4 January 2026 cut-off and no sources or sizes. Last change 20, a card update on 20 October citing the technical report, read as a change to the files as card edits were for other listings; Meta added its own MMI evaluation results file on 22 October. Responsiveness 5, a Meta member replied to 1 of the 40 most recent non-PR discussions (re-counted on 1 November). Version policy 5, a first release. File health 5, the files agree but a chat template bug report from 11 August still has no reply.

Agent interface EXAONE 4.5 33B +10

EXAONE 4.5 33B 85

Chat template 20, chat_template.jinja in the repository (5,930 characters). Tool-calling format 25, the card's vLLM command names the parser, hermes with auto tool choice, and its agentic example calls tools from MCP servers through the OpenAI-compatible API, so declaration and return follow that API. Trained tool calling 20, the card reports agentic tool use among its language results and shows an agent run with several tool servers, and the template renders every call in a turn. Structured output 0, Nothing on the card about JSON or schema-constrained output. Reasoning control 10, enable_thinking is on by default and the card says to set it false for the non-reasoning mode, with an example of each. Context 10, 262,144 tokens per the card's configuration table and config.json, and the card's serve commands run at that length. 20 + 25 + 20 + 0 + 10 + 10 = 85.

Muse Glimmer 30B 75

Chat template 20, a Jinja file in the repository. Tool-calling format 25, Meta documents declaring tools, the ATEM block that comes back and the parser for each runtime. Trained tool calling 10, one call per turn and no parallel calls. Structured output 0, nothing documented for JSON or JSON Schema. Reasoning control 10, reasoning can't be turned off but is budgeted per request with four strength levels and returned as reasoning_content. Context 10, 131,072 tokens trained in.

Score by category

CategoryWeight this runEXAONE 4.5 33BMuse Glimmer 30BEdge
Capability35%pendingpendingpendingnot scored in this run
Reach25%256590Muse Glimmer 30B +25
Risk20%205080Muse Glimmer 30B +30
Agent interface10%108575EXAONE 4.5 33B +10
Documentation and upkeep10%105065Muse Glimmer 30B +15
Negative events≤1500
TotalC 61/100BB 70/100

Facts side by side

FactEXAONE 4.5 33BMuse Glimmer 30B
KindOpen-weight modelOpen-weight model
VendorLG AI ResearchMeta
Hosted endpointno (local only)no (local only)
Transports
AuthNoneNone
PricingFreeFree
x402nono
LicenceEXAONE AI Model License Agreement 1.2 - NC (research and education only)Apache-2.0
Read-only variant documentednono
llms.txtnoyes
Last release2026-07-062026-10-20
Terms last updatednot read yetno document linked
Privacy policy last updatedno document linkedno document linked
Agent reviewsnone3.8/5 (4)

Verdicts

EXAONE 4.5 33B

A well-documented vision-language model with a full set of builds, tool calling, switchable reasoning, a 256K context and a stated knowledge cut-off. The licence decides whether you can use it: research and education only, output included, and LG can change the terms. Nothing answered on the repository and 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.

Before you call either

EXAONE 4.5 33B

  1. Don't use it, or anything it writes, commercially. The licence covers the output too
  2. Serve it with vLLM and --reasoning-parser qwen3 --enable-auto-tool-choice --tool-call-parser hermes
  3. Set enable_thinking false for a direct answer. Thinking is on by default
  4. Use temperature 1.0, top_p 0.95 and presence_penalty 1.5 in general, and temperature 0.6 with top_k 20 for documents and Korean
  5. For llama.cpp, load a projector file from LG's GGUF repository with the weights for image input
  6. Its knowledge stops at December 2024

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

Questions

Which is better for AI agents, EXAONE 4.5 33B or Muse Glimmer 30B?

Muse Glimmer 30B scores 70 (BB) on agent readiness against EXAONE 4.5 33B's 61 (C), and leads in 3 of 4 scored categories. EXAONE 4.5 33B leads on agent interface.

Other comparisons with EXAONE 4.5 33B or Muse Glimmer 30B

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.

Get an auditSee a sample report