shipwithmuse

№ 0436GitHub

Muse Glimmer 30B on Ryzen AI and Radeon

A reproducible RDNA reference that adapts MI-series ROCm recipes to run Muse-Glimmer-30B on Ryzen AI (Radeon 8060S) hardware, measuring 2.2–2.5x single-stream speedups from DFlash.

Open source github.com
Post on X ↗LinkedIn ↗Reddit ↗Hacker News ↗
Muse Glimmer 30B on Ryzen AI and Radeon on github.com
aiwork4me/muse-glimmer-30b-rocmREADME ↗
# Muse-Glimmer-30B-ROCm

[![CI](https://github.com/AIwork4me/Muse-Glimmer-30B-ROCm/actions/workflows/ci.yml/badge.svg)](https://github.com/AIwork4me/Muse-Glimmer-30B-ROCm/actions/workflows/ci.yml)
[![License: Apache-2.0](https://img.shields.io/badge/license-Apache--2.0-blue.svg)](LICENSE)

> **The reproducible RDNA reference for Meta Muse-Glimmer-30B — from
> MI-series recipes to Ryzen AI and Radeon.**

![](./docs/hero.jpg)

**What you get:**

- Run a ~30B multimodal reasoning/tool-use model **locally on validated Ryzen
  AI-class hardware** (Radeon 8060S, `gfx1151`) with a one-command quickstart.
- **Measured, not guessed, speedups** — DFlash speculative decoding delivers
  **2.2–2.5× single-stream**; concurrency tradeoffs are benchmarked, including
  the pitfalls (see [known good and known bad](#known-good-and-known-bad)).
- A reviewed **[CDNA → RDNA adaptation map](docs/adaptation.md)** — reuse the
  engineering delta instead of rediscovering it.
- **Evidence-first claims**: every number links to raw cells with exact flags,
  hashes and manifests. Failures are preserved as findings, not hidden.
- A protocol to **contribute Radeon evidence that is comparable** rather than
  anecdotal ([hardware validation](docs/hardware-validation.md)).

Method: **Adapt → Validate → Benchmark → Explain → Reproduce.**

<!-- BEGIN GENERATED: validated-platform -->
**Actually validated here:** AMD Ryzen AI MAX+ PRO 395 / Radeon 8060S,
`gfx1151` (RDNA 3.5). Every additional platform remains evidence-gated by the matrix below.
<!-- END GENERATED: validated-platform -->

## Performance highlights

gfx1151 rows validated on **ROCm 7.14.0** via the GGUF/llama.cpp matrix
([`docs/results/matrix-714/`](docs/results/matrix-714/)). The W7900
(`gfx1100`) rows are community-validated and independently reproduced on
**ROCm 7.14.0** (recommended default) and **7.2.1**
([W7900 results](docs/results/w7900-gfx1100.md)).

**Single-stream (Study 1, greedy, Meta-aligned DFlash anchor):**

| Configuration | Baseline | DFlash | Speedup |
|---|---:|---:|---:|
| gfx1151, K-Quant-17GB | 10.42 tok/s | 23.08 tok/s | **2.22×** |
| gfx1151, dynamic K-Quant | 9.11 tok/s | 22.49 tok/s | **2.47×** |
| W7900 (`gfx1100`), K-Quant-17GB | 33.21 tok/s | 61.45 tok/s | **1.85×** |

W7900 rows: ROCm 7.14.0, draft acceptance ~0.24 — raw cells:
[`cells-rocm-7.14.0`](docs/results/hardware-validation/w7900-gfx1100/cell

Also filed under Local & open models

See all →
  1. 0805

    Muse drives a rover with a custom connector★

    Took your custom-connector idea to the physical world: the "service with an API" was my robot. Muse wrote the connector for my rover's API, then installed PyTorch & Depth Anything V2 in the VM because the camera is 2D, drove to the black ball and stopped a few inches short.

    @hrhraj

    X post

    Local & open models

  2. 0490

    Muse Glimmer on one Arc Pro B70★

    A vLLM-XPU and DFlash recipe for Muse Glimmer 30B on a single Intel Arc Pro B70, reporting 278 aggregate tok/s across eight clients and an 840.8 tok/s burst peak at concurrency 96.

    @mgaruccio

    GitHub

    Local & open models

  3. 0458

    Muse Glimmer 30B stretched to 512K context★

    My fun weekend project was to try to make the new Muse Glimmer 30B work with a longer context, deciding to go for 512k first. I had expected the usual YaRN shenanigans and maybe a LoRA. I couldn't have been wrong more. Upon closer look, Glimmer turned out to be rather unusual architecturally. The thing that make long-context adaptations painful in other models, full attention layers with token position encoding, it simply not there. Instead, only 2048 tokens-wide SWA layers have RoPE, and full GQA attention layers have no position encoding at all. It appears the model is trained to work with long-distance token relationships inferred from the context and SWA layers. It's a rather bold architecture bet, but it seems Meta managed to pull it off. As a result, the model architecture appears to be uniquely suited for context extension by simple mechanical means. To change model context length from stock 128k to, say, 512k, you need only to change “max_position_embeddings” config setting from 131072 to 524288. What confuses other models, like Qwen3.5 family, Glimmer just takes into its stride. I spent close to 70h of compute on DGX Spark to test stock model with extended context on a

    u/mr_il

    Reddit post

    Local & open models

  4. 0435

    Local credit card statement analysis with Glimmer★

    Using @AIatMeta's Muse Glimmer all locally to process personal monthly credit card statements. Your data belongs to you! Try different agent tasks using your favorite apps / harnesses with Ollama.

    @ollama

    X post

    Local & open models

More GitHub

See all →
  1. 1074

    Ziggy, a 24/7 voice assistant on Muse Spark

    An always-on laptop voice companion: local Porcupine wake word, local Whisper speech-to-text in Hindi and English, Muse Spark via the Meta Model API as the brain, offline TTS and local conversation memory.

    @TanayYadavDev

    GitHub

    Agents & automation

  2. 1066

    Muse remote-control bridge for Intel Macs

    Since Muse for Mac ships only for Apple silicon, this small service lets Muse's cloud VM screenshot, click and type on an Intel Mac, compressing each 5K frame to about 150 KB and handling Retina coordinate scaling.

    @LilMuh

    GitHub

    Errands & personal agent

  3. 1040

    CursorBench 4.0 score-vs-cost report

    A self-contained visual report comparing CursorBench 4.0 score against cost per task for Opus 5.5, Fable 5.1, Grok 4.7 and Muse Spark 1.3, where Muse Spark 1.3 Max scores 41.6% at $2.64 per task. GPT-6 points are clearly marked as estimates.

    @dominicletz

    GitHub

    Benchmarks & research

  4. 0995

    BitNet Gateway: cheap CPU triage, Muse Spark decides

    A hybrid FastAPI gateway where a 1-bit BitNet layer on CPU filters routine traffic and Muse Spark 1.3 is called only for sales, urgency, money or low-confidence cases; the author estimates the local filter handles about 60-70% of volume.

    @rafaelnovaes22

    GitHub

    Agents & automation

Curator picks

  1. 1046

    Medical bills audited line by line, $4,000 saved★

    Got Muse logged in to my medical provider’s portal, he pulled the itemized bills, and questioned every line. So far he’s found several times I’d been double billed, asked for some discounts and has saved me over $4,000. If your moat is bureaucracy, you’re cooked.

    @Ryan_Holdaway

    X post

    Errands & personal agent

  2. 1013

    Shop Pay agentic checkout on every Shopify store★

    We are excited to announce we are partnering deeply with Muse to enable agentic checkout with Shop Pay on all Shopify stores, offering people an easy and delightful way to shop and check out with Muse.

    @tobi

    X post

    Business & commerce

  3. 1009

    Private e-book library app from Google Drive★

    Muse built me a private library for the e-books and articles in my Google Drive. Everything is organized by topic, and each section opens onto its own subcategorized shelves. Each book opens like a real book and is readable in-app

    @chiasmus_cap

    X post

    Apps & websites

  4. 1007

    Plumbing company run by a Muse agent★

    I still can’t believe I can run my plumbing company with an agent so easily. I send this message to my Muse agent while in bed at 6am. And it: updates my job board, texts customer, updates office manager who arrives at 8am in slack Notifies technician

    @HouseHackerJon

    X post

    Agents & automation

ChatFormTgmlabsAdvertise hereChatFormTgmlabsAdvertise hereChatFormTgmlabsAdvertise hereChatFormTgmlabsAdvertise here