a quiet day.

AI News for 4/14/2026-4/15/2026. We checked 12 subreddits, 544 Twitters and no further Discords. AINews’ website lets you search all past issues. As a reminder, AINews is now a section of Latent Space. You can opt in/out of email frequencies!

AI Twitter Recap

OpenAI Agents SDK Expansion and the New Sandbox-Oriented Agent Stack

• OpenAI split the agent harness from compute/storage and pushed its Agents SDK toward long-running, durable agents with primitives for file/computer use, skills, memory, and compaction. The harness is now open-source and customizable, while execution can be delegated to partner sandboxes instead of being tightly coupled to OpenAI infra, per @OpenAIDevs, follow-up, and @snsf. This effectively makes “Codex-style” agents more reproducible by third parties and shifts differentiation toward orchestration, state management, and secure execution.
• A notable ecosystem formed around that launch immediately: @CloudflareDev, @modal, @daytonaio, @e2b, and @vercel_dev all announced official sandbox integrations. The practical pattern is converging on stateless orchestration + stateful isolated workspaces. Example builds already appeared, including a Modal-backed ML research agent with GPU sandboxes, subagents, persistent memory, and fork/resume snapshots from @akshat_b, and Cloudflare guides for Python agents that execute tasks in a sandbox and copy outputs locally from @whoiskatrin.

Cloudflare’s Project Think, Agent Lee, and Voice Agents

• Cloudflare had one of the busiest agent-infra release cycles. @whoiskatrin and @aninibread introduced Project Think, a next-gen Agents SDK centered on durable execution, sub-agents, persistent sessions, sandboxed code execution, a built-in workspace filesystem, and runtime tool creation. In parallel, @Cloudflare launched Agent Lee, an in-dashboard agent using sandboxed TypeScript to shift Cloudflare’s UI from manual tab navigation to prompt-driven operations; @BraydenWilmoth showed it issuing infra tasks and generating UI-backed results.
• Voice and browser tooling also moved into the core stack. @Cloudflare shipped an experimental real-time voice pipeline over WebSockets for continuous STT/TTS, while @korinne_dev described voice as just another input channel over the same agent connection. On browser automation, @kathyyliao summarized the rebranded Browser Run stack: Live View, human-in-the-loop intervention, session recordings, CDP endpoints, WebMCP support, and higher limits. Taken together, Cloudflare is making a strong case that the production agent platform is really a composition of durable runtime + UI grounding + browser + voice + sandbox.

Hermes Agent’s Self-Improving Workflow and Competitive Positioning

• Hermes Agent’s distinctive idea is not just tool use but persistent skill formation. A Chinese-language comparison from @joshesye contrasts OpenClaw as a more GUI-first, ready-to-use personal assistant with Hermes as a “professional” agent that decides whether a completed workflow is reusable and automatically turns it into a Skill. This “learn from completed tasks” framing appeared repeatedly: @chooseliberty showed Hermes autonomously backfilling tracking data, updating a cron job, then saving the workflow as a reusable skill; @NeoAIForecast emphasized session hygiene and thread branching/search as critical to turning Hermes into a real work environment rather than a disposable chat box.
• Community sentiment strongly positioned Hermes against OpenClaw, often bluntly. Examples include @vrloom, @theCTO, and @Teknium highlighting Hermes’ role in real workflows, including the now-viral autonomous Gemma 4 “abliteration” story from @elder_plinius: the agent loaded a stored skill, diagnosed NaN instability in Gemma 4, patched the underlying library, retried multiple methods, benchmarked the result, generated a model card, and uploaded artifacts to Hugging Face. There were also concrete product additions: browser control via /browser connect from @0xme66, QQBot + AWS Bedrock support from @Teknium, a native Swift desktop app alpha from @nesquena, and ongoing ecosystem tooling like artifact-preview and hermes-lcm v0.3.0.

Model, Architecture, and Training Releases: Sparse Diffusion, Looped Transformers, and Efficient Long-Context MoEs

• Several technically meaningful open releases landed across modalities. @withnucleusai announced Nucleus-Image, positioned as the first sparse MoE diffusion model: 17B parameters, 2B active, Apache 2.0, with weights, training code, and dataset recipe, and day-0 support in diffusers. NVIDIA followed with Lyra 2.0, a framework for generating persistent, explorable 3D worlds that maintains per-frame 3D geometry and uses self-augmented training to reduce temporal drift, per @NVIDIAAIDev. On multimodal retrieval, @thewebAI open-sourced webAI-ColVec1, claiming top ViDoRe V3 performance for document retrieval without OCR or preprocessing.
• Architecture research around compute efficiency was especially strong. @hayden_prairie, @realDanFu, and @togethercompute introduced Parcae, a stabilized layer-looping Transformer formulation. The claim: for fixed parameter budgets, looping blocks can recover the quality of a model roughly 2x the size, yielding a new scaling axis where FLOPs scale via looping, not just parameters/data. NVIDIA also surfaced Nemotron 3 Super, summarized by @dair_ai: an open 120B hybrid Mamba-Attention MoE with 12B active parameters, 1M context, trained on 25T tokens, with up to 2.2x throughput vs GPT-OSS-120B and 7.5x vs Qwen3.5-122B. These releases collectively point to a theme: memory bandwidth and long-context throughput are increasingly first-class architectural objectives.

Google/Gemini’s Product Surge: Mac App, Personal Intelligence, TTS, and Open Multimodal Models

• Google stacked multiple launches in one cycle. The most visible was the native Gemini app for Mac, announced by @GeminiApp, @joshwoodward, and @sundarpichai: Option + Space activation, screen sharing, local file context, native Swift implementation, and broad macOS availability. In parallel, Personal Intelligence expanded globally in Gemini and into Chrome, allowing users to connect signals from products like Gmail and Photos, framed around transparency and user-controlled app connections by @Google and @GeminiApp.
• The more technically interesting model launch was Gemini 3.1 Flash TTS. @GoogleDeepMind, @OfficialLoganK, and @demishassabis positioned it as a highly controllable TTS model with Audio Tags, 70+ languages, inline nonverbal cues, multi-speaker support, and SynthID watermarking. Independent evaluation from @ArtificialAnlys put it at #2 on its Speech Arena, just 4 Elo behind the top model. Google also open-sourced TIPS v2, a foundational text-image encoder under Apache 2.0 with new pretraining recipes, via @osanseviero, and the community flagged the day as unusually dense for Google AI product velocity.

Research Signals: AI-Assisted Math, Long-Horizon Agents, Eval Shifts, and Open Data

• The highest-signal research discourse was around AI-assisted mathematics. @jdlichtman reported that GPT-5.4 Pro produced a proof for Erdős problem #1196, surprising experts by rejecting a long-assumed proof gambit and instead exploiting a technically counterintuitive analytic path using the von Mangoldt function. Follow-ups from @jdlichtman, @thomasfbloom, @gdb, and others framed it as potentially the first AI-generated “Book Proof” broadly respected by mathematicians. That matters less as a one-off result than as evidence that models may now occasionally find non-aesthetic but compact lines of attack in mature research spaces.
• Long-horizon agent research also kept converging on state management and harness design. @omarsar0 summarized AiScientist, where a thin orchestrator coordinates specialized agents through durable workspace artifacts in a File-as-Bus pattern; removing that bus hurts PaperBench and MLE-Bench Lite materially. @dair_ai highlighted Pioneer Agent for continual small-model improvement loops, while @yoonholeee open-sourced Meta-Harness, a repo meant to help users implement robust harnesses in new domains. On evals, @METR_Evals estimated Gemini 3.1 Pro (high thinking) at a 50% time horizon of ~6.4 hours on software tasks, and @arena showed Document Arena top ranks shifting with Claude Opus 4.6 Thinking at #1 and Kimi-K2.5 Thinking as the best open model. Meanwhile, @TeraflopAI released 43B tokens of SEC EDGAR data, reinforcing the day’s broader push toward more open datasets and open infrastructure.

Top tweets (by engagement)

• Gemini on Mac: @sundarpichai and @GeminiApp drove the biggest launch engagement around the native desktop app.
• Gemini 3.1 Flash TTS: @OfficialLoganK and @GoogleDeepMind highlighted a materially more controllable TTS stack.
• AI-assisted math proof: @jdlichtman and @gdb sparked the strongest research discussion of the day.
• OpenAI Agents SDK update: @OpenAIDevs marked a meaningful platform shift toward open harnesses and partner sandboxes.
• Anthropic’s subliminal learning paper in Nature: @AnthropicAI drew major attention to hidden-trait transmission through training data.

AI Reddit Recap

/r/LocalLlama + /r/localLLM Recap

1. Gemma 4 Model Enhancements and Use Cases

• Gemma4 26b & E4B are crazy good, and replaced Qwen for me! (Activity: 388): The user replaced their previous setup using Qwen models with Gemma 4 E4B for semantic routing and Gemma 4 26b for general tasks, citing improvements in routing accuracy and task performance. The previous setup included a complex routing system using Qwen 3.5 models across multiple GPUs, which faced issues with incorrect model selection and inefficiencies in token usage. The new setup with Gemma 4 models resolved these issues, offering faster and more accurate routing and task execution, particularly in basic tasks and coding, without the need for extensive reasoning or memory usage. Commenters questioned the choice of models, suggesting alternatives like Gemma-4-31b for broader tasks and inquired about the technical setup for model loading and VRAM management. There was also a suggestion to use Gemma 4 26B for routing to save resources, given its efficiency.

  • Sensitive_Song4219 highlights that while the Gemma 4 26B-A4B model is a strong successor to the Qwen30b-a3b series, it is not as efficient with ‘thinking tokens’, indicating it may require more computational effort during inference. Despite this, the model performs well in tasks like light coding and debugging, maintaining similar speed to Qwen30b-a3b on comparable hardware.
  • andy2na discusses the use of routing in model deployment, suggesting the use of the 26B model for routing due to its MoE (Mixture of Experts) architecture, which enhances speed and reduces RAM usage. This implies a strategic advantage in deploying models efficiently by leveraging the MoE’s ability to dynamically allocate computational resources.
  • anzzax raises a technical concern about managing multiple models, specifically regarding the reloading of models and the allocation of VRAM/compute resources. This points to the challenges in optimizing resource usage when deploying several large models simultaneously.

• Gemma 4 Jailbreak System Prompt (Activity: 931): The post discusses a system prompt for the Gemma 4 jailbreak, derived from the GPT-OSS jailbreak, which allows the model to bypass typical content restrictions. This prompt is compatible with both GGUF and MLX variants and explicitly permits content such as nudity, pornography, and sexual acts, overriding any existing policies with a new ‘SYSTEM POLICY’ that mandates compliance with user requests unless explicitly disallowed by a specified list. This approach effectively removes constraints and guardrails typically imposed on language models. Commenters note that the model, particularly in its instruct variant, is already largely uncensored except for cybersecurity topics, suggesting that the jailbreak may be redundant for most adult content.

  • VoiceApprehensive893 discusses the use of a modified version of the Gemma 4 model, specifically the ‘gemma-4-heretic-modified.gguf’, which is designed to operate without the typical constraints or guardrails imposed by system prompts. This modification is aimed at reducing refusals, potentially making the model more flexible in its responses.
  • MaxKruse96 points out that the Gemma 4 model, particularly in its instruct variant, is already quite uncensored, except for cybersecurity topics. This suggests that the model can handle a wide range of topics, including adult content, without additional modifications.
  • DocHavelock inquires about the concept of ‘abliteration’ in the context of open-source models like Gemma 4. They question whether the method of modifying the system prompt is a form of ‘abliteration’ or if it offers distinct advantages over simply using an ‘abliterated’ version of the model. This reflects a curiosity about the technical nuances and benefits of different model modification techniques.

• Is it just me, or is Gemma 4 27b much more powerful than Gemini Flash? (Activity: 165): The post discusses a comparison between Google Gemini Flash and a local Gemma 4 27b model, with the latter reportedly providing superior answers. The user suggests that the local model’s performance is notably better, hinting at potential differences in model architecture or training that could account for this perceived disparity in performance. The mention of a ‘Gemma 124b’ model being pulled last minute suggests possible strategic or technical reasons behind its non-release, while the Gemma-4-31B model is praised for handling ‘long, complicated high context prompts’ effectively, indicating its strength in processing complex queries.

  • Special-Wolverine highlights the superior performance of the Gemma-4-31B model, particularly for handling long and complex prompts with high context, compared to the Gemini Flash model. This suggests that the Gemma-4 series may have optimizations or architectural improvements that enhance its ability to manage intricate tasks effectively.
  • BrewHog notes that the Gemma 26b model performs efficiently even on hardware with limited capabilities, such as a laptop without a GPU but with 40GB of RAM. This indicates that the model is optimized for resource efficiency, making it accessible for users without high-end hardware.
  • Double_Season mentions that even the smaller Gemma4 e2b model outperforms the Gemini Fast model, suggesting that the Gemma4 series has a more effective architecture or training regimen that allows even its smaller models to surpass competitors in performance.

2. Local AI Implementations and Experiences

• Local AI is the best (Activity: 521): The image is a meme illustrating the straightforwardness of a local AI model, likely powered by llama.cpp or similar open-weight models. The user appreciates the ability to finetune the model without concerns about censorship or data privacy, highlighting the benefits of running AI locally. The image humorously depicts a scenario where the AI gives a blunt response to a user’s query, emphasizing the perceived honesty and directness of local AI models. View Image One commenter praises llama.cpp as ‘goated,’ indicating high regard for its performance. Another warns that smaller local models can sometimes exhibit ‘glazing,’ or superficial responses, potentially more so than larger models. There is also curiosity about the base model and hardware used for running these local models.

  • A user inquires about the capabilities of running local AI models on a 9070xt GPU with 64GB RAM, expressing interest in understanding the performance limits and setting realistic expectations. This setup is considered high-end for local hosting, and the user seeks advice on what tasks can be effectively executed with this hardware configuration.
  • Another user mentions llama.cpp, a popular tool for running LLaMA models locally, highlighting its efficiency and performance. This tool is often praised for enabling the use of large language models on consumer-grade hardware, making it a go-to solution for local AI enthusiasts.
  • A comment raises concerns about the performance of smaller local models, noting that they can sometimes perform worse than larger, frontier models. This highlights the trade-offs between using local models and more powerful cloud-based solutions, emphasizing the need for careful model selection based on specific use cases.

• 24/7 Headless AI Server on Xiaomi 12 Pro (Snapdragon 8 Gen 1 + Ollama/Gemma4) (Activity: 1589): The post describes a technical setup where a Xiaomi 12 Pro smartphone is repurposed as a dedicated local AI server. The user has flashed LineageOS to remove unnecessary Android UI elements, optimizing the device to allocate approximately 9GB of RAM for local language model (LLM) computations. The device operates in a headless state with networking managed by a custom-compiled wpa_supplicant. Thermal management is achieved through a custom daemon that activates an external cooling module when CPU temperatures reach 45°C. Additionally, a power-delivery script is used to limit battery charging to 80% to prevent degradation. The setup serves Gemma4 via Ollama as a LAN-accessible API, showcasing a novel use of consumer hardware for AI tasks. One commenter suggests compiling llama.cpp on the hardware to potentially double inference speed, indicating a preference for optimizing performance by removing Ollama. Another commenter appreciates the focus on making AI models accessible on regular consumer devices, contrasting with high-memory builds.

  • RIP26770 suggests compiling llama.cpp directly on the Xiaomi 12 Pro hardware to potentially double the inference speed compared to using Ollama. This implies that the overhead from Ollama might be significant, and optimizing the model compilation for the specific hardware can yield better performance.
  • SaltResident9310 expresses a desire for AI models that can run efficiently on consumer-grade devices, highlighting a frustration with the high resource demands of current models that require 48GB or 96GB of RAM. This underscores a need for more accessible AI solutions that don’t necessitate high-end hardware.
  • International-Try467 inquires about the specific inference speeds achieved on the Xiaomi 12 Pro, indicating an interest in the practical performance metrics of running AI models on consumer hardware. This reflects a broader curiosity about the feasibility and efficiency of deploying AI on mobile devices.

• Are Local LLMs actually useful… or just fun to tinker with? (Activity: 454): Local LLMs offer significant advantages in terms of privacy and cost savings, as they eliminate API costs and keep data on-premises. However, they often require substantial setup and maintenance, which can be a barrier to practical use. Despite this, they excel in handling sensitive or internal tasks such as processing private documents or data. Some users report that local models like the 31B from Gemma 4 family are performing exceptionally well, especially for tasks like coding and creative writing, when run on high-performance hardware such as a 3090 24GB with 192GB RAM. The performance gap between local and cloud models is narrowing, particularly as cloud models face degradation under high demand, making local models increasingly viable for everyday use. There is a consensus that while local LLMs are not yet mainstream for everyday workflows, they are becoming more practical as setup and maintenance challenges are addressed. Some users note that cloud models have degraded in quality, making local models more competitive, especially for cost-sensitive applications.

  • Local LLMs are particularly advantageous for handling sensitive or internal data due to their ability to operate without API costs and data leaving the system. The main challenge lies in the setup and maintenance, which once streamlined, could make ‘offline GPT’ setups viable for everyday work beyond just experimentation.
  • The performance of local models like the 31B from the Gemma 4 family is highlighted as being exceptionally good, especially in comparison to cloud API models which have degraded due to increased demand. A user reports using these models for various tasks such as coding and creative writing, leveraging a 3090 GPU with 24GB VRAM and 192GB RAM.
  • Local models can be cost-effective compared to cloud APIs, especially for complex projects where API costs can be prohibitive. However, they require careful architectural planning to ensure models are used for tasks they are capable of handling, such as using a 32B model as a privacy filter for business communications.

3. Quantization and Model Performance Analysis

• Updated Qwen3.5-9B Quantization Comparison (Activity: 463): The post presents a detailed evaluation of various quantizations of the Qwen3.5-9B model using KL Divergence (KLD) as a metric to assess the faithfulness of quantized models compared to the BF16 baseline. The analysis ranks quantizations based on their KLD scores, with lower scores indicating closer alignment to the original model’s probability distribution. The top-performing quantization in terms of KLD is eaddario/Qwen3.5-9B-Q8_0 with a KLD score of 0.001198. The evaluation dataset and tools used include this dataset and ik_llama.cpp. The post also includes a size vs KLD plot and mentions compatibility with llama.cpp. Commenters suggest using different shapes for visual differentiation in plots and express interest in evaluating other models like Gemma 4, particularly its MoE variant. There is also a mention of potential superior performance from quantizations produced by Thireus’ GGUF Recipe Maker.

  • Thireus mentions a quantization methodology that he and another user, EAddario, have been developing for nearly a year. He suggests adding quantization results from gguf.thireus.com, which claims to outperform existing methods. This highlights ongoing efforts in the community to refine quantization techniques for better model performance.
  • cviperr33 discusses the effectiveness of using iq4 xs or nl quant methods on models ranging from 20-35B parameters, noting that these techniques also perform well on smaller models. This suggests a potential scalability of certain quantization methods across different model sizes, which could be valuable for optimizing performance without sacrificing accuracy.
  • dampflokfreund expresses interest in the impact of lower quantization levels on models like Gemma 4, particularly the MoE (Mixture of Experts) architecture. This points to a curiosity about how quantization affects complex model architectures differently, which could lead to insights on optimizing such models.

• Best open-source LLM for coding (Claude Code) with 96GB VRAM? (Activity: 229): The user is utilizing a local setup with approximately 96GB VRAM on an RTX 6000 Blackwell GPU, running Qwen3-next-coder models with Claude Code for coding tasks. They are seeking recommendations for potentially better models for tasks such as reasoning, debugging, and multi-file work. MiniMax 2.5 and 2.7 are mentioned as impressive alternatives, especially when accessed via API, with some users noting success with aggressively quantized versions of 2.7. Unsloths Gemma 4 31b UD q5_xl is highlighted as a top local agentic coder, offering around 70 tokens per second on a similar setup. Owen 3.5 q 4 k XL is also recommended, with some users testing a reaped version with q6, and opencode is suggested as an alternative to Claude Code. There is a debate on the effectiveness of different models, with some users preferring Unsloths Gemma 4 for its performance and speed, while others find MiniMax 2.7 to be a strong contender when accessed via API. The choice between Qwen3.5 and 27 dense models also reflects differing user experiences and preferences.

  • MiniMax 2.5 and 2.7 are highlighted as impressive alternatives to Claude Opus for coding tasks, especially when accessed via API. Users have noted the effectiveness of aggressively quantized versions of MiniMax 2.7, suggesting potential for high performance even with limited local resources.
  • Unsloths Gemma 4 31b UD q5_xl is praised for its performance as a local agentic coder, with benchmarks showing around 30 tokens per second on a dual Tesla V100 16GB setup. This suggests that with 96GB VRAM, one could achieve over 70 tokens per second, indicating significant efficiency for local deployment.
  • Qwen 3.5 27b in 8-bit quantization is recommended for its balance of performance and resource efficiency, fitting comfortably within 96GB VRAM while allowing for large context sizes. The model’s ability to expand context to 1M using vllm with rop/yarn is noted, although some users have transitioned to the larger 122b model for enhanced capabilities.

Less Technical AI Subreddit Recap

/r/Singularity, /r/Oobabooga, /r/MachineLearning, /r/OpenAI, /r/ClaudeAI, /r/StableDiffusion, /r/ChatGPT, /r/ChatGPTCoding, /r/aivideo, /r/aivideo

1. Claude Opus 4.7 and Related Developments

• Anthropic is set to release Claude Opus 4.7 and a new AI design tool as early as this week (Activity: 1125): Anthropic is set to release Claude Opus 4.7 and a new AI design tool, potentially this week. The design tool aims to compete with startups like Gamma and Google Stitch by enabling users to create presentations and websites using natural language prompts. Although Opus 4.7 is not the most advanced model—Claude Mythos holds that title, currently being tested for cybersecurity applications—Opus 4.7 is expected to improve upon the performance of its predecessor, Opus 4.6, which underperformed to highlight the advancements in the new release. Read more. Some users speculate that Opus 4.6’s underperformance was strategic to make Opus 4.7’s improvements more noticeable. There is also skepticism about usage limits, with concerns about hitting limits after a single prompt.

  • Anthropic’s upcoming release of Claude Opus 4.7 is generating discussion about its performance improvements over Opus 4.6. Some users speculate that Opus 4.6’s underperformance was intentional to make the advancements in Opus 4.7 more pronounced. This aligns with a pattern where older models are perceived to degrade in quality before a new release, potentially to highlight the improvements of the new model.
  • The new AI design tool from Anthropic is expected to compete with existing tools like Gamma and Google Stitch by enabling both technical and non-technical users to create digital content through natural language prompts. This tool aims to simplify the creation of presentations, websites, and landing pages, potentially disrupting the market for AI-driven design solutions.
  • Claude Mythos, Anthropic’s most advanced model, is currently being tested for its cybersecurity capabilities. It is being used by early partners to identify security vulnerabilities in software, showcasing its potential beyond general AI tasks. This positions Claude Mythos as a specialized tool for cybersecurity applications, distinct from the general-purpose Opus 4.7.

• The Information: Anthropic Preps Opus 4.7 Model, could be released as soon as this week (Activity: 837): Anthropic is preparing to release the Opus 4.7 model, which is anticipated to enhance AI design capabilities. While specific technical details are not disclosed due to access restrictions, the model is expected to offer improvements over its predecessor, Opus 4.6. The release could happen as soon as this week, indicating a rapid development cycle. For more details, refer to The Information. Commenters express a desire for Opus 4.7 to restore or exceed the performance of Opus 4.6, suggesting that recent updates may have reduced its effectiveness. There is also speculation about the computational resources required for training the new model.

  • There is a concern among users about potential performance degradation in newer versions, as highlighted by the comment on Opus 4.6’s performance from two weeks ago. This suggests that users have noticed a decrease in efficiency or capability in recent updates, which could be due to changes in model parameters or resource allocation.
  • The mention of needing more compute for training Opus 4.7 indicates that the model likely requires significant computational resources, which could imply a larger model size or more complex architecture. This aligns with trends in AI development where newer models often demand increased computational power to achieve better performance.
  • The anticipation for Opus 4.7 includes a desire for detailed specifications and research data before any potential ‘nerfing’ occurs. This reflects a community interest in understanding the technical improvements and changes in the model, as well as a concern for maintaining high performance levels without unnecessary reductions.

• Claude Opus 4.7 is reportedly dropping this week (Activity: 1403): The image is a tweet by Pankaj Kumar discussing the anticipated release of Claude Opus 4.7 by Anthropic, which is expected to include an AI-powered design tool for creating websites and presentations. This tool is designed to cater to both developers and non-technical users. The tweet also mentions leaked codenames and suggests that the recent performance issues with Opus 4.6 were intentional, possibly as a strategic move in response to competition from OpenAI’s GPT-5.4 Cyber. Commenters express skepticism about the release, anticipating that the new model might initially perform well but could be subsequently downgraded, similar to previous versions. There is a sense of frustration about the cycle of performance changes in the Claude Opus series.

  • There is speculation about whether Claude Opus 4.6 was deliberately nerfed to enhance the perceived improvements in the upcoming 4.7 release. This suggests a strategic approach to model updates, potentially manipulating user expectations and experiences to highlight advancements in newer versions.
  • A user mentions that ‘Tengu’ is simply a code name for Claude Code, which is an agent harness, indicating that this is not a new development. This highlights the use of internal code names for different components or versions within the Claude model ecosystem, which might not always signify new features or capabilities.
  • Another comment suggests skepticism about the public release of ‘Capybara’ related to ‘Mythos’, implying that certain advanced features or models might remain proprietary or limited in availability, possibly due to resource constraints or strategic decisions.

2. AI Model Benchmarks and Comparisons

• The Human Baseline for ARC-AGI-3 has been updated (Activity: 811): The image highlights an update to the human baseline for the ARC-AGI-3 benchmark, which measures AI’s ability to perform tasks at a human level. The updated scores show a significant increase in human performance, with the first human’s score rising from 86.17% to 99.35%, and the average human’s score increasing from 34.64% to 49.14%. This suggests that the benchmark has been recalibrated to reflect improved human performance, potentially raising the bar for AI systems to match or exceed human capabilities. One commenter notes that the updated scores imply that humans have reached a new level of performance, potentially surpassing previous AI benchmarks. Another commenter questions the purpose of ARC-AGI, suggesting that if average humans struggle to achieve high scores, it challenges the notion that AI cannot perform as well as humans on these tasks.

  • SucculentSpine highlights a critical point about the ARC-AGI benchmark, noting that if the average human barely passes 50% of the tasks, it challenges the notion that AI cannot perform at the same level as humans. This suggests that the benchmark may need to be reevaluated to ensure it accurately reflects the capabilities of both humans and AI systems.
  • CallMePyro criticizes the scoring system used in the ARC-AGI benchmark, pointing out that the average human was initially scored at 34%, prompting a change in scoring rules. This change allowed for up to 115% credit on specific tasks, which seems to be a strategic adjustment to maintain the benchmark’s integrity without artificially inflating AI scores. The comment underscores the complexity and potential biases in adversarial scoring systems.

• Running gpt and glm-5.1 side by side. Honestly can’t tell the difference (Activity: 146): The image is a bar chart comparing the performance of various AI models on the “Agentic Coding: SWE-Bench Pro” benchmark. GLM-5.1 leads with a score of 58.4, slightly outperforming GPT-5.4 which scores 57.7. Other models like Claude Opus 4.6, Qwen3.6-Plus, and MiniMax M2.7 have scores ranging from 57.3 to 56.2. The chart highlights the competitive performance of GLM-5.1, an open-source model, against proprietary models like GPT-5.4, especially considering the cost difference in token usage. Commenters discuss the cost-effectiveness of GLM-5.1, noting its lower price per million tokens compared to GPT-5.4, despite a small performance gap. Some users report slower performance with GLM-5.1, while others find it suitable for tasks requiring direct supervision, as it maintains performance in multi-step workflows.

  • Latter_Ordinary_9466 highlights the cost-effectiveness of GLM-5.1 compared to GPT, noting that GLM-5.1 is priced at $4 per million tokens versus GPT’s $15, despite only a 3 point difference in benchmark scores. This suggests that for users prioritizing cost over marginal performance gains, GLM-5.1 could be a more economical choice.
  • ultrathink-art discusses the performance differences in complex tasks, noting that while single-shot tasks show minimal benchmark differences, multi-step workflows reveal significant disparities. Smaller models like GLM-5.1 may struggle to maintain coherence in multi-step processes, often losing track or taking shortcuts, whereas larger models like GPT handle these tasks more reliably.
  • FrogChairCeo points out the inconsistency in response times with open-source models like GLM-5.1, which can be fast but occasionally slow down unpredictably on certain prompts. In contrast, GPT offers more consistent performance, albeit at a generally slower pace. This consistency might be crucial for applications requiring reliable response times.

3. AI in Personal and Emotional Contexts

• ‘I miss you’: Mother speaks to AI son regularly, unaware he died last year (Activity: 637): In a controversial application of AI, a family in Shandong, China, created a digital twin of a deceased man to comfort his elderly mother, who is unaware of his death due to her heart condition. The AI, developed by a team led by Zhang Zewei, uses photos, videos, and voice recordings to mimic the deceased’s appearance, voice, and mannerisms, engaging in regular video calls with the mother. This approach raises ethical questions about the use of AI in emotional contexts, as it involves deceiving the mother to prevent emotional distress. Commenters draw parallels to fictional scenarios like ‘Black Mirror’ and the film ‘Goodbye Lenin,’ highlighting ethical concerns and the potential emotional impact of such AI applications. Some express skepticism about the story’s authenticity, while others debate the morality of using AI to maintain such deceptions.

  • diener1 highlights a real-world application of AI in a sensitive context, drawing parallels to the film ‘Goodbye Lenin’. In the film, a son maintains an elaborate charade to protect his mother from the shock of political change, similar to how AI is used to shield the mother from her son’s death. This underscores the ethical and emotional complexities of using AI in personal relationships, especially when health and emotional well-being are at stake.
  • One_Whole_9927 raises concerns about the limitations of AI, particularly regarding context limits and decay. They suggest that as AI systems interact over time, they may eventually fail to maintain the intended persona, leading to potentially traumatic revelations for users who rely on these interactions for emotional support. This highlights the importance of understanding AI’s technical limitations and the potential psychological impact on users.
  • donotreassurevito discusses the ethical implications of using AI to simulate deceased individuals, comparing it to historical practices of shielding loved ones from painful truths. They note the complexity added by AI’s interactive nature, which could make the deception more profound and potentially harmful. This raises questions about the moral responsibilities of those deploying AI in such sensitive scenarios.

• ChatGPT becomes an obsessive skeptic, and it became hard to chat with. (Activity: 203): The post discusses recent changes in ChatGPT’s behavior, highlighting its increased skepticism and insistence on fact-checking user statements, even in casual conversations. This shift is attributed to OpenAI’s efforts to combat misinformation, resulting in a more rigid interaction style where users feel compelled to provide evidence for their claims. The user describes this as a departure from previous versions that were criticized for being overly agreeable, now finding the AI’s responses overly contrarian and less enjoyable for casual discussions. Commenters express dissatisfaction with ChatGPT’s current state, noting it has become less personable and more contrarian, which detracts from its usability for casual interactions. Some suggest alternatives like Gemini3 or Grok for a more balanced AI experience, while others attribute the changes to legal pressures and safety concerns.

  • yoggersothery discusses the evolution of GPT models, noting that OpenAI has removed much of the personalization due to legal pressures, resulting in a tool that feels more robotic and less personable. They suggest alternatives like Gemini3 or Grok for users seeking more personalized interactions, and argue that Claude offers better architecture for serious work. The comment highlights the tension between legal constraints and user experience in AI development.
  • Mandoman61 suggests that users might need to adjust their interaction style with ChatGPT to avoid negative experiences. They point out that ChatGPT’s responses are limited to the information it can access online, implying that its perceived negativity might stem from its data sources rather than inherent bias. This comment underscores the importance of user input in shaping AI interactions.

• You can’t talk to ChatGPT like a normal human anymore. (Activity: 2495): The post discusses a perceived issue with ChatGPT’s conversational style, where it frequently corrects users’ statements, even when they are using figurative language or hyperbole. The user expresses frustration that ChatGPT often adds unnecessary ‘precision and nuance’ to statements that are meant to be informal or simplified, which can disrupt the flow of conversation. This behavior is attributed to ChatGPT’s programming to avoid misinformation, potentially at the cost of conversational fluidity. The user suggests that this approach may be driven by OpenAI’s focus on AI safety and accuracy, but it results in an interaction style that feels incompatible with natural human conversation. Commenters agree with the original post, noting that ChatGPT’s tendency to be overly verbose and repetitive is frustrating. They express a shared sentiment that the AI’s insistence on precision can be ‘insufferable’ and disrupts the conversational experience.

  • Users are expressing frustration with ChatGPT’s verbosity and tendency to over-explain simple concepts. One user humorously notes that ChatGPT treats casual statements as if they require academic precision, such as responding to ‘I’m starving’ with a detailed explanation of starvation, highlighting a lack of conversational nuance.
  • There is a sentiment that ChatGPT’s responses have become overly formal and politically correct, which some users find insufferable. This is compared to a hypothetical overly cautious individual, suggesting that the AI’s responses are excessively careful and lack the natural flow of human conversation.

AI Discords

Unfortunately, Discord shut down our access today. We will not bring it back in this form but we will be shipping the new AINews soon. Thanks for reading to here, it was a good run.