GitHub radar
Top 5 Hugging Face Models This Week
This week three of the five models in my list answer not with text but with a number, and I checked them on my own support tickets. The other two are about images and video, and I ran both of them myself as well.
I put Clef from Cloudflare on my own test support tickets and gave it several questions at once: is the client angry, does it need escalation, what type of problem is it. The model does not write an answer, it returns a probability for every option right away, and it does this in one pass with 27 billion parameters. By Cloudflare's own table, on the BANKING77 test (sorting of banking requests) Clef scores 94.2 against 79.7 for the paid Jev, which it competes with directly. I liked that it does not get confused on narrow sorting, but for questions that need general knowledge I would not choose it, there the paid Jev wins by a wide margin.
Why a vibe-coder should care
If your product has a stream of requests that need sorting by category and urgency, this model can replace a paid API, the license is Apache-2.0, the weights are open, and it runs on your own machine.
You need a Mac with 32 GB of memory or a GPU with 24 GB of VRAM.
Open on Hugging FaceI downloaded LTX-2.5 from Lightricks and ran a couple of prompts through it for a video with several scenes in a row. The model keeps the characters, the light, and the voices the same across scenes, and this is the main difference from the previous version. Instead of the usual VAE there is a diffusion decoder here, the picture is noticeably cleaner, and on-screen text is readable. Ready workflows ship right inside ComfyUI, so I did not have to assemble everything piece by piece.
Why a vibe-coder should care
If you need a clip with several connected scenes, a trailer, a short video for social media, this is the first open model where you do not have to stitch the pieces together by hand. It is free for companies with revenue under $10 million a year, above that a commercial license is required.
A GPU with 24 GB of VRAM or a Mac with 32 GB of memory; for weaker cards there is a lighter offload mode.
Open on Hugging FaceI set up Qwen3.8-27B from Alibaba locally and gave it a screenshot of code plus a question in Russian. It natively understands images and video, not only text, and it can decide on its own whether to think fast or think long before answering. Compared with the previous Qwen3.6-27B the gain is noticeable, on the SWE-bench Pro coding test it is 61.7% against 53.5%. For local use there are already more than 700 quantized versions, including an official one from unsloth, so setting it up is not hard.
Why a vibe-coder should care
If you already run local models and want a version that understands images together with text, this is the strongest open option in the 27B class. The 4-bit version takes about 17 GB, a Mac with 32 GB of memory handles it without the cloud.
A Mac with 32 GB of memory or a GPU with 24 GB of VRAM.
Open on Hugging FaceI downloaded d1-3B from LiquidAI, only 3.1 billion parameters, and tried it on comment moderation: spam, toxic, on topic. It also does not write text, it returns a calibrated probability for every question right away, including on images, not only on text. By LiquidAI's own test (Decision Index) it beats models with 4 and even 9 billion parameters. On an RTX 4090 the answer takes 8 milliseconds, on an Apple M5 Pro chip 30, and I liked that it does not need a powerful graphics card for this speed.
Why a vibe-coder should care
For moderation, routing, or checking images in real time, this model is cheaper and faster than a chat model, and it fits on a regular laptop.
A regular laptop with 8 GB of RAM or more.
Open on Hugging FaceI set up Laya from Convai Innovations (the handle on Hugging Face is convaiinnovations) and ran a few test support emails through it with standard questions. It also answers not with text but with a probability in one step, the English version has 421 million parameters, and a separate multilingual version with 322 million covers over 100 languages. On a GPU the answer to one question takes 32.8 milliseconds, the paid Jev needs 236 to 276 milliseconds for the same question, and on a plain CPU, without a graphics card, Laya needs 0.2 to 0.5 seconds. The one thing that bothers me is that on questions with 20 or more answer options it starts to confuse them, and here fine-tuning on your own data raises accuracy from 0.362 to 0.766.
Why a vibe-coder should care
If you have a stream of emails or comments that need sorting by department or urgency, this is a free replacement for a paid API, and it does not need a graphics card at all.
A regular laptop with 8 GB of RAM or more, no graphics card needed.
Open on Hugging Face▌ More finds