Despite a lot of rumors of a “Sonnet 5”, Anthropic opted to launch Sonnet 4.6 today, bumping their cheaper workhorse model up to match Opus 4.6, touting some preference wins from Sonnet to 4.5 Opus and a 1m token context, though generally lagging in usual benchmarks, and on GDPVal-AA (explained in our podcast with them) it uses 4.5x more tokens so the all-in cost can be higher than Opus in some tasks. The API platform tools and the Excel integrations also got minor upgrades.

Some of the key highlights are the long term improvements in Computer Use, first launched in Oct 2024, which was at launch completely slow and so inaccurate as to be impractical, but now is productized as Claude Cowork, which has anecdotally seen more successful adoption than OpenAI’s equivalent Operator and Agent iterations.

We have tuned the Twitter recap below to include more datapoints, but really that’s all that you truly need to know.

AI Twitter Recap

Top Story: Sonnet 4.6 launch

What happened (timeline + headline claims)

Anthropic launched Claude Sonnet 4.6 as an upgrade to Sonnet 4.5, positioning it as their most capable Sonnet model with broad improvements across coding, computer use, long-context reasoning, agent planning, knowledge work, and design, plus a 1M-token context window (beta) [@claudeai]. Early chatter preceded the announcement (“Sonnet 4.6 incoming!”) [@kimmonismus], then the launch triggered a wave of benchmark callouts, tooling/platform integrations (Cursor, Windsurf, Microsoft Foundry, Perplexity/Comet, etc.), and mixed early user feedback about quality and reliability.

• Official announcement + feature list + 1M context (beta) [@claudeai]

• Anthropic employee framing: “approaching Opus-class… insane jump over 4.5” [@alexalbert__]

• Independent eval org update: Sonnet 4.6 leads GDPval-AA ELO (agentic knowledge work), with much higher token use than 4.5 [@ArtificialAnlys]

• Pricing claim: “same pricing as Sonnet 4.5” [@kimmonismus]

• Post-launch “regression?” report: hallucinated function names / broken structured outputs; later “seems fixed” [@rishdotblog], [@rishdotblog]

Factual / checkable claims

• Sonnet 4.6 is described by Anthropic as a full upgrade across multiple capability areas and includes a 1M token context window in beta [@claudeai].

• Benchmark datapoints cited:

  • 79.6% SWE-Bench Verified, 58.3% ARC-AGI-2 (as posted) [@scaling01].

  • “Users preferred Sonnet 4.6 over Opus 4.5 59% of the time” [@scaling01].

  • “Sonnet 4.6 the best model on GDPval” (claim) [@scaling01].

• Artificial Analysis (independent benchmarking org) claims:

  • Sonnet 4.6 reached GDPval-AA ELO 1633 (in “adaptive thinking mode” and “max effort”), and is #1 on their GDPval-AA leaderboard but within the 95% CI of Opus 4.6 [@ArtificialAnlys].

  • Token usage to run GDPval-AA: Sonnet 4.6 used 280M total tokens (vs Sonnet 4.5 58M); Opus 4.6 used 160M in equivalent settings [@ArtificialAnlys].

  • Sonnet 4.6 improved aesthetic quality of generated docs/presentations relative to 4.5 on GDPval-AA outputs [@ArtificialAnlys].

• Tooling update: Anthropic web search/fetch tools now execute code to filter results; reported effect: +13% accuracy on BrowseComp with 32% fewer input tokens when enabled (as posted) [@alexalbert__].

Opinions / interpretations (what’s not settled)

• “Approaching Opus-class capabilities… insane jump” [@alexalbert__] is qualitative framing (though consistent with some benchmark movement).

• “Near human-level computer use” extrapolation [@alexalbert__] depends strongly on which “computer use” evals + harnesses + task distributions are used.

• “Warmer and kinder… smarter and more overcaffeinated” is pure UX vibe [@sleepinyourhat].

• “Taste is off the charts” / SVG skyline anecdote is subjective (but points to improved design/visual generation) [@scaling01].

• Post-launch reliability concerns (“hallucinations everywhere… 4.6 crapping the bed”) are anecdotal reports from a specific workflow, though notable because they compare to 4.5 on the “same tasks” [@rishdotblog].

Technical details extracted (numbers, benchmarks, systems implications)

Core model/product knobs surfaced in tweets

• Context window: 1M tokens (beta) [@claudeai].

• Pricing: “same pricing as Sonnet 4.5” [@kimmonismus] (no $/tok quoted directly in these tweets, but note RundownAI cites “Sonnet pricing [$3/$15 per mil tokens]” as context [@TheRundownAI]).

• Search/fetch tool change: pre-context filtering via executable code; +13% BrowseComp accuracy, -32% input tokens [@alexalbert__].

  • Systems read: this is an explicit shift toward tool-side “compute before context”—spending tool compute to reduce prompt budget and improve signal-to-noise in retrieved context.

Benchmarks and what they suggest (with caveats)

• SWE-Bench Verified 79.6% (posted) [@scaling01].

  • Interpretation: SWE-Bench Verified is sensitive to harness, timeouts, repo setup, and tool reliability. Still, 79.6% is “frontier-tier” in the common discourse.

• ARC-AGI-2 58.3% (posted) [@scaling01].

  • Also see longitudinal claim: “141 days… 13.6% to 60.4% on ARC-AGI-2” (Sonnet line progress, presumably 4.5→4.6 or earlier→now) [@scaling01].

• Preference eval: “preferred over Opus 4.5 59%” [@scaling01].

• GDPval-AA (Artificial Analysis): ELO 1633, #1 but statistically overlapping Opus 4.6; token usage 280M for Sonnet 4.6 vs 58M for Sonnet 4.5; cost to run GDPval-AA “just ahead of Opus 4.6” (because of token usage) [@ArtificialAnlys].

  • Important implication for engineers: “Best” may be bought with more thinking tokens, which impacts latency and spend; a router may pick 4.6 selectively.

• Vending-Bench Arena strategy claim: with 1M context, Sonnet 4.6 uses a “capacity-first then profitability pivot” plan [@felixrieseberg].

  • This is a rare example of a behavioral shift attributed to long-context planning capacity, but it’s still a single benchmark anecdote.

Cost/latency + throughput signals

• Engineers are explicitly noticing that frontier labs “blast millions of tokens… scaffold like a skyscraper” [@scaling01], aligning with Artificial Analysis’ disclosure that Sonnet 4.6 needed ~4.8× the tokens of Sonnet 4.5 on GDPval-AA [@ArtificialAnlys].

• Cursor’s note: Sonnet 4.6 better on “longer tasks” but “below Opus 4.6 for intelligence” [@cursor_ai] suggests practical routing: Sonnet 4.6 as default long-horizon workhorse; Opus as max-capability.

Different perspectives in the dataset

Strongly positive / “this is a big jump”

• Anthropic-side: “most capable Sonnet… full upgrade… 1M context” [@claudeai] and “approaching Opus-class… jump… insane” [@alexalbert__].

• Benchmark boosters: SWE-Bench/ARC-AGI-2 callouts [@scaling01], GDPval best-model claim [@scaling01], “crushes Gemini 3 and GPT-5.2 on Vending-Bench 2” [@scaling01].

• Practitioners: “beast for real-world work… computer usage” [@kimmonismus], “computer use standout… more consistent over long sessions” [@mikeyk].

Neutral / adoption & positioning notes

• “no Sonnet 5” reaction [@dejavucoder] reflects expectations management rather than capability.

• Cursor’s measured product note (better than 4.5, below Opus 4.6) [@cursor_ai].

• Artificial Analysis: #1 GDPval-AA but within CI of Opus 4.6 + disclosure that it uses more tokens [@ArtificialAnlys].

Negative / skeptical / “something broke”

• Reliability regression report: hallucinated function names in agent workflows; structured output errors; “4.5 still works great” [@rishdotblog]. Follow-up: “Whatever this was seems fixed!” [@rishdotblog].

• Cost sensitivity: “Sonnet and Slopus… munching through my credits” [@scaling01], plus later “price hurts” / cost follow-ups (not fully detailed in provided snippet) [@scaling01].

• A comparative take in infra/product terms: “50% more expensive than xhigh and 228% over 5.2 codex… vast improvement over 4.5” [@teortaxesTex]—this frames Sonnet 4.6 as improved but potentially cost-inefficient vs alternatives depending on workload.

Context: why Sonnet 4.6 matters (engineering implications)

1. Long-context is becoming “operational,” not just a spec.The launch pushes a 1M token window into the Sonnet tier [@claudeai]. But Artificial Analysis’ disclosure that Sonnet 4.6 used 280M tokens to run GDPval-AA in “adaptive thinking/max effort” configs [@ArtificialAnlys] is a reminder: long-context + long-think can silently move your budget envelope. Expect more routing, summarization, context management, and “retrieve then filter” patterns (consistent with the new search/fetch filtering improvement [@alexalbert__]).

2. Agent performance claims are increasingly harness-dependent.GDPval-AA uses an agentic harness (shell + browsing loop), and Sonnet 4.6’s lead is reported under a specific setup (“adaptive thinking mode”, “max effort”) [@ArtificialAnlys]. Cursor’s note that it’s better on longer tasks but below Opus for raw intelligence [@cursor_ai] reinforces that “best model” is not a scalar; it’s workload × harness × budget.

3. Computer use is becoming a marquee capability, and Sonnet is being pushed there.Multiple tweets highlight “computer use” progress and near-human-level framing [@alexalbert__], and deployments like Perplexity’s Comet browser agent explicitly default to Sonnet 4.6 for Pro users [@comet].

4. Release risk: small serving/config changes can look like “model regressions.”The reported post-launch hallucination spike across Opus 4.6 and Sonnet 4.6 [@rishdotblog]—and then “seems fixed” [@rishdotblog]—reads like a potential routing, toolchain, system prompt, or safety-layer change rather than weights. For teams: pin versions where possible, run canary evals, and monitor structured output validity + tool-call correctness separately from “chat quality.”

Other Topics (standard coverage)

Open models & independent benchmarking (Qwen/GLM/Seed/Aya, etc.)

• Artificial Analysis deep breakdown of Qwen3.5-397B-A17B (397B total / 17B active MoE, Apache 2.0, 262K ctx, native multimodal); big gains on agentic evals, but hallucination rate still high by their metric [@ArtificialAnlys].

• GLM-5 cited as strong open model on WeirdML and other benches (48.2% WeirdML; comparisons to Opus/gpt-* claims) [@htihle], plus GLM-5 technical report highlights: DSA adoption, async RL infra, agent RL algorithms [@Zai_org].

• ByteDance “Seed-2.0” announced (agent/reasoning/vision; “no distillation”; CN-only initially) [@TsingYoga].

• Cohere Labs launched Tiny Aya: 3.35B open multilingual model family (70+ languages; “runs on a phone”), with claims of training on 64 GPUs and a detailed report [@nickfrosst], [@_akhaliq], [@mziizm].

Agents, harnesses, memory, and long-horizon infrastructure

• “Agent World Model (AWM)” proposes fully synthetic executable environments (1,000 envs, 35,062 tools, 10,000 tasks, SQL-backed state, verification code) for RL tool-use agents [@dair_ai].

• Lossless Context Management (LCM) / Volt claims: deterministic hierarchical DAG compression with lossless pointers; on OOLONG, “beats Claude Code at every context length 32K→1M” (reported) [@dair_ai], amplified [@omarsar0].

• Moltbook multi-agent “society” study: 2.6M LLM agents, 300k posts, 1.8M comments; macro “culture” stabilizes, micro influence ~noise; critique of “just add agents” assumptions [@omarsar0].

• LangChain “Harness Engineering” theme: traces → eval mining → self-verification loops; TerminalBench positioning [@Vtrivedy10], plus LangSmith Insights scheduling [@LangChain].

• Open-sourcing an agent runtime (“Hankweave”) focused on removing context, maintainability, and reusable blocks across models [@hrishioa].

Systems & inference optimization (kernels, scheduling, throughput)

• Carmack proposes OS-like GPU job preemption via UVM paging + MPS shim, aiming for seconds-scale task switching (acknowledges thrash risk) [@ID_AA_Carmack].

• Moondream MoE kernel: 2.6% faster by tuning launch config to real routing distributions; kernel ~37% runtime [@vikhyatk].

• Together-style “ThunderAgent” / “program abstraction” for end-to-end agent workflow scheduling; claims up to 3.9× faster rollout/serving without quality tradeoff (as posted) [@ben_athi], plus explanation thread [@simran_s_arora].

Frontier product moves: Codex, Grok, “computer use” competition

• Codex usage report: users trying (and failing) to hit limits; heavy parallel agent usage within subscription windows [@theo].

• OpenAI infra hiring pitch (agent orchestration, sandboxes, observability) [@gdb].

• Grok 4.20 / 4.x discussion includes launch notices and architecture claims, plus highly polarized political framing by Elon [@kimmonismus], [@elonmusk], with critics calling performance weak vs “Flash” models [@teortaxesTex].

Robotics, video/image generation, and multimodal research

• Unitree humanoid performance discourse (claims of distributed coordination, terrain adaptation, safety spacing, multi-DOF manipulation) [@ZhihuFrontier].

• “Perceptive Humanoid Parkour” (depth-perception long-horizon traversal) [@zhenkirito123].

• ByteDance BitDance: 14B AR image generator predicting binary visual tokens; claims FID 1.24 on ImageNet 256 [@iScienceLuvr], plus author promo [@multimodalart].

• “Sphere Encoder” few-step image generation in spherical latent space; Meta/Goldstein thread with details including 65K latent dims for ImageNet and <5-step refinement [@tomgoldsteincs].

AI Reddit Recap

/r/LocalLlama + /r/localLLM Recap

1. Qwen3.5 Model Release and Performance

• Qwen3.5-397B-A17B is out!! (Activity: 1088): Qwen3.5-397B-A17B has been released on Hugging Face, featuring a 397 billion parameter model with a native context length of 262,144 tokens, which can be extended up to 1,010,000 tokens. This model is part of the Qwen series, known for its large-scale language capabilities. Additionally, a GGUF version is available here, which may offer optimized performance for specific use cases. There is anticipation and curiosity in the community about the model’s performance, with users eager to test its capabilities.

  • The Qwen3.5-397B-A17B model boasts a significant improvement in decoding throughput, being 3.5x to 7.2x faster than its predecessor, Qwen3-235B-A22B. This suggests substantial enhancements in efficiency, which could be crucial for applications requiring rapid processing of large datasets.

  • The model supports a native context length of 262,144 tokens, which can be extended up to 1,010,000 tokens. This extensibility is particularly beneficial for tasks that require handling extensive sequences of data, offering flexibility and scalability in various computational scenarios.

  • A user has shared a link to the GGUF version of the model on Hugging Face, indicating the availability of different formats for deployment. This could be useful for developers looking to integrate the model into diverse environments or optimize it for specific hardware configurations.

• Qwen3.5-397B-A17B Unsloth GGUFs (Activity: 716): The image highlights the release of Qwen3.5, a 397 billion parameter multimodal reasoning model by Alibaba. It is designed to perform on par with models like Gemini 3 Pro, Claude Opus 4.5, and GPT-5.2 across various benchmarks such as IFBench, GPOA Diamond, and BFLC V4. The model supports advanced features like 256K context and is suitable for applications in coding, vision, and chat. The release includes support for running the model in 3-bit on a 192GB RAM Mac or 4-bit (MXFP4) on an M3 Ultra with 256GB RAM. The image and accompanying links provide resources for accessing and running the model, including dynamic GGUFs from Unsloth. The comments express excitement about the model’s size and capabilities, with one user noting the impressive 397B parameters and another appreciating the zero-day release.

  • The discussion highlights the verbosity of the Qwen3.5-397B-A17B model, which appears to overanalyze simple inputs like ‘hi’ by generating an extensive internal thought process before producing a response. This verbosity could be indicative of the model’s complexity and its attempt to simulate a human-like thought process, but it may also suggest inefficiencies in handling straightforward tasks.

  • A technical inquiry is raised about the performance comparison between two quantization formats, UD-Q4_K_XL and MXFP4. The commenter notes the lack of benchmarks directly comparing these formats, which are crucial for understanding their relative efficiency and effectiveness in model deployment scenarios. This highlights a gap in available performance data that could inform decisions on model optimization and deployment.

  • The comment by Ok_Brain_2376 points out that only 17 billion parameters are active in the Qwen3.5-397B-A17B model, suggesting a potential use of parameter-efficient techniques like AutoRound. This could imply that the model is designed to activate only a subset of its parameters for certain tasks, optimizing computational resources while maintaining performance.

• Qwen3.5 is released! (Activity: 113): Alibaba has released Qwen3.5, a 397B MoE (Mixture of Experts) vision reasoning LLM, which is highlighted in the image. The model is compared against others like Gemini 3 Pro and GPT-5.2 across benchmarks such as instruction following, multilingual knowledge, and video reasoning. The image emphasizes Qwen3.5’s capabilities in coding, vision, and agent interaction, and provides technical details for running the model, though specific hardware requirements like VRAM are not detailed in the image. Commenters are curious about the hardware requirements, specifically VRAM, needed to run Qwen3.5, and are discussing equivalent setups to Apple’s 512 M3 Ultra configuration.

  • A user inquired about the VRAM requirements for running Qwen3.5, which is crucial for determining the feasibility of running the model on different hardware setups. This is a common concern for users with limited resources, as large models typically require significant VRAM to operate efficiently.

  • Another user asked about a non-Mac setup equivalent to the 512 M3 Ultra configuration. This suggests a need for understanding the hardware specifications and performance benchmarks of the M3 Ultra to find comparable alternatives in the PC ecosystem, particularly for those interested in high-performance computing tasks.

  • A user expressed interest in running Qwen3.5 on a setup with 2 x RTX 3090 Ti GPUs, indicating the high computational demand of the model. The RTX 3090 Ti is known for its substantial VRAM and processing power, yet the user anticipates needing to wait for a more optimized version to run on their hardware, highlighting the model’s intensive resource requirements.

2. AI Model Benchmarking and Performance

• I gave 12 LLMs $2,000 and a food truck. Only 4 survived. (Activity: 829): The image is a line graph illustrating the performance of 12 language models (LLMs) in a simulated business environment where each model was given $2,000 and a food truck to manage over 30 days. The graph shows that only four models survived the simulation, with Claude Opus 4.6 achieving the highest net worth of $49K, followed by GPT-5.2 with $28K. The simulation revealed that models taking loans were more likely to go bankrupt, as all eight models that took loans failed. The experiment highlights the decision-making capabilities of different LLMs in a controlled business scenario, with a notable finding that Gemini 3 Flash Thinking consistently got stuck in an infinite decision loop. One commenter suggested using a logarithmic scale for the y-axis to better represent the data, especially since going to $0 ends the benchmark. Another noted that Opus performed exceptionally well, suggesting it might have been optimized for such tasks.

  • HeadlessNicholas suggests using a logarithmic scale for the y-axis in the benchmark results to better visualize the data, especially since reaching $0 ends the benchmark. This implies that the current linear scale might not effectively represent the performance differences among the models, particularly when some models fail early.

  • DinoAmino references the ‘Vending-Bench’ and notes that Opus performs exceptionally well in both scenarios, suggesting a consistent superiority in decision-making tasks. The mention of the arXiv paper implies that there is documented evidence of Opus’s capabilities, which could be useful for further technical analysis.

  • DarthLoki79 questions the novelty of the benchmark by comparing it to the ‘vending bench’, implying that the methodology or outcomes might not be significantly different. This raises a point about the need for clarity in how this benchmark distinguishes itself from previous ones, potentially in terms of parameters or evaluation criteria.

• Qwen 3.5 goes bankrupt on Vending-Bench 2 (Activity: 836): The image presents a graph from a simulation called “Vending-Bench 2,” which evaluates the financial performance of various AI models over a period of 350 days. The graph shows that the model “Qwen 3.5 Plus” performed poorly, maintaining a balance near zero, indicating it went bankrupt. In contrast, “Claude Opus 4.6” demonstrated a strong upward trend, achieving the highest financial balance among the models tested. Other models like “GLM-5” and “Gemini 3 Flash” also showed positive growth, but not as significantly as Claude Opus 4.6. This suggests that Claude Opus 4.6 may have superior capabilities or strategies in this simulation context. One comment criticizes the use of similar colors in the chart, which may make it difficult to distinguish between the models. Another comment humorously suggests that Qwen 3.5 could operate as a non-profit organization due to its poor financial performance.

  • Chromix_ provides a detailed analysis of the Vending-Bench 2 results, noting that the chart displays the average balance in dollars across five runs. They mention that Qwen3.5 Plus is not included in the chart because it hasn’t been added to the official results page yet. The benchmark link is provided for further details: Vending-Bench 2.

  • SkylarNox raises a question about the versions of Qwen 3.5, specifically asking for clarification on the size difference between Qwen 3.5 Plus and the 397B version. This indicates a need for more transparency or documentation regarding the specifications and capabilities of different model versions.

• Difference Between QWEN 3 Max-Thinking and QWEN 3.5 on a Spatial Reasoning Benchmark (MineBench) (Activity: 399): The post discusses the significant improvement of QWEN 3.5 over QWEN 3 Max-Thinking on the spatial reasoning benchmark, MineBench. QWEN 3.5’s performance is noted to be competitive with leading models like Opus 4.6, GPT-5.2, and Gemini 3 Pro. The benchmark results, available on GitHub, show QWEN 3.5 ranked 6th, while QWEN 3 Max is 19th, indicating a substantial performance gap. The model’s architecture is described as a hybrid linear-linear-linear-full attention model, with some issues in token prediction and language drift noted. Commenters highlight the robustness of QWEN 3.5, despite some issues with token prediction and language drift. There is confusion about the differences between the Plus and open-source versions of QWEN, with speculation that Plus includes extended context and tool calling features.

  • NandaVegg highlights that Qwen 3.5, including its Vision-Language (VL) capabilities, is notable for its hybrid linear-linear-linear-full attention model architecture. Despite some issues, such as occasional instruction ignoring and language drift, it is competitive with leading models in robustness. However, it may not be ideal for agentic tasks due to the lack of post-training mini-CoT adjustments common in agentic-maximized models.

  • Chromix_ provides a performance comparison from the MineBench leaderboard, noting that Qwen 3.5 ranks 6th, positioned between Gemini 3 Pro and GLM 5, while Qwen 3 Max is 19th, between Kimi K2 and GPT-4o. This indicates a significant performance gap between Qwen 3.5 and Qwen 3 Max, although Qwen 3.5’s results are still subject to change due to limited votes.

  • NandaVegg also mentions confusion regarding the “Plus” and open-source versions of Qwen models, noting that testing on Alibaba Cloud did not clarify the differences. The “Plus” version is assumed to be open-source with extended context to 1 million tokens and default tool calling enabled, including a search function on Alibaba Cloud.

3. Local AI Development and Optimization

• [macOS] Built a 100% local, open-sourced, dictation app. Seeking beta testers for feedback! (Activity: 101): SpeakType is a new open-source dictation app for macOS that operates entirely offline, ensuring user privacy by processing all data locally. It aims to provide high-quality speech-to-text conversion without the recurring costs associated with cloud-based services. The app is currently in beta, seeking feedback on performance across different Mac hardware and accents, and is available for free during this phase. The project is hosted on GitHub and more details can be found on tryspeaktype.com. Commenters are curious about the app’s RAM requirements and how it compares to similar tools like Handy, questioning whether SpeakType includes additional logic or features. There is also interest in whether the app uses a Voice Activity Detector (VAD) to process audio before passing it to the Whisper model.

  • JohnHawley inquires about the differences between SpeakType and another dictation app, Handy, questioning if SpeakType includes additional logic not present in Handy. This suggests a comparison of feature sets and possibly performance or accuracy differences between the two applications.

  • rusty_daggar asks whether the app uses a Voice Activity Detector (VAD) to clean up audio before processing or if it sends all audio directly to the Whisper model. This question highlights interest in the app’s audio preprocessing techniques, which can significantly impact performance and accuracy.

• The Mac Studio vs NVIDIA Dilemma – Best of Both Worlds? (Activity: 93): The user is considering two options for running local LLMs and training models: a Mac Studio with up to 192GB of unified memory, which allows running large models without VRAM constraints but lacks CUDA optimization and raw compute power; and an NVIDIA GPU setup, which offers superior performance and CUDA optimization but is limited by 32GB VRAM even on high-end GPUs like the 5090. The user seeks a solution that combines the memory capacity of Mac with NVIDIA’s computational power, which currently doesn’t exist in a single system. One commenter suggests that the use of models is more critical than training, emphasizing that inferencing is the primary use case, and recommends checking out vmlx.net for Mac users. Another suggests renting high-performance GPUs like B200 or H100x8 on platforms like RunPod for training, while using Mac’s memory for inference of models like Qwen and MiniMax. A third commenter notes that commercial APIs like Claude Max and ChatGPT Pro can be cost-effective alternatives to local hardware for building codes.

• I’m an Android dev who knows nothing about x86. During my vacation I built a system that genetically evolves machine code — now I can run 80B models on a single RTX 4090. (Activity: 70): An Android developer utilized AI to create a system called Genesis that evolves x86 machine code, enabling the execution of 80B models on a single RTX 4090. The system uses an evolutionary approach to optimize AVX-512 kernels, achieving a 165x speedup over traditional CPU methods like bitsandbytes, and allowing for efficient hybrid inference by minimizing data transfer between CPU and GPU. The project is open source, with the kernel code available on GitHub, but the evolutionary engine remains private. The approach demonstrates that AI-driven code evolution can surpass human-optimized code, achieving up to 19.25% improvement over hand-tuned baselines. Some commenters expressed skepticism, likening the post to ‘delusional mad scientist fanfic,’ while others appreciated the technical depth, noting the inclusion of a detailed test suite in the shared code.

Less Technical AI Subreddit Recap

1. Claude Sonnet 4.6 Release and Benchmarks

• Sonnet 4.6 released !! (Activity: 1384): The image announces the release of Claude Sonnet 4.6, highlighting it as the most advanced version yet with significant improvements in areas such as coding, computer use, long-context reasoning, agent planning, knowledge work, and design. Notably, it features a 1 million token context window in beta, which is a substantial enhancement for handling extensive data inputs. This release positions Sonnet 4.6 as a competitive model in the AI landscape, potentially surpassing other models like Grok in certain capabilities. One comment humorously suggests that Grok has been outperformed by Sonnet 4.6, indicating a competitive edge in the AI model space. Another comment provides a practical example of Sonnet 4.6’s reasoning capabilities, demonstrating its ability to offer logical advice on everyday decisions, such as whether to walk or drive a short distance.

  • The release of Sonnet 4.6 has sparked discussions about its practical advice capabilities, as demonstrated by its response to a simple query about whether to walk or drive 40 meters. The model suggests walking due to factors like time efficiency, fuel savings, and health benefits, highlighting its ability to provide contextually relevant and practical advice.

  • There is a comparison between Sonnet 4.6 and other models like Grok, with some users humorously suggesting that Sonnet 4.6 has outperformed or ‘claudemogged’ Grok. This reflects ongoing debates in the AI community about the relative performance and capabilities of different language models.

  • The timing of Sonnet 4.6’s release is noted as strategic, potentially diverting attention from controversies surrounding other AI models, such as those associated with Elon Musk. This suggests a competitive landscape where release timing can influence public and professional perception.

• This is Claude Sonnet 4.6: our most capable Sonnet model yet. (Activity: 1245): Claude Sonnet 4.6 is a significant upgrade in the Sonnet series, enhancing capabilities in coding, computer use, long-context reasoning, agent planning, knowledge work, and design. It introduces a 1M token context window in beta, which is a notable feature for handling extensive data inputs. The model shows improved performance across various benchmarks, nearing Opus-level intelligence but at a more accessible price point, making it suitable for a broader range of applications. It demonstrates human-level proficiency in complex computer tasks, such as navigating spreadsheets and completing multi-step web forms. The model is now available across all plans, including Cowork, Claude Code, and major cloud platforms, with the free tier also upgraded to Sonnet 4.6. More details can be found on Anthropic’s website. One commenter noted the model’s rollout was initially confusing due to legacy model displays. Another expressed curiosity about the impact on creative writing, while a third inquired about the availability of the 1M context feature in both the API and the website.

  • FriendlyTask4587 inquires about the context length of the Sonnet 4.6 model, asking if the 1 million token context is available both in the API and on the website, similar to the Opus model. This suggests a focus on the model’s ability to handle large inputs, which is crucial for tasks requiring extensive context retention.

  • nanolucas questions the differentiation between Sonnet and Opus models, specifically if cost is the only factor for choosing Sonnet over Opus. This implies a need for understanding the performance or feature differences between the two models, such as efficiency, speed, or specific use-case advantages that Sonnet might have over Opus.

  • Stupefied_Gaming notes an observation during the rollout of Sonnet 4.6, where the model was initially labeled as a legacy model. This could indicate a transitional phase in deployment or a temporary mislabeling, which might affect user perception or usage during the initial release period.

• Claude Sonnet 4.6 just dropped, and the benchmarks are impressive (Activity: 785): Claude Sonnet 4.6 has been released, showcasing significant advancements in AI capabilities, including approaching Opus-level intelligence at a reduced cost. Key features include human-level computer use for tasks like navigating spreadsheets and multi-step forms, and an enhanced long-context reasoning ability with a 1M token context window. The model has shown strong performance in complex automation workflows, multi-step reasoning tasks, and knowledge-intensive applications, and is now available across all platforms, including API, Claude Code, and Cowork, as the default free tier model. A notable debate centers on the cost-performance ratio, with some users pointing out that the performance difference between Opus 4.6 and GPT-5.2 is minimal, yet the latter is significantly cheaper. There is also discussion about the practical availability of the 1M context length feature, with some users expressing difficulty in accessing it.

  • cowwoc highlights a critical issue in the AI model market: the performance gap between Opus 4.6 and GPT-5.2 is minimal, yet GPT-5.2 is significantly cheaper, costing 10x less. This cost-performance imbalance could drive users away from Anthropic’s offerings unless they adjust their pricing or enhance their models’ capabilities.

  • SatoshiNotMe points out a recurring issue with the promised ‘1M context length’ feature in beta, which seems elusive to users like Max20. This suggests potential communication or implementation gaps in delivering this feature to end-users, which could affect user satisfaction and trust.

  • joyfulsparrow compares Claude and Codex, noting that Codex offers seemingly unlimited token usage, whereas Claude’s token limit is quickly reached, even on a $20 plan. This limitation, coupled with Codex’s potential superiority in handling ‘agentic loop’ tasks, suggests that Codex might be a more efficient choice for users with heavy usage demands.

• Claude Sonnet 4.6 is live in Cline v3.64.0 and it’s free until Feb 18. (Activity: 21): Anthropic has released Sonnet 4.6 in Cline v3.64.0, available for free until February 18. This update features improved speed, enhanced context provision during task execution, and effective library integration. Notably, the model excels in utilizing subagents for parallel tasks, offering a 1M token context window to handle entire codebases in a single request. In testing, ~70% of developers preferred Sonnet 4.6 over its predecessor, with 59% favoring it over Opus 4.5, citing reduced overengineering and fewer hallucinations. Post-free period, pricing remains at $3/$15 per MTok. Source. A user expressed renewed interest in using Cline, indicating positive reception of the update.

2. Grok 4.20 and Elon Musk Controversy

• The newly released Grok 4.20 uses Elon Musk as its primary source (Activity: 2383): The image is a meme that humorously critiques the AI model Grok 4.20, suggesting it uses Elon Musk as a primary source for its responses, particularly on topics like gender pronouns. The conversation depicted in the image highlights a controversial stance on pronoun usage, attributed to Musk, emphasizing a focus on ‘biological reality.’ This reflects broader discussions about AI bias and the influence of prominent figures on AI training data. One comment highlights skepticism about the AI’s alignment with Musk’s views, noting it took multiple interactions to confirm this bias. Another comment criticizes the broader implications of Musk’s influence, touching on environmental and ethical concerns.

• Grok 4.20 is just four Grok 4.1 agents (Activity: 699): The image humorously suggests that the Grok 4.20 model is essentially composed of four instances of the Grok 4.1 model, as indicated by the model name and ID ‘grok-4-1-thinking-1129’ in the log entry. This implies a potential lack of significant advancement or change in the model architecture, despite the new version number. The title and comments playfully critique this by likening it to a common trope of disguising something as more than it is, such as ‘four agents in a trenchcoat.’ One comment suggests that the company, possibly x.ai, might be experiencing operational issues, including delays in releasing Grok 4.20 and employee departures, which could impact the model’s development.

  • Brilliant-Weekend-68 highlights potential operational issues at x.ai, noting delays in the release of Grok 4.20 and significant employee departures. This suggests possible internal challenges that could impact the company’s ability to innovate and compete effectively in the AI space.

  • Glittering-Neck-2505 draws a parallel between xAI’s current struggles and Meta’s decline post-Llama 3 405b, suggesting that xAI’s initial promise has not been realized. This comparison implies that xAI may face similar challenges in maintaining momentum and delivering on expectations.

  • The discussion reflects skepticism about xAI’s strategic direction, with Glittering-Neck-2505 expressing relief that Grok 4.20 might not gain traction due to its perceived missteps, indicating a broader industry sentiment that xAI’s branding and execution may not resonate well with the technical community.

3. Qwen 3.5 Model Launch and Comparisons

• Qwen3.5-397B-A17B <Release> (Activity: 302): Qwen3.5-397B-A17B is a new model featuring 397 billion total parameters with 17 billion active parameters, offering a native context length of 262k tokens, extendable to 1 million. It supports over 200 languages and employs a hybrid architecture combining Gated Delta Networks with Sparse Mixture of Experts (MoE) for enhanced speed. The model excels in true multimodality, performing well in GUI interaction, video comprehension, and agentic workflows. More details can be found on Qwen’s blog, Hugging Face, and GitHub. Commenters are surprised by the model’s 397 billion parameters, questioning the VRAM requirements for running such a model. There is also curiosity about the software used for the model’s GUI interactions, particularly in Excel, and whether it is publicly available or proprietary to the Qwen team.

  • Efficient_Cattle_958 highlights the unexpected scale of the Qwen3.5-397B model, which features a massive 397 billion parameters. This scale is significant as it suggests a substantial increase in computational power and potential capabilities compared to smaller models, which typically range from billions to tens of billions of parameters.

  • Sirius_Sec_ inquires about the VRAM requirements for running such a large model. Typically, models of this size require substantial VRAM, often in the range of hundreds of gigabytes, depending on optimizations like model parallelism or quantization techniques that might be employed to make them more accessible on consumer-grade hardware.

  • nunodonato asks about the software environment used to run the model, particularly in a demonstration involving Excel. This raises questions about whether the software is proprietary to the Qwen team or if it is available for public use, which could impact accessibility for developers and researchers interested in leveraging the model’s capabilities.

• Alibaba just open-sourced a model that rivals GPT-5.2 (Activity: 140): Alibaba has open-sourced a new language model, Qwen 3.5, which is positioned as a competitor to OpenAI’s GPT-5.2, Claude 4.5 Opus, and Gemini-3 Pro. The model’s performance is reportedly comparable to these leading models, marking a significant milestone in open-weight releases. The release underscores Alibaba’s commitment to advancing AI technology and contributing to the open-source community. For more technical details, refer to the original article. Commenters are curious about the usage limits on the public website and express interest in a smaller, local version of the model, suggesting that while the large model is impressive, a more accessible version would be beneficial for broader use.

  • A user expressed skepticism about the performance claims of Chinese models like MiniMax, GLM-5, and Kimi-k2.5, comparing them to models like OPUS. They noted that after using 500M tokens on GLM 4.7, GLM 5, and MiniMax m2.1, these models required significantly more steering and additional context compared to Codex or Opus, and also highlighted a noticeable speed difference.

  • Another user discussed the desire for a smaller version of the model to run locally, acknowledging the practicality of releasing a large model first. This reflects a common interest in balancing model size and performance with the feasibility of local deployment, which is often a challenge with large-scale models.

  • There is anticipation for future releases, such as Qwen code 3.5 400b, indicating a community interest in the evolution and scaling of these models. This suggests a focus on both the capabilities of current models and the potential improvements in upcoming versions.

• Qwen-3.5 is here (Activity: 31): Alibaba has released the first open-weight model in the Qwen-3.5 series, named Qwen3.5-397B-A17B. This model is part of the ongoing development in the Qwen series, which is known for its large-scale language models. The release is significant as it provides open access to the model weights, allowing for broader experimentation and application in various domains. The announcement was made on Alibaba’s official X account. A notable comment questions the practicality of running such a large model, hinting at the computational resources required. Another comment suggests that the model will be accessible through an app and web app, indicating potential ease of use for end-users.

AI Discord Recap

1. Claude Sonnet 4.6 + Frontier Model Rollouts

• Sonnet 4.6 Goes on Tour, Steals the Coding Crown: Claude Sonnet 4.6 shipped broadly and showed up in multiple surfaces: it landed in LMSYS Arena Text/Vision/Code (and Code Arena), became available to Perplexity Pro and Max subscribers, and got covered in Anthropic’s release note “Claude Sonnet 4.6”.

  • Cursor users echoed the upgrade notes from Anthropic—“Users even preferred Sonnet 4.6 to Opus 4.5...”—and Latent Space circulated benchmark claims from the same announcement (e.g., 79.6% SWE-bench, 59.1% Terminal-Bench 2.0, and 1M-token context in beta) while Arena published first impressions in Peter Gostev’s YouTube video.

• Qwen 3.5 and GLM-5 Crash the Party (with Receipts): The qwen3.5-397b-a17b model joined Arena’s new-model feed on Text/Vision/Code, and Hugging Face users highlighted a local GGUF option: unsloth/Qwen3.5-397B-A17B-GGUF.

  • Meanwhile, Nous Research discussed the GLM-5 technical report (arXiv:2602.15763) alongside a demo YouTube video showcasing GLM 5, and Windsurf announced availability via tweet: “GLM-5 and Minimax M2.5 hit Windsurf!”.

• Model Access Whiplash: Limits, Tokens, and Pulling the Turbo: Moonshot users reported Kimi K2 Turbo disappearing from Kimi-Coding, triggering subscription backlash (“...they remove it?!?”), while OpenClaw users hit Kimi 2.5 weekly usage ceilings (one claimed 95% in two days) and discussed switching providers via OpenRouter models.

  • Perplexity users similarly complained about product-tier constraints—Deep Research allegedly dropping from 300/month to 20/month—and LMArena users probed ways around a 24-hour video cap but got pushback that the limit is intentional (i.e., don’t try to bypass it).

2. OpenClaw Agent Systems: Power, Cost, and Risk

• OAuth, Bans, and the Agent That Touched the Forbidden API: OpenClaw users debated whether running Claude via OpenClaw violates Anthropic ToS, with reports of bans and the claim that “Using OAuth for unauthorized 3rd party software is considered reverse engineering their networks, and a violation of the Terms of Service.”

  • The same security anxiety echoed elsewhere: Unsloth and Yannick Kilcher communities flagged the risk of giving an LLM read+write access (API key leaks, prompt injection, even “rm -rf /”), with OpenClaw’s general approach discussed alongside a demo video on YouTube.

• Make the Harness Less ‘Bloated Slop’ (and Cheaper): OpenClaw engineers questioned the system’s architectural complexity and token usage, arguing “The harness needs to be built on lightweight sophistication, not bloated slop” and proposing tactics like heartbeat checks in sub-agents to cut chatter.

  • Showcase builders reported concrete savings from “agentic context engineering” and memory work: ~30% token reduction on an OpenRouter→opus-4.6 setup and 50+% reduction when using the OpenClaw Browser Relay, framing cost as the primary bottleneck vs. local hardware.

• The OpenClaw Ecosystem Ships: Recipes, CRM Skills, and a Fallback Brain: A community member open-sourced an OpenClaw “agency server” toolkit after “north of 200 hours” of work, publishing JIGGAI/ClawRecipes for project management/task distribution and daily tracking of ecosystem events (including ProductHunt finds).

  • Hugging Face also surfaced Microclaw (v2026.2.17) as a distilled fallback agent for OpenClaw—microclaw-for-openclaw-version-2026.2.17 README—while others showed “OpenClaw as CRM” via the Nex skill (nex-crm/nex-as-a-skill + nex-crm/clawgent).

3. Infra & Security Reality Check (401s, Panics, and Key Leaks)

• 401 Apocalypse Now: Routers Down, Scripts Cry: OpenRouter suffered a major incident causing widespread 401 errors across API surfaces, tracked on OpenRouter Status with the team spinning up a “war room” and later announcing a fix in the OpenRouter announcements thread.

  • Perplexity API users separately reported scripts failing with 401 despite credits, and the best guidance was basic key validation + escalation to api@perplexity.ai, underscoring how auth failures cascade across automation stacks.

• Inference Endpoints ‘Service Panicked’ (So Users Rebuilt Prod): Hugging Face Inference Endpoint users hit Error 500 and “Service panicked” even while Hugging Face Status looked green, and at least one team fixed it by recreating the endpoint and migrating production traffic.

  • Members suspected the instability might correlate with new CPU autoscaling, which is exactly the kind of “silent platform change” that makes endpoint recreation a pragmatic (if painful) incident playbook.

• API Keys: Gitignored, Still Toasted: An OpenRouter user reported an API key leak that burned $10 in ~20 minutes via “Cloud Code,” despite the key living in a gitignored file and OpenRouter requiring email verification for login.

  • In parallel, OpenClaw + Unsloth discussions highlighted agentic systems as an exfiltration risk multiplier (tools + read/write permissions + prompt injection), making secret-scanning, least-privilege, and runtime key isolation non-optional.

4. Performance Engineering: Kernels, Quantization Paths, and Fast Toolchains

• 350→368 TFLOPS: The Matmul Gym Bro Era Continues: GPU MODE members iterated on persistent-kernel matmul work (350 TFLOPS baseline) in theCudaBender/matmul_V3 and traded concrete tuning ideas like async stores and smem→rmem pipelining, citing Cutlass references such as dense_gemm.py.

  • They also emphasized measurement hygiene: use Nsight Compute for qualitative metrics on a single kernel and CUDA Events for real timing, because Nsight’s replay can inflate durations when you profile too much at once.

• FlashInfer Baseline Drops a 5.74× Speedup (and FP8 Weirdness): A GPU MODE participant reported a 5.74× speedup on the MoE track using flashinfer-ai/mlsys26-agent-baseline (evolve agent, total_steps=100, pool_size=6, evaluated on B200) with Claude Opus 4.6.

  • Follow-up questions targeted whether high max_relative_error/max_absolute_error is expected for FP8 kernels (even when marked correct) and asked about final-eval details like Triton version and workload weighting—classic “fast now, will it pass the judge?” anxiety.

• FP4 Isn’t One Thing: MXFP4 Wants Blackwell (Ampere Gets the Slow Lane): Unsloth users clarified that MXFP4 is designed for Blackwell (RTX 50 series) and can run slower on Ampere (RTX 30 series) due to emulation, because the fast path needs native FP4 tensor cores (compute capability ≥ 12.00).

  • Modular’s MAX channel echoed the datatype reality: NVFP4 is the current focus and MXFP4 support is “lagging,” but the types exist in base Mojo and may follow once NVFP4 is solid (MAX customized Mojo kernels announcement).

5. Benchmarks, Evals, and Agent Protocol Plumbing

• Benchmarks Get Audited: ‘Every Eval Ever’ and Cybench’s Flag Fumble: The EvalEval Coalition launched the benchmark standardization effort “Every Eval Ever”, with Eleuther members comparing it to the Brain Imaging Data Structure (BIDS) standardization push.

  • Nous Research also highlighted how Cybench overestimated performance by using non-randomized CTF flags and saw success rates drop after randomization (Cybench site), a reminder that “benchmark design bugs” can dwarf model deltas.

• KV Cache Goes on a Diet: 160GB → 136MB: Eleuther shared CoDA-GQA-L (bounded-memory attention) claiming KV cache reduction from 160GB to 136MB, described in a Zenodo paper “CoDA-GQA-L” with code at anthony-maio/CoDA-GQA-L.

  • The mechanism (as summarized in-channel) uses 384 slots/layer split across a recent window (256 exact tokens), a landmark bank (64 novelty-filtered tokens), and a summary bank (64 EMA prototypes), making it directly relevant to long-context agent stacks where KV dominates cost.

• MCP Grows Up: Resources Spec Cleanup and Paying Tools: MCP contributors debated monetization primitives via SEP modelcontextprotocol PR #2007 to let servers request payment (starting with X402) so agents can pay for tools under guardrails.

  • In parallel, the community pushed for clarity in resources semantics with a spec tidy-up PR modelcontextprotocol PR #2093, especially around the ambiguity of whether resource/read returns a single resource vs. a collection of children.