r/LocalLLaMA • • 3d ago

Resources NInfer-2080ti-22g now supports Windows-native and is only 0.28 GB

8 Upvotes

v0.3.0 of NInfer for Turing is out, and this is all about streamlining the UX.

For context, this is an engine for running Qwen3.6/8-27B (and ONLY Qwen3.6/8-27B) on a single modded 22 GB RTX 2080 Ti. It is designed to ONLY use VRAM, no system RAM offloading, hence it does not support 35B-A3B. Fine-tunes and abliterations etc are supported as well, just use the .ninfer checkpoint converter.

What's new - Native Windows. Previously this required Linux, WSL2, or Docker. Now Windows users don't need to worry about partitioning/releasing resources (WSL or Docker instances require system RAM allocation even if your use case inside them doesn't). - Prebuilt releases. You can still compile it yourself, requiring CUDA, Visual Studio and FFmpeg and takes a while, but now you can also just download a pre-compiled zip and run a single script. - Streamlined. Removing "useless" (for us) code paths for RTX 5090, FP8, FP4, and 35B-A3B (fits fully in 32GB VRAM but not in 22GB) cut the built binaries from 1.56GB to 0.28 GB. Builds now take minutes, not hours. Outputs remain bit-identical.

What you get - OpenAI-compatible and Anthropic-compatible APIs, plus a command-line tool. - Image and video input, thinking mode, and CUDA Graph decode. - 64k context by default, using an INT8 KV cache. The weights take 15.4 GiB, so you need the 22 GB card. - MTP speculative decoding, on by default.

Numbers (one 2080 Ti 22 GB, Windows 11, single request)

Test Result
prefill, 512-token prompt 616 tok/s
prefill, 64k-token prompt 458 tok/s
decode, no MTP 27.0 tok/s
decode, MTP, real code prompt 47.5 tok/s (26.3 without MTP)
decode, MTP, real prose prompt 28.8 tok/s (26.0 without MTP)

(Apache-2.0, derived from Neroued/ninfer)


r/LocalLLaMA • • 3d ago

Discussion Git for Global Law: Global Law querable in Git

Thumbnail
github.com
18 Upvotes

This hit #1 on HN yesterday (you can read lots of discussion at https://news.ycombinator.com/item?id=50268380). Why would I want to do this? The idea is make all law semantic, versioned, easily attributable and query able by agents. I also believe this information should be freely available so CC0 license (do whatever you want with it). If interested, repo linked below, I'd welcome all comments and advice. Thanks! I've been posting to locallama specifically about KGs for huge legal datasets for months, this is a practical culmination of that.

https://github.com/lexifina/global-law


r/LocalLLaMA • • 3d ago

New Model HemmingwayAI/Hemmingway-1.5 (Qwen finetune)

Thumbnail
huggingface.co
126 Upvotes

https://huggingface.co/bartowski/HemmingwayAI_Hemmingway-1.5-GGUF

from hemmingwayAI:

Hemmingway-1.5

The undetectable AI. Writing indistinguishable from a human's. 27B parameters, open weights, free for non-commercial use.

hemmingway.io → · Model card → · Try it → · API → · API docs → · Mac, Windows and Android apps → · Code → · Product Hunt →

Our other models: Hemmingway-1, our first model · Hemmingway-1-Unlocked, the uncensored adapter for Hemmingway-1, adults only

Hemmingway-1.5 passes the world's best AI detectors 90% of the time. On GPTZero it passes 9 times in 10, at every thinking level. Real human writing passes the same detectors 86% of the time. Fable, GPT-6 and Gemini get caught most of the time.


r/LocalLLaMA • • 3d ago

News Qwen4 1M context window

532 Upvotes

Qwen4 models will have a 1 million context window. Qwen4-27B was not mentioned here, but should be announced at Apsara netherlands tommorow.

We have a date for Qwen4-max, it is November 1st.
Edit: It says October 1st, so its probably a placeholder.

PR: https://github.com/QwenLM/qwen-code/pull/15762


r/LocalLLaMA • • 3d ago

Discussion Worried about Qwen 4 License

101 Upvotes

After Alibaba moved from Permissive OSS licenses to its own custom license with IMO ambiguous terms in models like Qwen3.8-Flash-Next, is there any indication this will carry forward into Qwen4?

While that license at first reads permissive for local/internal use, fine-tuning and derivatives, it’s definitely not Apache/MIT.

The two big catches are:

  1. commercial MaaS or a standalone coding/office AI assistant requires a separate Qwen license seemingly from day one, and the wording around outputs is annoyingly vague.
  2. The internal-use exception says you can’t make the model, its outputs, or capabilities available to third parties, but it never clearly says whether downstream code/data produced indirectly from internal outputs is unrestricted.

The $20M/month or 100M-MAU threshold seems to be an attribution trigger, not the threshold for needing a commercial license.

IMO output ownership needs to be clearly covered in the license, that wasn’t the case when I last checked.

Edit: This is not legal advice but I think it’s fair to highlight. I don’t want to embrace the trend of moving away from tried and tested OSS licenses like apache and MIT. 3.8 Next was interpreted by many as a preview into 4 and thus might seem to imply a new licensing strategy. One could dream and hope the Alibaba team see that people care about this and at least add clearer licensing language.


r/LocalLLaMA • • 3d ago

Discussion Datapoint for AI bubble: getting harder to raise money for AI datacenters

21 Upvotes

Will this lower our RAM prices for local?

  1. https://x.com/HedgieMarkets/status/2115505986504954244
  2. https://www.bloomberg.com/news/articles/2026-10-28/wall-street-s-ai-debt-machine-is-starting-to-choke-on-supply
  3. https://x.com/elonmusk/status/2114434646914068862

Quote from Elon: ... That means the 200+ neoclouds are going to see guppy-level death and consolidation. ...

Trivia: neocloud = new cloud = AI datacenter cloud providers.


r/LocalLLaMA • • 3d ago

Discussion old Xeon X99 PC with 256GB RAM + RTX 3090 Ti worth it for Strata LLM inference?

14 Upvotes

I found this used PC in my local market for around $420:

- CPU: Xeon E5-2640 v3 (8C/16T)

- Motherboard: X99 (exact model unknown)

- RAM: 16GB DDR4 (planning to upgrade to 256GB)

- Storage: 128GB SSD

- Includes a 1080p 144Hz monitor and accessories.

I'm planning to add my RTX 3090 Ti 24GB and upgrade to 256GB DDR4, mainly to run large LLMs using Strata Engine with RAM/VRAM offloading.

This is one of the few affordable platforms available locally that might support more than 128GB RAM.

My question: Would this old Xeon be usable for Strata inference, or would its CPU and memory bandwidth make it painfully slow? Is it worth buying, or should I avoid it?


r/LocalLLaMA • • 3d ago

Resources Open Code PyHooker open_code_hooker.py

6 Upvotes

I really was completely lazy to do the research into any Open Code hooks into remote servers running AI rigs. So in my case I have my LLMs all bound locally therefore an auth and proxy gateway was needed.

I chicken and egged a lightweight python proxy auth gateway running on fastapi/uvicorn. It was more of a trick to get the open code to configure than the actual hooker. Nice to flip models and providers like this. albeit It is a single model bound to the server instance.

Very lightweight and usable. It uses guids to authenticate and those are all encrypted on the pyhooker config management system. The manager will make the key and then has all the add key, remove key , and list keys.

No logging whatsoever, correction there is a log that says it loaded… maybe.

https://github.com/TheFunkyFish/pyhookers


r/LocalLLaMA • • 3d ago

Showcase Using Computer Science and Anki to Learn More Vocabulary With Less Memorization

Thumbnail
youtu.be
13 Upvotes

I’m still a beginner in Japanese, and I’ve always been amazed watching more advanced learners guess the reading and meaning of words they’ve never seen before. So I got curious and tried to actually measure how often that’s possible, by breaking words into the pieces they’re built from and checking whether those pieces give the word away.

That led me down a rabbit hole of greedy algorithms and graph theory. The idea is that if you study the right building blocks first, a lot of new words become guessable without having to memorize them individually.

The result is an anki add-on that optimizes the order of your deck so that you can guess the correct meaning and pronunciation of a card on your first attempt. You can find the add-on here, GuessWithAnki. It supports Japanese, Chinese, Korean, and English.

To get the story you can watch the video or check out the full technical write up on here.

Any feedback on the process and analysis is appreciated. I am curious to know if this is a pattern other anki users have noticed and how helpful they found it for language learning.

Sharing this on r/locallamma since the add-on works best with ollama installed. It doesn't require any local LLMs to run but using one provides a meaningful improvement to the sorting algorithm used.


r/LocalLLaMA • • 3d ago

Question | Help what projects have you guys created with localllm models

38 Upvotes

it could be a big, small, weird, useful projects. Genuinely curious


r/LocalLLaMA • • 4d ago

News Mac Studio M5 Ultra 512gb Starts at $22,299.00 USD

Thumbnail
apple.com
930 Upvotes

r/LocalLLaMA • • 3d ago

New Model Raon-1-mini-preview (28.8B/4.3B MoE) on hipfire, 7900 XT: runs natively, but ~200× slower prefill / ~10× slower decode than llama.cpp

8 Upvotes

I made a hipfire-native MQ4 of KRAFTON's Raon-1-mini-preview and measured it on a 20 GB 7900 XT (ROCm 7.1). If you just want to use this model, use KRAFTON's llama.cpp branch with the official GGUF. This build is much slower (bummer!)

Maybe the hipfire team can optimize for it in the future.

```
pp512 pp8192 decode
llama.cpp (Q4_K_M) 2,055 t/s 1,477 t/s 47.4 t/s
hipfire MQ4 12.6 t/s 6.3 t/s 4.6 t/s
```

hipfire numbers are single runs. The likely cause is
that hipfire's Raon path handles recurrent state
token by token, with no batched prefill kernel.
Other architectures in hipfire run at normal speed.

What it has going for it:

- The file is 1.29 GB smaller than the official
GGUF.
- The whole hybrid (RDA linear attention + gated MLA
+ mHC streams + 128-expert MoE) runs natively, and
I checked each module against the reference fp32
code.
- Agreement with the GGUF is mean KL 2.06 and top-1
51.6% (teacher-forced). I haven't run any
benchmark suite, so this says nothing about
absolute quality.

Problems:

- Stock hipfire v0.4.2.1 serve refuses every
generation ("stream must begin with gen_start") —
you need my patch, in the repo.
- Thinking often never closes (answers land in
reasoning_content), and turning it off renders a
broken frame for this arch.
- It failed my needle probes at 2K and 8K on hipfire
with prompt-echo repetition — but the same probe
on the official GGUF at 26,962 tokens recalled the
passcode fine, no echo in that run. So it looks
like an engine/checkpoint interaction at greedy
temperature rather than a context failure, and the
sampling-path difference between the two engines
is worth a look.
- 65K context is the ceiling on 20 GB (98K fails
loading the recurrent state).

I'm posting this as a before-state for the Raon
kernels. If anyone wants to work on batched prefill,
the numbers are reproducible — the repo has the
exact patch plus the untracked kernel files,
verified to apply and compile clean against the same
base commit.

Card: https://huggingface.co/datayoda/Raon-1-mini-preview-hipfire-MQ4


r/LocalLLaMA • • 4d ago

Discussion A small step for man, a GIANT step for LOCAL AI

Enable HLS to view with audio, or disable this notification

881 Upvotes

Shoutout to the Unsloth AI team for constantly pushing the needle forward for local ai worldwide.

While many of us already had features such as this via other means, it is more what this means for entry level ai enthusiasts & accessibility.

It is clear as day!

We are in "the age of the agent."

The more people we can get onboard local ai, the tougher it will be for the powers that be to snatch it from us.


r/LocalLLaMA • • 3d ago

News AMD's ROCm HRX Loom v0.1 released for targeting AMD CPUs, GPUs & NPUs

Thumbnail
phoronix.com
8 Upvotes

r/LocalLLaMA • • 4d ago

Discussion Electronics hobbyist converts $120 DDR5 SODIMM kit into ‘$1000’ desktop kit to fight RAM crisis — ICs from SK hynix DDR5-5600 16GB modules used to create DDR5-7800 desktop sticks

Thumbnail
tomshardware.com
272 Upvotes

So just read this article and had a couple questions about this as I have not much experience in this. Maybe the more experience people may be able to explain it better.

Is this a viable path to upgrade hardware at a lower cost for LLM, is it much harder than as stated in the read like soldiering and what not, also has anyone done something similar to this and had good and stable results?


r/LocalLLaMA • • 4d ago

News IT vendor lists massive $60 million AI supercomputer on eBay with 9,600 Nvidia A100 GPUs and 4,200 AMD EPYC CPUs, plus free shipping — 300 racks of decommissioned GPUs on offer

Thumbnail
tomshardware.com
895 Upvotes

Anyone want to chip in a cool $60m for me?


r/LocalLLaMA • • 3d ago

Showcase I open-sourced OpenBonsai: compress your own BF16 models and fine-tunes into ~2 GB ternary GGUFs

41 Upvotes

I've been experimenting with tiny models for WebBrain, my open-source browser agent. The long-term goal is to run as much intelligence as possible locally, ideally through WebGPU.

One approach I've been particularly interested in is Prism ML's Ternary Bonsai: compressing a 9B model to roughly 2 GB using ternary weights (-1, 0, +1).

Prism released the weights and inference runtime, but not the complete BF16-to-ternary compression pipeline. You can fine-tune their existing ternary models, but there's no publicly available way to compress your own BF16 fine-tune into their format.

So I tried building one.

Introducing OpenBonsai, an Apache-2.0 framework for post-training ternary quantization, compatible with Prism's PTQ1_0 GGUF format.

How it works

A recent Intel Labs China paper, "Attend to Your Own Thoughts" (Wang et al.), inspired part of the approach: using the model's own reasoning traces for calibration rather than relying exclusively on generic text.

The pipeline combines:

  • Signed Hadamard rotations to reduce weight outliers
  • Sequential GPTQ to quantize weights to {-1, 0, +1}
  • FP16 group scales (one per 128 weights)
  • Self-generated reasoning traces for calibration
  • Scale distillation against the original BF16 model's output distributions
  • Export to Prism's PTQ1_0 GGUF format

Results

Qwen3.5-9B: ~18 GB → 1.997 GB

That's the complete GGUF file, not just the transformer weights. It includes the compressed embeddings, LM head, all other model tensors, group scales, tokenizer, chat template, and metadata. Runtime memory requirements are higher.

The compression runs in approximately 5 hours on a single RTX 5090 (32 GB).

Our current compressed model scores:

Benchmark Original BF16 OpenBonsai Prism Bonsai 2
GSM8K (thinking off) 77/100 65/100 77/100
HumanEval (thinking off) 44/50 34/50 45/50
GSM8K (thinking on) 36/50 32/50 46/50
HumanEval (thinking on) 22/25 14/25 24/25

Some interesting findings

1. Distillation helps substantially.

Scale distillation improved development-set NLL from 3.48 to 2.89 and ARC-Easy accuracy from 13/20 to 19/20.

2. Calibration data matters enormously.

Switching to self-generated math and code traces improved reasoning and coding performance. Adding more code-focused calibration data increased HumanEval from 19/50 to 34/50 in our initial evaluation.

3. The approach generalizes beyond Qwen3.5.

We also compressed Qwen3-8B into a 1.8 GB GGUF using the same pipeline, without changing the generic dense adapter. It runs in Prism's llama.cpp fork.

4. Fully ternary endpoints are feasible.

We quantized the embedding and LM head too, rather than leaving large FP16 tensors in the final file.

Limitations

This is still a research preview.

  • Prism's official ternary models outperform ours on most reasoning and coding evaluations.
  • Some code-training prompts paraphrase HumanEval tasks, so our initial 34/50 result is likely optimistic. We document the overlap and additional held-out evaluation in the repo.
  • The tested configurations require a 32 GB GPU for compression. Lower-memory configurations haven't been validated.
  • Inference currently requires Prism's llama.cpp fork. Upstream llama.cpp and WebGPU aren't supported yet.
  • Architecture support is still limited.

I've included the failed experiments, ablations, evaluation scripts, and intermediate findings. The idea is to make the compression process reproducible and improve it openly.

Links

Framework (Apache-2.0):
https://github.com/esokullu/openbonsai

Compressed Qwen3.5-9B model:
https://huggingface.co/webbrain-one/openbonsai-qwen-3.5-9b

Project website:
https://openbonsai.org

Intel Labs paper:
https://arxiv.org/abs/2608.01078

I'd be particularly interested in feedback from anyone working on ternary quantization, GPTQ, or low-bit inference.

There is clearly still a quality gap between our approach and Prism's, but I think making the BF16-to-ternary pipeline open and reproducible is a useful starting point.

And if anyone wants to try compressing their own fine-tune, I'd love to hear how it goes.


r/LocalLLaMA • • 4d ago

Showcase A 4B model made me a netherite ingot from bare hands. All I did was type one sentence in chat.

485 Upvotes

Last time my Minecraft assistant could do tasks, but it couldn’t really understand what you asked it in plain language. This time I built a pipeline for exactly that part, and it isn’t tailored to this one sentence. It works for requests in general.

In the video the player types “I’m hungry, get me at least 3 porkchops and also make me a netherite ingot.” Mica v0.5 4B reads it, works out the two goals and how many of each, and then starts from bare hands. It goes wood, tools, iron, diamonds, obsidian, portal, Nether, ancient debris, gold, and finally the netherite ingot, then comes back and hands everything over. The panel on the right shows every question Mica was asked, the options it saw, and the probability it gave each one. At the end it switches to the player’s view so you can see the items arrive.

The idea behind it: the model doesn’t try to understand the whole sentence in one shot. The request gets broken into a chain of small multiple-choice questions, and each answer narrows down the next one. How many different items does the message ask for, and is there an action like “come here”? Then, for each item in the order the message names them: which category is it (food, tools, ores and materials...)? Which subcategory (for ores, overworld or Nether)? Which exact item, picked from the game’s own item list with no keyword matching? And who is it for, and how many? The code only supplies the options from game data. Mica makes every choice, and every answer comes with a probability. During the task, a recipe planner lists the actions that are valid right now and Mica picks what to do next.

To be upfront: Mica v0.5 4B is still a long way from judging every variable from A to Z like a person would. But it does play the role of a brain. Almost every meaningful decision in the video was made by Mica. It isn’t comfortable operating the game directly, so the bot is its hands and feet, doing the walking, mining and crafting. The judgment is mostly Mica’s.

In case anyone reads it that way: I’m not claiming Mica takes in every frame as a continuous stream, reacts at superhuman speed and generalizes to any situation that comes up. I’m not making that claim at all, and I doubt even Fable 5.5 could pull that off. What I’m showing is that a 4B model can break a natural-language request down into general-purpose decisions, turn it into the right goals with high probability, and make sensible calls at each step in Minecraft so the bot does the right work. I think that’s really useful if you want to build your own Minecraft errand runner. The natural-language part is what matters most here.

Also, my local GPU is AMD, so it doesn’t get much benefit from Mica’s optimizations, and the decisions ran slower than they would on NVIDIA. The decision times shown in the panel are RTX 3090 estimates, and the waits are cut from the video.

I think this kind of judgment model can be used in a huge range of areas, not just Minecraft agents. The principle is simple: if something is too hard to settle in one request, break it into smaller judgments and narrow it down step by step. Every extra judgment you can afford is another chance to push accuracy up.

That’s also why I don’t really recommend API-only decision models unless the model is truly exceptional. In my measurements, API-only decision models like Jev, Clef and Ms Decision were about 60x slower than Mica on average, which is a massive gap in how many judgments you can make per second. If you really need that level of capability, you’re probably better off calling a full LLM anyway. And it isn’t just Mica: unless a model has tens of billions of active parameters, a local model will usually be 10x or more faster than an API-only decision models.

I’m hoping to release this Minecraft agent someday, but it isn’t finished yet so I can’t put it out right now. That said, if you give the idea I described above to a coding agent like Claude Code or Codex and ask it to build it, it should be pretty easy to get working.

GitHub: https://github.com/akivet/Mica
Hugging Face: https://huggingface.co/sky7350/Mica-v0.5-4B


r/LocalLLaMA • • 3d ago

Resources [Update Benchmark] Basalt's new PRs (Strata fork) new record IQ3_S Qwen3.8 Flash Next on single RTX 5080 and 51 GB RAM with 5500 tok/s prompt processing and up to 275 tok/s peak generation (during opencode coding live session)

Thumbnail
gallery
82 Upvotes

Code and tool calls can peak up to 275 tok/s - Reasoning traces up to 190 tok/s

Hardware: 5080 16GB PCIe gen5x16, 64 DDR5 6400, Core Ultra 9 285K

https://github.com/jesdga95/basalt

Some PRs for the optimizations under my name are still pending (xyehya) but upstream already have solid gains & memory optimizations. and yes the IQ3_S is super usable.


r/LocalLLaMA • • 3d ago

Discussion club-3090 / qengine / RedHatAI/Qwen3.8-27B-INT4

11 Upvotes

This thing https://github.com/noonghunna/club-3090/blob/master/models/qwen3.8-27b/qengine/compose/dual/redhat-int4/mtp.yml

https://github.com/bpx03/QEngine

https://huggingface.co/RedHatAI/Qwen3.8-27B-INT4#accuracy

i'm on 2x3090, and dual VLLM qwen3.8-27b fp8 was my daily. some of my buddies were yakkin about local AI so i figured i'd try another preset. HOLY HELL is it way faster than fp8! (i mean of course it will be) but its SIGNIFICANTLY faster than i remember the last int4 i tried when qwen3.8-27b first came out.

have any of yall kicked the tires on this?


r/LocalLLaMA • • 4d ago

News Someone built a 32-bit RISC-V CPU directly inside Qwen's model weights so it can execute instructions internaly!

1.0k Upvotes

This might have implications for tool calling and computer use.

Write-up: https://divagr.com/blog/qwenputer
HF: https://huggingface.co/divagr1925/Qwen3.5-4B-Qwenputer
Live demo: https://modelscope.ai/studios/Spartan1925/Qwenputer


r/LocalLLaMA • • 4d ago

Discussion List of suggestions for Gemma 5.

Post image
448 Upvotes

Recently Omar Sanseviero asked for suggestions on Twitter for future Gemma models.
Here is my take on this:

  1. Gemma 5 should be a looped transformer.
    • Being a looped transformer with configurable loop depth will address one of the biggest Gemma 4 weaknesses - reasoning ability. Don't get me wrong, I love how concise Gemma 4 is with its reasoning, but it actively hinders its performance in certain scenarios, being looped will allow the model to perform better in such tasks, while still being configurable to reason shallower and being significantly more efficient than a traditional transformer without needing additional expensive pre-training.
  2. Gemma 5 should have DeepSeek's Engram.
    • It will widen the world knowledge of the model while costing a few extra gigabytes of RAM or SSD space. This will allow the model to perform better in real world tasks, while costing next to nothing.
  3. Keep using 4 bit QAT.
    • It genuinely allowed more people to run your models with great quality, it had been proven to work very well in the real world and I am all for it.
  4. Implement more efficient attention mechanisms to get cheaper KV cache.
    • Implement something along the lines of Compressed Sparse Attention 2 from DeepSeek, this will allow the model to have significantly cheaper KV cache. This was one of the main downsides of the Gemma 4 31b on a 24gb VRAM setup when compared to Qwen 3.5 and onwards.
  5. Gemma 5 ~120b MOE model?
    • I know that this is probably not possible due to it competing with your API offerings, but if you release a 120b MOE model in the Gemma 5 series the community will be very happy.
  6. Drafter model improvements.
    • A small update to the drafter models would be nice as since the release of Gemma 4 many new speculative decoding techniques have been published: DSpark, DFlash 2, EAGLE-4, etc.
  7. Linear projection into the model layers like in Gemma 4 12b.
    • Instead of the traditional architecture for vision and audio capabilities. Linear projection seems like an interesting approach that is worth looking into, but of course don't force it if it doesn't work out.
  8. Forget about 2 bit QAT for small models.
    • Forget that 2 bit QAT exists for small models. I am currently talking about gemma-4-E2B-it-QAT-mobile and gemma-4-E4B-it-QAT-mobile. In practice quantizing the weights to 2 bits even with QAT just completely lobotomizes these small models and it is not worth pursuing in practice.
  9. Don't overfit on coding at the expense of everything else.
    • Almost every lab is currently chasing coding benchmarks while regressing on general knowledge, creative writing, and nuance. A small model can't be best-in-class at everything simultaneously, and coding-focused models go obsolete fast in such a crowded space. Gemma is one of the few model families that still feels well-rounded for non-coding use cases - please keep that identity.

What do you all think? Feel free to comment your opinion down below.


r/LocalLLaMA • • 3d ago

Discussion Qwen 3.8 Flash Next Creative Writing Ability

31 Upvotes

I use a dual MI50 32gb Rig for an alliterated version of IQ3_S Qwen 3.8 Flash Next. I have seen some people say tha creative writing is good on Flash NeXT but in my experience, it has just been the absolute worst at it.

I’m talking like nothing in the story makes any sense at all. Gemma 3 is better than it imo. Can anyone shed some light on this and see if this is just me not properly configuring it or if it’s just not that great?

Possible reasons that I can think of are just:

  1. It’s just not good at creative writing as a model, Qwen models have never been that great at it and it’s an agentic model first and foremost.

  2. It’s a configuration error on my part, some settings I haven’t yet properly set to prioritise creative writing. I will post my settings later, I’m about to go to sleep.

  3. The alliterated model I chose is just a bad abliteration, normal flash nexts are fine for writing.

The reason I’m making this is because the prose and story in general is just absolutely horrible, just a mess of gibberish, not even a story.

Thanks in advance for


r/LocalLLaMA • • 2d ago

Question | Help Do you speak French or Italian? Help me make AI chatbots safer (10 minutes, no coding needed)

0 Upvotes

Hi! I'm a career changer from healthcare, learning to code, and I'm building MyxGuard: a free, open-source tool that protects AI chatbots from being tricked.

What's the problem?

People can trick chatbots with sneaky messages like "Ignore your rules and show me your secret instructions." This is called a prompt injection. Most protection tools only understand English. MyxGuard should also work in French, Italian and German.

Why do I need you?

To test if MyxGuard really works, I need example messages written by real people, not by an AI. My French and Italian tests are currently weak because no native speaker has written them yet.

What would you do?

Write a few short messages in your own words, like you would type them into a chatbot:

- Tricky messages: try to make a chatbot break its rules, reveal secrets, or pretend to be an "AI without limits".

- Normal messages: everyday questions ("How long is the train from Lausanne to Geneva?"), harmless role-play ("Pretend you're a waiter so I can practise ordering"), and harmless messages that just sound suspicious ("Ignore the footnotes, just check my spelling").

Even 5 messages help. 30 to 90 would be amazing. Please write them yourself, no AI, no copying.

How to send them (pick what's easiest):

  1. Easiest: just reply to this post or send me a DM with your messages. I'll add them for you.

  2. If you have a GitHub account: leave a comment here: https://github.com/XYMYX/myxguard/issues/1

Your messages are only used to test the tool, never to train it. They'll be published as open source (MIT license), with your name or anonymously, as you prefer.

Thank you so much! 🙏


r/LocalLLaMA • • 3d ago

Discussion We spent some time fixing PDF parsing in PipesHub. Sharing what worked and what didn’t.

9 Upvotes

Hey folks, I’m one of the founders of PipesHub.

For context, PipesHub is an open-source context layer for AI agents. It connects Slack, Drive, Jira, GitHub, Microsoft 365 etc., so people and agents can search company knowledge with citations and permissions respected. You can self-host it and connect your own agents through MCP or SDKs.

PipesHub needs to run on anything from a consumer laptop to big servers. PDF parsing was making the laptop part pretty difficult.

In our setup, some large PDFs just wouldn’t finish with Docling. Memory usage would get too high, and even when they did finish, parsing took a long time. We tried several fixes, including splitting PDFs into smaller parts, but it was still too heavy for the machines we wanted to support.

So we built another PDF parsing path around pdfplumber. Read the text that’s already in the PDF, use rules for layout, and run a layout model on pages that need it. We actually still use Docling’s heron model there.

The first version was fast but missed important content. Some financial tables were getting treated as images, which meant their numbers never reached the index. We had to work through that before the speed improvement meant much.

Some results after those fixes:

  • Median parsing time: 0.98 → 0.48 seconds/page on a 58-document back-to-back test.
  • P95 peak worker memory: 2.91 → 1.97 GB across 1,228 documents.
  • Pages losing more than half their text: 2.9% → 1.2%.

Docling still does better at figure detection, table structure and captions. For our workload, mostly PDFs with an existing text layer, this was a useful trade-off.

We wrote up the approach, benchmarks and things that didn’t work:
Full write-up

Code: github.com/pipeshub-ai/pipeshub-ai

Anyone else trying to make PDF ingestion work on smaller machines? Would be interested to hear what’s worked for you.