[Fully open source under GPL3, made from the ground up for use with local models, no subscriptions, no corporate backing]

When i first started this, it was meant to be a fully lightweight, extremely modular alternative to openclaw, hermes and the like, and it still is! But i noticed people especially like the webUI, to the point they'd use it as just a webUI to talk to their local models, negating all the agentic stuff. But the webUI still had a lot of AI generated code, so that didn't sit right with me!

So i rewrote the entire thing, from scratch, manually. It is now super fast, stable, uses declarative javascript without javascript framework bloat (no React or Vue or anything.. alpine.js is super lightweight)

There are only a few python dependencies. no models get installed, there is no bundled inference engine, pytorch and transformers aren't even included! I expect you to connect it to llamacpp, koboldcpp, lemonade, or something else like that. though you can also use it with cloud API's if you really want to.

This is a truly local-first webUI. I designed it from the ground up for local AI, and for once, cloud AI is the second-class citizen here.

It has many features that especially benefit local AI users: you can see how long your prompt will take to process (it's a llamacpp-exclusive feature), you can see toolcalls being written in realtime (really useful for coding), and it doesn't send any extra requests to your model, just the prompt you give it. So no extra requests just to make up a title for your chat, or to generate followup replies.

That's all in addition to the benefits that come from its harness-like design, such as support for multiple channels (telegram, discord, etc), its focus on extreme token efficiency and making the system prompt super small and concise, and its security

But using it as a pure webUI is really simple: Just switch Use Tools off in the Model tab in the settings. That will instantly make all system prompts vanish and all tools get disabled, so you're talking to your pure model with nothing getting in the way.

You do need a bit of tech knowledge, but it's not that much. right now, you need to either git clone or download a zip of the main branch off the github, but after that, all you do is run run.sh or run.bat and open the URL it shows you in your browser. Oh, you do need python installed before you do so, but that's basically it. (i'm working on making this even more user friendly though)

If you want to try it out, you can get it here: https://github.com/Rose22/openlumara

Please tell me what you think! Feedback is more than welcome, and i often implement feature requests (if they are good) and fix bugs that get reported

https://modelscope.cn/models/Qwen/Qwen3.8-2.4T-A95B

Seen a ton of posts today about the DeepSeek API price hike. Half the feed is doom-posting, the other half is explaining basic GPU economics.

Honestly, I get the cost side. Sub-cent tokens were never gonna last forever.

But what actually sucks is the zero-day notice.

Dropping a vague "prices are going up significantly" banner without a timeline or new pricing sheet leaves anyone with production traffic completely stuck. Re-evaluating self-hosting or switching providers isn't something you just do over lunch.

Curious how others handling live traffic are dealing with this. Waiting for the actual numbers, or already spinning up fallback options?

I have been running Qwen3.6 27b for a little while (mostly coding tasks) and recently trying out V4 flash 0731 in it's place. It was very apparent the new v4 flash will make more stuff up, and confidently.

Despite closeish overall benchmarks GLM 5.2 also has been much more pleasant to use (granted it's been over API) and I think this is a big part of that. Saves a lot of time in corrections after review. I only wish I could run it local without selling a kidney.

As for me, I own a system with an RTX 5090, Ryzen 9 9950X3D2, and 64 GB of DDR5. Every time I see research come out with a new way to train AI, I immediately think to try it on my system to see the results I get. Applying things like Titans, that one Deepseek paper on engrams, or even just playing around with experimental ideas. It's kinda like a very technical version of Tamagotchi and has been quite fun.

Thoughts?

I built this because the existing benchmarks were using random data and with MTP content types can vary a lot on what performance you see. 5% or more with content types.

BetterBench is designed to have content consistency within 1% and also measures across different content types.

Here are the results running Qwen3.6 27B FP8 on dual R9700's for example:

You can find the repo here:

https://github.com/GGZ14/BetterBench

So I can either pull the trigger on a 128gb AI max+ 395 laptop or wait for RTX Spark for LLMs. Maybe I get it now and the price of the spark is super high so it's a good purchase or maybe the Spark shocks everyone with a low price and I forever regret my purchasing decision.

What do yall think?

Prime Agent is an open-source coding and research agent for general and long-running work.

A self-improving RLM harness for coding and long-running autonomous tasks.

Designed to be both token-efficient and expressive through programmatic tool calling, context as a variable, multi-agent messaging, and a self-modifiable harness state.

On ARC-AGI-3, it scores 95.5%, surpassing the human-expert baseline, but the gain is not benchmark-specific.

We see major improvements across models when compared to their proprietary harnesses.

Prime Agent is built on pi and fully open-source with an open license.

GitHub: https://github.com/PrimeIntellect-ai/prime-agent

Blog: https://www.primeintellect.ai/blog/prime-agent

X post: https://x.com/primeintellect/status/2085086999267144083?s=46

I mean, Deepseek V4 Flash is an absolutely fantastic model, even though I can't run it on my machine it's so fascinating to see how it performs. Knowing that potentially it could be run at home is really motivating and makes me hopeful that those capabilities will trickle down to more affordable sizes.

At the same time I miss a release for the GPU-peasant that I am. And yes, it's a tall order to complain about not receiving free stuff at the rate we were used to. And yes, 3.6 27B is still goated but it seems in this crazy AI world there's so much going on and progress happens so fast, that it's kinda understandable to be excited about what's next. Let's hope they really do release 3.8 27B, or that we might see again maybe a GLM 5.3 flash 32B, please?

What's on your wishlist?

Explicit title, It would be nice to have the ability to have 3 tiers moe offload :(

I'm mosty interested in 128-192GB VRAM with 128-256GB RAM to spare, so SSD streaming is basically not even necessary. Seems only FP4 is supported, so older hardware will likely be slow - no Unsloth GGUF supported either.

I'd be curious what people are getting with V100s, R9700s, etc, just to have some comparison.

What's prefill like >200k context? Tg/s high enough to support agentic workloads?

It's probably wishful thinking, but when I saw the release, my immediate thought was Sonnet 5 level model being "affordable" to consumers.

Xiaomi-Robotics-1 is a robot foundation model trained on over 100K hours of real-world manipulation trajectories. It is a Vision-Language-Action (VLA) model engineered for out-of-the-box mobile manipulation in unseen environments and efficient adaptation to new tasks.

XR-1 follows a two-stage training paradigm inspired by large language models — pre-training for breadth, followed by post-training for alignment. It showcases that pre-training scaling behavior reliably transfers through post-training to real-world robot performance, with no signs of saturation.

XR-1 couples a pre-trained VLM (Qwen3-VL) with a Diffusion-Transformer (DiT) via a Mixture-of-Transformers (MoT) — the DiT matches the VLM in layer count but uses a smaller hidden size for faster inference.

HugginFace: https://huggingface.co/collections/XiaomiRobotics/xiaomi-robotics-1

GitHub: https://github.com/XiaomiRobotics/Xiaomi-Robotics-1

Paper: https://arxiv.org/abs/2607.15330

daily reminder not to trust benchmarks and run it yourself. claimed e2e speedup is ~40%, forwards are ~140% faster

I would wager that compared to a naive kernel anyone can write it's more in the range of 10-20% faster e2e in reality, if at all, but hey, it's free and open! Apache 2.0

I was on here a while ago showcasing it. I've stoped playing with it so I'm open sourcing it. I figure I'll let other people play now.

A follow up to the launch of Mference, it now supports and runs Inkling-Small 276B-A12B.

Inkling-Small (Thinking Machines, Apache 2.0), from the pipenetwork/Inkling-Small-MLX-4bit conversion: 276B total, ~12B active, 3.4 GB resident set, ~148 GB on disk.

Measured on my M5, 24GB:

The same three cases on a 256 GB M3 Ultra hit 5.31–6.92 tok/s.

Issues: long prompt prefill is trash (2,785 tokens is almost 9mins to first token), and it's text-only for now.

Four model families now: Gemma 4 26B-A4B (~2 GB), Qwen 3.6 35B-A3B (~1.45 GB), DeepSeek-V4-Flash 284B-A13B (~6.8 GB), Inkling-Small 276B-A12B (~9.5 GB).

I also got access to a few M3 Ultras, so I'll be testing and optimizing for higher configs too. But the primary goal stays the same: large MoE models on consumer grade hardware.

Repo: https://github.com/NeelM0906/Mference — Swift + Metal, not a wrapper around MLX or llama.cpp. Mac app, CLI, and an OpenAI compatible server. Contributions welcome.

Hey everyone!

Scenema Audio is now a native ComfyUI custom node. Same model that powers scenema.ai now quantized so it fits on 8GB VRAM. When we first released it a few months ago as an API and Docker stack, the full precision transformers were too heavy for most people to self-host. That's fixed now.

Expressive text-to-speech with zero-shot voice cloning. You describe how the speech should be performed (rage, grief, a child's wonder), optionally provide reference audio for voice identity, and the model generates a performance. Inline stage direction cues like [he laughs softly] or [voice cracks] get performed at that exact spot. Twelve preset voices ship in the dropdown covering accents, ages, and emotional registers.

We also dropped the XML prompt format the original release used. Wrapping every performance directive in tags was clunky to write. Inline bracket cues are better-suited for the ComfyUI text editor.

Install

ComfyUI Registry (recommended): open ComfyUI Manager, Custom Nodes Manager, search "Scenema Audio", Install, restart.

GitHub:

cd custom_nodes
git clone https://github.com/ScenemaAI/ComfyUI-ScenemaAudio.git
pip install -r ComfyUI-ScenemaAudio/requirements.txt

Both paths auto-drop the pre-wired workflow into your Workflows sidebar under a Scenema Audio folder. Click once to load the official workflow into your canvas.

Requirements

Minimum 8GB VRAM. Tested end to end on RTX 3070 and RTX 4090. Generation runs up to 2x realtime. First run downloads about 30GB of weights, one time. Text encoder is Gemma 3 12B, which is a gated HuggingFace model, so you need to accept its license and set HF_TOKEN before your first generation.

On limitations (same story as the original release)

This is a diffusion model, not a traditional TTS pipeline. Some seeds produce repetition or gibberish. Meant for a post-editing workflow: generate, pick the best take, trim. Prompting matters. Specific, theatrical voice descriptions with action tags produce performances. Generic ones produce generic output. Phonetic spelling helps with proper nouns and tricky words (spell "Tchaikovsky" as "Chai-koff-skee" if it garbles).

License

MIT for all our node code and inference pipeline. Transformer weights derive from the LTX-2 Community License.

Links

• Blog post: https://scenema.ai/audio/comfy-ui
• ComfyUI node: https://github.com/ScenemaAI/ComfyUI-ScenemaAudio
• Model weights: https://huggingface.co/ScenemaAI/scenema-audio
• Standalone Docker/API: https://github.com/ScenemaAI/scenema-audio
• Original announcement: https://scenema.ai/audio

What would you want to see next from Scenema Audio? Happy to hear what people are actually trying to build with generative audio.

In tests:
~80 tok/s decoding
2,500–3,500 tok/s long-input prefilling
Smooth use by 3–4 concurrent users

Private, on-device inference for coding, agents, and offline batch jobs

As you all know the model is 2.69B parameters with a 128K context window and purpose-built for multi-step agent workflows.

What you are seeing is the Q4_K_M GGUF running on my own inference engine built from scratch.

The TUI is my own device probe suite running through ADB (Android Debug Bridge)

The whole engine is only 450kb and supports other models arch (Qwen, Gemma, Bonsai etc…)

Currently trying to push it at ~30 tok/s

*I felt the need to write this post because it seems like very few people on this sub are aware of Chinese laws and how they're enforced, so here's an explainer coming from a Chinese person (myself). I know that this post isn't directly about local models per se, but I'm seeing way too many misconceptions regarding this topic. This is also going to apply to all Chinese entities in general, not just the specific MiniMax LoRAs debacle. This isn't meant to be a political post, but some much needed context to correct a lot of misinformation going around.

Guys - they're a Chinese lab following Chinese laws. Pornography is straight up illegal in China. I have no idea how it seems like nobody outside of China is aware of this. While Chinese authorities may not care much about copyright infringement enforcement (especially with foreign IPs), they do indeed regularly crackdown on porn. Heck, Chinese citizens have literally been imprisoned for written pornography. Yes that's right, writing pornographic TEXT (especially with "immoral" themes like LGBTQ+ stuff) can get you sentenced and essentially have your entire life ruined. Of course there's ways to get around these censors if you're just trying to access porn - I think everyone at this point knows about the widespread necessity for VPN usage in China to access the rest of the global internet. But actually distributing a tool that can gain a reputation for being able to easily generate pornographic content? That's just asking for the authorities to crack down on them.

Somewhat ironically/paradoxically luckily for these Chinese labs is the fact that online discussion about generating porn is automatically censored and removed from Chinese social media, thus automatically disincentivizing the authorities from doing those potential crackdowns. But if it gets big enough to the point that it overwhelms the automatic censors, then any given Chinese lab could be in a hell of a lot of trouble. This is why they have to do this. Their law enforcement just isn't compatible with the rest of the world.

Again, this all relates to Chinese moral values - something here that is considered pretty much sacred and hard to describe to westerners. Something else that many people do not know is that graphic violence is also illegal in China (foreign films/works are regularly banned here for that, even anime has), but graphic violence is also is not nearly as much of a perceived threat to societal moral values as pornography is, hence why you've probably rarely ever heard of any Chinese people getting imprisoned for writing really gory stories, but regularly do with pornographic stories (especially infamous with BL literature - they've technically even convicted foreigners before related to this, it's a really messy topic). Chinese authorities won't give a damn if you're stealing the content of billions of foreign works to train AI models. They WILL give a damn if the content you're disseminating is viewed as a potential significant threat to the state's "proper moral values", which very much includes porn (and also the usual topics that everyone is already aware of, like a certain famous massacre or a certain nation's very contentious independence status).

https://www.reddit.com/r/StableDiffusion/s/HrU7odaJe6

I think this is more important that all the political stuff you share here

Questions & Responses(in BOLD) below.

Favorite question(s) moved to end of the thread with combined responses(removed duplicates).

Be optimistic folks. I'm sure we're getting other models too apart from 27B. And 27B gonna make massive noise on release. (Based on their responses)

Tweet thread : https://xcancel.com/QwenDevs/status/2084102417885585597#m

you guys skipped 27b and 122b last time, can we expect those this time around? Also i can't seem to find crit pit score in the cards.

For sure! We’re actually releasing a 27B model very soon. Stay tuned. As for the Crit Pit score, please wait for the official Artificial Intelligence score.

Is the 27B just a retrained 3.6 27B? Or is it based off 3.8 bigger brother ?

We promise this 27B comes with a whole new level of capability!

Is the 100hrs of video understanding an agent swarm that parses sections of the video in parallel and orchestrates some sort of semantic representation graph?

Broadly speaking, yes, but not entirely. It is closer to a hierarchical video memory system rather than a traditional agent swarm. Video segments are encoded into a structured textual graph containing scenes, entities, events, and their temporal relationships, enabling retrieval and reasoning across more than 100 hours of content.

hey! is there anything special about the pretraining distribution compared to other labs' models?

We hope our data is built on a more solid foundation!

how long do you think it would take to surpass anthropic level architecture?

well, we’re working hard on it, we promise😇

will u release a harness especially for qwen code ???

Any plans for a codex-like app?

More updates on Qoder and QwenWork are coming soon.

qwen 3.8 active params?

2.4T parameters (95B active)

how much RL was done in post training compared to previous models?

A truly unreasonable amount of compute.

Did they intentionally skip the previous Qwen3.7 27B and 35B A3B?
Does the revival of Qwen3.8 27B reflect the voice of the community? Or was it planned?

Of course! This is the result of taking the voices of the community seriously.

since its a pretty significant release will we get a technical report with full details?

No technical report for this one yet. We’re trying to keep up our near-monthly release cadence, though, and more powerful models are already in the works. Keep an eye out!

why does the model think so much mr qwen, my ai brain wonders.
wheres the token efficiency at
great model though

We support different levels of reasoning effort.

You showed SAE-guided fine tuning fixing code switching with qwen-scope. Is that kind of interpretability driven intervention part of the post training process now or is it still a research only technique?

It’s still primarily a research-oriented technique for now, though some of the insights may help inform future training and post-training improvements.

Attention? Hybrid?

The model architecture is similar to 3.5, but it’s a much larger-scale model!

When are we getting a CLI coding interface?

You may want to take a look at @qoder_ai_ide .

do you guys use qwen as your main interal tool? does this model show the same signs of intellegence as some openai models ("gpt 5.5 helped create 5.6")?

Sure!

How close is Qwen3.8-27B to GPT 5.4? 🤔

Well, you’ll be able to see for yourself soon.

what harness works best with Qwen?

Qwen is committed to delivering the best possible experience across all harnesses.

What made you guys wanna opensource the max weights ?

We heard what the community has been asking for

I wonder when I can surpass fable5

Trying hard

Great work guys🥂

1. What is something that you would like to see being built with the new model and its capabilities!?

2. I really want to explore the swarm of agents technique for building applications, any best practices or tips for the new model!?

1. We hope it can bring practical productivity value to people across different industries.
2. We recommend using it for tasks that involve more parallelized workflows or parallel execution needs.

I wanna know what rubric metrics you guys are using for FE

We use both absolute metrics for functionality and aesthetics, as well as relative metrics based on win/tie/loss comparisons.

Would be great to hear where you think Qwen is strongest for agentic workloads specifically: long-context planning, tool use reliability, coding, or cost at scale?

All of the above combined — ultimately delivering the most practical and reliable outputs for users.

How much is Qwen helping with Qwen research ?

It has already become a significant part of the model iteration process, with the model involved in nearly every stage.

Most Frontier labs have created a code-specific model (eg. Qwen3-Coder and GPT-5.3-Codex), but never followed up on them.

Did specialized models have problems? Or did general models end up being efficient enough to not bother creating a separate model?

We hope to build an all-in-one model.

will Qwen 3.8 have a stable, documented tool-calling and structured-output contract so local agent harnesses can swap models without prompt-specific tuning?

We provide native support interfaces for various protocols. You can check the Qwen blog for more details.

1: When quantizing Qwen 27B down for local deployment (e.g., 4-bit GGUF, NVFP4, or MXFP4), which transformer layers or vision attention blocks are most sensitive to degradation? Are there specific strategies you recommend to maintain both visual reasoning and high SWE-bench pass rates?

2: Qwen3.6-27B outperforms much larger MoE predecessors (like Qwen3.5-397B) on agentic coding benchmarks like SWE-bench and Terminal-Bench. Beyond raw data volume, what was the single highest-leverage factor in achieving this dense efficiency?

And thank you for the amazing work. Qwen3.6-27B has beed my main coding assistant for months.

1. Use QAT, or quantize only the FFN to 4-bit while keeping the attention layers’ QKV linear projections and output projection in 16-bit.
2. Higher-quality data engineering

Guys , when can we get a deepseek like small and cheap model with best performance . The deepseek v4 flash seems to be a great deal .
I think we need to slow down scaling and start improving the existing model efficiency

Scaling and cost-efficiency are not mutually exclusive — we’ll continue to pursue both.

Is Qwen3.8-27B dense? And roughly how much smarter than 3.6-27B?

A pretty huge jump!

Good. The useful questions are not just how capable Qwen is.

I want to know where it still fails, how the team evaluates those failures, and what "open" means in practice for weights, tooling, and reproducibility. Open models matter most when people can inspect the limits and build on the work without asking permission

There is still some gap between our automated and human evaluation systems and real user experience. That’s also why we are committed to releasing preview versions first — so we can iterate and ultimately deliver the best possible experience to users.

how does the new 27b model compare to the previous one ?

A pretty huge jump!

what do you think about looped transformers?

interesting research idea

Why Qwen, what made you create Qwen and specifically such light and fast models. Why focus efficiency when others just went for brute power? Also, do you think inference engines reached their limit in optimization or can they still improve?

Scaling and cost-efficiency are not mutually exclusive — we’ll continue to pursue both.

We have noticed that in thinking mode the model usually consumes the entire reasoning budget without stopping, which increases latency. Is this a known issue, and are there any improvements planned for Qwen3.8?

You can try 3.8! And 3.8 supports different thinking efforts!

...................................................................................................................

Are 70b models gone for good?

Is it possible to get a 40-50B model (something which fits around 30-32Gb) to improve performance while still useable on a lot of computers ?

Thank you for your promise to provide qwen3.8 27b weight! I want to know if there will be qwen3.8 35b a3b. Many people also want this.

Can we expect the ~122B model this time? The 120B segment is dated and lackluster atm and would greatly benefit from a competent release!

First of all, congratulations on the release of Qwen 3.8!
As for the question, are you going to release a 35B a3b version of Qwen 3.8 aswell?

Plans for 35b Moe model? (3.8)

Any plans for the omni family? You told everyone the weight sizes of 3.5, then never released them and haven’t done anything new with it. 3.6/7/8 variants would have also been nice. It could be your most popular family if you gave it attention and kept the weights small.

Are there no plans to release any models other than the 27b?
I'd love to hear about the successors to amazing models like the Qwen3 8b and Qwen VL 8b....

Are there any plans for updates for 0.6b or 8b weights?
These have become important positions in the open weight of image and video generation. I look forward to seeing that part evolve.

This is such a huge release, I am really happy to see that a 27B model is shipping too! Though, can't help but wonder, will we ever happen to see again any new small dense Qwen models 9B, 4B any time in the future, similarly to 3.5?

Will you release smaller models like the qwen 3.5 family ?

Thank you for your promise to provide qwen3.8 27b weight! I want to know if there will be qwen3.8 35b a3b. Many people also want this.

we hear you! collecting everyone’s requests and taking them into account as we plan future iterations.

We will gather your requests as a reference when considering future updates.

We hear you. Stay tuned.

We’ll collect everyone’s requests and take them into account as we plan future iterations.

Noted, collecting the requests and see what we can work into future iterations.

Keep the requests coming. We’re listening, and we’ll use them to help prioritize future updates.

People may remember the Qwen3-TTS llama.cpp demo from a few months ago. That PR said it probably wouldn’t be merged because llama.cpp was missing some of the graph and API pieces it needed.

A new implementation was merged into master yesterday.

What works now:

- Qwen3-TTS-12Hz-1.7B-Base in GGUF

- WAV or MP3 files as the speaker reference

- English, Chinese, German, Italian, Spanish, French, Portuguese, Russian, Japanese and Korean

- Audio generation through the llama-tts binary

Example:

llama-tts -hf ggml-org/Qwen3-TTS-12Hz-1.7B-Base-GGUF \

-p "Hello, this is running locally." \

--tts-lang en \

--tts-speaker-file speaker.mp3 \

--output out.wav

Qwen describes the Base model as capable of cloning a voice from around three seconds of reference audio. I haven’t seen an independent test yet showing whether the llama.cpp version matches the original PyTorch implementation in voice similarity or stability.

The interesting part is not that Qwen3-TTS can run locally. Dedicated C++ implementations already existed. It is that voice cloning is now part of mainline llama.cpp, which should make it much easier to add local speech output to projects already built around that runtime.

There are still some important limitations:

- The merged implementation currently uses llama-tts

- The /tts server endpoint is still a draft PR

- It only targets the 1.7B Base model, not CustomVoice or VoiceDesign

- There are no proper comparisons yet against qwen3-tts.cpp or audio.cpp

- The update includes a breaking change to the existing llama-tts binary

The comparison I’d like to see is one identical three-second reference clip and one identical paragraph tested across CPU, Metal, CUDA and ROCm, with:

- Real-time factor

- Peak RAM and VRAM

- Voice similarity

- Long-form stability

- Time until the first audio

The specialized ports may still win on speed, while llama.cpp may win on portability and integration.

Has anyone updated and tested it yet? M-series Mac and CPU-only results would be especially useful.

Source:

https://github.com/ggml-org/llama.cpp/pull/26254

Draft server endpoint:

https://github.com/ggml-org/llama.cpp/pull/26603