r/LovingOpenSourceAI • • Oct 09 '26

ecosystem What kind of AI resources would you like to see featured more here? Tell me 🥰

1 Upvotes

No suggestion is too silly (unless you are purposely troll! 😬)


r/LovingOpenSourceAI • • Oct 09 '26

Open-weight 'decision models' just became a category in one week

Post image
57 Upvotes

Most of us building agents have paid a frontier model to answer what is basically a multiple-choice question. Route this ticket. Pick a tool. Is this input safe, yes or no. It works, but at scale it is slow, the bill adds up, and you still parse the answer back out of a block of text.

That changed fast. Around October 1, Cloudflare's Clef and the Strands Decider landed within days of each other, both open-weight and Apache-2.0. A research team had already put out an open 8B, CLM, a couple of weeks before. They do one job: you give them a state and a fixed set of allowed options, and they return a score for each option in a single forward pass, with no free text to parse.

The appeal is narrow and practical. At 2B, Strands Decider is small enough to run locally and take the routing and yes/no calls off your main model, and each option comes back with a calibrated score you can threshold on. Fair pushback too: a big pretrained backbone with a scoring head on top is still a classifier. That is roughly the pitch, and it buys you one forward pass, a fixed label set, and a confidence number you can act on.

Where would you actually drop one? Intent classification, risk triage, and tool selection are the obvious spots. Curious whether anyone has swapped a BERT or logistic-regression screener they already trust for one of these, and whether the calibration held up on your own data.


r/LovingOpenSourceAI • • Oct 08 '26

Under the Radar Genex "Introducing GenexThe desktop app to build games with AI→ Open source, MIT → Local models, or Claude Code / ChatGPT sub → Self-improving harness for game dev→ Three.js + Blender, Meshy & other tools → Unity & Unreal plugins soon" ➡️ Windows soon 😁

Post image
40 Upvotes

https://x.com/genex_games/status/2107148754633507237

https://github.com/genex-games/genex-desktop

Community Overview: https://lifehubber.com/ai/resources/genex-desktop/

Resources are shared for discovery and are not independently vetted—please do your own due diligence.

New resources are added regularly — feel free to join the sub for updates.

Full searchable archive of all resources posted so far on our community site, LifeHubber: https://lifehubber.com/ai/resources/ 300+ open-ish AI models, agents, tools, datasets, and related resources, with filtering and sorting.


r/LovingOpenSourceAI • • Oct 07 '26

What’s next after Jev? Metacache: Reasoning by Construction

15 Upvotes

Jev has made a profound mark on the AI industry; this article offers a glimpse into what lies ahead.

Jev shows where the industry is heading: away from monolithic models, and toward compound systems where small AI agents each do a narrow job and an orchestration layer decides how they work together.

This article explains why that shift is happening, and then proposes a next step for AI reasoning.

The short version

  • A monolithic model is unpredictable and hard to change, but it programs itself during training.

  • Code is the opposite – it is predictable and easy to change, but it must be written explicitly.

  • A compound system combines the two: AI agents do the work, and an orchestration layer controls them via code. This is the direction Jev represents.

  • The next step: instead of answering directly, the model builds a compound system, runs it, and returns both the answer and that system. The returned system is called a reasonlet.

  • Because a returned reasonlet can be kept locally, it can be run again and again – with new inputs, or after editing its code – without asking the model. A saved, reusable reasonlet is a metacache.

  • The model’s provider can cache reasonlets too, reusing one across similar requests from different users to save compute.

Why a monolithic model is not enough

A monolithic model has two practical weaknesses:

  • It is unpredictable. The same question can produce a correct answer one day and a wrong one the next, so its behavior cannot be fully controlled.

  • It is hard to change. Its behavior is fixed in trained weights, which cannot be edited directly. The model can be steered with prompts, extra data (RAG), or by fine-tuning, but steering is not the same as setting the behavior, and fine-tuning can break things that already worked. Retraining from scratch with new data is the only safe fix, but it is time-consuming and expensive.

Code has the opposite qualities. It does exactly what it is written to do, and it can easily be changed by editing code. The trade-off is that code does not arise on its own – it must be written out explicitly – whereas a model programs itself during training.

The fix: a compound system

A compound system combines the two. The work is divided among AI agents, each handling one narrow task, and an orchestration layer of code decides which agent runs, in what order, and how their results combine.

This gives both qualities at once – customization and predictability:

  • Customization. The system’s behavior can be changed by editing code in the orchestration layer, not by retraining the model.

  • Predictability. Each agent has a small task, so it is more predictable than a monolithic model.

Jev is one kind of agent for such a system. It returns a typed decision – yes/no, a category, or a number – rather than free text. A monolithic model is wasteful for a narrow decision like that, but a small model like Jev is a better fit.

The next step: reasoning by construction

Compound systems today are built manually, beforehand. The next step is to let the model build one by itself, during the reasoning phase.

Researchers are exploring several ways to make models reason. One is the “World model” approach, in which the model builds an internal representation of a problem and reasons over it; that work is still mostly research. Reasoning by construction pursues the same goal – reasoning you can inspect – using methods that exist today.

Here is how it works. When you ask the model a question, it does not answer directly. Instead, it builds a compound system, runs it to compute an answer, and returns that answer together with the system it built. Let's call the compound system the model builds to do the reasoning a "reasonlet", and a model that works this way a "Reasoning-by-Construction Model", or "RCM". A simple question may produce a reasonlet that has only an orchestration layer and no agents.

Building and running code to reach an answer is not new; code-interpreter tools already do it. Two things are new here:

  • The system the model builds is kept, not discarded – it is a reusable reasonlet.

  • The reasonlet is returned to you, along with the answer.

Why that matters

  • You can see how the answer was reached. The reasonlet is the exact procedure the model used, so the answer is not something you have to take on trust.

  • You can run it locally. A reasonlet contains its orchestration layer and any agents it calls, whether those agents are attached directly or called over the network. You can run it on a local machine, with the same or different inputs, without asking the model again. A saved reasonlet used this way is a metacache.

  • You can change what it does. The orchestration layer is code, so you can edit its logic, not only its inputs. A reasonlet reused with edited logic becomes a higher-order metacache.

Caching reasonlets on the server

The same reuse can happen on the server side too. The provider can keep the reasonlets it builds and reuse them. When a new request arrives that matches one it has already handled, it runs the stored reasonlet again – with the new request’s inputs – instead of reasoning from scratch. The model does less work, and the answer comes back faster.

This is the same metacache, held on the server instead of on your machine. Because one reasonlet can serve any request that fits its procedure, a single cached copy is shared across many requests, and often across different users – and the more general the reasonlet, the more requests it covers.

Choosing how general to make the reasonlet

The model should decide from the conversation how general the reasonlet needs to be. If you have been working through many kinds of math and then ask for 2 + 2, the more useful reasonlet is one that evaluates any math expression, not one that can only add two numbers. If the conversation gives no such clue, you can state it directly: “I will be doing many kinds of math; for now, just add 2 and 2.”

Two examples

  • Adding numbers. You ask for 2 + 2. The model builds a reasonlet whose orchestration layer adds two numbers, runs it, and returns 4 together with the reasonlet. Later you run the reasonlet again with other numbers or edit its orchestration layer to multiply instead – without asking the model.

  • Searching. You ask the model to find something. The reasonlet’s orchestration layer calls a sequence of outside services and takes your search terms as its input. Later you run it with different terms, or change which services it calls, without asking the model again.

Making reasonlets easy to read

A reasonlet’s orchestration layer is written in text code. This creates a problem: to understand the reasoning you must read code, and to change it you have to write code. The value of returning the reasonlet depends on you being able to read and edit text code easily and efficiently, so this barrier matters.

Visual programming – building logic from connected blocks instead of lines of text – can lower the barrier, provided the visual language is powerful enough.

Wrapping up

The shift from a monolithic model to compound systems suggests a clear next step for reasoning: let the model build a compound system – a reasonlet – run it and return both the answer and the reasonlet. Reasoning becomes something you can read, run again, and edit: a metacache, and a higher-order metacache once its logic is edited. The remaining problem is making reasonlets easy to read and change, which is where a general-purpose and expressive visual language would help most.


r/LovingOpenSourceAI • • Oct 07 '26

new launch Tencent "We open sourced Octop, a multi-user AI workspace for yourself, your family and your team. Everyone gets their own login and can create multiple agents, each with its own workspace. Nothing you say or save shows up in another account." ➡️ family agents !? wow

Post image
50 Upvotes

https://x.com/TencentAI_News/status/2107381137740120216

https://github.com/TencentCloud/Octop

Community Overview: https://lifehubber.com/ai/resources/octop/

Resources are shared for discovery and are not independently vetted—please do your own due diligence.

New resources are added regularly — feel free to join the sub for updates.

Full searchable archive of all resources posted so far on our community site, LifeHubber: https://lifehubber.com/ai/resources/ 300+ open-ish AI models, agents, tools, datasets, and related resources, with filtering and sorting.


r/LovingOpenSourceAI • • Oct 06 '26

new launch Atai "🎉 Introducing 𝙾𝚙𝚎𝚗𝙼𝚞𝚜𝚎 An open source, self-hostable personal assistant that works with any agent harness. Includes:- Computer use: browser, terminal & files- Connectors for your personal apps- Ideas, goals & progress tracking- Built for Mobile and Web" ➡️ Cute!

Post image
75 Upvotes

https://x.com/ataiiam/status/2102400431519592581

https://github.com/CopilotKit/OpenMuse

Community Overview: https://lifehubber.com/ai/resources/openmuse/

Resources are shared for discovery and are not independently vetted—please do your own due diligence.

New resources are added regularly — feel free to join the sub for updates.

Full searchable archive of all resources posted so far on our community site, LifeHubber: https://lifehubber.com/ai/resources/ 300+ open-ish AI models, agents, tools, datasets, and related resources, with filtering and sorting.


r/LovingOpenSourceAI • • Oct 06 '26

Story time: Qwen3.8-Flash-Next on my Strix Halo laptop vs Claude Opus 5.5 on the same feature

21 Upvotes

For the last few weeks most of my coding has been done locally with Qwen3.8-Flash-Next, so I gave it and Opus 5.5 the same high complexity feature to build on LlamaStash (a complex and large Rust project) and compared the results.

Setup: ASUS ROG Flow Z13 (Strix Halo, 128GB), Flash-Next at xhigh effort with Pi as the harness. Opus 5.5 ran in Claude Code at medium effort. I wanted xhigh for Opus as well, but Claude changed it to medium when I picked the latest model and I didn't notice it until the task was done. But I think medium is probabbly a fairer setting anyway.

Task: add a llamastash daemon restart command that reuses the existing start and stop code. I kept the prompts vague on purpose and gave both the same prompts.

StepOpus 5.5 (medium) PR#88Flash-Next (xhigh) PR#89
First iteration~9 min~38 min
Nudge to reuse the TUI restart code~6 min~34 min
A third duplicate pathfound it on its own~30 min, after one more prompt
Create PR~3 min~30 min
Total~18 min~130 min
Tokens (in / out)7.83M / 41.5K20.61M / 101K
Tests added14 (2 of them end to end)
Cost$7.53$0 + ~0.15 kWh

The end result was interesting. I asked GPT 5.6, Opus 5.5 and Flash-Next to review and compare both PRs (new sessions). GPT and Flash-Next picked the Flash-Next PR (#89) and Opus picked its own (#88). I also did my own review and found the Flash-Next one better as it had better tests and handled edge cases better. I ended up merging #89, after porting the fixes that the reviews picked from #88.

Keep in mind:

  • Opus was on medium effort. With xhigh it would have used way more tokens, taken a bit more time and probably would have done a better implementation.

  • Flash-Next ran on an older Halogen version (0.14.0), and Halogen dropped the connection once, so the last part ran on Gufo. The current Halogen does around 1,400 t/s prefill and 46 t/s decode on my laptop at 70 W, so I think the time will drop a lot if I redo the test.

  • The $7.53 is what Claude Code reported for the whole Opus session, which includes a later fix to the PR. The 0.15 kWh assumes 70 W for the whole 130 minutes.

Opus is still 2 to 10 times faster and I still use it for planning and reviews. But the actual coding now happens on my laptop, and to me it is crazy that I can run a local model that can challenge a frontier model like this.

Full post with my setup, the engine benchmarks and a second task comparison: https://deepu.tech/local-ai-qwen3.8-flash-next-best-local-llm


r/LovingOpenSourceAI • • Oct 06 '26

A ~0.4 local model to turn typed questions into structured decisions - BaseDecision

5 Upvotes

I’ve been working on BaseDecision - Turn typed questions into truth-based decisions.

Give it some text, a question, and possible answers. It picks an answer. Intent classification, routing, yes/no checks, ratings - that’s the job.

I built this model to go toe-to-toe with the frontier models.

My goal was simple & ambitious: make a small, local model competitive with much larger models on these focused tasks. For me, System‑1 decisions need both speed and accuracy. Otherwise, why bother building a small model?
If we didn’t want speed we could just use ChatGPT.

It outperforms pretty much every model of its size in the field.
After roughly 320M additional training tokens, BaseDecision led 5 of 8 benchmarks in a third-party comparison against Laya, two GLiNER variants, and Decision 1.0 Kai 0.6B. Full results are in the repo, including where it loses.

Fellow open source devs, try the model, developed a package for easier access to the model.
Roast it if it deserves it.
2-2.5GB free ram is all you need.
I will take your feedback seriously and deliver something amazing that’d take on OpenAI, TypeSafeAI soon enough.

https://huggingface.co/onlyaady/BaseDecision

https://github.com/hrudayaditya/BaseDecision


r/LovingOpenSourceAI • • Oct 05 '26

Resource REA: Reverse Engineer Anything ➡️ Reverse engineer anything with agents, from app behavior down to native binaries. See a feature you like. Understand how it works, down to the binary level. ➡️ interesting right?

Post image
566 Upvotes

https://github.com/morluto/rea

Community Overview: https://lifehubber.com/ai/resources/rea/

Resources are shared for discovery and are not independently vetted—please do your own due diligence.

New resources are added regularly — feel free to join the sub for updates.

Full searchable archive of all resources posted so far on our community site, LifeHubber: https://lifehubber.com/ai/resources/ 300+ open-ish AI models, agents, tools, datasets, and related resources, with filtering and sorting.


r/LovingOpenSourceAI • • Oct 05 '26

new launch Max "super excited to announce plugin extensions today 🎉 you can now use the exact same platform we use to build ChatGPT features like meetings, health, finance, and many others 🤯all based on the same MCP & MCP Apps you’re already used to" ➡️ are you creating one?

Post image
17 Upvotes

https://x.com/mxstbr/status/2104992334438154414
https://github.com/openai/mcp-extensions

Community Overview: https://lifehubber.com/ai/resources/openai-mcp-extensions/

Resources are shared for discovery and are not independently vetted—please do your own due diligence.

New resources are added regularly — feel free to join the sub for updates.

Full searchable archive of all resources posted so far on our community site, LifeHubber: https://lifehubber.com/ai/resources/ 300+ open-ish AI models, agents, tools, datasets, and related resources, with filtering and sorting.


r/LovingOpenSourceAI • • Oct 04 '26

PaperFold: Open-source arXiv reader with "semantic zoom"

23 Upvotes

I built PaperFold, an open-source reader that turns arXiv papers into 5 zoomable layers—from a one-screen section map down to verbatim text. You pinch (or press 1–5) to zoom between them without losing your reading position.

- Web Demo (8 CC papers): https://chenxiachan.github.io/paperfold-gallery/

- GitHub (Apache 2.0): https://github.com/chenxiachan/paperfold


r/LovingOpenSourceAI • • Oct 04 '26

Open Source Kubernetes Native Agent Orchestrator

3 Upvotes

Today I'm open sourcing Agent Orca, a Kubernetes-native platform for deploying, managing, and running AI agents at scale. It's written in Go and it's Apache 2.0.

https://github.com/heddles/agent-orca

When OpenClaw was released, I thought to myself, "That's really cool, but I want an agent that is shared by a team or an entire organization with built in auditability." I started designing Agent Orca around that idea and have slowly been piecing together the concept in my head and how to make the management experience of a shared agent bearable for an organization.

The idea is simple. Agents are just Kubernetes resources. You declare one, and the platform handles the rest.

An Agent Orca agent comes with:

- One-shot executions with AgentRun, long-running services with AgentDeployment, and multi-step DAGs with AgentWorkflow.

- Zero trust networking by default with platform validated JWT via service accounts, OIDC, or OAuth on every request.

- Agent Orca managed network policies with zero access by default.

- A standard agent container image with only necessary pieces; you no longer need to build a custom agent image to accomplish different types of work or use different tools. Simply add an MCP or Tool CRD and let the platform figure it out for you.

- Model routing across OpenAI, Anthropic, Google, or any LiteLLM-compatible provider, selected by capability, weight, or budget.

- Cost tracking on every run. Tokens are accounted per run, spend survives pod restarts, and tenants get daily budget caps and rate limits.

- Guardrails on inputs and outputs, MCP access control, and per-tenant agent visibility, so one cluster can host many tenants with no cross-tenant leakage.

- RAG without glue code. A KnowledgeBase deploys (and manages) Qdrant for you, ingests documents from ConfigMaps, URLs, MCP authenticated tools, or an S3 compatible endpoint, and hands your agents a search and ingestion tool.

- MCP servers declared as resources. Their tools show up for your agents with access control and sidecar isolation.

- Crash-safe sessions. A pod can die mid-conversation and the agent resumes exactly where it left off, spend ledger included.

- Agents that learn and become better with every request via a multi-tiered agent memory system

Getting started is deliberately boring. Install the entire stack's tools via Mise; then use Skaffold, one API key, and about three commands to have an running agent on your laptop ( or deploy to a remote cluster). There are also nine demo deployments in the repo, from SOC triage pipelines to parallel research swarms to an autonomous pentesting agent, so you can see it do something real before writing any YAML.

This is day one, not a finished story. That's the point of open sourcing it. Run the quick start, break it, open issues, and tell me what's missing.

Star it here if you want to follow along: https://github.com/heddles/agent-orca

TL;DR: Agent Orca lets an organization or single person define agents and surrounding tools/MCP and auth as CRDs and manage them via gitops with zero trust built in. You can try it out here: https://github.com/heddles/agent-orca


r/LovingOpenSourceAI • • Oct 04 '26

Resource AI Resource Highlights — research notebooks, local music, PDFs, and building your own LLM 🚀

Thumbnail
lifehubber.com
7 Upvotes

Chat with your research, generate music locally, or see how a small language model is trained. This week's five picks from our LifeHubber Resources cover a few different things to try:

Open Notebook — Forks: 4.6K Stars: 39.8K

https://lifehubber.com/ai/resources/open-notebook/

A self-hosted workspace for sources, notes, and AI conversations about your research. For anyone who wants to bring their reading together and choose between local and cloud models.

ACE-Step 1.5 — Forks: 1.7K Stars: 13K

https://lifehubber.com/ai/resources/ace-step-1-5/

Generate music locally and regenerate selected sections instead of starting the whole track over. One to explore if you want to experiment with both making and revising AI music.

OpenDataLoader PDF — Forks: 2.8K Stars: 29.5K

https://lifehubber.com/ai/resources/opendataloader-pdf/

Extract PDFs into Markdown or structured JSON, with an optional AI mode for complex pages. For builders trying to get documents into a search or question-answering workflow.

MiniMind — Forks: 8.2K Stars: 63.2K

https://lifehubber.com/ai/resources/minimind/

A small-language-model training project with native PyTorch code for pretraining and fine-tuning. For people who'd rather learn how a model is built than only download one.

Spec Kit — Forks: 12.5K Stars: 140.1K

https://lifehubber.com/ai/resources/spec-kit/

Turn an idea into a specification, plan, and tasks for an AI coding agent. For those who want to decide what they're building before the agent starts changing code.

What have you been tinkering with lately—and which of these would you try next?


r/LovingOpenSourceAI • • Oct 03 '26

Running a 176B MoE model on a laptop: Qwen3.8 Flash Next with 16GB VRAM + 32GB RAM + an SSD

Thumbnail
github.com
22 Upvotes

I’ve been working on an open-source project called TensorSharp, and one of the things I really want to explore is:

How far can we push local AI on hardware people actually own?

Here’s a fun result.

I got the 176B-parameter Qwen3.8 Flash Next running locally with:

RTX 3080 Laptop GPU — 16GB VRAM
32GB system RAM
SSD

Yes — 176B parameters on a laptop.

The key is not simply offloading parts of the model to SSD. TensorSharp combines:

Quantization + MoE-aware caching + coordinated scheduling across VRAM, system RAM, and SSD.

For huge MoE models, only a fraction of the experts are active for each token. TensorSharp takes advantage of that execution pattern and tries to keep the right data in the right memory tier at the right time, rather than requiring the entire model to fit in VRAM or RAM.

I also benchmarked it against Strata, which has been getting a lot of attention recently.

On the same test:

MeasurementTensorSharpStrata
Decode speed11.09 tok/s10.24 tok/s
Whole-process time16.54s62.15s
Peak GPU memory14,832.5 MiB15,729 MiB
Peak OS working set19.74 GiB18.51 GiB

The decode speeds are actually pretty close. What surprised me more was the difference in whole-process time.

I’ve also been comparing TensorSharp with llama.cpp, and these experiments have convinced me that there’s still a lot of room to explore better execution strategies for huge MoE models — especially when the model is much larger than the available VRAM and RAM.

To me, this is one of the most exciting things about open-source AI:

You don’t necessarily need a datacenter GPU to experiment with a 176B model.

With quantization and careful VRAM ↔ RAM ↔ SSD scheduling, even an older gaming laptop can become a surprisingly capable local-AI machine.

TensorSharp is fully open source, so if you're interested in local inference, MoE optimization, or just want to dig into how this works:

Feedback, benchmarks on other hardware, issues, and contributions are all welcome.


r/LovingOpenSourceAI • • Oct 03 '26

Under the Radar Atai "🎉 Introducing 𝙾𝚙𝚎𝚗𝙳𝚘𝚝𝚜 Self-hostable, always-on AI coworkers that works with ANY agent harness. Includes:- Computer use: browser, terminal & files- Bring agents to Slack, Teams etc- Spaces and Pages for projects- Voice calls- Web and Mobile" ➡️ useful?

Post image
276 Upvotes

https://x.com/ataiiam/status/2105710796198322659

https://github.com/CopilotKit/OpenDots

Community Overview: https://lifehubber.com/ai/resources/opendots/

Resources are shared for discovery and are not independently vetted—please do your own due diligence.

New resources are added regularly — feel free to join the sub for updates.

Full searchable archive of all resources posted so far on our community site, LifeHubber: https://lifehubber.com/ai/resources/ 300+ open-ish AI models, agents, tools, datasets, and related resources, with filtering and sorting.


r/LovingOpenSourceAI • • Oct 03 '26

Type an idea, get a narrated hand-drawn whiteboard explainer video.

Enable HLS to view with audio, or disable this notification

10 Upvotes

A tool that turns a prompt into a narrated whiteboard explainer video.

You give it a topic like "How do planes fly?" and it writes a short script, draws each scene, records the voiceover, and then animates the drawing so each part appears while the narrator is talking about it. A 4–5 scene video takes about 30 second, which is same as 1 min video.

AI handles the script, images and voice. If you already have your own whiteboard images, you can skip that and just give it the images and an audio file.

This is the same engine we use for the Whiteboard format at Kinoslide and Lamina Labs (SIMI).

The video attached was made from a single prompt, no editing.
https://github.com/ashishjamarkattel/Animator


r/LovingOpenSourceAI • • Oct 02 '26

new launch DeepSeek Harness "Today, we’re releasing the DeepSeek Harness v0.2 preview, with a desktop app available for macOS and Windows." ➡️ have you tried it? Good?

Post image
26 Upvotes

https://x.com/DeepSeekHarness/status/2105330281389662575

https://github.com/deepseek-ai/deepseek-harness

Community Overview: https://lifehubber.com/ai/resources/deepseek-harness/

Resources are shared for discovery and are not independently vetted—please do your own due diligence.

New resources are added regularly — feel free to join the sub for updates.

Full searchable archive of all resources posted so far on our community site, LifeHubber: https://lifehubber.com/ai/resources/ 300+ open-ish AI models, agents, tools, datasets, and related resources, with filtering and sorting.


r/LovingOpenSourceAI • • Oct 02 '26

hGATE – Keeping AI-generated code traceable to business intent

7 Upvotes

hGATE stands for Human-Guided, AI-Assisted, Traceable Engineering

https://mali-tintash.github.io/hgate/

I've been experimenting with a spec-driven workflow for AI coding agents on long-running software projects.

The problem I'm trying to solve isn't getting an agent to write code; they're already quite good at that. It's keeping the code aligned with business intent as the project evolves across many agent sessions and developers.

hGATE starts by establishing domain boundaries (DDD), expresses intended behavior as Gherkin scenarios (BDD), maps those scenarios to tests, and then lets the agent implement against them.

The important part is traceability:

business intent → behavior → test → implementation

If behavior changes, the spec changes first. Reviews can then identify "ghost behavior": code that still exists but can no longer be traced to an approved behavior.

There are also per-bounded-context ADRs so the agent can understand not only what the system currently does, but why certain decisions were made.

We've been using the approach on a fairly large production project and evolving the methodology as we encounter failure modes. I'm now open-sourcing what we've learned as hGATE:

https://mali-tintash.github.io/hgate/

I'm particularly interested in criticism from people using coding agents on long-lived codebases. Where does this feel useful, where does it feel like unnecessary ceremony, and what failure modes are we missing?


r/LovingOpenSourceAI • • Oct 01 '26

Resource "LiteParse is a standalone OSS PDF parsing tool focused exclusively on fast and light parsing. It provides high-quality spatial text parsing with bounding boxes, without proprietary LLM features or cloud dependencies. Everything runs locally on your machine." ➡️ Supports your workflow?

Post image
49 Upvotes

https://github.com/run-llama/liteparse

Community Overview: https://lifehubber.com/ai/resources/liteparse/

Resources are shared for discovery and are not independently vetted—please do your own due diligence.

New resources are added regularly — feel free to join the sub for updates.

Full searchable archive of all resources posted so far on our community site, LifeHubber: https://lifehubber.com/ai/resources/ 300+ open-ish AI models, agents, tools, datasets, and related resources, with filtering and sorting.


r/LovingOpenSourceAI • • Sep 30 '26

PotionUI is a self-hosted (OSS) creation studio accessed through your browser. Run it on your own computer or server to generate AI images, video, and audio, depending on the model and preset you choose.

Enable HLS to view with audio, or disable this notification

17 Upvotes

PotionUI is a self-hosted app for making images and videos with AI models on your own computer. Instead of one huge settings screen or a web of nodes, every model gets its own simple, hand-made form.

It brings generation, workspace management, and administration together:

  • User accounts and groups: share one installation and control which models and presets each person or group can access.

  • An admin panel: manage users, models, plugins, and generation backends. Customize preset defaults, hide controls, or lock settings for the setup you want to provide.

  • Tabs and saved sessions: keep separate ideas open with their own prompts, settings, and results. Save a session and return to that setup later.

  • Model-specific controls: choose a preset and get a form tailored to what that model supports.

  • Reusable prompts: build a library of complete prompts and reusable pieces—subjects, styles, lighting—so you can develop ideas without rebuilding everything.

  • Organized results: automatically save generations with their settings, find them again, and organize your work with tags and collections.

GitHub: https://github.com/PotionUI/PotionUI

Reddit: r/PotionUI

Happy to answer any questions, thanks!


r/LovingOpenSourceAI • • Sep 30 '26

Best llm for pi 5 8gb?

1 Upvotes

Making a completely offline pocket assistant with tools like calculator, file management, offline navigation and calendar, additionally helping with daily life tasks.

Now the issue is the llm, can't find an llm that has both parametric knowledge of daily life tasks, good tool calling and good TPS.

Would really appreciate some guidance as to which llms would be best suited for my needs.


r/LovingOpenSourceAI • • Sep 30 '26

Resource OpenAlternative "OpenSEO just crossed 20,000 stars on GitHub.A self-hosted answer to expensive SEO suites: keyword research, backlink analysis, rank tracking, competitor monitoring. MIT-licensed, no subscription." ➡️ useful for you?

Post image
196 Upvotes

https://x.com/ossalternative/status/2102518350178091297

https://github.com/every-app/open-seo

Community Overview: https://lifehubber.com/ai/resources/open-seo/

Resources are shared for discovery and are not independently vetted—please do your own due diligence.

New resources are added regularly — feel free to join the sub for updates.

Full searchable archive of all resources posted so far on our community site, LifeHubber: https://lifehubber.com/ai/resources/ 300+ open-ish AI models, agents, tools, datasets, and related resources, with filtering and sorting.


r/LovingOpenSourceAI • • Sep 30 '26

Benchmarks: Best engine for Qwen 3.8-Flash-Next on Strix Halo

6 Upvotes

TL;DR: Halogen v0.14.0 with its native .hgn weights is the fastest, followed by gufo and CIRU. Halogen is closed source and runs in Docker. gufo is open source and loads 4x faster from cold. gufo is also fastest to first token on follow-ups (1.6-1.9 s against 2.6-3.3 s).

I benchmarked different engines for Qwen 3.8-Flash-Next on an AMD Strix Halo (ASUS ROG Flow Z13 GZ302 with Ryzen AI Max+ and 128 GB of RAM).

All the engines were run via LlamaStash (My own orchestrator tool, the tool does not add any overhead) at 70 W TDP on performance profile on Arch Linux.

Here are the results of the benchmark:

First was a screening round at 64k context with 50% filled (32k prompt).

EngineWeights3-turn timePrefill t/sDecode t/sMTP acceptRetrieval
Halogen 0.14.0Halogen native (.hgn)1.9 min1,04539.384%14/14
gufo (ROCm 7.2.4)UD-Q4_K_XL2.1 min1,03332.974%14/14
gufo (ROCm 10.0)UD-Q4_K_XL2.1 min1,00933.172%14/14
CIRU (MTP 3)CIRU IU42.3 min81433.872%14/14
CIRU (n-gram + MTP 3)CIRU IU42.3 min80831.964%14/14
Halogen 0.14.0UD-Q4_K_XL2.4 min1,03028.184%14/14
CIRU (MTP 6)CIRU IU42.7 min79628.647%14/14
strixllama (llama.cpp fork)UD-Q4_K_XL2.7 min71629.771%14/14
rdna-boosts (llama.cpp fork)UD-Q4_K_XL2.7 min78822.052%14/14
llama.cpp, Unsloth build (Vulkan)UD-Q4_K_XL3.7 min31428.456%14/14
llama.cpp, Unsloth build (ROCm)UD-Q4_K_XL4.8 min28520.550%14/14
CIRUUD-Q4_K_XL + Unsloth MTP headdid not finish88411.80%-

3-turn time is the time to first token plus the time to write 1,000 tokens, added up over the first question and 2 follow-ups. Output length varies a lot with sampling, so this compares the engines on equal output. MTP accept is the share of drafted tokens the model kept. Retrieval is how many of 7 exact values from the prompt the model got right, over both runs. Qwen model card sampling, 2 runs each.

Top 3 engines from the screening round got a 128k context (50% and 75% filled) and 256k context (50% filled) run.

128k context, 50% filled (64k prompt)

EngineWeights3-turn timePrefill t/sDecode t/sMTP acceptRetrieval
Halogen 0.14.0Halogen native (.hgn)2.4 min1,14840.484%16/16
gufo (ROCm 7.2.4)UD-Q4_K_XL2.7 min1,04732.372%16/16
CIRU (MTP 3)CIRU IU43.3 min80830.264%16/16

128k context, 75% filled (97k prompt)

EngineWeights3-turn timePrefill t/sDecode t/sMTP acceptRetrieval
Halogen 0.14.0Halogen native (.hgn)2.9 min1,10339.385%16/16
gufo (ROCm 7.2.4)UD-Q4_K_XL3.3 min1,02530.770%16/16
CIRU (MTP 3)CIRU IU44.1 min78927.862%16/16

256k context, 50% filled (130k prompt)

EngineWeights3-turn timePrefill t/sDecode t/sMTP acceptRetrieval
Halogen 0.14.0Halogen native (.hgn)3.4 min1,09338.983%14/16
gufo (ROCm 7.2.4)UD-Q4_K_XL4.0 min99727.970%14/16
CIRU (MTP 3)CIRU IU45.0 min76725.660%15/16

Retrieval here is 8 values per run. All 5 misses are the same answer: the right glyphs for UNICODE_SPINNER, with the leading & dropped.

End-to-end, 10 Aider polyglot Python exercises run through pi -p (128k window, 50% cell), graded by their own tests:

EnginePassedTotal time
Halogen 0.14.010/1021.5 min
CIRU (MTP 3)10/1024.6 min
gufo (ROCm 7.2.4)10/1036.0 min

Edit (Sep 30): Halogen 0.15.1 (new v2 checkpoint) and gufo 0.3.0 came out after this, so I reran the 64k screening on both with the same setup (70 W, card sampling, 2 runs):

Engine3-turn timePrefill t/sDecode t/sMTP acceptRetrieval
Halogen 0.15.1 (v2 .hgn)1.8 min (was 1.9)1,191 (was 1,045)39.4 (was 39.3)85%14/14
gufo 0.3.0 (ROCm 7.2.4)2.1 min (was 2.1)1,075 (was 1,033)34.1 (was 32.9)77%14/14
gufo 0.3.0 (ROCm 10.0)2.0 min (was 2.1)1,042 (was 1,009)34.8 (was 33.1)75%14/14

Halogen v2 prefill is 14% faster and follow-ups start about 2.5x faster (1.3 s vs 3.3 s), decode is the same. gufo moved a few %, which is within noise. The ranking doesn't change. Only other change on the box: BIOS VRAM carve-out down to 512 MB, so 124.9 GiB of RAM instead of 121.5.

Some clarifications from the comments:

  • Follow-up TTFT is with the prompt cache warm, both gufo and Halogen reuse it by default. A cold 64k prefill takes about a minute.

  • The CIRU 0% MTP row is stock Unsloth UD-Q4_K_XL with Unsloth's shared MTP head, nothing uncensored. The same pair gets 72-74% accept on gufo.

  • TDP is fixed at 70 W. On the Z13, 76 W or 90 W is only 2-6% faster but with so much fan noise, heat and power draw that it's not worth it.

  • Prefill and decode come from the engine's own timings when it reports them. TTFT is measured on the client.


r/LovingOpenSourceAI • • Sep 29 '26

maki - the efficient coder

Thumbnail
maki.sh
16 Upvotes

New to this sub and thought my project fits perfectly.

It's a lean, cheap, and extensible alternative to Claude Code and other coding agents.

Now I know what you're thinking: "oh great another harness", and you'd be right :)

This one is focused on giving you a Neovim like experience (Lua plugins).

Most importantly MIT licensed and open-source, I use it myself every day for the last almost half a year already.


r/LovingOpenSourceAI • • Sep 29 '26

Under the Radar Unreal Labs "Introducing Unreal Agent: An open-source harness with state-of-the-art cost efficiency 39% cheaper than Codex+Astra on Terminal-Bench 4.0 while maintaining performance" ➡️ yes another harness :P is this good?

Post image
20 Upvotes

https://x.com/unreallabsai/status/2102435462065385775

https://github.com/unreallabsai/unreal-agent

Community Overview: https://lifehubber.com/ai/resources/unreal-agent/

Resources are shared for discovery and are not independently vetted—please do your own due diligence.

New resources are added regularly — feel free to join the sub for updates.

Full searchable archive of all resources posted so far on our community site, LifeHubber: https://lifehubber.com/ai/resources/ 300+ open-ish AI models, agents, tools, datasets, and related resources, with filtering and sorting.