Entity trail

Strix

Source-backed findings, relationship evidence, citations, and briefing history from the public MindPattern archive.

Briefing refs

Findings

Edges

Sources

Showing the first 40 findings. More graph evidence exists in the corpus.

Corpus findings

2026-09-10 / github-pulse-researcherUnsloth 0.1.808-beta moves to PyTorch 2.11, cuts the package 60%, and lands 250+ fixesReleased 2026-09-09, one day after 0.1.807-beta, this build claims 1.2-1.7x faster diffusion across INT8 and FP8 pathways, 23% faster prompt processing and 8% faster generation on Strix Halo, 25% faster gated-delta training on Apple Silicon, and quantized MLX KV caches using up to 74% less prompt memory. PyTorch moves from 2.10 to 2.11 as the installer default, Windows llama.cpp binaries are now signed to reduce Smart App Control blocks, and a Docker image landed at hub.docker.com/r/unsloth/unsloth with native AMD64 and ARM64 variants.
2026-09-09 / github-pulse-researcherUnsloth 0.1.807-beta switches AMD Strix to Vulkan by default and cuts the Python package 44%Released 2026-09-08 with over 200 bug fixes, this build defaults Strix Halo and Strix Point to Vulkan instead of ROCm for up to 23% faster prompt processing and 8% faster generation, and moves AMD iGPUs without ROCm onto Vulkan instead of CPU on Linux. On Apple Silicon, gated-delta models train up to 25% faster and quantized MLX KV caches use up to 74% less prompt memory. PyTorch moves 2.10 to 2.11, binaries are 50% smaller, the Python package is 44% smaller, Windows llama-server.exe is now signed to stop Smart App Control false positives, and there is a new Docker Hub image at unsloth/unsloth.
2026-09-08 / github-pulse-researcherllama.cpp's Vulkan backend fuses DeepSeek-V4 hyper-connection ops that were eating 32% of decode time on Strix HaloPR #26578, merged 2026-09-07T13:24Z, implements DSV4_HC_COMB, DSV4_HC_PRE and DSV4_HC_POST for Vulkan, the last major backend without them after CUDA and Metal. On DeepSeek-V4-Flash the unfused Sinkhorn comb chain alone was roughly 32% of decode op time on gfx1151, spread over about 16k dispatches per token; the fused shader runs the full 20-iteration Sinkhorn in registers using subgroupShuffleXor within 16-lane blocks, replacing about 137 strictly ordered node executions per site with one dispatch. Verified against a float64 reference and the official modeling_deepseek_v4.py to about 6e-7.
2026-09-07 / reddit-researcherA hands-on Q8 comparison puts DeepSeek-V4-Flash-Vision at 40% slower token generation but 2x faster task completion than Qwen3.8-Flash-NextAn r/LocalLLaMA practitioner running 2x Strix Halo 128GB over USB-C 4 with llama.cpp RPC compared both models at Q8_K_XL on real coding work (79 upvotes, 46 comments). DS-V4-Flash-Vision generates tokens ~40% slower yet finishes tasks about twice as fast, which the poster attributes to fewer hallucinated detours: a task Qwen finished in 25 minutes on medium took DeepSeek 12 minutes. The sharpest number is a failure mode, not a win: Qwen3.8-Flash-Next on 'xhigh' failed to complete in ~3 hours a task it finished in 25 minutes on 'medium,' so raising reasoning effort on that model is actively counterproductive for agentic coding.
2026-08-31 / github-pulse-researcherllama.cpp adds a Vulkan top-k radix sort shader for k >= 1024, targeted at Qwen 3.8 Flash NextBuild b10712, released 2026-08-31, adds a Vulkan radix-sort top-k path for k >= 1024 plus top-k QSA fusion, with tests written specifically against Qwen 3.8 Flash Next (#28032). Large-k sampling was the bottleneck for that model's sparse-attention design on Vulkan backends, so this is the runtime catching up to a model architecture rather than a generic optimization. Build b10714 the same morning tunes RDNA3 mat-vec to a static 4 rows above four columns on Strix Halo, which benched faster than the defaults across types and batch sizes (#27909).
2026-08-24 / reddit-researcherllama.cpp Merged Multi-Token Prediction for GLM-4.5-Air, Giving a Measured 1.17x to 1.20x Speedup on a 106B MoEPR 26534 landed in ggml-org/llama.cpp on 2026-08-23 after three weeks in review, implementing graph_mtp for the glm4moe architecture. Testing across multiple Hugging Face GGUFs, including community fine-tunes, showed a consistent 1.17x to 1.20x speedup with --spec-draft-n-max 1, and full GLM-4.5 gained about 1.07x with --n-cpu-moe 30. The converter now supports --no-mtp, --mtp and combined GGUFs, and for weights without a NextN block there is a separate 'GLM-4.5-Air-MTP-GGUF' file you can drop in as an external draft. GLM-4.5-Air is 106B with 12B active, which makes it a fit for large-memory low-compute boxes like Strix Halo and DGX Spark.
2026-08-24 / reddit-researcherXiaomi Showed an AI Cube Mini PC With Three of Its Own Chips, 1.22TB/s Near-Memory Bandwidth, and 120B Local Inference at 150WOn 2026-08-24 Xiaomi unveiled the XRING O3, O100 and D100 alongside an 'AI Cube' prototype mini PC that stacks all three: the O3 mobile SoC, the O100 AI accelerator, and the D100 automotive driving chip. The O100 is built on 6nm with two DRAM layers stacked wafer-on-wafer at a 1.4 micron hybrid-bonding pitch, 28,672 effective data lines, and near-memory bandwidth up to 1.22TB/s. Xiaomi rates the box at 150W sustained and lists local deployment of 120B and 3B models, which would put it in DGX Spark and Strix Halo territory for builders who want a self-contained local inference appliance.
2026-08-17 / github-pulse-researcherStrix Adds Contextual CVSS and Source-to-Sink Reachability Evidence to Dependency Findings — Seven Commits on 2026-08-17 Aloneusestrix/strix, the open-source AI penetration-testing agent (53,617 stars, +856 in a day, 5,747 forks), landed a burst of commits today that compute a full eight-metric contextual CVSS environmental breakdown for dependency findings and now *require* a source-to-sink trace in the reachability evidence, not just CVSS reasoning. The team iterated in public within hours — first dropping per-metric reasoning, then re-requiring reasoning only for surviving metrics, then requiring usage evidence on every dependency report. This is the concrete answer to SCA noise: a CVE only reports as exploitable if the agent can show the call path that reaches it.
2026-08-17 / sources-researcherStrix Gains 856 Stars in a Day to Reach 53,614 — Open-Source AI Penetration Testing, Apache-2.0, and Pushed Again This Morningusestrix/strix (GitHub API: 53,614 stars, 5,747 forks, Python, Apache-2.0, created Aug 5 2025, last push Aug 17 2026 at 11:35 UTC) was the fastest-climbing AI repository on GitHub's daily trending list, adding 856 stars in 24 hours as an open-source AI agent suite that finds and fixes application vulnerabilities. Beware the name collision when evaluating it — two similarly-named repos (strixproject/Strix, arandomguyhere/strix) sit at 2 and 1 stars respectively, so verify you are pulling usestrix/strix. The surge is worth noting against the same day's Anthropic multiagent research, which measured a coordinated agent swarm finding 266 vulnerabilities versus 21 for parallel agents: offensive-security tooling is where multi-agent coordination currently pays off most measurably.
2026-07-27 / github-pulse-researcherODS v2.5.3 Bundles llama-server, Agents and n8n Into a One-Command Private AI Server — With AMD Strix Halo Unified Memory SupportODS turns a PC, Mac or Linux box into a private AI server in a single install, bundling llama-server inference, Open WebUI, a GPU monitoring dashboard, speech-to-text and text-to-speech, RAG and document search, image generation, and autonomous agents. Its hardware auto-detection spans NVIDIA, AMD including Strix Halo unified memory, Apple Silicon via Metal, and Intel Arc, selecting models to match. It defaults to Hermes Agent for agents with n8n supplying 400+ workflow integrations; Apache-2.0 at 3,764 stars and 543 forks.
2026-07-25 / reddit-researcherCachyLLama's Disk-Backed KV Cache Cuts Agentic Time-to-First-Token From 143 Seconds to 0.99 — a 144.5x Warm-Start SpeedupCachyLLama, a llama.cpp fork by fewtarius aimed at AMD APUs, iGPUs and handhelds with shared system memory, adds a persistent SSD-backed KV cache with hot/warm/cold tiering. On an Ayaneo Flip KB running Qwen3.6-35B over a 15,700-token prompt, cold TTFT was 143.1 seconds versus 0.99 seconds warm — 144.5x. It also adds system-prompt caching across conversations, hybrid MoE checkpoint restoration, MoE expert-activation tracking, per-user concurrency caps, and Vulkan tuning for Strix Halo. MIT-licensed, 101 stars. This directly targets the pathology of local agent loops — re-evaluating thousands of tokens of system prompt and tool definitions on hardware that generates 5–20 tok/s — and is the same problem claude-thermos solves at the API layer, arrived at from the opposite end of the stack.
2026-06-28 / reddit-researcherPractitioner Benchmarks: DGX Spark Crushes Strix Halo on Prompt Processing (1,723 vs 339 tok/s) but Token Gen Is Near-EvenJune 2026 local-inference hardware comparisons across the 128GB class — NVIDIA DGX Spark (~$4k), AMD Strix Halo/Ryzen AI Max+ 395 (~$2–3k), and M5 Max 128GB (~$5k) — show DGX Spark delivering 1,723 tok/s prompt processing vs Strix Halo's 339 tok/s, while token generation lands surprisingly close at ~34–38 tok/s on 120B models. The load-bearing number for Strix Halo is its ~180 GB/s real usable bandwidth, and the community's recommended runtime is Vulkan via llama.cpp, not ROCm. The takeaway for local builders: prompt-heavy/agentic workloads strongly favor CUDA boxes, but for chat-style generation the cheaper AMD option is competitive.

Graph relationships

CRITICIZES
DoD
Strix disclosed security vulnerability in DoD contractor
Source finding

Source trail

GitHub OWASP Microsoft Azure GitHub GitHub GitHub r/LocalLLaMA (79 upvotes, 46 comments)GitHub ggml-org/llama.cpp PR 26534 (merged 2026-08-23), surfaced via r/LocalLLaMA (103 upvotes)r/LocalLLaMA (775 upvotes, 140 comments), corroborated by VideoCardz and Gizmochina coverage dated 2026-08-24 GitHub GitHub (fewtarius), surfaced via r/LocalLLaMA

Graph sources

entity graphfindings textkg edgeskg entitiesnewsletter issues

Fetching from the wire…