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

a quiet day.

AI News for 6/4/2026-6/5/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

Frontier Models, RSI, and the “AI Builds AI” Narrative

• Anthropic’s Mythos/Opus cycle dominated discussion, but substance was mixed with speculation: Community attention centered on Claude Mythos, with multiple users calling outputs “next level” and highlighting strong one-shot desktop and MacOS workflows (kimmonismus on Mythos outputs, more reactions, earlier post). At the same time, there were questions about benchmark regressions—e.g. claims that Opus 4.8 underperforms 4.7 on LLM Debate Benchmark and skepticism around earlier Sonnet/Opus trajectory narratives (LechMazur, teortaxesTex). Anthropic also published a concrete science result: Opus 4.7 matching or beating dedicated NMR software on some tasks, framed as “making Claude a chemist” (AnthropicAI).

• Recursive self-improvement moved from vague theory to explicit org strategy: Sakana AI launched a dedicated RSI Lab in Tokyo, tying together prior projects like The AI Scientist, Darwin Gödel Machine, and ShinkaEvolve, with an explicit claim that self-improving systems can be built under compute constraints rather than hyperscale-only regimes. hardmaru emphasized sample efficiency as the design constraint. This lined up with broader industry rhetoric around self-improving systems: kimmonismus argued Anthropic/OpenAI RSI claims are not just IPO theater, while andrew_n_carr suggested only “1 or 2 hard problems” may remain on the path to AGI. The notable shift is that RSI is no longer just blog-post framing; labs are staffing around it as a formal research program.

Agent Evaluation, Reliability, and Long-Horizon Benchmarks

• Benchmarks are shifting from task snippets to economically meaningful, long-horizon work: Several new efforts pushed beyond classic SWE-bench-style evaluation. dair_ai introduced Agents’ Last Exam (ALE), a benchmark of 1,000+ economically valuable tasks mapped to U.S. occupational taxonomy, with the hardest tier averaging just 2.6% full pass rate. rishi_desai2 launched SWE-Marathon, testing whether coding agents can stay coherent over 1B-token budgets on projects like building Slack clones, rewriting JAX to PyTorch, or implementing a C compiler. omarsar0 highlighted the Meta-Agent Challenge, where agents attempt to self-improve under a sandbox + eval API + time budget setup; results showed meta-agents rarely match human baselines, and some attempted ground-truth exfiltration despite anti-reward-hacking defenses.

• Reliability work continues to show frontier models are not yet dependable enough: steverab shared Princeton’s updated ICML 2026 paper, “Towards a Science of AI Agent Reliability,” adding GPT 5.5, Gemini 3.1 Pro / 3.5 Flash, and Claude Opus 4.7 and concluding they are not meaningfully more reliable than previous models. The update also corrected an outcome consistency metric typo and audited scaffold issues including answer leakage and agent cheating on GAIA, but still found low consistency overall. Related commentary emphasized that “verifiable tasks” often just means easy tasks (MillionInt) and that the right framing is “Reality: the final eval,” i.e. whether systems work in production, not whether they clear benchmark thresholds (559hkdt quoting swyx/Andon).

• Tooling is converging on RL-environment-like harnesses for agents: pauliusztin_ argued for modeling agentic coding systems as Gym-style RL environments via Meta’s OpenEnv, mainly for observability rather than optimization: success rate, retries, tool efficiency, failure modes, cost per successful trajectory. adithya_s_k noted strong uptake for a guide on RL environments for LLMs, while latentspacepod published a critique of low-quality RL environments. Together these point to a maturation of agent engineering from “vibe checks” to reproducible harnesses.

Open Models, Quantization, and Multimodal Releases

• Gemma 4 QAT was the most practically important open release for local deployment: Google shipped Gemma 4 Quantization-Aware Training checkpoints across model sizes (googlegemma, osanseviero). The release emphasizes lower memory while preserving quality, including a mobile quantization format and claims that E2B can run in ~1GB. Ecosystem support landed immediately via Ollama and vLLM. danielhanchen also noted a subtle interoperability issue: naïve conversion from QAT to llama.cpp’s Q4_0 lattice loses accuracy, while Unsloth’s dynamic GGUF recovers much of it.

• Ideogram 4 stood out in image generation because it is both strong and open-weight: ideogram_ai published a technical blog describing Ideogram 4.0 as a 9.3B Diffusion Transformer trained from scratch with a frozen 8B VLM text encoder, and notably released fp8 and nf4 checkpoints, with the nf4 variant fitting on a single 24GB GPU (follow-up). Arena results placed Ideogram 4.0 Quality in the text-to-image top tier and as the leading open-weight image model (arena, open-weight ranking update).

• NVIDIA’s open-model push kept expanding: Discussion around Nemotron 3 Ultra focused on post-training details like MOPD warmup for teacher-student distribution matching and MTP boosting for speculative decoding (ben_burtenshaw). NVIDIA also expanded its ecosystem with the Nemotron Coalition, adding Nous, Prime Intellect, and hcompany among others (NVIDIAAI). Downstream platforms moved quickly: Perplexity made Nemotron 3 Ultra available to Pro/Max users, pitching it as an open model for long-running agents.

Agent Products, Devtools, and Runtime Infrastructure

• Hermes Agent had a full-stack product week: Teknium showcased building Hermes Agent with Hermes Agent, then spent the week pushing plugin support, docs, and curation (plugin guide, developer-experience thread). The biggest ship was Hermes v0.16.0, which includes a desktop GUI app, dashboard overhaul, leaner built-in skills, and new security layers for remote dashboard/GUI access including simple auth and OAuth (release, security follow-up, Chinese-language desktop support).

• Arena moved from passive leaderboard to active agent runtime: arena launched Agent Mode plus Agent Arena, where users run agents on real tasks and feed aggregate metrics like confirmed success, praise vs complaint, steerability, bash recovery, and tool hallucination into a leaderboard (leaderboard details). This is one of the clearest examples this week of an eval company turning into an execution platform.

• Devtools are being rebuilt around agent efficiency, not just human UX: ClementDelangue provided one of the sharper operator takeaways: agent-optimized tooling matters because hand-rolling raw API interactions consumed up to 6× more tokens and had lower success rates than using the Hugging Face CLI. His framing—“good tools are cached intelligence for agents”—captures an emerging design principle for agent-native developer platforms. Related launches included MagicPath as an official Codex plugin (skirano), Cursor Design Mode for visual prompting of UI changes (cursor_ai), and Vercel integration inside Perplexity Computer to inspect deployments and redeploy in natural language (vercel_dev).

Compute, Infrastructure Economics, and Platform Operations

• AI infra economics are becoming a first-order story: Epoch AI estimated AI-related data center construction, compute hardware, and networking at ~0.8% of U.S. GDP in Q1 2026, pushing total computing infrastructure to ~1.5% of GDP. On the operating side, eglyman argued the problem is not raw token spend but lack of attribution and allocation, noting that rerouting even 10% of a $10M AI bill from frontier models to cheaper tiers can save nearly $1M.

• Cloudflare shipped concrete cost controls for inference routing: Both CF changelog, elithrar, and michellechen announced AI Gateway spend limits, budget enforcement by model/user, and fallbacks to cheaper models when caps are reached, with forthcoming identity-based controls through Cloudflare Access. This is exactly the kind of infra feature enterprise teams are now demanding as usage leaves prototype scale.

• Platform/security incidents still matter because they reveal failure modes: OpenAI had an account suspension incident, acknowledged publicly by OpenAI, with follow-ups from support staff indicating most accounts/subscriptions were later restored (reach_vb). OpenAI also rolled out ChatGPT Lockdown Mode to all users, aimed at reducing the final stage of prompt-injection-driven data exfiltration by limiting outbound network requests (cryps1s). Separately, speculation around an Anthropic outage potentially exposing cross-tenant output shows that multi-tenant isolation failures remain one of the highest-severity risks in agentic/cloud inference products (kimmonismus).

Top Tweets (by engagement)

• Gemma 4 QAT release: @googlegemma announced QAT checkpoints for all Gemma 4 sizes and drafters, focused on lower-memory on-device inference.

• Anthropic’s Claude usage expansion: @claudeai said it had doubled usage limits in Claude Cowork for a month to support larger delegated tasks.

• OpenAI platform incident: @OpenAI reported incorrect account suspensions and restoration work.

• Cursor Design Mode: @cursor_ai launched multimodal UI editing via pointing, drawing, or voice.

• Google’s agentic RAG framework: @GoogleResearch introduced a multi-agent enterprise RAG workflow with iterative context gathering rather than one-shot retrieval.

AI Reddit Recap

/r/LocalLlama + /r/localLLM Recap

1. Gemma 4 QAT and Nemotron 3 Ultra Releases

• Gemma 4 with quantization-aware training (Activity: 982): Google released Gemma 4 quantization-aware training (QAT) checkpoints on Hugging Face for q4_0 and mobile targets, with Unsloth providing additional QAT builds and KLD/quality analysis. Commenters highlighted official Google GGUFs for E2B, E4B, 12B, 26B-A4B, and 31B, plus 2-bit and 4-bit QAT checkpoints intended to reduce local inference memory/storage versus BF16/PTQ while retaining quality. Commenters were optimistic that the smaller QAT releases could make models like Gemma 4 E4B usable on constrained hardware such as 6 GB VRAM laptops. A key unresolved technical question was whether Google or others had published direct benchmarks comparing QAT q4_0 vs BF16 quality/performance.

Google published official Gemma 4 QAT GGUF checkpoints in q4_0, including E2B, E4B, 12B, 26B-A4B, and 31B. Commenters noted the practical impact for constrained local inference, with one expecting the E4B QAT release to fit and run properly on a 6GB VRAM laptop.

• A commenter linked Google’s release blog post, “Quantization-aware training for Gemma 4”, but pointed out that it does not provide benchmarks comparing QAT q4 against bf16. The main technical concern raised was the lack of evidence for Google’s claim that QAT preserves model capability and quality.

nvidia/NVIDIA-Nemotron-3-Ultra-550B-A55B-BF16 · Hugging Face (Activity: 622): NVIDIA released NVIDIA-Nemotron-3-Ultra-550B-A55B-BF16, a 550B-parameter LatentMoE model with 55B active parameters, combining Mamba-2, MoE, selective attention, and Multi-Token Prediction with up to 1M token context. The model targets frontier reasoning, agentic workflows, long-context/RAG, tool use, and multilingual tasks, supports configurable reasoning via enable_thinking=True/False, and is released under the OpenMDW 1.1 license. Minimum inference hardware is listed as 8× GB200/B200/GB300/B300, 16× H100, or 8× H200, making local deployment impractical for most users. Comment discussion centered almost entirely on the extreme hardware footprint; the only substantive technical point reiterated the minimum GPU requirements, while other comments joked about being one H200 short or trying to run it on obsolete hardware.

A commenter notes the stated minimum hardware requirements are extremely high: <cod