How to Run Muse Glimmer Locally with Ollama (2026 Guide)
Muse Glimmer is Meta's 30B agentic model with a 128K context window and vision input. Install Ollama, pick the right tag, and run it on a single GPU or Mac.

Muse Glimmer is Meta's newest local model, a 30 billion parameter causal language model with a dedicated perception encoder, distilled from Meta's larger Muse Spark. It's built for a different job than a general chat model: autonomous agentic work, where a model plans several steps, calls tools, and has to recover when something along the way goes wrong instead of just answering one question. It ships under Apache 2.0 with real local Ollama tags starting at 18GB, small enough for a single consumer GPU or an Apple Silicon Mac with enough unified memory.
It calls functions with precise schema handling across long, multi-turn workflows, and when a tool call fails or returns something unexpected, it diagnoses the error and retries rather than stopping cold. The perception encoder lets it read interleaved text and images in the same request, useful for an agent that needs to check a screenshot, a chart, or a document mid-task. Meta trained it on data spanning more than 100 languages, and built in four reasoning strength levels, low, medium, high, and xhigh, so you can trade speed for depth depending on what the task actually needs.
This guide covers picking the right tag for your hardware, installing Ollama, running your first prompt, using vision input and reasoning strength from the command line and the API, and connecting Muse Glimmer to an agent scaffold like Hermes Agent or OpenClaw through Ollama's built-in launch shortcut. The alternatives section compares it to Gemma4-31B, the Qwen3 family, and DeepSeek R1 for anyone whose hardware or use case fits a different model better.
Prerequisites
- Ollama, updated to its latest release (run `ollama --version`; re-run the install command below if the model is not recognized)
- 16-20 GB or more of combined RAM and VRAM for the default 18GB tag
- 18-21 GB of free disk space depending on which tag you pull
- An Apple Silicon Mac with enough unified memory can use the 21GB MLX-optimized tag for better performance on the same hardware
- Basic terminal familiarity for `ollama pull` and `ollama run` commands
- (Optional) A rented GPU if your machine cannot handle the model locally
Need more GPU power?
Rent a RTX 4090 on Vast.ai from $0.20/hr. On-demand GPU rentals by the hour, useful for running larger models without buying hardware.
In This Guide
What Muse Glimmer Is and Which Tag to Run
Muse Glimmer is a 30 billion parameter causal language model distilled from Meta's larger Muse Spark, with a dedicated perception encoder for image understanding. It's built for agentic work specifically, tasks where a model has to plan multiple steps, call tools with the right arguments, and keep going when something breaks partway through, rather than a general chat model that happens to also do those things.
Meta benchmarked it against Gemma4-31B and Qwen3.6-27B, two models in the same size class, across general agentic tasks, agentic coding, multimodal understanding, and safety. On MCP Atlas, a public benchmark for tool-using agents, Muse Glimmer scored 75.5 against Gemma4-31B's 54.2 and Qwen3.6-27B's 62.5. On SWE-Bench Verified, a benchmark for resolving real GitHub issues, it scored 76.0, ahead of Gemma4-31B's 66.6 and just behind Qwen3.6-27B's 77.2. No model sweeps every category here, which is the normal pattern at this size class, so check the benchmark closest to what you'll actually be doing rather than trusting a single score.
On Ollama's library, the model ships with two real tags:
| Tag | Download Size | Recommended RAM/VRAM | Best For |
|---|---|---|---|
| muse-glimmer (= latest = 30b) | 18 GB | 16-20 GB+ | A single consumer GPU or a Mac with enough unified memory |
| muse-glimmer:30b-mlx | 21 GB | 20-24 GB+ unified memory | Apple Silicon Macs, MLX-optimized with image input support |
The plain `muse-glimmer` tag, the explicit `30b` tag, and `latest` all point at the identical 18GB download. Muse Glimmer's Ollama library page lists just that one standard build plus the Apple Silicon MLX variant, unlike some local models that ship several quantization levels: pull the default tag on Linux, Windows, or Intel Macs, and the MLX tag on Apple Silicon.
Install Ollama and Run Your First Muse Glimmer Prompt
Getting Muse Glimmer running takes about ten minutes on a normal connection, most of it spent downloading the 18GB tag.
Step 1: Install Ollama
# Linux and macOS, one-command installer
curl -fsSL https://ollama.com/install.sh | shOn Windows, download the installer from ollama.com/download, or use winget:
winget install Ollama.OllamaConfirm Ollama is on its latest release, since Muse Glimmer was added recently:
ollama --versionStep 2: Pull and Run muse-glimmer
ollama run muse-glimmerExpected output on first run:
pulling manifest
pulling 7c19a4f2... 100% ââââââââââââââââââ 18 GB
pulling tokenizer... 100% ââââââââââââââââââ 3.8 MB
success
>>> Send a message (/? for help)On an Apple Silicon Mac, pull the MLX-optimized tag instead. Ollama's MLX engine is tuned for that hardware and adds image input support:
ollama run muse-glimmer:30b-mlxStep 3: Send a Test Prompt
>>> Write a Python function that checks if a string is a valid IPv4 address, then explain the edge cases it handles.Muse Glimmer is tuned for agentic and coding tasks, so expect a direct, structured response. The first response takes longer than later ones while the model and its context load fully into memory.
Step 4: Verify the Model
ollama list`muse-glimmer:latest` appears in the list at its full download size, 18 GB. This confirms the weights are actually on disk, not only cached for a cloud call.
Using Vision Input, Tool Use, and Controllable Reasoning
Muse Glimmer's three defining features, image understanding, reliable tool calling, and adjustable reasoning depth, are all reachable from the command line and the API.
Send an Image from the Terminal
ollama run muse-glimmer "What does this chart show? ./quarterly-revenue.png"The perception encoder reads the image and reasons over it alongside the text prompt in the same request, useful for an agent that needs to interpret a screenshot, chart, or document mid-task.
Control Reasoning Strength via the API
curl http://localhost:11434/api/chat -d '{
"model": "muse-glimmer",
"messages": [
{ "role": "user", "content": "Plan a multi-step migration from a monolith to microservices for this codebase." }
],
"think": "high",
"stream": false
}'Muse Glimmer supports four reasoning strength levels: `low`, `medium`, `high`, and `xhigh`. Lower levels trade reasoning depth for faster, cheaper responses on simpler prompts, while `xhigh` is built for the longest, most complex agentic workflows.
Tool Use and Failure Recovery
Muse Glimmer calls tools with precise schema handling across extended workflows, and diagnoses and retries when a tool call fails or returns something unexpected instead of stopping. That's the actual thing its MCP Atlas and SWE-Bench Pro scores are measuring: whether it can carry a multi-step task through to a working result, not just answer one question well.
Connect Muse Glimmer to an Agent Scaffold
Muse Glimmer is designed to sit inside an agent scaffold, software that gives the model a loop, a set of tools, and a task to run end to end, not just answer prompts one at a time. Ollama ships a launch shortcut for this that skips the manual config step.
The ollama launch Shortcut
ollama launch hermes --model muse-glimmerollama launch openclaw --model muse-glimmerBoth commands start the named scaffold, Hermes Agent or OpenClaw, pre-configured to use Muse Glimmer as its model, instead of requiring a separate config file edit. Ollama's library also lists launch shortcuts for Claude Code and OpenCode using the same `--model muse-glimmer` pattern.
Manual OpenAI-Compatible Endpoint
If your scaffold or agent tool doesn't support the launch shortcut, point its OpenAI-compatible configuration at Ollama directly:
model:
default: muse-glimmer
provider: custom
base_url: http://localhost:11434/v1
context_length: 131072Troubleshooting
`ollama run muse-glimmer` fails or the model is not recognized
Cause: The installed Ollama version predates Muse Glimmer support
Fix: Update Ollama by re-running the install command (`curl -fsSL https://ollama.com/install.sh | sh` on Linux/macOS, or re-download on Windows), then retry.
Out-of-memory error or the model fails to load
Cause: Available combined RAM and VRAM falls short of the 18GB (standard) or 21GB (MLX) tag
Fix: Confirm your hardware has 16-20GB+ available for the standard tag, or 20-24GB+ unified memory for the MLX tag. Rent a GPU on Vast.ai rather than buying hardware if neither fits.
The MLX tag will not load on a non-Apple-Silicon machine
Cause: `muse-glimmer:30b-mlx` is built specifically for Apple Silicon's Metal/MLX stack
Fix: Use the standard `muse-glimmer` tag on Linux, Windows, or Intel Macs instead. MLX tags only run on Apple Silicon.
Image input is ignored or returns an error
Cause: The image path is wrong, or the reference sits too far from the relevant part of a longer prompt
Fix: Double-check the file path is correct and readable, and keep the image reference close to the part of the prompt it relates to.
Tool calls fail silently or the agent loop stalls
Cause: The scaffold's tool schema does not match what the model expects, or reasoning strength is set too low for a complex multi-step task
Fix: Raise `think` to `high` or `xhigh` for complex agentic tasks, and confirm the scaffold's tool definitions match its own documentation exactly.
Context window errors past a certain length
Cause: The application or agent config caps `context_length` below the model's native 131,072 tokens
Fix: Set `context_length` to 131072 explicitly in the agent or API config, as shown in the manual endpoint example above.
Alternatives to Consider
| Tool | Type | Price | Best For |
|---|---|---|---|
| Gemma4-31B | Local (Ollama) | Free | A similarly sized general-purpose model from Google, worth comparing directly since Meta benchmarked Muse Glimmer against it. |
| Qwen3.8 | Local (Ollama) | Free | Alibaba's dense 27.8B model with a much larger 262K context window, for tasks that need more context than Muse Glimmer's 128K. |
| DeepSeek R1 | Local (Ollama) or VPS | Free | Reasoning-heavy tasks with visible chain-of-thought output, on hardware from 4GB (distilled) up to 64GB or more (70B). |
| GLM 5.2 via Ollama Cloud | Cloud (Ollama) | Free within Ollama Cloud limits | A 1M token context window, for agentic tasks too large for any locally hosted 128K-class model. |
Frequently Asked Questions
Can I run Muse Glimmer locally with Ollama?
Yes. Muse Glimmer has real local Ollama tags starting at 18GB for the standard build, small enough for a single consumer GPU (an RTX 4090, for example) or an Apple Silicon Mac with enough unified memory.
An MLX-optimized tag (21GB) exists for Apple Silicon specifically, tuned for that hardware and adding image input support. The plain `ollama run muse-glimmer` command pulls the standard 18GB tag.
How much RAM or VRAM do I need for Muse Glimmer?
For the standard 18GB tag, plan on 16-20 GB of combined RAM and VRAM. For the 21GB MLX tag on Apple Silicon, plan on 20-24 GB of unified memory.
These figures track the download size closely, since Muse Glimmer ships as one standard quantization level rather than multiple tags at different precisions.
What is the difference between muse-glimmer and muse-glimmer:30b-mlx?
Both tags are close in size, 18GB for the standard build and 21GB for MLX, but they target different hardware. `muse-glimmer` (and its `30b`/`latest` aliases) runs through Ollama's standard engine, suited to Linux, Windows, and Intel Macs. `30b-mlx` is built for Apple's MLX framework, taking fuller advantage of Apple Silicon's unified memory and Metal acceleration, and adds image input support.
Use `30b-mlx` on any Apple Silicon Mac. Use the plain `muse-glimmer` tag everywhere else.
Does Muse Glimmer support images, or only text?
Muse Glimmer is multimodal through a dedicated perception encoder, accepting interleaved text and images in the same request. From the terminal, pass an image file path alongside your text prompt: `ollama run muse-glimmer "Describe this chart ./chart.png"`.
This is built into the model itself, not a separate vision-only variant, so it applies to both the standard and MLX tags.
What does controllable reasoning mean and how do I set it?
Muse Glimmer has four reasoning strength levels, `low`, `medium`, `high`, and `xhigh`, set through the `think` field in an API request, for example `"think": "high"`. Lower levels answer faster on simple prompts, higher levels spend more effort on complex, multi-step agentic tasks.
In an interactive session, `/set think` and `/set nothink` toggle thinking on and off without picking a specific level.
Can I connect Muse Glimmer to Hermes Agent or OpenClaw?
Yes. Ollama ships a launch shortcut, `ollama launch hermes --model muse-glimmer` or `ollama launch openclaw --model muse-glimmer`, that starts either scaffold already pointed at Muse Glimmer, no manual config file edit required.
If your agent tool doesn't support the launch shortcut, point its OpenAI-compatible configuration at Ollama's endpoint (`http://localhost:11434/v1`) with `context_length` set to 131072 to use the model's full native context window. See the Hermes Agent and OpenClaw guides for the full setup of each scaffold.
Who makes Muse Glimmer and what is Muse Spark?
Meta publishes Muse Glimmer under the Apache 2.0 license. It's distilled from Muse Spark, a larger Meta model it inherits its core capabilities from.
Ollama's library page doesn't publish separate specs for Muse Spark itself, since it isn't something you pull or run directly. Only the distilled Muse Glimmer is available to download and run locally.
Related Guides
How to Run Ollama Locally: Complete Setup Guide (2026)
How to Run Gemma 4 on Ollama: Complete Setup Guide (2026)
How to Run Qwen3.8 Locally with Ollama (2026 Guide)
How to Install Hermes Agent with Ollama Local Models (2026)
How to Run OpenClaw with Ollama Local Models (2026 Guide)
Best Local LLM Models to Run in 2026 (Benchmarks + Use Cases)