Open source

Open models, frameworks and repositories: open weights, community hits and the balance between open and closed.

329 picksRelated topicsModel releases Hugging Face AI coding

Latest picks

261–280 of 329

May 5Tuesday

r/LocalLLaMAMay 5, 23:02

SenseNova-U1-8B-MoT open-source multimodal architecture draws LocalLLaMA discussion

SenseNova open-sourced SenseNova-U1-8B-MoT, an 8B native multimodal understanding and image-generation model. Its Hugging Face text says NEO-Unify removes VE and VAE, supports interleaved image-text generation, and high-density rendering; the post does not disclose test scores. The key question is whether the monolithic design yields reproducible gains.

Why it matters: HKR-H/K/R all pass: the open 8B unified multimodal model has a concrete architecture hook. No benchmark scores, license detail, or deployment cost are disclosed, so it stays in the 72–77 band.

Take

SenseNova-U1-8B-MoT has the right bait: 8B parameters, open source, native multimodal understanding, image generation, and a NEO-Unify pitch that removes VE and VAE. That directly pokes at the messy stack around Qwen-VL, InternVL, LLaVA-style adapters, and separate diffusion/VAE plumbing. If one compact model handles interleaved text-image generation and dense information rendering reliably, the architecture deserves attention.

The evidence is thin. The Reddit body is blocked by 403, and the summary gives no benchmark, license, VRAM profile, sampling setup, or failure cases. “High-density rendering” is exactly where demos lie: OCR, tables, UI screenshots, and Chinese long images break polished claims fast. I’d file this as architecturally interesting, not yet performance-relevant.

r/LocalLLaMAMay 5, 15:33

vibevoice.cpp: Microsoft VibeVoice ported to ggml/C++ with no Python at inference

LocalAI released vibevoice.cpp, a ggml/C++ port of Microsoft VibeVoice for CPU, CUDA, Metal, and Vulkan inference. TTS uses a 30s reference clip for 24kHz cloned speech; ASR uses a 7B model with diarized JSON and was tested on 17min audio. The key constraint is memory: 17min CPU Q8_0 peaks near 26GB, with no streaming output yet.

Why it matters: HKR-H/K/R all pass: a practical open-source VibeVoice C++ port with concrete runtime numbers. Reddit-source scope and niche audio deployment keep it in the 72–77 featured band, not same-day must-write.

r/LocalLLaMAMay 5, 05:38

FastDMS: 6.4X KV-cache compression running faster than vLLM BF16/FP8

FastDMS released an MIT implementation that cuts KV memory to 1/5–1/8 of vLLM BF16 at 8K context. A Llama-3.2-1B replication reports PPL 9.200 with 6.4x compression; Qwen3-8B c=1 drops KV from 1.406 GiB to 0.184 GiB. The key detail is physical reclamation of evicted slots, not just nominal KV-byte reduction.

Why it matters: HKR-H/K/R all pass: the hook is counterintuitive, with compression, PPL, KV GiB deltas, and physical slot reclamation. Reddit/open-source sourcing keeps it in 78–84, below P1.

May 4Monday

r/LocalLLaMAMay 4, 19:09

Deep research report with Hermes Agent and qwen3.6-35b-a3b Q6_K

A Reddit user used Hermes Agent and qwen3.6-35b-a3b Q6_K to produce a 21-page research report. The run took 6 loops and over 5 hours on an RTX 4060, at about 28 tokens/s. The repo includes prompts, scripts, intermediate artifacts, and the final report.

Why it matters: HKR-H/K/R all pass: this is a local-agent experiment with hardware, runtime, speed, and artifacts. Reddit source limits reach, so it stays in the 72–77 featured-threshold band.

QbitAI · WeChatMay 4, 12:24

DeepSeek-TUI, a “DeepSeek Claude Code,” reaches 2.3k GitHub stars

DeepSeek-TUI reached 2.3k GitHub stars; the Rust project is MIT-licensed. It targets DeepSeek V4 with a 1M-token context, RLM up to 16 V4 Flash subtasks, MCP, Shell, Git, and three control modes. Watch cache misses: uncached tokens cost 10x cached tokens.

Why it matters: HKR-H/K/R all pass: the hook is a DeepSeek-flavored Claude Code, with 2.3k stars, 1M tokens, 16 subtasks, and a 10x cache-miss cost gap. Impact is developer-specific, so it sits in the 72–77 band.

Take

DeepSeek-TUI reached 2.3k GitHub stars in four months and wraps DeepSeek V4’s 1M-token context, prefix caching, and V4 Flash subtasks into a Rust TUI. My read is simple: this is less a “Claude Code clone” than an attempt to turn model pricing mechanics into product behavior. Its future depends on long-session reliability, sub-agent routing, and cache hit rates, not on how closely the README resembles Claude Code.

The feature list is broad: file edits, Shell, Git, web search, MCP, Skills, three control modes, session restore, and Git snapshot rollback. On paper, that matches the terminal-agent shape Claude Code popularized. But Claude Code’s edge is not just tool access. Anthropic has been tightening tool-call reliability, permission boundaries, task state, recovery loops, and the fit between Sonnet’s behavior and the UI. DeepSeek-TUI currently looks like a strong open-source interaction shell built around DeepSeek V4’s low cost and long context. That is a credible angle, but the failure mode is obvious: cheap model tokens do not automatically make cheap agents.

The RLM design is the important bit. A main model can dispatch up to 16 V4 Flash subtasks. That matches DeepSeek’s price profile well. The article says Flash output costs roughly one-third of Pro output, but it does not disclose input price, cache-hit price, context distribution, or a real task cost trace. I have doubts here. Parallel sub-agents can improve coverage and offload shallow work to cheaper models. They also create separate context branches, and those branches can destroy prefix-cache reuse. The article says uncached tokens cost 10 times cached tokens. That number matters more than the star count. It defines the product’s unit economics: savings come from stable prefixes; runaway cost comes from cache fragmentation.

I’ve long thought the post-2025 coding-agent divide is not “can it edit files?” It is whether the system can make state compression predictable. Cursor, Claude Code, OpenAI’s Codex CLI, Aider, and similar tools all hit the same wall: repository context is not better just because it is larger. Long context drags retrieval, attention, cache behavior, and cost into the same bottleneck. Gemini 1.5’s 1M-token window taught developers that long context is raw material, not product quality. DeepSeek-TUI defaults to filling V4’s 1M-token window. I understand the marketing value. I am not sure it is the right default. For many repos, stable indexing, symbol-level retrieval, incremental diff summaries, and disciplined prompt layout beat stuffing the window.

The smart mitigation is its compression strategy. The tool tries to preserve stable prefix content so DeepSeek’s prefix cache keeps hitting. That is a real engineering detail. Anthropic prompt caching, OpenAI cached-input pricing, and DeepSeek prefix caching all reward the same behavior: do not mutate the front of the prompt. A TUI agent naturally pollutes context. Users change goals, run Shell commands, paste logs, and branch tasks. The token stream gets messy fast. If DeepSeek-TUI can separate Git snapshots, session summaries, task plans, and tool output so the stable prefix stays stable, it is more than a UI wrapper. The article does not provide cache-hit curves or a one-hour coding-session cost sample. Without those numbers, the cost advantage remains a mechanism, not proof.

The open-source execution looks healthier. Rust, MIT license, prebuilt binaries for Linux/macOS/Windows, npm install, TUNA Cargo mirror support, Chinese README, and China-specific setup paths all fit DeepSeek’s community distribution pattern. The repo was created on January 19 and reached v0.8.8 after 37 releases. That is not a throwaway demo cadence. v0.8.2 fixed file-handle leakage in long sessions. v0.8.6 and v0.8.7 added retry countdowns for rate limits, input-history search, and running-message queue visibility. Those are user-pain fixes. Toy projects usually do not reach that layer this quickly.

I do not buy the “DeepSeek version of Claude Code” label without caveats. It drives clicks and sets the wrong expectation. Claude Code sits behind Anthropic’s model stack, product team, enterprise sales motion, billing system, and safety model. DeepSeek-TUI is an independent project. The detail that Claude authored more than 150 commits is funny and very 2026, but it also says this is still in the AI-assisted indie-tool category. It has not yet been validated across team workflows, private-repo permissions, audit logging, CI integration, enterprise proxies, or security review. YOLO mode that auto-approves Shell and file operations is great for personal hacking. Enterprise security teams will ask about sandboxing, secret redaction, command allowlists, and audit trails. The article does not disclose those protections.

Hunter Bown’s background makes for a good profile, but it does not carry the product case. Music, patent law, Shannon Labs, and “the Bell Labs of the AGI era” are narrative assets, not moats. What can matter is the depth of DeepSeek V4 adaptation: how it compresses 1M-token sessions, how RLM assigns work, how Flash and Pro switch, how cache misses are surfaced, and how MCP plus Git snapshots reduce damage. If the project ships reproducible benchmarks on the same repository and issue set, with success rate, human approvals, token cost, and cache-hit rate, it moves from GitHub heat to practitioner tool.

My stance is cautious-positive. DeepSeek-TUI is one of the first DeepSeek-native attempts to package cheap long-context models into a real coding-agent workflow. The 2.3k stars show demand, not Claude Code replacement readiness. If it keeps adding surface features, it will hit the same agent-tool swamp everyone else hits. If it treats cache cost and long-session reliability as first-class product metrics, it can become the DeepSeek ecosystem’s Aider-like tool. The key number here is not stars. It is the 10x price gap between cached and uncached tokens.

r/LocalLLaMAMay 4, 11:48

450M On-Board VLM Wildfire Detection Pipeline with Sentinel-2 and LFM2.5-VL

PauLabartaBajo shared a wildfire detection PoC using 450M LFM2.5-VL on Sentinel-2 imagery. It pairs RGB and SWIR tiles, simulates orbit with SimSat, and covers 22 fire-prone sites. The key constraint is bandwidth: on-board inference downlinks only a JSON risk profile.

Why it matters: HKR-H/K/R all pass: the story has a counterintuitive edge-VLM hook and concrete numbers. Single-source Reddit PoC and a narrow wildfire-use case keep it below the 78+ band.

May 3Sunday

r/LocalLLaMAMay 3, 20:12

LLM proxy that lets Claude Code talk to any model

DataNebula released open-source rosetta-llm, letting Claude Code call multiple providers through one gateway. It translates Anthropic Messages, OpenAI Chat, and OpenAI Responses, and round-trips encrypted reasoning via the signature field. The key detail is thinking-block fidelity for multi-turn agent prompt-cache hits.

Why it matters: HKR-H/K/R all pass, but this is a Reddit open-source tool post with no adoption, stars, or benchmark data disclosed. Score stays in the mid-weight tooling band, not 78+.

r/LocalLLaMAMay 3, 19:46

Upskill: skill registry your agent consults before it starts, with 10k+ indexed skills

Autoloops released Upskill, an open-source skill registry with 10k+ indexed skills for agents. Search combines Postgres full-text search, 1024-dim embeddings, and reranking by stars, installs, and feedback. LLM adversarial review blocked hundreds of skills at index time.

Why it matters: HKR-H/K/R pass: a useful open-source agent registry with concrete retrieval and safety mechanics. Source authority is low and adoption is unproven, so it stays in the 72–77 featured band.

Take

Upskill is betting on agent tool discovery, and I buy the direction, not the implied leap. The summary gives 10k+ skills, Postgres full-text search, 1024-dim embeddings, reranking by stars, installs, and community feedback, plus LLM adversarial review that blocked hundreds of skills at index time. That is distribution and filtering, not execution reliability.

MCP already pushed “tool availability” hard over the last year. The failure point moved to post-call verification. An agent finding Shell, browser, or cloud API skills is easy; knowing when arguments are wrong, permissions are excessive, or outputs are poisoned is the hard part. If Upskill lacks runtime sandboxing, permission scopes, and rollback logs, it becomes npm search for agents: useful, noisy, and a clean path for supply-chain risk into automated workflows.

QbitAI · WeChatMay 3, 11:16

GS-Playground Embodied AI Simulation Framework Open-Sourced with High-Throughput 3DGS Rendering

Tsinghua AIR DISCOVER Lab and partners open-sourced GS-Playground, accepted by RSS 2026. On an RTX 4090, it reports 10,000 FPS at 640×480 and 2,048 parallel scenes; a 50-humanoid benchmark reaches 1,015 FPS. The key point is coupling batch 3DGS rendering with parallel physics.

Why it matters: HKR-H/K/R pass: the open-source RSS 2026 work reports concrete RTX 4090 throughput and parallel-scene numbers. The robotics-simulation scope is narrower than a model launch, so it fits the 78–84 band.

r/LocalLLaMAMay 3, 02:11

Built a C++17 transformer from scratch with 0.83M params and CPU training

Reddit user Suspicious_Gap1121 released Quadtrix.cpp, a C++17 GPT-style model with 0.83M parameters. It uses 4 layers, 4 heads, 200d width, and a 128-character context; one CPU core trained on 31.4M characters for 76.2 minutes to 1.6371 nats val loss. The key detail is handwritten backprop for LayerNorm, attention, Q/K/V, dropout, and AdamW without PyTorch, BLAS, or autograd.

Why it matters: HKR-H/K/R all pass: the no-framework C++17 build is clickable, the training setup is specific, and local-LLM builders care about dependency-free control. It stays in the 72–77 band because it is a small personal project.

May 2Saturday

r/LocalLLaMAMay 2, 21:44

I built Semvec: A constant-cost semantic memory for LLMs, looking for testers

A developer released Semvec, replacing unbounded chat history with fixed-size semantic state. Its 48-turn benchmark claims about 76% token reduction, with identical input footprint at turn 10 and 10,000. It supports OpenAI-compatible LLMs, MCP, Claude Code, Cursor, and multi-agent shared state.

Why it matters: HKR-H/K/R all pass, but this is a Reddit self-release with author benchmarks only. Treat it as an interesting indie memory tool, not a same-day industry story.

Take

Semvec is betting against endless context growth by compressing dialogue into fixed-size semantic state. The summary gives two hard hooks: a 48-turn benchmark claims about 76% fewer tokens, and turn 10 has the same input footprint as turn 10,000. The Reddit body is blocked by 403, so the task, model, scoring, and failure cases are missing.

I like the direction, especially the OpenAI-compatible API, MCP, Claude Code, Cursor, and shared multi-agent state. That is closer to developer workflow than another generic vector-memory wrapper. The catch is brutal: fixed state always drops information. Which facts get dropped, when they get dropped, and whether the system can recover them decide whether Semvec is infrastructure or a neat demo. MemGPT, Zep, and LangGraph memory have all hit that wall.

r/LocalLLaMAMay 2, 16:12

Qwen3.6-27B hits 72 tok/s on RTX 3090 with native vLLM on Windows

Reddit user One_Slip1455 released a native Windows vLLM launcher for Qwen3.6-27B, reaching 72 tok/s on an RTX 3090. It reports 64.5 tok/s at ~25k tokens, 53.4 tok/s at 127k ctx on one GPU, and 160k ctx with PP=2 on 2×3090. The key detail is no WSL or Docker, an OpenAI-compatible endpoint, and an INT4 quant path.

Why it matters: HKR-H/K/R all pass: native Windows on an RTX 3090 is the hook, the post gives tok/s and ctx figures, and it hits local-inference cost concerns. Reddit single-source limits it to the lower featured band.

QbitAI · WeChatMay 2, 10:42

Tencent Hunyuan open-sources 440MB offline translation model, claims Google Translate quality lead

Tencent Hunyuan open-sourced Hy-MT1.5-1.8B-1.25bit, compressing a 1.8B translation model to 440MB. It supports 33 languages and 1,056 directions, with an Android demo running offline on Snapdragon 888 and 8GB RAM. The key detail is Sherry 1.25-bit quantization: 3 of every 4 weights use 1 bit and 1 is zeroed.

Why it matters: HKR-H/K/R all pass: the story has a strong offline-phone hook, concrete quantization details, and practitioner relevance around edge inference. It stays below P1 because this is a vertical translation model, not a major foundation-model release.

May 1Friday

r/LocalLLaMAMay 1, 22:53

PFlash: 10x prefill speedup over llama.cpp at 128K on an RTX 3090

PFlash cuts Qwen3.6-27B Q4_K_M 128K TTFT to 24.8s on an RTX 3090, versus 248.4s cold for llama.cpp. It uses a Qwen3-0.6B drafter to score token importance, keeps 5% of spans, and runs C++/CUDA without Python, Triton, or PyTorch. The quality caveat is clear: only NIAH single-needle passes from 32K to 128K; RULER and multi-needle results are not disclosed.

Why it matters: HKR-H/K/R all pass, but this is a single Reddit claim with quality evidence limited to single-needle NIAH 32K–128K. RULER and multi-needle results are not disclosed, so it stays at featured threshold.

Xinzhiyuan · WeChatMay 1, 13:29

Developer Builds WorldX, an AI World Generator, During a 10-Day Wedding Leave

An independent developer built WorldX in 10 days, generating a full AI world from one sentence in about 5 minutes. The system uses a 6-step map pipeline, about 30k–180k tokens per world, Tick loops, layered memory, and two-axis emotion. The key mechanism is overlay labeling plus color-difference localization for deterministic coordinates.

Why it matters: HKR-H/K/R all pass, but this is an indie project rather than a platform release, so it stays in the 72–77 band. The concrete pipeline, token range, and agent memory details justify featured.

Take

WorldX is easy to oversell as a text-to-game demo, but one engineering choice is sharp: let the model draw, then force the fuzzy image back into deterministic coordinates through overlay labels and color-difference localization. The disclosed setup has useful hooks: 10 days of building, about 5 minutes per world, 30k–180k tokens per world, a 6-step map pipeline, Tick loops, three memory layers, and two-axis emotion. That sounds less like a prompt stunt and more like scaffolding for a runnable town simulator.

I don’t buy the “world comes alive” framing yet. The WeChat body is blocked by verification, so there is no visible repo, failure rate, runtime cost, or long-horizon character consistency test here. Stanford’s Smallville was strong because the behavior logs and social loops held together. WorldX has shown coordinate grounding; it has not yet shown stable multi-agent life.

QbitAI · WeChatMay 1, 12:16

Peking University Open-Sources Unified World Model Framework for Synthesis and Reasoning Tasks

Peking University DCAI and Kuaishou Kling open-sourced OpenWorldLib for four task types: video generation, 3D modeling, VLA control, and multimodal reasoning. Its Pipeline coordinates Operator, Reasoning, Synthesis, Representation, and Memory modules, supporting forward and stream execution. The key test is whether unified interfaces cut cross-task reproduction cost.

Why it matters: HKR-H/K/R all pass: the post gives a concrete open-source framework, task scope, modules, and inference modes. It lacks benchmark results, adoption data, or major ecosystem integration, so it stays at 78.

Take

OpenWorldLib should be read as tooling first, not as a unified world model. The visible summary names four task families—video generation, 3D modeling, VLA control, and multimodal reasoning—and five modules: Operator, Reasoning, Synthesis, Representation, and Memory. Its Pipeline supports forward and stream execution. That sounds like a reproduction scaffold, not a capability jump.

I don’t buy the grand framing yet. The WeChat body is blocked by verification, so code layout, dependencies, benchmarks, and license are not disclosed. This sits near the agent-framework pattern we saw everywhere last year: clean interfaces, uneven backend reality. If OpenWorldLib can reliably plug into Kling-like video models, VLA policies, and 3D generators, it earns attention. Until then, it is mostly a bet on lowering experiment friction.

Hacker News front pageMay 1, 04:55

Show HN: Pu.sh – a full coding-agent harness in 400 lines of shell

Pu.sh ships a coding-agent harness in about 400 lines of shell, using only sh, curl, and awk. It supports Anthropic and OpenAI, 7 tools, REPL, auto-compaction, checkpoint/resume, pipe mode, and 90 no-API tests. It excludes TUI, streaming, images, OAuth, and Windows.

Why it matters: HKR-H/K/R all pass, but this is a small Show HN open-source tool, not a model or platform release. HN frontpage plus a reproducible 400-line implementation clears the featured bar.

Apr 30Thursday

r/LocalLLaMAApr 30, 01:19

inclusionAI/Ling-2.6-1T · Hugging Face

inclusionAI open-sourced Ling-2.6-1T on Hugging Face, with 1 trillion parameters. It uses MLA plus Linear Attention and Contextual Process Redundancy Suppression to reduce CoT overhead. The post cites AIME26 and SWE-bench Verified but does not disclose scores.

Why it matters: HKR-H/K/R all pass, but benchmark scores for AIME26 and SWE-bench Verified are not disclosed. A 1T open model with a named architecture mechanism fits featured, not P1.

X · @doteyApr 30, 01:02

Inside Hermes Agent's Memory System and How It Avoids OpenClaw's Pitfalls

Hermes Agent splits memory into 4 layers: prompt files, SQLite session search, skills, and optional Honcho. MEMORY.md is capped at 2,200 chars, USER.md at 1,375; writes apply after a new session or compression. The key design is cache-first: keep system prompts stable and retrieve long-tail history via tools.

Why it matters: HKR-H/K/R all pass: the OpenClaw contrast is clickable, and the memory limits/mechanisms are concrete. Single X-source tutorial, not a product release, keeps it at the featured threshold.

Take

Hermes Agent makes a very unfashionable call: persistent memory should stay tiny because the system prompt is expensive cache territory. MEMORY.md is capped at 2,200 characters, USER.md at 1,375; writes hit disk immediately but only enter the prompt after a new session or compression. That is a production constraint, not a toy limitation.

The stronger part is the split between SQLite session_search and skills. Old conversations go through full-text search, session grouping, and a cheap summarizer; procedural knowledge sits behind a skills index and loads on demand. Plenty of agent projects still dress “long-term memory” up as a vector DB feature. Hermes is colder: keep high-frequency facts resident, push long-tail history into tools. OpenClaw’s Markdown-log style reads nicer in a repo, but it ages into noise once the agent runs for real.

Apr 29Wednesday

QbitAI · WeChatApr 29, 20:44

Avenir-Web Open-Sources Web Agent Harness With 53.7% on ONLINE-MIND2WEB

UCL, Princeton, and Edinburgh open-sourced Avenir-Web, reaching 53.7% success on ONLINE-MIND2WEB. The training-free harness uses EIP, MoGE, checklists, and adaptive memory across 136 sites and 300 live tasks. The key signal: with Gemini 3 Pro, it beats Claude Computer Use 3.7 at 47.3%.

Why it matters: HKR-H/K/R all pass: the story has a sharp SOTA web-agent hook, concrete benchmark numbers, and practitioner resonance around agent reliability. This is a strong open-source research release, not a major lab model launch, so 82 fits the 78–84 band.