Live data from Hacker News

Muse Glimmer: 30B-parameter model optimized for always-on local agent workflows

research.meta.ai

651–660 of 675 posts

Re: Muse Glimmer: 30B-parameter model optimized for always-on local agent workflows

#651

Earlier quoted context omitted.

Llamscpp provides reasoning budget and message. You can use the message to redirect it. Once you get the agent and message consistent,itll keep moving.

You can use any message you want, but the model was tested to react reasonably well to the specific token sequence of "\nConsidering the limited time by the user, I have to give the solution based on the thinking directly now.\n .\n\n" (from a Alibaba paper, struggling to find it now) Edit: arXiv:2505.09388 Qwen3 Technical Report

Since i have tools to prune context and run subagents, i just tell it to do either since both require summarization which is usually what it needs to avoid the long if...then chains

Re: Muse Glimmer: 30B-parameter model optimized for always-on local agent workflows

#653
post #454

Meta is rocking AI. As of last week I have been using their excellent muse coding harness with their model Muse Spark 1.2. Starting this morning I am running their new local 30B model muse-glimmer on my old MacMini 32G using Ollama (remember to increase the context size!) and pi coding harness. I am getting good results with muse-glimmer running locally, with the caveat that everything runs slowly (e.g., give it a ta…

Friends Don't Let Friends Use Ollama https://news.ycombinator.com/item?id=47788385

From the Ollama docs for this new model:

Ollama's MLX engine provides state-of-the-art performance on Apple Silicon, with support for DFlash and image input:

ollama run muse-glimmer:30b-mlx

Re: Muse Glimmer: 30B-parameter model optimized for always-on local agent workflows

#654
post #516
post #264

Earlier quoted context omitted.

I am working on a project where we have to classify customer calls into more than 10 categories. As the client wants everything locally I tried a few local LLMs. Gemma turned out to be the best model for this task. The classification accuracy is impressive, and the client is happy that I am using an American model.

I guess the client is American.

Not necessarily. Except for SpaceXAI's (haha) models, there's less risk of reality distortion in Western models. Probably doesn't affect his use case but you wouldn't really want to ask Kimi K3 for a history of China for example.

Re: Muse Glimmer: 30B-parameter model optimized for always-on local agent workflows

#655
post #629

Earlier quoted context omitted.

I've been building this for the last 6 months or so. I've basically got it working. The model is not the issue, the infra is. Keeping everything in context just isn't possible and LLMs, even Fable, don't mode switch well. To get around this I've built a database software that ingests as much digital information as possible, and annotates it, then creates timelines with resolution gradients (longer ago = less resoluti…

I’m curious why you don’t just use them like a Meeseeks box, rather than compressing and context stuffing into one. One only checks and categorizes your emails, another one for each category of email or even subcategory, one that only handles calendar additions, a different one to check it and notify you; you can go infinite with it. Hell, I’ll have one instance find a file and read it into the context of a different…

I sort of do. For scheduled things I am using Goose and subagents per task. So I wake up at 6 am to a briefing that was composed by a ton of different agents. That works well in a narrow programmatic setting, but it breaks down in certain natural conversation context. For instance voice control of something like "text my sister that I'm running late" - self hosted models are terrible at figuring out who my sister is. I could annotate by hand but that is a never ending list that I'll always be one step behind. Another thing is just proactivity. For instance, if someone's birthday is coming up, the briefing may remind me a week early to get a card. But it will only do that if it's someone that I have a close relationship with, which it calculates by the magnitude of the cluster of conversation with them in embedded space.

I'm not confident it's that most efficient way to do it, but it's quite a bit of fun.

Re: Muse Glimmer: 30B-parameter model optimized for always-on local agent workflows

#656
post #294

Remember when we needed 200 servers for an enterprise website because Apache used one process or thread per connection - and Nginx collapsed that into a single box overnight? That moment for LLMs is near. It’s going to move us from the big iron era of AI to small portable brains. Nature has already proved it’s possible with 20 watts and very little heat generation. And I think the data center buildout will end in car…

brains do it with 20 watts because theyre analog. llms require massive amounts of power and this isnt changing any time soon without a breakthrough

If you adjust for writing speed, this model is already more efficient than humans. It can run at 233 tps on a 5090 which is roughly 10k words per minute compared to human typing speed of 80 wpm. If you duty cycle it down from 575 watts of 5090 to human speeds it’s about 5 watts.

Re: Muse Glimmer: 30B-parameter model optimized for always-on local agent workflows

#657

Earlier quoted context omitted.

Poolside Laguna was quite good too (if you look beyond some of the teething issues). Had Deepseek V4 Flash 0731 not launched, their latest Laguna release was really intelligent at non-coding tasks and it would have been my go-to model for my local workloads.

For me Laguna frequently slightly corrupted text then it would be unable to notice the difference and get stuck making the dumbest conclusions. Thinks like typoed directory or function names. It was a great model other than that, but I ended up just going back to Qwen3.6

Make sure you've got the latest updates - both Poolside and Unsloth updated about a week after release, and that you're running via llama.cpp (I've noticed on the same model and same command line arguments, ik_llama.cpp loses quality for me).

Also just in case you didn't see it, Laguna S 2.1 was having issues on MXPF4 but people on Q4 and Q6 couldn't repeat the problem.

Re: Muse Glimmer: 30B-parameter model optimized for always-on local agent workflows

#659
post #629

Earlier quoted context omitted.

I’m curious why you don’t just use them like a Meeseeks box, rather than compressing and context stuffing into one. One only checks and categorizes your emails, another one for each category of email or even subcategory, one that only handles calendar additions, a different one to check it and notify you; you can go infinite with it. Hell, I’ll have one instance find a file and read it into the context of a different…

I sort of do. For scheduled things I am using Goose and subagents per task. So I wake up at 6 am to a briefing that was composed by a ton of different agents. That works well in a narrow programmatic setting, but it breaks down in certain natural conversation context. For instance voice control of something like "text my sister that I'm running late" - self hosted models are terrible at figuring out who my sister is.…

I was afraid my description sounded like agents, and it kind of is, but not like most implementations. Most use a “boss bot” to craft a prompt/system message and launch the model, and sometimes they redo it every time it launches the agent. It’s a low effort attempt that’s immediately flawed because it uses LLM output for LLM input. It can look like it’s working for some time, but the perplexity guarantees it’s a roll of the dice. That’s what eats away at these kinds of projects. “It was doing great until it rm’d prod.”

Run the same exact prompt 100x in a single step test (one prompt, one response), hash the full responses, and you’ll see 10-50+ unique responses. The higher the unique the worse your prompt; focus on the system. A highly tuned system prompt will result in one response, even at a temperature of 1.0. Really. Once that’s done that’s the only thing it does and it’s the only one that does it and it never changes. Other LLMs that call ‘check_email()’ are unknowingly just passing a prompt to the specialized one.

I use the API directly, craft a small Python script for the API call and task interface, then hyper-optimize the system/user prompt using test scenarios and automated loops. My system prompts rarely/never contain complete sentences, yet include all the tools/functions and requirements.

Make your error messages user prompt instructions, not errors. That’s why “agent optimized” models exist. Chat models are primarily trained on conversational text, meaning the stackoverflow “How do I fix ‘too many levels of symbolic links’?” -> Explanation/resolution. It’s far less on “# ls broken_loop” -> “# ls: cannot access ‘broken_loop’: Too many levels of symbolic links” -> “# namei -l broken_loop”

It’s not that the good ones are bad, but you’re leaning on the million training documents rather than the trillion.

Anyway, go that route with your system. Think about it more like automating a factory floor rather than hiring interns.

The least efficient methods, by definition, have the most room for improvement, which means they have the greatest reward potential, but for that one “eureka” moment. The path less taken is often interesting, but the ill-advised path still has fruit on the trees.

Post reply on HN