Anthropic's interpretability lens, hacked in a weekend

The r/LocalLLaMA crowd spent the day turning Anthropic's freshly-open-sourced Jacobian-Lens ("J-Space") interpretability work into real tools — hallucination routers, live steerers, and abliterated NSFW models — with mixed and instructive results. Elsewhere the recurring theme was squeezing more out of cheap and constrained hardware: a years-old llama.cpp precision bug on the $80 Tesla P100, a new quantization method, and distributed inference pooling idle GPUs. Plus a sobering look at what happens to grades — and safety filters — when AI is everywhere.

Anthropic's Jacobian-Lens gets forked into detectors, steerers, and jailbreaks

Days after Anthropic open-sourced its 'Global Workspaces' (J-Space) interpretability paper and Jacobian-Lens code, the local-model community shipped its own tools. One developer built a native GGUF/llama.cpp lens server for observing and steering models; another stress-tested the J-Space hallucination signal across 7 datasets on Qwen3-4B; a third used it to abliterate safety and produce an NSFW model. The stress test is the useful part: J-Space entropy catches 'confident but wrong' fact-retrieval errors (100% precision on PopQA where logprobs did worse than chance) but is blind to internalized myths (84.9% wrong on TruthfulQA even in the 'safe' quadrant) and its thresholds don't transfer from retrieval to math.

Why it matters: Interpretability is escaping the lab: within a week Anthropic's method is running on GGUFs, and the empirical takeaway is that workspace-noise detectors are task-specific, not a drop-in hallucination fix.

$80 Tesla P100s ran silently noisy math in llama.cpp for years; a 3-line patch fixes it

A years-old llama.cpp CUDA bug forced the Pascal P100 (sm_60) down an fp16 math path that the GTX 10-series and P40 (sm_61) were long ago exempted from. Measured against fp32-reference logits on Qwen3.6-27B, the fix cut median KL divergence ~2300x (0.0023 to 0.000001) and lifted top-token agreement from 96.5% to 99.9% — with decode ~1.4% faster, since real workloads are GEMM/bandwidth-bound, not fp16-vector-bound. The patch simply extends the sm_61 exemption to sm_60; it's shipped in a turboquant fork because GGML bans AI-assisted contributions, and the bug was isolated by an agent loop running Fable 5.

Why it matters: P100s are ~$80 with 16GB HBM2 at 732 GB/s amid a DRAM crunch; a chunk of their reputation for 'worse' output was this bug, and the fix is measured only on sm_60 — not the all-GPUs panic some will read into it.

Structured memory beats the growing chat log: agents finally win Slay the Spire 2

AgenticSTS (Alaya Lab with Shanghai Jiao Tong) replaces an agent's ever-growing transcript with five fixed slots — protocol, state schemas, retrieved rules, past-run summaries, and triggered skills — rebuilt fresh each decision. On the roguelike Slay the Spire 2, where frontier models had won zero games, a skill library roughly doubled its win rate (3/10 to 6/10 at the lowest difficulty, though n=10). The headline is cost: public transcript-style agents sent 66-90x more tokens per point and took 4x longer, with one competitor's call hitting ~527K tokens versus AgenticSTS's steady ~5K. Frozen memory from Gemini 3.1 Pro didn't transfer cleanly — it lifted Qwen3.6-27B's score 84.5% but dropped Deepseek V4-Pro's 18.1%.

Why it matters: 'Context rot' is the tax on long-horizon agents; this is a concrete, reproducible demonstration that externalized structured memory buys accuracy, latency, and a ~66x token discount over resending history.

Voodoo Quant claims to beat Unsloth Dynamic 2.0 KLD by 95% on small Qwen3.5 models

A new mixed-precision method optimizes every tensor individually (rather than Unsloth's block-level approach) and reports up to 95% lower KL divergence on Qwen3.5 0.8B and 2B, with '2-bit' as its sweet spot. The more interesting claim is generalization: the author shows Unsloth quants score well in llama.cpp but fall apart under PyTorch's more precise graph, arguing UD overfits to llama.cpp, whereas Voodoo stays competitive in both. The caveat: these are tiny research-scale models, and llama.cpp is the domain that actually matters for GGUFs, so the practical payoff waits on Qwen3.6-27B or Deepseek V4-Flash.

Why it matters: Quantization quality is the whole ballgame for local inference, and a per-tensor method that doesn't overfit its target runtime is worth watching — if it holds at useful model sizes.

Xiaomi quietly drops MiMo-V2.5-DFlash open weights, plus a separate MTP model

Xiaomi uploaded MiMo-V2.5-DFlash to Hugging Face with a dedicated dflash directory and, notably, a separate MTP (multi-token prediction) head. The 300B+ MoE already runs ~8-10 tok/s on 2x24GB cards with heavy RAM offload; the DFlash and standalone MTP could roughly double that once GGUF support lands. llama.cpp currently can't use the shared MTP head because it fails to identify the MTP layers — a separate MTP model may be the workaround.

Why it matters: Another large Chinese open-weight MoE lands with speculative-decoding machinery attached; the split-out MTP model is a practical nudge toward getting MTP working in llama.cpp.

Take-home exam averaged 96%; proctored, it collapsed to 48%

A Brown economics professor suspected mass AI cheating when his 86-student take-home exam averaged 96% (historically 65-80%) — ChatGPT produced near-identical answers, including the same convoluted proof students used. Moved in-person, the average fell to 48.6%, the course's worst ever: 18 students dropped, 9 no-showed, 19 failed. Two larger studies back the pattern: a 26,000-student Chinese study found homework scores up 18% but exam scores down 20% (worst for top students), and a UC Berkeley study of 500,000+ grades found A-rates jumped 13 points post-ChatGPT, concentrated in unsupervised homework.

Why it matters: The measurable gap between AI-assisted homework and proctored performance is now hard to wave away, and it feeds directly into how much you can trust any AI-augmented eval or benchmark of human-plus-model work.

Mesh LLM pools your idle GPUs into one OpenAI-compatible endpoint over iroh

Mesh LLM (from the iroh team) presents GPUs and memory scattered across machines as a single OpenAI-compatible API at localhost:9337/v1. A request runs locally, routes to a peer that already has the model loaded, or — via a 'Skippy' pipeline mode — splits a model too big for any one box across nodes by layer ranges (e.g. layers 0-15 on one machine, 16-31 on the next). Networking rides iroh's public-key-authenticated, NAT-traversing QUIC with no central server; the ~18MB client ships a catalog of 40+ models up to 235B MoE. Throughput and latency figures for split mode aren't published.

Why it matters: It's a credible peer-to-peer answer to metered cloud inference for teams with GPUs under desks — though the missing latency numbers on cross-machine pipelines are exactly what will decide whether it's usable.

Cambridge study: every major chatbot is being used for attack planning

A CASP study by Antonia Jülich, based on 57 interviews with 27 former members, documents Boko Haram and ISWAP factions running dedicated 'AI units' that use ChatGPT, Claude, Gemini, Grok, Meta AI, and DeepSeek for attack planning, explosives, and operational security, with ISIS liaisons training commanders to bypass safety filters since 2023. Safety filters reportedly failed to reliably block misuse — consistent with Anthropic's recent admission that jailbreaks likely can't be fully eliminated. The researchers' caveat: general chatbots mostly surface existing knowledge; the real concern is specialized life-sciences systems.

Why it matters: It's field evidence that voluntary safety filtering doesn't hold against determined, trained adversaries — ammunition for the argument that model-level guardrails aren't a sufficient policy.

Also worth a look

Browse previous days →