[AINews] The Future of Latent Space

潜空间，AI Engineer 通讯与顶级 AI 技术播客，报道前沿实验室如何构建 Agents、模型、基础设施与 AI4Science。关注

It’s been an absolutely MONSTER week already, from new Chinese Open Weight Frontier Lab claiming the throne for the first time, to new SOTA LLM and price cuts from Anthropic and OpenAI, to Meta Connect, to TypeSafe AI’s $10B fundraise after our exclusive podcast this weekend (already one of our top of all time, with two pods on genomic language models and AI scientists sending us above heavyweights like TBPN and MKBHD in Apple Podcasts, and helping cross 200K on YouTube).

Today is the calm before the DevDay storm, so we’re taking some time to share some long overdue changes we are making to Latent Space in the coming week:

  • Plans for AINews v3: This op-ed you are reading has always been human-authored by swyx (hi!!) every weekday for the last 3 years, and what started as a simple way to solve Discord fatigue eventually became LS’s newspaper: an awkward hybrid of Money Stuff mixed with engineer-tuned TechMeme mixed with AI writing evals that somehow . Meanwhile, the Latent Space Discord is now tens of thousands of members and yet quieter than ever with increasing amounts of self promotional spammers. The solution is obvious: merge the “job to be done” of the LS Discord and AINews.
  • Plans for a new home: with the success of our AI for Science pod and writing, and new podcasts from food to FDE rising, we’re slowly becoming a multi-show, multi-newsletter network of the best technical news, analysis and edutainment in AI. We’ll be exploring a migration to Beehiiv and a new homepage.
  • Open for business: with a new Business/Ops Manager and Head of Editorial, we are once again reopening for sponsorships (business@latent.space) and PR/tips! That said, join us next week at Supabase Select in SF!!! Supabase is the universally preferred integrated backend by every frontier model and we’re excited to interview their founders on their incredible journey building a fully remote open source database company from 0 to $10B, and see what’s next.

Sponsored by Supabase

Everything Supabase has been building will be unveiled on October 2 — live for one day in San Francisco!

See what Supabase is launching →

AI News for 9/23/2026-9/24/2026. We checked 12 subreddits, 544 Twitters and no further Discords. AINews’ website lets you search all past issues. As a reminder, AINews is now a section of Latent Space. You can of email frequencies!

AI Twitter Recap

Frontier Model Wave: Claude Opus 5.5, GPT-6 Astra/Sol/Luna, Gemini 3.8 Flash, and Xiaomi MiMo-V2.6-Pro

“System One” Decision Models: Jev, CLM, and Cheap Judges/Rerankers

Agent Infra: LangChain Interrupt, Perplexity Photon, and Retrieval

  • LangChain launches at Interrupt:
  • Perplexity Photon: Photon is a Rust retrieval and ranking engine built by a small team, hundreds of agents, and about $300K in tokens.
  • Retrieval and data systems:
    • Weaviate 1.39 makes MMR diversity GA at query time. Set balance explicitly, since the default of 0.0 means pure diversity.
    • Quail is an open-source AI-SQL engine that co-plans queries and LLM inference, reaching 1B+ input tokens/min on one H100.

Inference Speedups and Compute Hardware

Research: Harness Distillation, Agent Failure Modes, RL Environments, and Autonomous Science

World Models, Realtime Avatars, and Code-Rendered Media

Top tweets (by engagement)

AI Reddit Recap

/r/LocalLlama + /r/localLLM Recap

1. Jev System-One Model Scrutiny and CLM Alternative

  • Jev isn’t new tech. Its marketing targets people who think AI started with LLMs. (Activity: 1306): The post argues that Jev/System One Models appear to expose standard constrained-choice classification semantics—probability over fixed labels, schema-valid outputs, non-autoregressive inference, and inference-time labels—rather than a fundamentally new model class, and says the relevant baseline should be zero-shot/NLI classifiers, embedding models, cross-encoders, and rerankers rather than LLM JSON generation. It cites BTZSC, an ICLR benchmark covering 22 zero-shot classification datasets and multiple classifier families (paper), plus an external Banking77 baseline where BGE-small + logistic regression reportedly scored 93.3% vs Jev at 83.2% with ~9 ms local inference (repo). The post also challenges Jev’s “0% hallucination” framing, noting Typesafe’s own explanation only guarantees outputs conform to the allowed schema, not that the selected valid class is factually correct (Typesafe blog). Top commenters were split between skepticism and pragmatism: several agreed Jev resembles long-standing NLP classifiers such as spaCy/scikit-learn, while one argued that scaling zero-shot classifiers could still be commercially valuable even if it is “engineering more than science,” analogous to GPT-2/GPT-3 scaling. Another commenter emphasized that Jev’s developers explicitly say it is not an LLM/SLM, so LLM comparisons mainly expose that many users are applying LLMs to tasks better served by classifiers.
    • Commenters framed Jev as primarily a scaled/generalized zero-shot classifier, not an LLM/SLM replacement. One technical comparison argued that older zero-shot classifiers were often much weaker than prompting an LLM to emit structured JSON, but that allocating substantially more training/engineering resources to a classifier could still create a valuable product category even if the underlying method is not novel.
    • Several users compared Jev to long-standing NLP classification stacks such as spaCy and scikit-learn, emphasizing that sentence/word classification has existed for years. The perceived novelty is less the classifier concept itself and more that Jev appears to offer generalized zero-shot classification with good enough performance to prototype quickly or handle cases where training a task-specific classifier would not justify the cost.
    • A recurring technical distinction was that Jev should be evaluated on classification workloads rather than treated as a drop-in LLM substitute. Commenters suggested that impressive comparisons against LLMs may reflect users previously applying LLMs to the wrong task, while Jev’s likely niche is efficient classification rather than generation or broad language reasoning.
  • JEV almost dead: CLM vs JEV (Activity: 714): **The post positions CLM (GitHub, HF) as an open-weights, self-hostable replacement for TypeSafe AI’s Jev, implemented as a new projection head for Qwen3-8B supporting the same primitives: Choice, Noul, and Score. Claimed advantages are disaggregated state/action heads with action embedding caching, yielding 4×–13× lower latency in agent-style benchmarks, plus fine-tunable ~75 MB heads; reported verifier results include Terminal-Bench 2.1 87.6% and DeepSWE 81.6%, versus Jev around ~71% on DeepSWE. Stated limitations versus Jev include weaker zero-shot breadth (BFCL v4 95.2% vs Jev 99.2%; WikiRacing 26/30 vs 30/30), shorter calibrated context (2K–8K vs Jev 64K), and probability estimates normalized only over the supplied candidate set rather than an internally calibrated absolute scale. Top commenters dispute the “Jev competitor” framing, arguing that Jev’s core value is precisely zero-shot broad knowledge, so API parity alone is insufficient. Other comments are mostly anti-hype/anti-“Jev circlejerk,” with skepticism that CLM represents a full replacement rather than a narrower open verifier/head approach.
    • A commenter argues that JEV’s core differentiator is Zero-Shot Broad Knowledge, so a CLM-style system that lacks that capability should not be framed as a direct JEV competitor. They compare it to claiming parity with ChatGPT while removing the chat interface: the missing capability changes the problem class rather than merely reducing performance.
    • One technically useful setup note explains how to run CLM with GGUF models via llama.cpp for users with limited GPU resources. The commenter recommends serving a Qwen3-8B GGUF quantization such as Q4_K_M, Q5_K_M, or Q8_0 using llama-server --embedding --pooling last, because CLM heads were trained on last-token representations and older llama.cpp defaults like mean pooling can degrade score accuracy.
    • Another commenter proposes improving CLM confidence calibration by adding an explicit garbage / none-of-the-above candidate to the candidate set before applying dot products and softmax. The idea is that if none of the provided labels fit, probability mass could be assigned to this extra class, allowing the model to express low confidence instead of forcing all probability across bad candidates.

2. Local LLM Efficiency: Swift, HySparse2, GGUF Transformers

  • UkisAI Swift Series / 27B, Flash Next and Bonsai 2 + GSQ-RCO / -63.4% thinking, x1.95 speed with xhigh accuracy (Activity: 657): UkisAI released the Swift family of Qwen-based reasoning models trained to reduce pathological overthinking by penalizing overthinking-related tokens, then recovering accuracy with GSPO RL and on-policy distillation. The release includes Swift1.5 27B with -58.5% thinking tokens and +0.35% score vs base, Swift Flash Next with -63.4% thinking tokens, 1.8x speedup, and -0.2% xhigh score delta, plus experimental Swift Bonsai 2 with -39.8% thinking tokens and +0.19% score. Benchmarks were averaged over 5 seeds across GPQA, AIME26, LiveCodeBench, ERQA, and Terminal Bench 2.1; releases include GGUF, NVFP4, MLX, W4A16, and requested GSQ-RCO quants, with a 9B variant planned. Top comments were mostly positive but not deeply technical; one user reported the 27B model worked well as a homelab/sysadmin assistant, while others praised UkisAI responsiveness and joked about storage usage from downloading the models.
    • A user reports running the 27B UkisAI Swift variant for several weeks in a homelab/sysadmin-assistant role and describes it as strong for that workflow, though no quantitative benchmark is provided. Another commenter points directly to the GGUF release, Swift-1.5-Qwen3.8-27B-GSQ-RCO, indicating interest in the GSQ-RCO quantized/local-inference format.
    • There is explicit demand for smaller UkisAI Swift variants aimed at “RAM poor setups,” suggesting the 27B release may be too memory-heavy for some local users despite the title’s claimed -63.4% thinking reduction and x1.95 speedup. Storage pressure is also implied by a commenter joking about their SSD, consistent with large GGUF model distribution sizes.
  • MiMo-V3 is getting a new architecture. The core of it, HySparse2, is out today. (Activity: 427): The image is a technical announcement screenshot from Fuli Luo stating that MiMo-V3 will adopt a new architecture centered on HySparse2, with the linked paper at arXiv:2609.26368. The claimed significance is an efficiency-oriented sparse-attention design: lower prefill FLOPs, reduced KV-cache footprint, and better long-context retrieval via mechanisms such as KV Bridging, KV Reuse, token-level selection, and a shared KV-cache design. Commenters frame this as part of a broader trend where “sparse attention is the new king”, while another asks whether MiMo is among the very large model families. No substantive benchmark critique or implementation debate appears in the provided comments.
    • A commenter highlights HySparse2 as targeting two local-inference bottlenecks: KV-cache size and prefill cost, arguing this could make 1M context more practical on systems with 48GB unified memory for roughly 27B–35B models. They estimate that by “reading only half the model” and doing roughly 1/5 of the math during prefill, prefill time could drop by about 60–70%, potentially cutting total task latency by around half for long-context workloads.
    • Another technical concern is model scale: the architecture appears to be tested on an 80B model, while users are hoping the same sparse-attention/KV optimizations will be released in smaller local-friendly sizes. One user also reports MiMo 2.6 Pro “overthinking” and links a follow-up system-prompt mitigation post: Reducing overthinking.
  • GGUFs in transformers natively! (Activity: 353): Hugging Face Transformers now supports loading GGUF / llama.cpp quantized checkpoints directly via AutoModelForCausalLM.from_pretrained(..., gguf_file=...), exposing them through standard Transformers APIs for debugging, evaluation, custom generation, and PyTorch-based workflows; details are in the HF post: GGUFs in Transformers natively. On Apple Silicon, supported configs reuse ggml kernels to execute from packed quantized weights, with reported M2 Max throughput close to llama.cpp: Qwen3.5-4B Q4_K_M70.4 tok/s vs 71.8, Qwen3.8-27B UD-Q4_K_M15.9 vs 13.4, and Qwen3.5-35B-A3B UD-IQ4_XS60.2 vs 61.3. Commenters focused on ecosystem impact: potential obsolescence of separate ComfyUI GGUF loader nodes, and enabling LoRA training directly over GGUF in Transformers-based stacks like Unsloth and Axolotl, potentially reducing memory versus bitsandbytes 4-bit and improving MoE support; one PoC was linked at woct0rdho/transformers5-qwen3.5-recipe.
    • A commenter highlights the main technical implication: because frameworks like Unsloth and Axolotl are built on transformers, native GGUF support could enable LoRA training directly over GGUF quantized models, potentially using less memory than LoRA over bitsandbytes 4-bit models. They also note that bitsandbytes still lacks MoE support, while GGUF already supports MoE quantized models, and share a proof-of-concept recipe for Qwen training: https://github.com/woct0rdho/transformers5-qwen3.5-recipe.
    • There is discussion about downstream tooling impact: native GGUF loading in transformers may reduce the need for custom loaders in UIs like ComfyUI, depending on when Comfy updates its transformers integration. The same change could also benefit non-training “model surgery” tools such as Heretic, since they may be able to operate on GGUF-backed models without custom conversion or loading paths.
    • One practical evaluation use case mentioned is easier swapping between different GGUF quantizations inside the same transformers-based workflow to compare behavior, such as long-conversation character retention in roleplay chats, without additional loader-specific setup.

Less Technical AI Subreddit Recap

/r/Singularity, /r/Oobabooga, /r/MachineLearning, /r/OpenAI, /r/ClaudeAI, /r/StableDiffusion, /r/ChatGPT, /r/ChatGPTCoding, /r/aivideo, /r/aivideo

1. Opus 5.5 Agentic Creative Builds

  • Made entirely with Opus 5.5 + $3.21 of OpenRouter API usage (Activity: 2308): OP reports a true one-shot autonomous Claude Code generation using Opus 5.5 to create a 30s–60s pure-JavaScript whimsical hand-drawn collage animation on “what is the purpose of life?”, including script, assets, animation, concept, and TTS. The run took ~1h20m, cost about $20 of Opus usage or ~10% of a Max 5-hour quota, plus $3.21 on OpenRouter across 8 APIs—mostly NanoBanana 2, TTS, and minor auxiliary calls—under a $10 OpenRouter budget; OP compares it to an earlier similar post here. The hosted video link was not accessible during fetch because Reddit returned 403 Forbidden for v.redd.it/cdejwwaqobrh1, requiring login/developer-token access. Comments were light on technical critique: one commenter was impressed by the AI-generated voice and framed the result as evidence that creative workers are increasingly exposed to automation, while another expressed concern that this kind of low-cost generated media could flood YouTube feeds.
  • Jaw literally dropped. I ran the prompt from the “Made entirely with Opus 5.5” post on my own project. Here’s what Claude Code made on its own for about $4. (Activity: 1490): A user replicated a prior “Made entirely with Opus 5.5” workflow by giving Claude Code an OpenRouter API key capped at $10 and prompting it to autonomously produce a 30–60s explainer video for Friendr.nl. In ~1.5–2h and for ~$4, it reportedly generated the script/concept, collage-style assets, TTS voice-over, music/SFX, a pure JavaScript canvas animation rendered to MP4, beat-synced animation to narration, and used another model for self-review; an English version took ~30min more. A commenter reproduced the pattern for “blueprintr” with a similar prompt targeting a 45–60s JS/vellum-style animation, noting only minor manual corrections and sharing a Streamable result. Commenters characterized the result as near-term disruptive for automated video production—e.g. joking that Pixar could soon prompt “make Toy Story 6”—but the thread contained little substantive technical critique beyond anecdotal confirmation that the workflow also worked on another project.
    • A commenter shared the exact autonomous generation prompt used to create a 45–60s pure JavaScript animated explainer locally runnable in Firefox, with constraints to generate the script, assets, animation, concept, and audio end-to-end. The workflow explicitly allowed Claude Code to use internet resources and a .env OpenRouter API key for a high-quality TTS model, with a max OpenRouter spend of $10; the commenter said only minor corrections were needed and linked the resulting video: https://streamable.com/tsn19a
  • Opus 5.5 is insane at making videos (Activity: 1329): The post claims Claude Opus 5.5 generated an SNES-style video-game combat video entirely from code, including character assets, animation/timing, fight sequencing, and music, without user-provided assets. The prompt theme was Sydney—Microsoft’s early GPT-4-powered Bing Chat persona with different RLHF behavior, referenced via the archived NYT Bing/Sydney transcript—facing Sam Altman and then Claude itself; the Reddit-hosted video could not be independently inspected because v.redd.it/ghsiido07erh1 returned 403 Forbidden. Top comments were uniformly impressed, specifically highlighting the generated video’s timing and pacing as unexpectedly strong; no substantive technical debate or critique was present.
    • Commenters highlighted Opus 5.5 as showing unusually strong video-composition behavior, especially around timing and pacing: one noted its “sense of timing and pacing is actually good”. Another compared it to the launch-day viral p(doom) video, saying outputs are “packed with quick jokes and small details,” suggesting improved scene-level coherence and comedic beat placement rather than just visual generation quality.
  • This interactive island was built in 8 hours with Opus 5.5 (Activity: 1125): Dan Greenheck built the browser-based interactive island demo TideWater in roughly 8 hours using Opus 5.5, reportedly relying on simple iterative prompts like “add X” and “make it better” (tweet). The demo includes multiple interactive/simulated elements—birds, crabs, fish/whale behavior, wind effects, night lighting, walking/interaction, and boat sailing—and consumed about $1,874.40 in tokens, or 59% of a Max 20x weekly allowance. Commenters were mostly impressed by the scope of the demo beyond the video preview, with one predicting this style of AI-assisted generation could enable “great GTA offshoots” soon. Other reactions were brief/speculative, including jokes about “Opus 50” and one negative comparison that it “looks like crisis.”
    • Commenters noted that the demo’s technical scope is clearer when run interactively rather than viewed as a video: users can walk around, interact with objects, and sail the boat, suggesting the Opus 5.5-generated environment includes basic game-loop mechanics beyond static scene generation.
    • Several comparisons framed the output as resembling early Crytek / Far Cry 1-era engine visuals, while another commenter specifically highlighted the water physics as visually competitive with some modern AAA titles, though these observations were qualitative rather than benchmarked.

2. Claude-Discovered CRISPR-like Enzyme System

  • Claude discovered a novel enzyme system with properties reminiscent of CRISPR (Activity: 1100): Anthropic reports that Claude-agent genome-mining workflows identified a previously uncharacterized bacteriophage system dubbed array-associated reverse transcriptases (ART): an RT gene plus accessory gene adjacent to a long CRISPR-like tandem repeat array. In the described campaign, ~950 Claude agents used 210M tokens over 21 hours to collect >200k reverse transcriptases, nominate 3,500 candidate systems, and prioritize 20 reports; early BSL-1/2 validation found the ART array is transcribed into distinct short RNAs, but Anthropic explicitly says the system’s biological function and any programmable editing utility remain unknown. Commenters were cautiously optimistic, framing this less as an AlphaFold-scale biology result and more as evidence that LLM agents can contribute to original hypothesis generation: “Claude selected an unusual candidate… and brought it to human researchers for validation.” Others speculated that Anthropic’s bio lab could improve public support if it leads to disease-relevant discoveries, while emphasizing that ART is not yet demonstrated to cut/copy/paste DNA or enable gene editing.
    • Several commenters emphasized that the reported ART system is not yet comparable to AlphaFold 2 or CRISPR-level functional discovery: Anthropic reportedly shows that the repeat array is transcribed into distinct short RNAs, but the biological function remains unknown and there is no evidence yet of programmable gene editing or a demonstrated mechanism analogous to CRISPR.
    • A technical critique argued the work appears incomplete because identifying repeat arrays and showing they produce short RNAs is a fairly standard genomics workflow, with similar analyses already seen in systems such as VIPR. The commenter noted that repeat arrays are already known to be interesting motifs, so the novelty would need to come from either a new biological function or a substantially novel discovery process, neither of which they felt was clearly established.
    • One substantive point was that the most important result may be methodological rather than biological: Claude reportedly selected an unusual candidate, noticed an overlooked pattern, assessed novelty, and escalated it for human experimental validation. Commenters framed this as early evidence of AI acting as a research collaborator, even if the enzyme system’s actual importance remains uncertain.
  • The moment Claude agents discover a new molecular mechanism, talking as if they were human, using interjections and cues (Activity: 1056): The image appears to show Claude agents reasoning through genomic sequence flanks and identifying repeated DNA motifs, with a highlighted realization that the structure may resemble a CRISPR-like or msDNA/retron-like repeat array. The technical significance is not a validated discovery from the screenshot alone, but rather an example of LLM-style agentic hypothesis generation in molecular biology: comparing tandem repeats, spacer regions, and known mobile genetic element architectures such as CRISPR arrays, diversity-generating retroelements, msDNA, and retrons. Comments mostly frame the screenshot as evidence of rapid AI progress, with one user analogizing it to recent gains in mathematics and asking whether “Biology [will be] solved soon?” Others focus on the model’s human-like enthusiasm rather than the biological claim itself.
添加评论
点赞收藏
点踩分享查看原文
评论
?
参与讨论