b8604
<details open=""> <p>common : cleanup logs and modernize the progress bar (<a class="issue-link js-issue-link" data-error-text="Failed to load title" data-id="4176956315" data-permission-text="Title is private" data-url="https://github.com/ggml-org/llama.cpp/issues/21215" data-hovercard-type="pull_request" data-hovercard-url="/ggml-org/llama.cpp/pull/21215/hovercard" href="https://github.com/ggml-org/llama.cpp/pull/21215">#21215</a>)</p> <div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="$ build/bin/llama-server -hf unsloth/Qwen3.5-0.8B-GGUF common_download_file_single_online: HEAD failed, status: 404 no remote preset found, skipping Downloading mmproj-BF16.gguf ——————————————————————————————————————— 100% Downloading Qwe
$ build/bin/llama-server -hf unsloth/Qwen3.5-0.8B-GGUF common_download_file_single_online: HEAD failed, status: 404 no remote preset found, skipping Downloading mmproj-BF16.gguf ——————————————————————————————————————— 100% Downloading Qwen3.5-0.8B-Q4_K_M.gguf ——————————————————————————————— 100% ...$ build/bin/llama-server -hf unsloth/Qwen3.5-0.8B-GGUF common_download_file_single_online: HEAD failed, status: 404 no remote preset found, skipping Downloading mmproj-BF16.gguf ——————————————————————————————————————— 100% Downloading Qwen3.5-0.8B-Q4_K_M.gguf ——————————————————————————————— 100% ...Sign in to highlight and annotate this article
Conversation starters
Daily AI Digest
Get the top 5 AI stories delivered to your inbox every morning.
More about
llamareleasegithub
🚀 Build a Professional Image Converter GUI in Python (Step-by-Step)
👉 Full source code: https://github.com/rogers-cyber/python-tiny-tools/blob/main/63-Image-resizer/ImageConvertPRO.py 🧠 What You’ll Build In this tutorial, we’ll create a modern desktop app that can: 📂 Add images (files, folders, drag drop) 🖼 Preview thumbnails 🔄 Convert formats (PNG, JPEG, WEBP, etc.) 📏 Resize images 💾 Save conversion history (SQLite) ⚡ Run conversions in background (no freezing UI) 📦 Step 1: Install Dependencies pip install pillow ttkbootstrap tkinterdnd2 🔍 Why we need them: Pillow → image processing ttkbootstrap → modern UI styling tkinterdnd2 → drag drop support 📁 Step 2: Project Setup Create a Python file: image_convert_pro.py ⚙️ Step 3: Import Libraries import os import sys import sqlite3 from threading import Thread from PIL import Image , ImageTk 🧠 Explana
I Built a Self-Hosted AI Agent That Runs on a Raspberry Pi
Most AI coding tools live in someone else's cloud. Cursor, Devin, GitHub Copilot: useful, but your context and conversations flow through a third-party server. For some teams that's fine. For others it's a non-starter. I wanted an AI agent engine I could deploy on my own hardware, connect to whatever model I wanted, and extend without waiting for a vendor to ship the feature. So I built profClaw . The problem with the current landscape There are roughly two categories of AI dev tools right now: Cloud-only agents (Cursor, Devin, Claude Code web, Copilot Chat): polished and easy to start, but you're locked into their infra, their model selection, and their pricing. No offline mode, no control over what gets logged. Single-purpose CLIs (Aider, shell wrappers around OpenAI): simpler and self-h
Same Agents, Different Minds — What 180 Configurations Proved About AI Environment Design
Google tested 180 agent configurations. Same foundation models. Same tasks. Same tools. The only variable was how the agents talked to each other. Independent agents — working in parallel, no communication — amplified errors 17.2 times. Give the same agents a centralized hub-and-spoke topology, and error amplification dropped to 4.4 times. Same intelligence. Same training. A 3.9x difference in error rate, explained entirely by communication structure. This isn't a story about better prompts or smarter models. It's a story about environment. And it follows directly from a claim I made in Part 1 of this series : the interface isn't plumbing between the AI and the world. It's a mold that shapes what the AI becomes. Part 1 argued this through cases — a developer who felt hollowed out by AI, a
Knowledge Map
Connected Articles — Knowledge Graph
This article is connected to other articles through shared AI topics and tags.
More in Open Source AI
Gemma 4 Complete Guide: Architecture, Models, and Deployment in 2026
Google DeepMind released Gemma 4 on April 3, 2026 under Apache 2.0 — a significant licensing shift from previous Gemma releases that makes it genuinely usable for commercial products without legal ambiguity. This guide covers the full model family, architecture decisions worth understanding, and practical deployment paths across cloud, local, and mobile. The Four Models and When to Use Each Gemma 4 ships in four sizes with meaningfully different architectures: Model Params Active Architecture VRAM (4-bit) Target E2B ~2.3B all Dense + PLE ~2GB Mobile / edge E4B ~4.5B all Dense + PLE ~3.6GB Laptop / tablet 26B A4B 25.2B 3.8B MoE ~16GB Consumer GPU 31B 30.7B all Dense ~18GB Workstation The E2B result is the most surprising: multiple community benchmarks confirm it outperforms Gemma 3 27B on s
I scored 14 popular AI frameworks on behavioral commitment — here's the data
When you're choosing an AI framework, what do you actually look at? Usually: stars, documentation quality, whether the README looks maintained. All of that is stated signal. Easy to manufacture, doesn't tell you if the project will exist in 18 months. I built a tool that scores repos on behavioral commitment — signals that cost real time and money to fake. Here's what I found when I ran 14 of the most popular AI frameworks through it. The methodology Five behavioral signals, weighted by how hard they are to fake: Signal Weight Logic Longevity 30% Years of consistent operation Recent activity 25% Commits in the last 30 days Community 20% Number of contributors Release cadence 15% Stable versioned releases Social proof 10% Stars (real people starring costs attention) Archived repos or projec
Running OpenClaw with Gemma 4 TurboQuant on MacAir 16GB
Hi guys, We’ve implemented a one-click app for OpenClaw with Local Models built in. It includes TurboQuant caching, a large context window, and proper tool calling. It runs on mid-range devices. Free and Open source. The biggest challenge was enabling a local agentic model to run on average hardware like a Mac Mini or MacBook Air. Small models work well on these devices, but agents require more sophisticated models like QWEN or GLM. OpenClaw adds a large context to each request, which caused the MacBook Air to struggle with processing. This became possible with TurboQuant cache compression, even on 16gb memory. We found llama.cpp TurboQuant implementation by Tom Turney. However, it didn’t work properly with agentic tool calling in many cases with QWEN, so we had to patch it. Even then, the
Help running Qwen3-Coder-Next TurboQuant (TQ3) model
I found a TQ3-quantized version of Qwen3-Coder-Next here: https://huggingface.co/edwardyoon79/Qwen3-Coder-Next-TQ3_0 According to the page, this model requires a compatible inference engine that supports TurboQuant. It also provides a command, but it doesn’t clearly specify which version or fork of llama.cpp should be used (or maybe I missed it). llama-server I’ve tried the following llama.cpp forks that claim to support TQ3, but none of them worked for me: https://github.com/TheTom/llama-cpp-turboquant https://github.com/turbo-tan/llama.cpp-tq3 https://github.com/drdotdot/llama.cpp-turbo3-tq3 If anyone has successfully run this model, I’d really appreciate it if you could share how you did it. submitted by /u/UnluckyTeam3478 [link] [comments]
Discussion
Sign in to join the discussion
No comments yet — be the first to share your thoughts!