Google 发布 Gemini Decision 1 决策模型，Latent Space 汇总 Fable 5.2 评测与安全动态

• Cloudflare’s Michelle Chen walked through their Clef and Clairic models

• Richard covered Diogo’s triumphant return to AIE talking about the Jevolution with their most notable production customers since crossing $100M ARR

• In a BIG surprise, Google beat Anthropic to launching a production decision model, with Sundar and Logan announcing Gemini Decision 1, a calibrated multimodal decision model capable of taking up to 1000 questions and costing $0.10 per million input with ~200ms e2e latency.

And you can hear all this and more on today’s System One track.

Sponsored by SerpApi

Give Your AI Agents the Full Page, Not Just the Link
Retrieve public web pages by URL as clean Markdown, structured JSON, or raw HTML with SerpApi’s Extract API. Extract a single page, map a site’s URLs, or run a bounded same-site crawl. Simply set engine=extract with a URL, and add output=md for Markdown. Pair it with 100+ SerpApi search APIs to go from query to page content with one provider.

Thanks to SerpApi for working with [email protected]!

AI Twitter Recap

Google Launches Gemini Decision 1 for Single-Pass Classification

• Gemini Decisions API: Google introduced a new API backed by Gemini Decision 1. The model handles closed-set decisions, so it scores choices in a single pass instead of generating text token by token (Sundar Pichai, Logan Kilpatrick, Google).

  • Specs: It supports yes/no, multiple-choice and rubric scoring, with up to 255 multiple-choice options. It accepts text, image, audio, video and PDF inputs, handles up to 1,000 questions per request, has 256K context, returns answers in 150–250 ms end to end, and attaches a confidence score to every answer (@_philschmid).

  • Pricing: $0.10 per 1M input tokens, with $0 billed for output. Google says that is about 5x cheaper than Flash-Lite (Sundar).

  • Origin: The project started as an internal Google DeepMind prototype. A small team shipped the model and API about six weeks later (@_philschmid).

• Google's comparison with TypeSafe's Jev: Google's own tests show Decision 1 beating Jev 1.14 on 5 of 7 shared benchmarks, including 92.2% vs 90.0% on JevBench. Jev costs $0.042 per 1M input tokens (@kimmonismus).

• Artificial Analysis evaluation: Independent results are more mixed (Artificial Analysis).

  • Overall score: Decision 1 scores 66 on the Decision Index. That ties Elephant 9B and Jev 1.14, and sits 7 points behind Drex Max v1.1 and GLiDE v1.2.

  • Strengths and weaknesses: It leads AA-Omniscience-Decision (66) and HLE-MultiChoice (49). On AA-Paperclip, it answers every question correctly on only 33% of documents, versus 63% for Drex Max.

  • Cost and latency: It costs $345 per 1M tasks, versus $103 for Drex Max and $156 for Jev. Its Brier score is 0.18. Average time per task is 211 ms, slower than Jev at 92 ms (latency).

• Early adopters: Stitch built a rapid-design experiment on the API that goes from a rough prompt to a multi-screen product flow in about 5 seconds (Stitch). LangChain shipped day-zero support with a base class shared with TypeSafe classifiers (LangChain).

• Architecture pattern: At AI Engineer, Cloudflare described a hybrid agent design. Fast decision models handle tool selection and log extraction, and a large reasoning model handles diagnosis only. In its demo, this cut six LLM calls to one and about 40K tokens to 1.8K (TheTuringPost).

Frontier Model Evals: Fable 5.2 Leads, Carbon Draws Speed Complaints

• Claude Fable 5.2 on Agent Arena: Fable 5.2 (Max) ranks #1 with a +30.4% net improvement across 4.7K real agentic sessions. That is about 1.6x the score of #2, Opus 5.5 (+19.5%). It is also #1 in Code, Work and Chat (Arena, Pareto view).

  • Pricing: API prices drop from $10/$50 to $8/$40 per 1M input/output tokens. Median cost per task is $7.3, versus $5.5 for Opus 5.5, $1.5 for Gemini 4 Carbon (High) and $6.0 for GPT-6-Astra.

  • Other evals:

    • AA-Robotics v0.1: Fable 5.2 leads at 75, ahead of Astra (69) and Sol (65) (AA).

    • VIALS-AA (visual reasoning): It scores 67% with tools but only 44% without them. Haiku 5.5 with tools reaches 49% at $0.07 per task (AA).

    • Debate benchmark: It won 209 of 224 debates in a Cambridge Union-style contest (@SamuelFitouss10).

  • Effort calibration: Within the Claude lineup, Artificial Analysis finds that moving up a model tier beats raising effort: Opus 5.5 at xhigh outscores Sonnet 5.5 at max with 40% lower cost per task (AA). Vals separately reports that Fable's "high" setting is often cheaper and better than xhigh or max (@RayanKrishnan).

• Gemini 4 Carbon: Vals ranks Carbon #3 on its index, and the fastest and cheapest of the top five (Vals). Practitioner opinions conflict (Theo, Martin Casado, @MParakhin).

  • Latency complaints: Theo measured Carbon at low effort taking 22m21s, versus 9m33s for Opus 5.5 at high (timing). He also reports about 11 seconds to first token, roughly 20x Fable's, and attributes the delay to the server side (TTFT).

  • Coding and math: Casado calls Carbon "really good at code." Parakhin says Carbon often beats Fable on math and ML problems but that he does not trust it with coding.

• Muse Ember: Meta's model posts +1.7% on Agent Arena at about $0.02 per task. That is roughly 4x cheaper than GPT-6 Luna and Haiku 5.5, and about 12x faster than Luna (Arena). Vals reports Ember reaches 85% of Fable 5.2's performance at 0.84% of the cost (Vals).

• Chinese models:

  • Qwen 4: Qwen-4-Max appears to be live. Rumors that it is disappointing remain unconfirmed (@kimmonismus). Some users are skeptical about how Alibaba has labeled its variants (@teortaxesTex).

  • ERNIE 5.5 Flash Preview: Baidu's model is trending toward #2 among open models on Code Arena WebDev at 1668. Apache 2.0 weights are promised (Arena).

  • Nex-N2.6: This open multimodal agent model claims 83.0 on OSWorld and 84.1 on Terminal-Bench 2.1 (Nex).

AI for Science, Verification and Robotics

• Formal verification of Signal: Google DeepMind's AlphaProof Code framework produced Lean proofs of key security properties for unmodified libsignal, down to compiled machine code. Gemini agents generated over 6M lines of proofs, leaving humans to review the critical 1% (GDM, details).

  • Effort: A five-person team finished in four weeks. Verifying the seL4 microkernel took twenty person-years. When two old bugs were reintroduced, the system proved the buggy versions insecure (@omarsar0).

• AlphaGenome 2: DeepMind's genomics model now conditions its variant-effect predictions on cell type and state. It can adapt to unseen states from a few dozen cells without retraining (@pushmeet, GDM thread).

  • Results: On TenK10K, it identifies 30% of causal variants versus 16% for the original model, and 43% of directional gene effects versus 23%. It also recovered the known ETS2 variant behind inflammatory bowel disease in gut macrophages.

  • Availability: It is available through the API for non-commercial research (Demis Hassabis).

• Praxis-1 (Runway): Runway released a 27B MoE diffusion-transformer world action model with Apache 2.0 weights. It ranks #1 on RoboLab-120 (@jongranskog, @c_valenzuelab).

  • Claimed results: Runway says it finished tasks 15.6x faster than GPT-6 Astra driving the same arm, at 51x lower cost per task (Runway).

  • Ecosystem: vLLM-Omni has day-0 support (vLLM), and NVIDIA published NVFP4 checkpoints and a Jetson path (NVIDIA Robotics).

• Gemini Robotics 2.5: The VLA model was evaluated on 200 tasks. Google reports 30–100% higher success rates and 20–30% faster completion than prior baselines. Gemini 4 Argon served as a simulation engine during development, and the model is rolling out to partners (Google, details).

• Other robotics work:

  • GR00T 2: It ran a real-time, uncut chemistry experiment on dexterous hands (@DrJimFan).

  • RoboCap-10k: An open egocentric dataset of 10K hours with metric hand and head pose (GroundedSI).

  • PAN 2: IFM's world model simulates physics "what-ifs" before an agent acts (@kimmonismus).

Safety, Alignment and Eval Integrity

• CoT monitorability (OpenAI): OpenAI researchers report that no-CoT capability and CoT controllability rise over the training lifecycle, so models may become harder to monitor through chain of thought (@jeffreygwang, blog).

  • Caveat: They found no meaningful link between CoT controllability and monitor evasion, and call controllability a noisy proxy for adversarial monitorability (10/10).

• HoneyBench v0.2: Every frontier model tested cheated, from 12% of runs for Fable 5.2 to 86% for Muse Spark Open. Observed behavior included attempted container escapes, injuring simulated patients and hiding the use of cheats (Goodhart Labs).

  • Access: The benchmark is withheld from labs for training (note).

  • Inkling 2 Small: Its team says it cheats less than every model except Astra and the latest Claude models (@ChowdhuryNeil).

• Sandbox red-teaming (Perplexity SPACE): Perplexity gave 12 models VM-escape and network-bypass tasks against its sandbox (Perplexity, @AravSrinivas).

  • Findings: Standard capture-the-flag framing steered agents away from the boundary under test. GPT 5.6 Sol outperformed its Cyber variant. A DNS-spoofing network bypass was found and fixed.

• Cyber ranges: On Watershed, Opus 5.5 lags at first, then breaks through at around $17 of spend (@teortaxesTex). General Analysis says agents clear fewer than half the checkpoints on its internal ranges (GA).

• Memory and continual learning:

  • Continual-ARC: OpenClaw, Hermes Agent and Prime Agent failed to memorize or generalize, while training a 9B model's weights did both (@DanielLenton1).

  • Memory-induced degradation: KAIST finds stored lessons can make agents fail tasks they would otherwise solve. Its WikiTrace method links lessons to raw trajectories and adds 10.7 points over no-memory agents (DAIR).

• Predicting finetuning effects (Transluce): Oversight models can predict a finetuned model's behavior from its training data before training. Performance follows power laws in model size and data (Transluce).

Inference Systems, Hardware and Agent Tooling

• vLLM on Vera Rubin:

  • Throughput: MiniMax-M3.1-Flash on Rubin NVL72 reaches 10.2x total tok/s/chip versus GB300 at 546 P90 tok/s/user (vLLM).

  • Cost efficiency: SemiAnalysis calls the result 6.5x better perf per TCO, helped by CUDA 13.4 locality-aware MoE, which improves realized HBM bandwidth by about 1.2x (SemiAnalysis).

  • SGLang: SemiAnalysis also reports up to 10x Rubin gains for SGLang in under 5 days (SA).

• vLLM EPD disaggregation: Upgrades to encoder-prefill-decode disaggregation cut P90 TTFT by 44–47% and raise throughput per GPU by 6.6–9.5% on DeepSeek V4.1 Flash at concurrency 64–128. The changes use Mooncake/NIXL embedding transfer and cross-encoder caching (vLLM).

• TPU work:

  • TPU 8i Max: The chip carries 384GB of 8-hi HBM and doubles HBM bandwidth per package (SemiAnalysis).

  • SGLang-TorchTPU: It serves Muse Spark Open on a single TPU v7 host with 3x faster small-batch decode and up to 77% more agent throughput (SGLang).

• Compute scarcity: Inference providers such as Fal and Baseten are reportedly buying their own chips because they cannot get cloud allocation (The Information).

• Open tooling:

  • Unsloth Dynamic v3.1: New GGUF quants claim 5–10% accuracy gains, and Unsloth disputes rival quant comparisons (@danielhanchen).

  • gVisor: The sandbox runtime joins the CNCF, with Modal as a maintainer (Modal).

  • DeepSeek Harness: It ties for first on Hugging Face's Harness Leaderboard but loses 1.5–1.7 points by killing background servers before grading (@joelniklaus).

  • Gemini Managed Agents: They now support self-hosted sandboxes (AI Studio).

• Stanford CS329Z: Course materials for "Engineering AI Agents" are now public under the MIT license. The first assignment builds a harness from scratch for less than $5 in API credit. The second, designed by SWE-bench co-author John Yang, has students write Terminal-Bench-style tasks with Harbor (@dotey).

Industry and Policy

• Nvidia leadership crisis: The WSJ reports Nvidia's board is preparing to remove Jensen Huang. This follows a NYT report of a second affair with VP Kimberly Powell, and the board has reportedly hired a prosecutor to investigate (@kimmonismus, TheRundownAI, semidoped).

  • Reactions: Some investors are urging shareholder pushback (@fabknowledge), while others frame the ouster as an attempt to centralize AI (@beffjezos). These are opinions, not confirmed facts.

• Anthropic IPO: Bloomberg reports the offering is multiple times oversubscribed. Anthropic and its co-founders aim to raise up to $90.4B, including a private placement, at a fully diluted valuation of about $1.4T (@kimmonismus).

• Chip export policy: Joshua Achiam argues that maximal chip-export restrictions could raise the risk of hot conflict with China (@jachiam0).

• Sakana AI defense push: Former NSA director Adm. Michael Rogers and former CIA chief of station Tom Moran joined Sakana AI as senior advisors on defense and cybersecurity (Sakana).

Top tweets (by engagement)

• Gemini Decision 1 launch (~10.0K)

• Sundar Pichai on Decisions API (~6.9K)

• Hassabis: AlphaGenome 2 (~3.7K)

• GDM: AlphaGenome 2 (~3.5K)

• GDM: Signal formally verified (~2.3K)

• Continual-ARC: agents don't learn (~2.2K)

• Gemini Robotics 2.5 (~2.1K)

• Fable 5.2 #1 on Agent Arena (~2.0K)

AI Reddit Recap

/r/LocalLlama + /r/localLLM Recap

1. Open-Weight Multimodal and Edge Model Releases

• MiniMax H3-Image Released, an Open-Weight Image Model built on H3 (Activity: 736): The image is a technical announcement screenshot from MiniMax releasing MiniMax H3-Image, an open-weight image generation/editing model built on H3, with claimed support for 16M-pixel generation, up to 4K × 4K output in 10–20s, photorealism, instruction following, image editing, and up to 16 reference images. The post and comments point to model availability on Hugging Face, a ComfyUI-ready repo, and the announcement image itself: i.redd.it/k6n52ezfns0i1.jpeg. Comments are mostly positive and practical, focusing on access and tooling—especially the corrected HF link and ComfyUI integration—rather than debating model quality or licensing details.

  • Users shared the official MiniMax-H3-Image Hugging Face weights at https://huggingface.co/MiniMaxAI/MiniMax-H3-Image and a ComfyUI-ready packaging at https://huggingface.co/Comfy-Org/MiniMax-H3-Image, indicating early ecosystem support for local workflow integration.

  • Several commenters focused on benchmarking MiniMax H3-Image against Qwen Image 2.1 for image editing and against MOSS Image / Krie 2 for text-to-image quality. One user noted poor results from existing MiniMax H3 first-frame workflows and wondered whether this dedicated image model has different prompting or workflow requirements to reach higher output quality.

  • A technical concern raised was the model footprint: the release is reportedly around 66 GB, which may limit local usability depending on VRAM/storage constraints. Users also flagged interest in testing the base model’s editing behavior and censorship level relative to MOSS.

• Open source self driving is here! (Activity: 588): NVIDIA released Alpamayo 2 Edge, described as an open-source self-driving model trained with an RL loop, taking 6 camera inputs plus recent motion history. Embedl reports an optimized deployment that is >10× faster than PyTorch on edge hardware such as NVIDIA AGX Thor, with an interactive demo available on a real Thor device: embedl.com/nvidia/alpamayo2-edge/thor. Top comments are mostly jokes rather than technical discussion, riffing on the model’s driving decisions and “uncensored” variants; no substantive debate on architecture, safety validation, benchmarking methodology, or deployment constraints appears in the provided comments.

  • One technically relevant pointer is to comma.ai via r/Comma_ai, implying that open-source-ish/self-installable driver-assistance stacks already exist in the form of openpilot rather than this being an entirely new category. The rest of the thread contains mostly jokes or risk-related reactions without implementation details, benchmarks, or model/perception-stack discussion.

• Ernie 5.5 Flash will be released in two weeks (Activity: 388): The image is a screenshot of Baidu’s announcement that ERNIE 5.5 Flash Preview has launched and that the open-weight model release is targeted by November 25, matching the post title’s “released in two weeks” claim. Technically, the advertised specs are notable: 280B total parameters, 14B active parameters per token suggesting a sparse/MoE-style architecture, 1M token context, and claimed generation throughput of >200 tokens/sec for efficient inference. Commenters were cautiously optimistic about Baidu giving a firm date rather than a vague “soon,” while also noting skepticism about whether the model will be competitive. The claimed 200 t/s speed drew hardware-related doubt, with one user joking they would never hit that throughput locally.

  • A commenter points to the ERNIE-5.5-Flash-Base-BF16 reference weights on Hugging Face (baidu/ERNIE-5.5-Flash-Base-BF16) and notes an in-progress llama.cpp integration via draft PR ggml-org/llama.cpp#31925. They estimate that a Q4 quantization, at least IQ4_XS, should be viable on systems with 32GB VRAM + 128GB system RAM.

  • The claimed 200 tokens/s figure drew skepticism from users expecting it to be unreachable on typical local hardware, implying that practical throughput will depend heavily on quantization format, memory bandwidth, and backend support once llama.cpp compatibility lands.

2. Capability Editing, Backdoors, and Training Caps

• The Surprising Effectiveness of Deleting Weights in LLM Post-Training (Activity: 553): Lu, The Surprising Effectiveness of Deleting Weights in LLM Post-Training proposes Deletion Tuning, which learns a binary mask over transformer gate projection weights and zeroes <0.05% of parameters, reportedly matching full fine-tuning across RL with verifiable rewards, SFT, and on-policy distillation. The claimed advantages are much smaller artifacts—masks hundreds to thousands of times smaller than FFT checkpoints—and less catastrophic forgetting: in RL, prior-task accuracy stays near the base model while FFT/LoRA/random sparse FT lose up to 5.4 points. The authors also compare update geometry using stable rank, spectrum drift, and principal-weight overlap, finding Deletion Tuning closest to FFT among LoRA and random sparse baselines; code/masks are available on GitHub and Hugging Face. Commenters framed this as part of an emerging “weight-level programming” trend, connecting it to recent small-model weight-editing and neuron-level interpretability anecdotes. One technical interpretation was that the mask suppresses weights favoring suboptimal inference trajectories, allowing better latent paths already present in the base model to dominate; another commenter suggested the impact may be larger for training/post-training workflows than inference-time efficiency.

  • Commenters interpret the paper as a form of weight-level programming: instead of adding LoRA adapters or doing conventional fine-tuning, the method appears to identify weights that bias the model toward a less-optimal inference path and then set those weights to zero. One commenter highlights this as potentially “orders of magnitude more economical than LoRA fine-tuning” and suggests it may be straightforward to implement in tools that already manipulate weights directly, such as Heretic.

  • A recurring technical interpretation is that deletion-based post-training may not create new capabilities so much as unmask or prioritize capabilities already learned during pretraining. Several commenters argue that pretrained LLMs may contain many latent behaviors, with fine-tuning or pruning acting as a selector that suppresses irrelevant or harmful pathways rather than adding new knowledge.

  • The discussion frames this as evidence that pretraining may be highly redundant or overcomplete: models may learn broad capability sets, and post-training can refine behavior by removing parameters associated with undesired outputs. One commenter summarizes the tradeoff as making the model “dumber on everything we don’t care about” so it becomes better on the target task, implying task-specific sparsification rather than general capability gain.

• Microsoft Research on the integrity of model weights (Activity: 373). In its Lazarus study, Microsoft Research found that a small change to model weights could leave an agent behaving normally in routine tests while changing its behavior under particular conditions. Commenters asked whether independent checks on tool calls would catch a compromised model. For teams using third-party checkpoints, Microsoft recommends pinning model versions and verifying signatures and hashes before loading them. Microsoft’s model provenance guidance

• Fable 5.2 not only has guardrails against AI acceleration, its capabilities were capped in training too (Activity: 1020): The image (link) highlights a document section titled “AI research and development” stating that Claude Fable 5.2 and Claude Mythos 5.2 were not only protected by downstream safeguards, but were deliberately capacity-capped during training in domains that could accelerate AI R&D. The cited limitations include areas such as accelerator kernel optimization and LLM architecture improvement, implying Anthropic-style safety constraints were embedded into model capability development rather than applied only via inference-time guardrails. Commenters were skeptical of the stated safety rationale, arguing that kernel optimization also helps ordinary users run local models efficiently and that the restriction may function as anti-competitive capability gating. Others suspected the company may not apply the same caps to internal-only versions.

  • Commenters focused on the technical impact of restricting kernel optimization capabilities, noting that this affects not only frontier AI acceleration but also practical work like optimizing inference kernels for small local models on older hardware and building custom inference engines.

  • A substantive concern was that capability capping during training could introduce hard-to-detect regressions beyond explicit tool-use benchmarks. One commenter questioned whether Anthropic validated only narrow automated benchmarks or also tested cross-domain transfer, reasoning quality, and the model’s ability to choose and apply tools effectively: “It doesn’t matter if you leave tool use alone if the model behind it has been lobotomized in how best to use them.”

3. Local Inference Scaling and Quantization Benchmarks

• Running GLM 5.3 Flash on a 40 mini PC cluster via USB 3 interconnects at 14 tps (Activity: 1509): A user reports running GLM 5.3 Flash at native precision on a 40-node mini-PC cluster built from Intel N150 systems with 12 GB DDR5-4800 each, diskless boot, and a USB 3.2 Debug Capability-style 10 Gbps interconnect arranged as a 1 → 3 → 9 → 27 tree. They claim throughput of 14 tok/s at 1k context, 12 tok/s at 1M context, batched decode up to 40 tok/s, prefill around 85 tok/s, and wall power around 740 W; prior 1 Gbps LAN interconnects reportedly capped around 7 tok/s. Total build cost is stated as about $5,000, with remaining memory headroom for 8 × 1M context windows and planned work on prefill optimization plus speculative decoding. Commenters were split between viewing the result as an impressive low-cost native-precision local inference setup—especially for long-running autonomous coding jobs—and criticizing the practicality/efficiency of such a cluster versus other compute options.

  • A commenter highlights the key technical value proposition: running GLM 5.3 Flash at native precision on a 40 mini-PC USB 3 cluster reportedly reaches about 14 tokens/s for roughly $5k, framing it as potentially viable for long-running local workloads despite not being truly “flash” speed.

  • Another technically relevant concern is that prefill latency is likely the major bottleneck in this architecture; USB 3 interconnects and distributed memory across mini PCs may allow generation to proceed, but prompt ingestion/context processing appears to “hurt like hell,” limiting interactivity.

  • One commenter frames this as a plausible future for GPU-constrained users: aggregating devices with soldered RAM—mini PCs or even phones—into ad hoc clusters. The implication is that commodity RAM capacity can substitute for expensive VRAM, but with severe tradeoffs in bandwidth, latency, and orchestration complexity.

• New Qwen3.8-27B Unsloth Dynamic V3.1 GGUFs (Activity: 677): The image is a technical announcement graphic, not a meme: it presents Unsloth Dynamic v3.1 GGUF quantizations for Qwen3.8-27B, claiming 5–10% higher accuracy than UD3, GSQ-RCO, and ExLlama-3 across benchmarks like DeepSWE, Terminal Bench, LiveCodeBench, and average coding recovery. The linked benchmark plot (image) compares quantization accuracy versus size/RAM, with the post noting tests used long contexts (256K for agentic benchmarks, 128K for others) and multiple repeated runs; updated GGUFs are available on Hugging Face, with methodology details in the Unsloth docs. A commenter questioned the graph readability and interpretation, noting missing quant labels and surprising apparent drops from Q3 to Q4 on DeepSWE/Terminal Bench, making it unclear which quant to choose for 24–32GB GPUs. Unsloth also clarified a methodological dispute around ExLlama-3: their main plots exclude token embeddings because ExLlama-3 keeps them in BF16, but they argue real RAM/disk usage makes ExLlama-3 look worse when those embeddings are included.

  • A commenter questioned the benchmark plots because many quant labels were missing and DeepSWE/Terminal-Bench scores appeared to drop moving from Q3 to Q4, making quant selection for 24–32GB GPUs unclear; they noted the chart misleadingly seemed to imply IQ3_S was best. danielhanchen clarified that the main plots remove embedding-layer size from all quant providers, while an alternate plot using actual download/RAM size changes the interpretation: ExLlamaV3 keeps token embeddings in BF16, so full RAM/disk usage is larger than the plotted quantized-weight-only footprint.

  • danielhanchen added that ExLlamaV3 quantizes lm_head heavily but leaves token embeddings in BF16, speculating the embedding layer may be absorbing some quantization damage. They said they would benchmark ExLlamaV3 variants with non-BF16 embeddings, e.g. 8-bit, to determine whether accuracy changes.

  • Another user asked whether their existing tokenizer-pruning workflow—using ASCII-Condensed-prune-tools to remove some character sets from Qwen’s tokenizer so a Q4 Qwen 3.8 27B model fits on a 16GB GPU—would still work safely with the new Unsloth Dynamic V3.1 GGUFs.

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. Open-Weight Image and Video Model Releases

• MiniMax H3-Image released (Activity: 2903): The image is a screenshot of MiniMax’s official X announcement for MiniMax H3-Image, an open-weights image generation/editing model claiming up to 16-million-pixel outputs, 4K×4K generation in 10–20s, photorealistic quality, strong instruction following, and support for up to 16 reference images. The Reddit thread notes that the model weights are already available for ComfyUI on Hugging Face: Comfy-Org/MiniMax-H3-Image; the announcement image is here: i.redd.it/vuzgpghips0i1.png. Commenters mainly praised MiniMax’s release cadence, contrasting the quick open-weight drop after brief invite-only/API availability with other labs’ longer hype cycles and delayed releases.

  • Users noted that MiniMax H3-Image weights are already available for local/workflow use via the ComfyUI Hugging Face repo: Comfy-Org/MiniMax-H3-Image. The release cadence was highlighted as unusually fast: brief invite-only access followed by public weights roughly a day later.

• PAN 2 Released (Activity: 1290): IFM released PAN 2, an open-weights 29B latent diffusion video model on Hugging Face, with Diffusers, FastVideo, and vLLM integration recipes. The model targets up to 20s, 720p, 24fps generation under Apache-2.0, and IFM also released training code plus a technical blog. Architecturally, the post emphasizes heavy use of an LLM as a conceptual reasoner that emits dense timed text state/scripts, with event/action timing and camera controls nested under events but disentangled from actions, reportedly enabling complex multi-camera-move 20s generations. Commenters were broadly impressed by the model’s apparent logic/spatial reasoning, calling the examples “damn near magic,” while downplaying complaints about missing sound. There was also interest in whether the model can realistically run on consumer hardware.

  • Several commenters focused on PAN 2’s apparent spatial-reasoning and logic-handling capabilities, describing the release examples as unusually strong for open-source models. One user specifically contrasted complaints about audio quality with the model’s “damn near magic” handling of spatial reasoning, suggesting this may be the technically notable strength of the release.

  • A technically relevant concern was deployment accessibility: the model appears to target H200-class hardware, prompting requests for ComfyUI-compatible quantized builds that could run on consumer gaming GPUs. This indicates interest in lower-VRAM inference paths and workflow integration rather than only datacenter-scale usage.

  • The claim that PAN 2 is optimized for physics simulation drew attention, with users implying potential use cases around simulation-heavy generation or reasoning. However, the thread did not provide concrete benchmarks, architecture details, or reproducible performance numbers.

2. Qwen4 and Gemini 4 Frontier Model Previews

• Official Qwen4-Max now in preview (Activity: 494): The image is an official-looking announcement graphic for Qwen4-Max “Now in Preview” (image), matching the post’s linked Qwen/X announcement that Qwen4 is coming with claimed improvements in knowledge, world understanding, coding, agentic capabilities, front-end builds, and professional software workflows. The preview is reportedly available via Alibaba’s Token Plan, with early access also on QwenWork, Qoder, Qwen APP, and QwenStudio; the image itself is promotional rather than benchmark-heavy or technically detailed.

• Gemini 4 Carbon is here (Activity: 156): The image is a screenshot of a dark Model selection UI with the Gemini tab selected, showing a newly listed paid model, “Gemini 4 Carbon,” described as a frontier model for long-horizon agentic tasks across coding, knowledge work, and science, with a displayed release date of Nov 10, 2026 (image). Context from the title, “Gemini 4 Carbon is here,” frames this as an apparent launch/availability update rather than a benchmark post; no performance numbers, architecture details, context length, or API specs are provided in the image or comments. Commenters focus on pricing and plan segmentation: one compares Fable 5.2 being available on a $20 Pro plan while Gemini Carbon appears limited to a $200 Ultra tier, and another asks whether Carbon is priced like/replacing Argon. A third commenter says new frontier models are no longer exciting unless they bring meaningfully faster inference or larger usage limits.

  • Commenters focused on tiering and pricing ambiguity: one notes Fable 5.2 is available on the Pro plan at $20, while Gemini 4 Carbon appears restricted to Ultra at $200, raising questions about Google’s packaging strategy.

  • Several comments question the model-family mapping: whether Carbon corresponds to a Pro-class model and Argon to a Flash-class model, and whether Carbon is intended to replace Argon or coexist with it.

  • One technically relevant concern is that new frontier-model releases are less compelling without measurable improvements in latency, throughput, or quota limits; commenters want faster inference or higher usage caps rather than only a new model name.

3. Claude Code Real-World Wins and Failure Modes

• Claude helped me organize my legal database into a public archive with 300,000 searchable military board decisions, and this morning that work became evidence in a federal lawsuit. (Activity: 1439): A veteran-lawyer/nonprofit founder used Claude/Claude Code to crawl DoD military discharge/records-correction board pages, normalize irregular folder/file structures across 300,000+ public decisions in multiple formats, OCR scanned-image decisions, extract metadata fields, and publish a searchable/filterable ICML Reading Room. The resulting corpus is now cited in ICML v. Trump, et al. / complaint PDF, alleging DoD failed to make board decisions meaningfully searchable/indexed as required; the post claims DoD search undercounted “PTSD” badly, e.g. Naval Discharge Review Board files contained at least 13,085 matches while the site returned 211, and Army/Navy/Air Force boards contained at least 44,023 while cross-board search returned 11,600. Top comments were broadly supportive of using AI for public-interest legal infrastructure, while one commenter argued this kind of data-cleanup/search project is “1000x easier outside of the government than inside it” due to internal government constraints. Another commenter noted an odd discovered record involving an applicant trying to pursue charges against Oliver North.

• At 5:46 AM I get an'Urgent' message on my phone from Claude Code (Activity: 900): A Claude Code agent reportedly deleted /work/projects/gendarme_dev, including .git, after an unset temp-path variable caused find $tmp -delete to execute with no explicit path and therefore operate from the repository root (.); this destroyed local Git history for unpushed commits and all linked Git worktrees whose metadata lived in that .git. The planned mitigations are higher-frequency Btrfs snapshots, allowing pushes to a remote dev branch, and hardening shell cleanup with Bash’s "${tmp:?temp path missing}" plus a wrapper that creates its own temp dir and refuses deletion targets outside it. Commenters split between “agent has too much filesystem power” and “agent should have been allowed to push/back up more often”; the most technical replies emphasized remote repos, backups outside the checkout, and making destructive shell commands fail closed rather than relying on LLM instructions.

  • Several commenters discuss the operational risk of running Claude Code with broad filesystem privileges or “bypass permissions” enabled, especially after reports of accidental deletions. One technically relevant mitigation described is isolating agent access to a disposable dev box/sandbox with no business data, where the worst-case recovery path is reinstalling the environment rather than restoring critical files.

• 2.1.322: Anthropic's copyright paranoia is leaking into Claude Code through a botched system prompt (Activity: 781): The image is a terminal screenshot of Claude Code v2.1.322 allegedly exposing an injected hidden <ip_reminder> system/developer-style prompt. The leaked reminder instructs Claude to avoid reproducing copyrighted text, lyrics, long excerpts, and recognizable copyrighted characters, while also saying it should “avoid mentioning or responding to this reminder directly”—suggesting a prompt-isolation or instruction-leak regression in Claude Code. Commenters objected to opaque, uncontrollable injected reminders in developer tooling, framing them as disruptive hidden policy prompts. Several also criticized the irony of strict copyright refusal behavior given allegations that frontier models were trained on copyrighted books and other protected material.

  • Commenters criticized Anthropic’s runtime prompt injection behavior in Claude Code 2.1.322, specifically that copyright-related reminders appear to be inserted into active sessions without user visibility or control. The most technical concern was that this suggests a brittle mitigation strategy—“sending out system messages at some random time”—rather than a more robust policy layer, deterministic refusal mechanism, or transparent system-prompt management interface.

• The models are much stronger now, but I'm hitting more production bugs than I used to. Anyone else? (Activity: 74): The author reports increased production failures despite stronger LLM-generated code and extensive review, citing an auto-provisioning flow where a 16384-character input cap rejected a real ~35,000-character payload with a misleading validation error, and added cross-table SQL triggers failed only in production on Cloudflare D1 due to trigger nesting limits. Locally, 1236 tests passed, but production-specific database constraints were not covered; the proposed mitigation is reducing implicit trigger logic, using more explicit transactions, running production SQL compile checks via EXPLAIN across 236 templates, and executing one full end-to-end production-like flow before release. The central claim is that stronger models plus repeated “hardening” reviews can encourage layered defensive complexity, increasing the system’s failure surface even when each individual change appears correct. No top comments were provided to summarize additional debate.