The Best Image Model is back!

Congrats to Perplexity on Computer and for replacing Bixby as default AI on hundreds of millions of Samsung phones going forward, but those are more consumery news.

News that AI Engineers can use from today is Nano Banana 2, which is more formally called 3.1 Flash Image. The big story is the pricing: it is rated the #1 image model in the world per Arena and ArtificialAnalysis, and yet costs half the price (At $67/1k images, vs Nano Banana Pro ($134/1k) and GPT Image 1.5 ($133/1k) for generation, and FLUX.2 [max] at $140/1k images for editing).

It comes with 6 character consistency and search grounding, and great text rendering. Of course every generation is stamped by SynthID.

Of course, there’s no research detail or paper whatsoever, so our coverage ends here.

AI Twitter Recap

Google’s Nano Banana 2 (Gemini 3.1 Flash Image Preview) and the new image-eval meta

• Nano Banana 2 launch + rollout footprint: Google and DeepMind shipped Nano Banana 2 (aka Gemini 3.1 Flash Image Preview) as a “Flash-tier” image generation/editing model rolling out across Gemini App, Search (AI Mode/Lens), Flow, Google Ads, and in preview via AI Studio / Gemini API / Vertex AI (Google, GoogleDeepMind, GeminiApp, sundarpichai, demishassabis). Product claims emphasize world knowledge, improved i18n text rendering, aspect ratio control, upscaling up to 4K, and multi-subject consistency (e.g., “up to 5 characters & 14 objects”) (Google, joshwoodward).

• Arena/Artificial Analysis results + pricing signal: Multiple evaluators report Nano Banana 2 taking #1 Text-to-Image and strong editing placements, while undercutting “Pro” pricing—e.g., $67 / 1k images cited by Artificial Analysis vs ~$133–134 for GPT Image 1.5 and Nano Banana Pro (ArtificialAnlys, arena, kimmonismus). Arena added image subcategories and highlighted largest gains in text rendering and 3D imaging/modeling (arena). This is also a reminder that leaderboards are becoming product levers: “day-0” integrations (e.g., fal) and prompt packs/templates ship alongside eval wins (GeminiApp templates, GoogleAI prompts).

• Real-time search-conditioned generation: Google repeatedly frames NB2 as powered by real-time information and images from web search (not just static pretraining), positioning it as “more accurate views from any window in the world” style demos (sundarpichai).

• Downstream availability: Nano Banana 2 quickly appeared in third-party products, including Perplexity Computer (AravSrinivas).

Agentic coding + productized “tasks”, memory, and evals (and the backlash against complexity)

• Agents “just work” more often now, but still fail off-distribution: Several practitioners describe a step change in reliability/utility for coding agents across recent frontier models (e.g., GPT-5.2 / GPT-5.3 Codex, Opus 4.6, Gemini 3.1), shifting from “proof of concept” to something like delegating CLI work to juniors (teortaxesTex, paul_cal). Others caution that advanced ML/data engineering remains brittle off-distribution (michalwols, MParakhin).

• “Tasks” as the new packaging layer: Microsoft’s Copilot Tasks pitches “talk less, do more” delegation with user-visible plans and control, in “research preview” (mustafasuleyman, yusuf_i_mehdi).

• Persistent memory becomes table stakes—and introduces interoperability pain: A widely shared update claims Claude rolled out auto-memory (“remembers what it learns across sessions”) (trq212), echoed in the Claude ecosystem (omarsar0). Developers immediately hit workflow friction when memory/state lives in tool-specific hidden directories (hurting “multi-agent, multi-tool” continuity) (borisdayma).

• Tooling ships fast: PR bug-fixing bots, code↔design loops, and editor-level improvements:

  • Cursor Bugbot Autofix automates fixing issues found in PRs (cursor_ai, aye_aye_kaplan).

  • OpenAI’s Codex “code → design → code” roundtrip with Figma aims to make UI iteration less lossy (OpenAIDevs, figma).

  • VS Code’s long-distance Next Edit Suggestions focuses on predicting where not to edit and supporting “flow” (code, pierceboggan, alexdima123).

• Eval inflation + benchmark gaming concerns: Threads call out that high leaderboard scores can mask token-inefficient reasoning and failures on “bullshit tests” (e.g., repeated-token “strawberry” variants), warning against over-trusting HLE/GPQA-style metrics without cost accounting (scaling01). Arena responds by adding more granular test regimes like Multi-File React for code models (arena).

• Complexity is the real tax: A recurring engineering concern is that “10k LOC/day” bragging creates long-term complexity debt—agents make it easier to ship, not easier to maintain (Yuchenj_UW). Another angle: coding agents can create implicit lock-in if they “sloppify” your codebase such that working without them becomes painful (typedfemale).

Perplexity’s distribution + retrieval stack: Samsung integration and new embedding models

• Samsung S26 system-level Perplexity (“Hey Plex”): Perplexity says every Galaxy S26 will ship with Perplexity built in, including a wake word and deep OS integration; Bixby routes web/research/generative queries to Perplexity while handling on-device actions (perplexity_ai, perplexity_ai, AravSrinivas). This is framed as part of a broader partnership that also targets Samsung Internet and optional default search positioning (perplexity_ai).

• pplx-embed / pplx-embed-context released (MIT): Perplexity launched two embedding model families at 0.6B and 4B, including a “context” variant intended for doc chunk embeddings in RAG; both are MIT licensed and available via HF + Perplexity API, with a paper (arXiv:2602.11151) (perplexity_ai, perplexity_ai, alvarobartt). They also disclose internal benchmarks like PPLXQuery2Query / PPLXQuery2Doc with 115k real queries over 30M docs from 1B+ pages (perplexity_ai). Arav claims the embedding models are “industry leading” (AravSrinivas).

• Strategic read: The pair of moves—OS distribution + retrieval primitives—suggests Perplexity is trying to own both front door (assistant entry point) and core search stack (embeddings + evals), rather than depending on third-party platforms.

Inference, kernels, and infra: MoE support, heterogeneous hardware, and KV movement

• MoE becomes “first-class” in 🤗 Transformers: Hugging Face shipped deeper MoE plumbing (loading, expert backends, expert parallelism, hub support) and highlights collaboration on faster MoE training (including with Unsloth) (ariG23498, mervenoyann).

• DeepSeek and multi-hardware inference seriousness: Early in the batch, DeepSeek is called out as “serious about inference support on diverse hardware” (teortaxesTex). Separately, a DeepSeek DualPath detail describes staging KV cache in decode-server DRAM then moving it to prefill GPUs via GDRDMA to avoid local PCIe bottlenecks (JordanNanos). This reflects a broader shift: inference is increasingly a systems architecture problem, not just kernel-level optimization.

• Kernel coverage and GPU generations: vikhyatk describes building inference kernels across NVIDIA architectures (sm80→sm110) and notes edge-device ISA issues like Orin CPU lacking SVE (vikhyatk, vikhyatk).

• Quantization isn’t uniformly safe: Evaluations show MiniMax M2.5 GGUF quantizations degrade much more than expected vs Qwen3.5, arguing “just take Q4” doesn’t generalize across model families (bnjmn_marie).

World models, agents in simulators, and “multiplayer” environments

• Solaris: multiplayer Minecraft world modeling stack: A major research drop proposes that world modeling should focus on shared global state rather than pixel rendering, releasing (1) a multiplayer data collection engine, (2) a multiplayer DiT with a “memory efficient self forcing design” trained on 12.6M frames, and (3) a VLM-judge evaluation suite for multi-agent consistency (sainingxie, georgysavva). The pitch: multi-agent capability requires a shared representation beneath individual views.

• LLMs as embodied controllers (toy but telling): A CARLA→OpenEnv port shows a small Qwen 0.6B learning to brake/swerve to avoid pedestrians in ~50 steps using TRL + HF Spaces (SergioPaniego). This exemplifies a trend toward “LLM+env” loops where reversibility is limited and mistakes persist.

Governance flashpoint: Anthropic vs the Pentagon on surveillance and autonomous weapons

• Pentagon pressure campaign reported, then Anthropic responds publicly: A widely shared claim says the DoD issued a “final offer” to Anthropic, including threats to label it a “supply chain risk” and demands for unrestricted military use (KobeissiLetter). Anthropic then published a CEO statement drawing explicit red lines: no mass domestic surveillance and no fully autonomous weapons (given current reliability), also alleging threats involving the Defense Production Act (AnthropicAI). A widely quoted excerpt is reposted with detail (AndrewCurran_).

• Industry reaction + solidarity mechanics: The stance triggered strong support from prominent researchers/engineers, framing it as values-under-pressure rather than “policy theater” (fchollet, TrentonBricken, awnihannun). A petition aiming to coordinate “shared understanding” reportedly gathered signatures from OpenAI/Google staff (jasminewsun, sammcallister, maxsloef). This is notable as an explicit attempt to prevent a race-to-the-bottom dynamic via transparency about where each lab stands.

• Why this matters technically: The core dispute is about capability vs. reliability and “lawful use” language being misaligned with what frontier models can safely do today. Reliability concerns show up elsewhere in the dataset too (e.g., minimal security test cases where models leak confidential info even when instructed not to) (jonasgeiping, random_walker).

Top tweets (by engagement)

• Anthropic CEO statement on DoD demands (surveillance + autonomous weapons red lines) — @AnthropicAI

• Google launches Nano Banana 2 / Gemini 3.1 Flash Image Preview (broad rollout + “pro at flash speed”) — @GeminiApp, @sundarpichai, @GoogleDeepMind

• Perplexity + Samsung S26 system-level integration (“Hey Plex”) — @perplexity_ai

• Claude connectors available on free plan (150+ connectors) — @claudeai

• Pentagon vs Anthropic “final offer” reporting thread — @KobeissiLetter

• Claude Code auto-memory is huge (developer reaction) — @trq212

AI Reddit Recap

/r/LocalLlama + /r/localLLM Recap

1. Qwen3.5 Model Performance and Comparisons

• Qwen3.5-35B-A3B Q4 Quantization Comparison (Activity: 635): The post presents a detailed comparison of Q4 quantization methods for the Qwen3.5-35B-A3B model, focusing on their faithfulness to the BF16 baseline using metrics like KL Divergence (KLD) and Perplexity (PPL). The analysis highlights that AesSedai’s Q4_K_M achieves the lowest KLD of 0.0102, indicating high faithfulness, while Ubergarm’s Q4_0 significantly outperforms other Q4_0 quantizations. The post also notes that MXFP4 is less effective when applied post-hoc compared to during Quantization Aware Training (QAT). The efficiency score, which balances model size and KLD, ranks AesSedai_Qwen3.5-35B-A3B-IQ4_XS as the most efficient quantization. The setup used for testing includes an Intel Core i3-12100F CPU, 64 GB RAM, and an RTX 3060 GPU, with results based on the wikitext2_test.txt dataset. Commenters appreciate the detailed comparison and suggest that quantizers should include such analyses in their documentation. There is also a discussion about the potential bias in using wikitext for PPL/KLD measurements, as it might be included in some imatrix datasets, suggesting the use of a fresh dataset for more accurate comparisons.

  • The comment by ‘ps5cfw’ highlights the ambiguity in quantization terminology like ‘Q4_K_M’, emphasizing the need for standardization and clarity in documentation. This is crucial for making meaningful comparisons between different quantization methods, especially after issues like the XL debacle.

  • ‘noneabove1182’ points out a potential issue with using wikitext as a PPL/KLD measurement, as some datasets might include wikitext, potentially skewing results. They suggest using a fresh dataset, such as STT from a recent podcast, for more accurate comparisons. This highlights the importance of dataset transparency and selection in benchmarking.

  • ‘danielhanchen’ discusses ongoing investigations into the high perplexity of Q4_K_XL due to MXFP4 layers. They note that other quantizations like Q2_K_XL and Q3_K_XL are unaffected. The comment also mentions that the UD-Q4-K-XL quantization significantly outperforms Q4-K-M in real-world benchmarks, as shown in Benjamin Marie’s LiveCodeBench v5.

• Qwen3.5 122B in 72GB VRAM (3x3090) is the best model available at this time — also it nails the “car wash test” (Activity: 706): The post discusses the performance of the Qwen3.5 122B model, which is optimized to run on a setup with 72GB VRAM using three 3090 GPUs. The user highlights its efficiency, achieving 25 tokens per second with specific settings like Temperature 0.6, K Sampling 20, and Top P sampling 0.8. The model is noted for its ability to handle a 120k context in Q3 mode, despite being slower than other models like GLM Air and GPT-OSS-120B. The user also mentions challenges with other configurations like MXFP4 and IQ4_XS, which require offloading layers to RAM, reducing speed to 6-8 tok/s. One commenter notes achieving 34-36 tok/sec with a different setup, using Qwen3.5-122B-A10B-UD-Q4_K_XL and a Ryzen 9 9950X3D with RTX 5090. Another comment critiques the ‘car wash test’ as a biased scenario that exploits model training biases, suggesting it is not a definitive measure of model intelligence.

  • A user reports achieving 34-36 tokens per second with the Qwen3.5-122B-A10B-UD-Q4_K_XL model and 16-18 tokens per second with the Qwen3.5-122B-A10B-UD-Q8_K_XL model, both at a maximum context size of 256K. Their setup includes a Ryzen 9 9950X3D, RTX 5090, and 128 GB DDR5 5600 RAM, running on Cachy OS Linux, which is based on Arch Linux.

  • The ‘car wash test’ is critiqued as being less meaningful than often suggested. It is described as a scenario that frequently appears in training data, which biases the model to replicate learned logic rather than demonstrating genuine reasoning ability. This test is seen as a targeted probe of a specific model weakness rather than a comprehensive measure of intelligence.

  • There are reports of issues with the 4-bit Unsloth quantization in the Qwen3.5 model series, suggesting potential for further optimization. Despite these issues, the model is noted for its impressive performance, especially in contrast to previous releases that did not meet expectations.

• Qwen/Qwen3.5-35B-A3B creates FlappyBird (Activity: 372): The post discusses the use of the Qwen/Qwen3.5-35B-A3B model to create a Flappy Bird clone using HTML, CSS, and TypeScript, initialized with Vite. The model, hosted locally, demonstrated effective coding capabilities by generating a basic game structure and implementing features like music using the Web Audio API, a scrollable parallax background, and a flock of birds. The user noted some initial visual glitches with the parallax effect, which were resolved with minor adjustments, and successfully added a sound settings panel in a single attempt. One commenter suggested the potential for open model companies to conduct repeated benchmarks or tests with different games to evaluate performance, indicating interest in further exploration of the model’s capabilities.

  • BitXorBit raises an interesting point about the potential for open model companies to prepare for repeated benchmarks or tests. They suggest trying different games and sharing results, which could provide insights into the model’s adaptability and performance across various tasks. This could be particularly relevant for evaluating the generalization capabilities of models like Qwen/Qwen3.5-35B-A3B.

  • ShengrenR suggests a next step in the project: training a reinforcement learning (RL) model to play Flappy Bird based on screen input. This would involve using the visual data from the game to inform the model’s actions, potentially leading to a more sophisticated AI capable of learning and adapting to the game’s challenges in real-time.

• Qwen 3.5 craters on hard coding tasks — tested all Qwen3.5 models (And Codex 5.3) on 70 real repos so you don’t have to. (Activity: 917): The image is a snapshot from the APEX Testing website, which evaluates AI coding models on real-world coding tasks. It shows that 34 models were tested across 65 tasks, with a total of 2208 runs, and highlights the top models based on ELO scores, including Claude Opus 4.6 and GPT 5.2 Codex. The post discusses the performance of various models, notably Qwen 3.5 and Codex 5.3, on a benchmark designed to test coding models on real codebases. Qwen 3.5 models, particularly the 397B variant, struggle with complex tasks requiring coordination across multiple files, while Codex 5.3 shows consistent performance across difficulty levels. The GLM-4.7 quantized model is noted as the best local model, outperforming Qwen 3.5 models. The post also mentions the use of an agentic tool-use system for fairer comparisons and highlights the importance of the framework used in testing, as it can significantly impact model performance. Commenters discuss the performance of specific models like gpt-oss-20b and GLM-4.7, questioning whether the custom agentic framework used might affect results. They suggest testing with popular frameworks to ensure the framework isn’t limiting model performance, as different frameworks can lead to significant performance variations.

  • UmpireBorn3719 highlights a comparison between gpt-oss-20b and Qwen3 Coder Next, noting that gpt-oss-20b scored 1405 while Qwen3 Coder Next scored 1328 in the coding task benchmarks. This suggests that gpt-oss-20b may perform better in certain coding scenarios, although the specific tasks and conditions of the benchmark are not detailed.

  • metigue discusses the impact of using different agentic frameworks on model performance, noting that open-source models can show more than 50% performance swings depending on the framework used. They suggest testing with popular frameworks as the choice of framework can significantly alter which model appears to be the best, citing examples where GLM-5 outperforms Opus 4.6 and Codex 5.3 outperforms both when using the Droid framework.

  • Hot_Strawberry1999 appreciates the inclusion of benchmarks with different quantization levels, noting that such comparisons are rare. This suggests that the quantization level can significantly impact model performance, and having this data is valuable for understanding how models might perform under different computational constraints.

• Qwen3.5 27B better than 35B-A3B? (Activity: 771): The image compares the performance of different models in the Qwen3.5 Medium series, specifically the 35B-A3B, 27B, and 122B-A10B models. It highlights various benchmarks such as instruction following, graduate-level reasoning, and multilingual knowledge. The 27B model is noted for its efficiency, particularly in environments with limited resources like 16 GB of VRAM and 32 GB of RAM, making it a potentially better choice over the 35B-A3B model in such scenarios. The image provides a visual representation of these performance metrics, aiding in the decision-making process for users with specific hardware constraints. One user mentions personal testing, indicating that the 27B model performs better on their hardware, a 3090 GPU, with a difference in processing speed of 100 t/s compared to 20 t/s. This suggests that the 27B model may offer better performance efficiency on certain hardware configurations.

  • FusionCow notes a performance difference between the Qwen3.5 27B and 35B-A3B models on a 3090 GPU, with the 27B model achieving 100 tokens/second compared to 20 tokens/second for the 35B-A3B. This suggests that the 27B model is more efficient in terms of speed, which could influence user choice based on processing time requirements.

  • boinkmaster360 suggests that the Qwen3.5 27B model is a dense model, implying it might be slower but potentially more intelligent. This highlights a trade-off between computational speed and model complexity, where denser models may offer improved performance in certain tasks due to their architecture.

  • Alternative_You3585 points out that the Qwen3.5 27B model likely excels in intelligence compared to the 35B-A3B, but the latter may have advantages in real-world knowledge and processing speed. This indicates a nuanced performance landscape where different models may be preferable depending on the specific application requirements.

2. Geopolitical and Access Issues in AI Models

• American closed models vs Chinese open models is becoming a problem. (Activity: 1387): The post discusses the challenges faced by organizations that require open AI models due to national security concerns, specifically avoiding Chinese models due to perceived risks. The only recent American model available is gpt-oss-120b, which is outdated compared to modern models like GLM and MiniMax. The author suggests that pressure on companies like Anthropic by the DoD may be due to a need for offline AI solutions. Alternatives like Cohere in Canada are considered, but the lack of competitive open American models is a significant issue. Commenters suggest modifying Chinese models to create custom solutions, and mention Mistral Large 3 as a potential alternative, though it may not match the capabilities of Chinese models. There is skepticism about StepFun-AI being a viable non-Chinese option, as it is also based in China.

  • The discussion highlights the availability of various AI models from different countries, emphasizing that the choice of model should be based on specific use cases rather than national origin. For instance, Mistral Large 3 is mentioned as a competitive model, though not necessarily superior to Chinese models like DeepSeek. The commenter suggests that enterprise environments can benefit from fine-tuning models to meet specific needs, which can mitigate potential security concerns.

  • A detailed list of AI models from different countries is provided, showcasing the diversity in AI development globally. Notable mentions include Llama from Meta Platforms in the US, Qwen from Alibaba Cloud in China, and Mistral from Mistral AI in France. The commenter argues that the effectiveness of a model is highly dependent on its application, and enterprises should focus on customizing models through techniques like fine-tuning and RAG databases to enhance performance and address security issues.

  • The commenter argues that concerns over the origin of AI models, such as potential backdoors, are less relevant when models are used offline and fine-tuned for specific enterprise needs. They suggest that companies can leverage open-source models by fine-tuning them, applying techniques like (Q)(Re)LoRAs, and building RAG databases to improve accuracy and security. This approach is common among hobbyists on platforms like Huggingface, indicating that enterprises with budgets should be capable of similar customizations.

• DeepSeek allows Huawei early access to V4 update, but Nvidia and AMD still don’t have access to V4 (Activity: 559): DeepSeek has provided early access to its V4 AI model update to Huawei and other domestic suppliers, aiming to optimize the model’s performance on their hardware. This strategic move excludes major US chipmakers like Nvidia and AMD, who have not received access to the update. The decision is likely influenced by the need for compatibility and optimization on non-Nvidia hardware, as DeepSeek’s models are typically trained on Nvidia platforms, suggesting a focus on enhancing performance for Huawei’s specific hardware architecture. Commenters speculate that Nvidia’s lack of access is not surprising, as DeepSeek models are generally optimized for Nvidia hardware. The early release to Huawei is seen as a strategic move to ensure compatibility with non-Nvidia systems, highlighting the competitive dynamics in AI hardware optimization.

  • jhov94 suggests that DeepSeek is likely optimized for Nvidia hardware, implying that Nvidia might not need early access to V4 since the models are already compatible with their systems. The early release to Huawei could be due to compatibility issues with their hardware, which might require additional adjustments or optimizations.

  • ResidentPositive4122 reflects on the media hype surrounding DeepSeek, particularly during its initial announcements, and advises skepticism towards mainstream media claims. They suggest that despite the lack of early access for Nvidia and AMD, major inference providers will likely adapt to V4 shortly after its release, as is common with new model launches.

  • stonetriangles questions the significance of Nvidia not receiving early access to V4 by comparing it to previous versions like R1, V3, or V3.2, where Nvidia also did not have early access. This implies that the current situation is not unusual and may not warrant concern.

3. AI Model Leaderboards and Benchmarks

• Anthropic Drops Flagship Safety Pledge (Activity: 354): Anthropic has decided to drop its flagship safety pledge, which was a commitment to prioritize safety in AI development. This decision marks a significant shift in their approach to AI governance and safety protocols. The pledge was initially designed to ensure that AI systems are developed with a strong emphasis on ethical considerations and risk mitigation, but the reasons for its withdrawal have not been explicitly detailed by the company. The comments reflect a critical view of Anthropic’s decision, with some suggesting that external pressures, possibly from governmental or defense entities, may have influenced this change. There is a sentiment that this move could compromise the ethical standards previously upheld by the company.

  • till180 discusses the implications of Anthropic dropping their safety pledge, suggesting that while public models may still have safety guardrails, the removal of the pledge could facilitate selling models to the US military. This is in light of recent demands from the Pentagon for Anthropic to provide their models, indicating a potential shift in the company’s operational focus and ethical stance.

• Anthropic is the leading contributor to open weight models (Activity: 839): Anthropic is reportedly the leading contributor to open weight models, albeit unintentionally, as their models are being distilled against their terms of service. The process of distillation involves using interactions with the model to create a smaller, efficient version, and tools like dataclaw facilitate publishing these interactions to platforms like HuggingFace. DeepSeek has distilled 150k chat rounds, but many users have significantly more data available. Commenters suggest a strategy of ‘distributed distillation’ where users contribute to distillation efforts, potentially incentivized by tokens. There’s a sentiment that open-source efforts, even if led by non-American entities, are beneficial for the community.

  • The concept of ‘distributed distillation’ is suggested as a method for improving model training by leveraging user interactions. This involves users asking questions that can be used for distillation, potentially incentivized by offering tokens like ‘qwen-3.5’. This approach could enhance the dataset diversity and quality for training open models.

  • A tool called ‘dataclaw’ is mentioned, which allows users to publish their Claude Code conversations to HuggingFace with a single command. This could facilitate the sharing and distillation of large datasets, as evidenced by DeepSeek’s distillation of 150k chat rounds, highlighting the potential for users to contribute significantly more data from their own collections.

  • The discussion touches on the geopolitical aspect of AI development, with some users expressing a preference for Chinese open-source contributions over American ones. This sentiment underscores the global nature of AI development and the importance of open-source models in fostering international collaboration and competition.

• Self Hosted LLM Leaderboard (Activity: 324): The image presents a leaderboard for self-hosted large language models (LLMs), categorizing them into tiers S, A, B, C, and D based on their performance. Models are listed with their names and parameter sizes, such as “Kimi K2.5” and “GLM-5” in the top S tier. The leaderboard allows filtering by specific capabilities like coding, math, reasoning, and efficiency, providing a comprehensive overview of model performance for self-hosting purposes. The leaderboard is hosted on Onyx. Commenters discuss the absence of the Qwen 3.5 models, suggesting they should be included in the A or B tier due to their capabilities, including vision support, which is beneficial for homelab and small business applications. There is also a mention of Qwen3-Next and Qwen3-Coder-Next as top-performing models for standard hardware.

  • The Qwen 3.5 models, particularly the 27B dense and 122B MoE versions, are highlighted for their potential to rank in the A-tier or B-tier of self-hosted LLMs. These models are noted for their vision capabilities, which are beneficial for applications in homelabs and small businesses, suggesting they should be included in the leaderboard.

  • Qwen3-Next and Qwen3-Coder-Next, both at 80B parameters, are praised for their performance on standard hardware. These models are considered highly effective, especially in coding tasks, and their absence from a coding-focused leaderboard is seen as a significant oversight.

  • There is a discussion about the hardware requirements for running S-tier models, though specific details are not provided in the comments. This suggests a need for further clarification on the computational resources necessary to effectively deploy top-tier self-hosted LLMs.

Less Technical AI Subreddit Recap

1. Nano Banana 2 and Gemini 3.1 Flash Developments

• Google releases Nano banana 2 model (Activity: 984): Google has released the Nano Banana 2 model, an advanced AI image generation model that integrates professional-grade capabilities with rapid processing speeds. This model is noted for its enhanced world knowledge, production-ready specifications, and improved subject consistency, allowing users to generate high-quality images efficiently. For more details, refer to the Google Blog. Users are impressed with the model’s performance, particularly in tasks it previously struggled with, such as complex image generation for home remodeling, indicating significant improvements in image quality and consistency.

  • BuildwithVignesh provides links to Google’s official blog and the Gemini API documentation, which are crucial for developers looking to integrate or understand the capabilities of the Nano Banana 2 model. The blog likely details the model’s features, improvements, and potential applications, while the Gemini API documentation would offer technical guidance on implementation and usage.

  • JTwoXX highlights a limitation of the Nano Banana 2 model, noting that it still struggles with generating PNG images without a background. This suggests that while the model may have advanced in other areas, there are still specific technical challenges that need to be addressed, particularly in image transparency and background handling.

  • bentendo93 shares a practical application of the Nano Banana 2 model, using it for home remodeling visualizations. This indicates the model’s improved performance in generating realistic and useful images for practical scenarios, which could have implications for industries like interior design and architecture.

• Gemini 3.1 Flash (Nano Banana 2) Spotted Live in Gemini Ahead of Official Release (Activity: 287): The image depicts an early access interface for the upcoming Gemini 3.1 Flash, internally known as Nano Banana 2. This suggests a staged rollout of the model within the Gemini platform, even though no official announcement has been made yet. The interface includes a loading message for “Nano Banana 2,” indicating that users can select and potentially interact with the model, hinting at its imminent release. One comment highlights the impressive detail in the model’s output, specifically noting the intricate depiction of a bird reflected in an eye, suggesting high-quality rendering capabilities.

  • Ggoddkkiller highlights a concern about Google’s handling of customer relations, particularly in the context of the Vertex AI platform. The comment suggests dissatisfaction with Google’s approach to customer engagement and support, especially when compared to the excitement around the Gemini 3.1 release. This reflects a broader sentiment in the tech community about the need for better customer service and transparency from major tech companies like Google.

• Nano Banana 2 is real! Gemini 3.1 Flash Image just appeared in Vertex AI Catalog (Activity: 264): The image in the post is a side-by-side comparison of two AI-generated portraits, showcasing the capabilities of the newly released Nano Banana 2 (also known as Gemini 3.1 Flash Image) and the existing Nano Banana Pro. The post highlights that the new model, despite being a ‘Flash’ tier, offers quality close to the Pro version, particularly excelling in spatial logic for dense compositions. This model is designed for high-speed, low-cost production, suitable for high-frequency pipelines like bulk UGC ad creation. It retains features from the Nano Banana series, such as multi-subject reference and high-fidelity style transfer, making it a significant release for 2026. One commenter believes that the Nano Banana Pro still has an edge over the new model in the provided example, while another expresses a desire for a video model with similar capabilities.

  • The original Flash Image model had solid image quality, but faced issues with prompt adherence, particularly with complex instructions where it would often ignore parts of the prompt or regenerate the same output. Additionally, it struggled with text and infographic rendering, as well as multi-image compositing. The key question for the new Gemini 3.1 Flash Image is whether these issues have been addressed, and proper testing on dense prompts is awaited to confirm any improvements.

• Nano Banana 2 pricing !!!! (Activity: 206): The image provides pricing details for two AI products, “Nano Banana 2” and “Nano Banana Pro.” “Nano Banana 2” is marketed as offering pro-level visual intelligence with a pricing structure of $0.50 for input and $3.00 for output. In contrast, “Nano Banana Pro” is described as a state-of-the-art image generation and editing model, with input priced at $2.00 and output at $12.00. Both products have a knowledge cut-off date of January 2025. The pricing suggests a tiered approach to AI services, with the Pro version being significantly more expensive, likely due to enhanced capabilities or features. Commenters compare the pricing and capabilities of “Nano Banana” products with “Gemini 3 Pro Image” and “Gemini 3.1 Flash Image,” noting that the latter’s pricing scales with image resolution. There is a debate on whether “Nano Banana Pro” offers better quality than “Nano Banana 2,” with some suggesting the quality is comparable.

  • Ggoddkkiller provides a detailed breakdown of the token costs for the Gemini 3 Pro Image and Gemini 3.1 Flash Image models. The Pro Image charges 560 tokens per input image, with output costs scaling by resolution, while the Flash Image charges 1120 tokens per input image with different scaling. The Flash Image is slightly cheaper than the Pro, but the pricing structure is complex and not as low as some users hoped.

  • Halpaviitta shares insights from personal testing, noting that the new model is approximately four times cheaper and slightly faster than the Pro version. This suggests a significant cost-performance advantage, making it a favorable option despite the initial concerns about pricing.

  • Actual_Committee4670 mentions that the generation speed is currently slow, which affects the ability to fully test the new model. However, they express a positive outlook on the cost of the new model, indicating that the pricing might be justified if performance improves.

2. Anthropic and Pentagon AI Safeguard Dispute

• Anthropic rejects Pentagon’s “final offer” in AI safeguards fight (Activity: 1863): Anthropic has declined the Pentagon’s final offer concerning the deployment of its AI model, Claude, due to inadequate safeguards against potential misuse in mass surveillance and autonomous weapons. The Pentagon has responded with threats to blacklist Anthropic and potentially invoke the Defense Production Act. Despite these tensions, Anthropic is open to further negotiations, underscoring the broader challenges of AI deployment in classified environments, as other companies like xAI face similar contractual dilemmas. For more details, see Anthropic’s statement. The comments reflect a positive view of Anthropic’s stance, with users expressing respect for the company’s commitment to its principles, despite the low bar set by industry standards.

• Exclusive: Hegseth gives Anthropic until Friday to back down on AI safeguards (Activity: 1434): Defense Secretary Pete Hegseth has issued an ultimatum to Anthropic, demanding the removal of safety guardrails from its Claude AI model by Friday, as reported by Axios. The Pentagon seeks unrestricted access to Claude for purposes including domestic surveillance and autonomous weapons development, which contravenes Anthropic’s terms of service. Failure to comply could lead to the invocation of the Defense Production Act or the designation of Anthropic as a supply chain risk, potentially blacklisting them from government contracts. A notable comment highlights the irony of AI companies imposing safety measures on government use, contrasting with typical regulatory roles. This reflects a broader debate on the balance of power and responsibility between tech companies and government entities in AI governance.

• Statement from Dario Amodei on our discussions with the Department of War (Activity: 917): Dario Amodei of Anthropic has issued a statement regarding their collaboration with the Department of War, emphasizing their stance against the use of AI for mass surveillance and autonomous weapons. The company is pioneering the integration of AI into classified networks, but insists on maintaining safeguards to protect democratic values, despite external pressures to relax these measures. For more details, see the original statement. Commenters express skepticism about Anthropic’s ethical stance, noting the irony of partnering with Palantir, a company known for its involvement in surveillance. Others view the statement as a bold move given the current political climate.

3. Qwen Model Performance and Optimization

• Big love to the Qwen 🧠 A true SOTA Open Source model running locally (Qwen 3.5 35B 4-bit) - Here is the fix for the logic loops! ❤️ (Activity: 173): The post discusses the implementation of the Qwen3.5-35B-A3B-4bit model, highlighting its initial issues with reasoning loops and logic errors typical of 4-bit quantized models. The author resolved these by adjusting the system prompt to enforce ‘Adaptive Logic,’ which separates the model’s internal ‘thinking’ from its final output, significantly improving performance on the Digital Spaceport Benchmark suite. The model successfully solved complex logic and math problems, generated SVG code, and performed accurate counting. Key configuration settings include a temperature of 0.7, top-p of 0.9, and a frequency penalty of 1.1. The ‘Anti-Loop’ system prompt is crucial for preventing repetitive loops and ensuring efficient task execution. A commenter noted the effectiveness of the Qwen3.5-35B-A3B model on a MacBook Pro M4 with 48GB RAM, appreciating the model’s ‘thinking’ feature and planning to incorporate the shared prompt tips. The context length was set to 128k, which may contribute to its improved performance.

  • A user reported using the Qwen 35B A3B model on a MacBook Pro M4 with 48GB RAM, highlighting its improved performance over the previous 30B version. They noted that the 35B model is less prone to getting stuck in logic loops, which was a concern with earlier versions. The context length is set to 128k, allowing for extensive input processing, and the ‘thinking’ feature provides insight into the model’s decision-making process.

  • There is a discussion about whether the Qwen 35B A3B model performs better with or without the ‘thinking’ feature enabled. This feature allows users to see what the model is considering, which can be beneficial for understanding its decision-making process. However, there is curiosity about the model’s behavior when it cannot generate an answer, suggesting that the ‘thinking’ feature might help mitigate such issues.

AI Discord Recap

1. Nano Banana 2 & Arena Leaderboards Heat Up

• NB2 Crowns Image Arena, Web Search Wobbles: Nano Banana 2 debuted as Gemini‑3.1‑Flash‑Image‑Preview and landed at #1 in Image Arena, adding a new web search capability (Gemini 3.1 Flash Image Preview, Image Arena leaderboard).

  • Users concluded NB Pro still beats NB2 on text curvature and non‑human characters while reporting frequent “something went wrong” errors and unreliable web search, noting NB2 remains faster but lower quality than Pro (Gemini 3.1 Flash Image Preview).

• P‑Video Debuts, Price‑Tagged Performance: P‑Video entered the Video Arena leaderboards, pricing generation at $0.04/second for 1080p outputs (Video Arena).

  • The community framed P‑Video as a competitive price‑performance option against incumbents, tracking its initial placement and waiting for longer‑horizon quality evals on the public leaderboard (Video Arena).

• Seedream‑5.0‑Lite Climbs Multi‑Image Edit: Seedream‑5.0‑Lite tied for top 5 on the Multi‑Image Edit Arena leaderboard, signaling rapid gains in multi‑image compositional editing (Multi‑Image Edit leaderboard).

  • Practitioners highlighted Seedream’s strong controllability and consistency in multi‑image edit tasks, watching for further advances as new datasets and evals roll in (Multi‑Image Edit leaderboard).

2. Quantization & Inference Infra: Practical Wins and Warnings

• MXFP4 Math Sparks Qwen3.5 Quant Quibbles: Engineers reported unusually high perplexity/KL on Qwen3.5‑35B ud‑q4_k_xl dynamic quants, prompting an investigation and suggestions to compare MXFP4 vs Q4K tensor mixes (Reddit: best Qwen3.5 GGUF for 24GB VRAM).

  • The Unsloth team emphasized their dynamic quants are validated for long context lengths while users proposed A/Bs that “replace MXFP4 tensors with regular Q4K ones” to isolate regressions, amid broader method talk spurred by their DPO primer (Unsloth DPO blog).

• LM Link Tunnels Remote LLMs, E2E Encrypted: LM Studio launched LM Link to load and use models on remote rigs as if local, built with Tailscale and end‑to‑end encryption with no open ports required (LM Link).

  • Users requested direct‑IP modes, image/video support, and mobile apps while noting 0.4.5 build 2 fixes and a Tailscale deep dive on the design and network posture (LM Link on Tailscale blog).

• E‑Waste GPUs Hit 26 t/s on Qwen 3.5 Q6: A practitioner hit ~26 t/s on Qwen 3.5 Q6 using P104 e‑waste cards in a budget rig, sharing hardware pics and setup deets (rig image).

  • Debate focused on PCIe Gen4+ sufficiency for multi‑GPU VRAM capacity builds and slot bifurcation solutions, with pointers to affordable risers for denser configurations (example PCIe bifurcation riser).

3. Agent Systems Go Practical: From Open Source to Ops

• Hermes Agent Ships: Open‑Source, Multi‑Level Memory: Nous Research released Hermes Agent, an open‑source agent with multi‑level memory, persistent machine access, and out‑of‑the‑box support for CLI plus Telegram/WhatsApp/Slack/Discord, with the first 750 portal signups getting a free month via code HERMESAGENT (Hermes Agent).

  • They expanded the Atropos agentic RL pipeline around Hermes’ primitives (subagents, programmatic tool calling, FS/terminal control, browser), drawing praise like “streets are saying hermes agent is the one” as devs dug into the codebase (hermes-agent GitHub).

• OpenClaw Runs a Real‑Estate Empire: An operator used OpenClaw to automate rent payment tracking, repair coordination, and lease generation, with plans to wire up bank accounts, WhatsApp messaging, and ad creation on immoscout24.de.

  • Builders compared model stacks—e.g., GLM‑5 + Claude Code for patching—with strong field reports for Qwen 3.5‑Plus via Alibaba’s plan as a cost‑effective backbone (Alibaba Cloud AI Coding Plan).

• Trigger.dev Tames OpenClaw’s Silent Fails: A post detailed re‑platforming OpenClaw on Mastra + Trigger.dev + Postgres to eliminate silent task failures and flaky gateway restarts, shipping a one‑command setup (I built a better foundation for OpenClaw).

  • The community cited improved reproducibility and observability with evented orchestration and durable state, calling the stack a pragmatic baseline for multi‑tool agent ops (I built a better foundation for OpenClaw).

4. Perplexity: OEM Deal Meets API/UX Headwinds

• Samsung Says “Hey Plex” on Galaxy S26: Perplexity partnered with Samsung to ship a system‑level assistant on Galaxy S26 devices with the wake word “Hey Plex” (Perplexity announcement).

  • Members speculated that Bixby will be powered by Perplexity’s search‑grounded LLMs, pointing to device‑level preloads and OS hooks that go beyond an app wrapper (Perplexity x Samsung details).

• Pro Query Caps Crash Workflows: Perplexity Pro users reported throttling from 250 to 20 queries, with some stating they switched to GPT chat to keep working.

  • One user lamented, “I used to use Perplexity literally every day... but now it’s impossible to use it even with a paid PRO subscription”, while others echoed frustration over repeated cap reductions.

• Sonar Deep Research Shrinks Sources, Same Cost: Reports flagged the Sonar Deep Research API dropping sourced citations from ~36 to ~10 while requests still cost about $0.45 (Perplexity status note, James Liounis on API changes).

  • Developers suspect backend changes and advised monitoring official status posts as they reassess cost‑per‑finding and pipeline reliability (Perplexity status note).

5. GPU Kernel Optimization & RL‑Tuned Codegen

• IterX RL Rockets MoE Fusion 14.84× on B200: DeepReinforce.ai unveiled IterX, an RL‑driven code optimization system for fused MoE tasks on FlashInfer, claiming 14.84× speedups on B200, with free credits and tutorials for competitors (IterX blog, IterX tutorials).

  • When asked for concrete latencies at longer sequences, they cited 21.252ms (901), 36.012ms (11948), and 45.247ms (14107), giving practitioners targets for reproductions and head‑to‑head evals (IterX tutorials).

• GDN Decode DSL Delivers 2.56µs: A contributor posted a GDN decode solution clocking 2.56µs, reportedly ~760× faster than PyTorch eager and 1.31× faster than the FlashInfer Cute DSL kernel, with code available for inspection (flashinfer-competition-codebase).

  • They also shared submission tips around tagging forks for the leaderboard, enabling clearer repro and organizer access for benchmarking (flashinfer-competition-codebase).

• Uniform Instructions: One Warp, One Issue: A GPU deep‑dive clarified uniform instructions execute once per warp (SIMD32 semantics) and recommended using elect.sync for single‑issuer patterns (NVIDIA GTC talk).

  • Engineers also shared the Tensor Memory Addressing PTX reference for elusive addressing tricks in tensor ops, pinning docs for future kernel archeology (Tensor Memory Addressing (PTX)).