今日は何も大きな出来事はありませんでした

a quiet day.

AI News for 6/9/2026-6/10/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 opt in/out of email frequencies!

AI Twitter Recap

Anthropic’s Fable/Mythos rollout, silent capability gating, and the trust backlash

• Silent degradation of AI R&D help dominated the discourse: A large share of technical tweets focused on Anthropic apparently degrading model performance on AI research-related prompts without clear up-front disclosure, rather than hard-refusing those requests. Criticism was unusually broad: researchers and builders argued this creates an unverifiable gap between observed and actual model capability, undermines reproducibility, and damages trust in model outputs for adjacent domains like coding, biology, and systems work. Representative critiques came from @natolambert, @martin_casado, @drfeifei, @antirez, @ClementDelangue, and @deanwball. Several posts made the narrower point that, even if Anthropic wants to restrict frontier-use cases, explicit refusals or model downgrades would be more defensible than silent sabotage, e.g. @hlntnr, @arohan, and @DBahdanau.

• Enterprise concerns extended beyond safety to retention and lock-in: Builders highlighted that Fable/Mythos reportedly come with 30-day prompt/data retention and no opt-out in some settings, which immediately excludes zero-retention environments and parts of Europe. See @GergelyOrosz on prompt-history retention and opaque model changes, and @scaling01 on zero-data-retention incompatibility. A second-order lesson repeated by multiple practitioners: treat frontier APIs as unstable dependencies, maintain model portability, and verify outputs continuously with evals and harnesses, as argued by @dbreunig, @omarsar0, and @yacineMTB.

• Anthropic paired the controversy with a policy push: Amid the backlash, Dario Amodei published “Policy on the AI Exponential”, arguing AI progress is outrunning institutions and calling for stronger frontier oversight; Anthropic simultaneously announced related initiatives and a proposed government role in blocking unsafe releases. See @DarioAmodei and @AnthropicAI. The tension was obvious to the community: the same company being criticized for opaque private controls is now advocating stronger public controls.

Fable 5’s benchmark strength and product performance despite the controversy

• Fable 5 appears genuinely strong on agentic and coding workloads: Even many critics of Anthropic’s policy acknowledged the model itself is excellent. Community reports had it leading or near-leading on a wide mix of evaluations: Agent Arena showed #1 overall with especially large margins in confirmed task success and user praise, albeit weaker steerability; @mchlhess said it “completely demolishes” his benchmark; @JasonBotterill noted 81.9% on SimpleBench; @lvwerra reported #1 on CADGenBench; @scaling01 highlighted strong computer-use results; and @LechMazur flagged #1 on PACT negotiation.

• Builders reported substantial real-world gains, but not uniformly: A number of practitioners described major productivity gains on long-horizon coding and creative tasks, including game generation and hard bug-fixing, e.g. @kimmonismus, @walden_yan, and @hrishioa. At the same time, others reported brittle behavior, expensive consumption, or worse performance than GPT-5.5 on specific tasks, such as @Sentdex and @QuixiAI. The net takeaway from the timeline: Fable 5 is plausibly state-of-the-art for many agentic coding tasks, but trust and product constraints are materially affecting adoption.

• Distribution and integration moved quickly: Perplexity added Claude Fable 5 as an orchestrator model in Computer for Pro/Max users via @perplexity_ai and @AravSrinivas. Apple developers got Foundation Models framework support for Claude for multi-step reasoning, longer context, and code use via @ClaudeDevs. Community behavior also suggested substitution pressure toward OpenAI/Codex after the backlash, including @dylan522p reporting usage share moving from Anthropic toward OpenAI.

Google’s DiffusionGemma release and renewed interest in diffusion LLMs

• Google released DiffusionGemma under Apache 2.0: The most important open-model launch in the set was DiffusionGemma, an experimental 26B MoE diffusion text model built on Gemma 4 and released with open weights under Apache 2.0. Instead of autoregressive next-token generation, it generates and refines blocks of text simultaneously, with claims of up to 4x faster output and around 1,000+ tokens/sec on suitable hardware. See @Google, @GoogleDeepMind, @googlegemma, and @sundarpichai.

• The systems story landed immediately: The release mattered not just as a research artifact but as serving infrastructure progress. @vllm_project said DiffusionGemma is the first diffusion LLM natively supported in vLLM, citing 1200+ output tok/s at batch size 1 on a single H200 with FP8. @danielhanchen showed it running locally via llama.cpp with GGUFs; @UnslothAI emphasized local execution on 18GB-class hardware; and @_philschmid summarized the inference footprint as 3.8B active params and 256-token block denoising.

• Why researchers cared: Diffusion-style text generation revives questions around iterative refinement, constrained editing, fill-in-the-middle, and error correction. Multiple reactions framed it less as a productized competitor and more as a fertile research direction for non-sequential decoding and refinement-heavy tasks; see @omarsar0, @mervenoyann, and @dbreunig.

Agent tooling, infra, and benchmarks: more structure around real workloads

• Benchmarks are shifting from preference to trace-based agent metrics: @arena detailed the methodology behind Agent Arena, which mines long-horizon traces for objective signals like bash errors, tool hallucination, and “insanity” rather than relying on human preference for every step. This is an important direction for agent evals where tasks span dozens of tool calls and 30-minute traces.

• Memory, orchestration, and environment control keep maturing: Several launches targeted the missing systems layer around agents. @Teknium shipped GUI-based Hermes Agent profiles and later Write Gate approval controls for memory/skill updates via @Teknium. @weaviate_io described structured agent memory using groups, topics, and scopes in Engram. @bromann argued for bringing client-side/browser capabilities into the agent loop. @FactoryAI launched Missions on Factory Desktop.

• Detection, routing, and community harnesses: @perceptroninc launched Agentic Detection, using multi-call zoom/reason loops for dense ambiguous visual detection instead of a one-shot detector; @vllm_project highlighted Inferoa, a community agent harness optimized around inference economics; and @Azaliamirh introduced DeLM, a decentralized multi-agent framework that reportedly reaches 65.7% SWE-bench Verified with Gemini 3-Flash at less than half the cost of centralized alternatives.

Optimization, retrieval, and scientific-modeling work worth tracking

• Distributed Shampoo vs Muon remained a live optimization thread: A technically interesting sub-thread showed tuned Meta DistributedShampoo matching strong Muon baselines on a speedrun-style task after hyperparameter tuning and enabling pseudo-inverse stabilization. @arohan reported validation losses around 3.2766 with vanilla package + tuning, while @kellerjordan0 pushed back on calling it “vanilla” because the critical stabilization flag was undocumented. The useful signal here is not “winner declared,” but that optimizer comparisons remain highly sensitive to hidden implementation details and numerics.

• Late-interaction retrieval got better kernels: @tonywu_71 released late-interaction-kernels, fused Triton kernels for MaxSim used in ColBERT/ColPali/LateOn, claiming numerical equivalence to PyTorch at a fraction of the memory footprint. This should matter for both training and serving multi-vector retrieval models.

• Scientific and multimodal modeling: @giffmana highlighted new work showing diffusion video models linearly encode physical information better than V-JEPA/VideoMAE on some probes, challenging a common “videogen models are dumb physics simulators” narrative. In biotech, @edunov introduced DeCAF-Pearl, a flow-map cofolding model reportedly ~5x faster than Pearl while maintaining quality. On architecture research, @ZyphraAI released Zamba2-VL under Apache 2.0, extending hybrid SSM-Transformer ideas into VLMs.

Top tweets (by engagement)

• Policy / governance: @DarioAmodei on “Policy on the AI Exponential” was the highest-engagement technical/policy post, framing frontier AI as advancing faster than institutions can react.

• Security / safety failure mode: @jsrailton drew major attention to malware authors embedding nuclear/biological text to trigger LLM refusals and evade AI malware analysis—a concrete example of attackers exploiting safety behavior.

• Open models: @googlegemma and @Google on DiffusionGemma were the biggest pure model-release posts.

• Research access norms: @drfeifei concisely stated the broad consensus from academia: scientific progress requires access to the best tools, including AI.

• Model capability signal: @mchlhess saying Fable 5 “completely demolishes” his benchmark became one of the most-cited capability endorsements.

AI Reddit Recap

/r/LocalLlama + /r/localLLM Recap

1. Open-Weight Model Drops: North Mini Code and DiffusionGemma

• Releasing Cohere North Mini Code (Activity: 388): Cohere officially released North Mini Code 1.0, with weights on Hugging Face, an FP8 variant, free access via OpenCode, and technical details in the HF blog / announcement. For deployment, Cohere recommends vLLM main plus cohere_melody>=0.9.0, serving with --max-model-len 320000, --tool-call-parser cohere_command4, --reasoning-parser cohere_command4, and --enable-auto-tool-choice; they also noted PRs were pushed based on LocalLLaMA feedback. Ecosystem support now includes an Unsloth GGUF conversion and reported MLX support, while Cohere says llama.cpp/quantization requests are being flagged internally. Commenters were broadly positive about Cohere doing LocalLLaMA-style early access, but pushed for day-0 llama.cpp/GGUF support in future releases. One commenter argued the published benchmarks appear worse than Qwen 3.6 35B A3B on most metrics, while others mainly asked about GGUF availability and a possible larger “Maxi Code” model.

Commenters asked for Day-0 llama.cpp / GGUF support for future Cohere releases, noting that immediate local inference compatibility would likely improve adoption in the LocalLLaMA ecosystem. One commenter mentioned that llama.cpp support for North Mini Code appears to be “in progress.”

• A benchmark-focused commenter observed that Cohere North Mini Code appears worse than Qwen 3.6 35B A3B on almost every listed metric, suggesting the release may not be competitive on raw benchmark performance despite being welcomed as a new open model.

• The Apache-2.0 license was specifically praised, which is relevant for developers evaluating commercial or permissive downstream use of the model.

• DeepMind Just Dropped "DiffusionGemma" — Text Generation via Image-Style Diffusion Model (Activity: 355): ****Google DeepMind released DiffusionGemma, an Apache 2.0 open-weight 26B MoE text-diffusion model based on Gemma 4/Gemini Diffusion research that activates only 3.8B parameters and denoises a 256-token block in parallel instead of autoregressive token-by-token decoding. Google reports 1000+ tok/s on an H100 and 700+ tok/s on an RTX 5090, with quantized deployment fitting in roughly 18GB VRAM; the design shifts low-concurrency local inference from memory-bandwidth-bound sequential decoding toward compute-heavy parallel refinement, with support in Hugging Face, vLLM, and Unsloth. Commenters framed this as a significant development for real-time/local applications, but several emphasized that quality may lag standard autoregressive Gemma models: “I don’t need ultra-fast if it’s going to be stupid.” There was also broader positive surprise at Google’s recent pace of open model releases.

Commenters highlight the reported 700+ tok/s generation speed as potentially important for agentic workflows, where a diffusion text model could generate candidate actions and a smaller autoregressive model could verify them within the same latency budget. One technical angle raised is that bidirectional attention may make code infilling more natural without requiring special FIM tokens, which could benefit local coding agents.

Several comments frame DiffusionGemma as a speed/quality tradeoff versus standard autoregres