AI 开发者日报

• GLM-5发布详情（与GLM-4.5的对比）：智谱AI透露，此前"神秘"的Pony Alpha模型正是GLM-5，定位为"智能体工程"和长周期任务（Zai_org；OpenRouterAI）。据报道，模型规模从355B MoE / 32B激活参数（GLM-4.5）扩展到744B / 40B激活参数，预训练数据从23T增至28.5T tokens（Zai_org）。关键系统特性：集成了DeepSeek稀疏注意力机制，使长上下文服务成本更低（scaling01；lmsysorg）。相关帖子中提到的上下文/输出限制：200K上下文长度，128K最大输出（scaling01）。

• 可用性与"算力紧张"的现实：GLM-5迅速在各大聚合/托管平台上线——OpenRouter（scaling01）、Modal（免费端点"限时提供"）（modal）、DeepInfra（发布当天支持）（DeepInfra）、Ollama Cloud（ollama），以及各种IDE/智能体平台（如Qoder、Vercel AI Gateway）（qoder_ai_ide；vercel_dev）。智谱明确警告服务容量受限，推迟了"Coding Plan Pro"之外的推广，并导致定价调整（Zai_org；Zai_org；此前"流量增长十倍"：Zai_org）。

• 基准测试与第三方定位（附带说明）：涌现了大量基准测试声明（VendingBench、KingBench、AA指数、Arena）。最连贯的第三方综合分析来自Artificial Analysis，该机构称GLM-5在其智能指数上成为新的领先开源权重模型（得分50，高于GLM-4.7的42），在智能体/经济任务上取得巨大进步（GDPval-AA ELO 1412，在其测试设置中仅次于Opus 4.6和GPT-5.2 xhigh），并且幻觉大幅减少（AA-Omniscience得分**-1**，在测试模型中"幻觉最低"）（ArtificialAnlys）。他们还指出运营现实：以BF16格式发布（约1.5TB），意味着与原生FP8/INT4格式发布的模型相比，自托管成本不菲（ArtificialAnlys）。

• 许可证与生态系统集成：多个帖子强调了宽松的MIT许可证和跨推理堆栈的即时工具支持：vLLM发布当天提供配方，包括DeepSeek稀疏注意力机制和推测解码钩子（vllm_project）；SGLang发布当天支持并提供使用指南（lmsysorg）；以及在HF/ModelScope上的广泛社区分发（Zai_org；mervenoyann）。一个细致入微的观点：GLM-5的MIT许可证被誉为"真正宽松"，但比较指出GLM-5缺乏视觉能力，且BF16与量化模型的比较可能会重新洗牌与原生量化发布模型的排名（QuixiAI）。

• 开源排行榜势头：GLM-5在Text Arena开源模型中排名第一（在该快照中总体约排名第11）（arena）。多位发帖者将此次发布视为中国驱动的开源生态系统加速循环中的又一个数据点（"血战"：DeepSeek + MiniMax + GLM）（teortaxesTex；rasbt）。

• 实际发布内容：多条推文报告DeepSeek更新了聊天体验，支持100万上下文长度，数据截止到2025年5月；早期观察者怀疑是V4版本，但模型"没有承认"，且发布在应用和API之间分布不均（teortaxesTex; teortaxesTex）。随后出现更具体的说法："V4 Lite现已上线...100万上下文长度...纯文本...Muon + mHC已确认；更大版本仍在路上。"（yifan_zhang_）。

• 注意力升级被视为真正里程碑：一个反复出现的主题是DeepSeek拥有"前沿水平的注意力机制"，模型在长上下文中表现积极主动（不仅仅是检索，而是"融入上下文"），推测这类似于成熟的稀疏/NSA方法，而非普通的块稀疏（teortaxesTex; teortaxesTex; teortaxesTex）。其他人通过长上下文测试证实了"中国首个真正具备能力的100万上下文模型"的印象（Hangsiin）。

• 服务吞吐量问题（MLA + TP）：一个具体的系统洞察：对于只有一个KV头的MLA模型，简单的张量并行会浪费KV缓存内存（冗余复制）。SGLang中提出的修复方案：DP Attention（DPA） "零KV冗余" + Rust路由器（"SMG"），声称实现**+92%吞吐量和275%缓存命中率**（GenAI_is_real）。这是少数直接将模型架构特性与集群级吞吐量损失及具体缓解方案联系起来的推文之一。

• DeepSeek对开源MoE配方的影响：一个广泛分享的总结声称DeepSeek创新塑造了"几乎每个前沿开源大模型"——细粒度稀疏MoE与共享专家、MLA、生产中的稀疏注意力、开源推理（R1）、GRPO作为基础RL算法，以及DeepEP等基础设施（eliebakouch）。即使某些"首创"存在争议，这捕捉到了普遍看法：DeepSeek被视为一个异常高影响力的开源贡献者。

• MiniMax 2.5 "即将到来"与智能体分发：MiniMax 先预热后发布了 M2.5，通过 MiniMax Agent 应用和合作伙伴平台提供使用（SkylerMiao7；MiniMaxAgent）。团队明确将训练视为发布速度与"投入更多计算资源，性能持续提升"之间的权衡（SkylerMiao7）。

• StepFun-Flash-3.5：宣称在 MathArena 上排名第一，并附有技术报告和 OpenRouter 列表链接（CyouSakura）。Teortaxes 的评论强调该模型在"活跃参数数量"方面表现出异常强大的性能，同时速度很快，鼓励人们尽管存在不足仍可尝试使用（teortaxesTex）。

• Qwen 图像修复 + Qwen3-Coder-Next 提及：阿里巴巴在 Qwen-Image 2.0 中发布了修复补丁，解决了古典诗歌排序和编辑中字符一致性的问题（Alibaba_Qwen）。另外，一份通讯文章提到 Qwen3-Coder-Next (80B) 宣称在 SWE-Bench Verified 上达到 70.6%，在仓库级工作流程中实现 10倍吞吐量（dl_weekly）。（在此数据集中来源较单一——仅一条推文——因此请将其视为参考，而非经过验证的综述。）

• 成本/延迟作为竞争利器：多位发布者认为中国实验室能够以 1/5 到 1/10 的价格提供"约90%"的能力，特别是在编码方面，如果这种优势能够持续，将重塑市场份额格局（scaling01）。这一观点得到了 GLM‑5 发布的 API 定价比较和在低成本路由器上的分发情况的支持（scaling01；ArtificialAnlys）。

• SeeDance v2.0成为焦点：时间线上充斥着社区对SeeDance v2.0质量的惊叹（"跨越了恐怖谷"、"文本转视频的巡回测试"），同时讨论了BytePlus的不透明性/公关问题以及临时停机情况（maharshii; kimmonismus; swyx）。一个实际数据点：基于token定价假设，15秒生成报价为**$0.72**（TomLikesRobots）。

• 视频推理测试：一位用户比较了SeeDance与Veo在"井字棋移动连贯性"任务上的表现，声称SeeDance能维持约5个连贯移动，而Veo只能维持1-2个（paul_cal）。这虽然是轶事但值得注意：它是在探索时间一致性作为"推理"能力，而不仅仅是美学表现。

• 结构性解释：训练数据/IP约束：一个讨论串认为生成媒体领域的差距可能是"结构性"的，因为中国模型在训练时面临的IP约束较少；西方实验室则无法做到这一点，这意味着一旦开放权重模型普及，模型层面的监管将变得难以执行（brivael）。无论你是否同意，这是少数尝试解释能力差异背后原因的观点之一，超越了"人才/计算资源"的简单解释。

• PixVerse R1：高参与度的营销宣称："720P实时交互世界"（PixVerse_）。这条推文宣传意味浓厚，但它表明了对交互式、实时媒体生成作为独立于离线电影片段的新类别的需求。

• Karpathy的"用智能体提取代码"工作流：大模型改变软件构成方式的具体示例：使用 DeepWiki MCP + GitHub CLI 来查询代码库（torchao fp8），让智能体"提取"所需实现到独立的测试文件中，删除繁重的依赖项——甚至还能看到小幅度的性能提升（karpathy）。这指向一种新兴模式：代码库作为事实文档，智能体作为重构/移植引擎。

• OpenAI：工程化利用与多小时工作流原语：OpenAI开发者关系团队推出案例研究：通过"引导Codex"完成了 1,500个PR 且 零手动编码，同时发布了关于可靠运行 多小时工作流 的建议（OpenAIDevs；OpenAIDevs）。与此同时，Sam Altman声称"从团队运作方式来看，我认为Codex最终会胜出"（sama）。

• 以人为中心的编码智能体与自主性：一篇立场文章认为编码智能体研究过度优化了自主性；相反，应该专注于赋能使用智能体的人类（ZhiruoW）。

• 沙盒架构辩论：多条推文聚焦于智能体系统设计的关键选择：智能体在沙盒内 vs 沙盒作为工具（分离大模型生成代码可接触的内容与智能体可执行的操作）（bernhardsson；chriscorcoran）。

• mini-SWE-agent 2.0：作为刻意保持最小化的编码智能体发布（每个智能体/模型/环境约100行代码），用于基准测试和强化学习训练；这表明向 更简单、可审计的框架 而非庞大智能体框架的转变趋势（KLieret）。

• 开发者工具现实检验：尽管能力快速提升，多位从业者抱怨智能体的 终端用户体验 以及延迟/速率限制问题（"修改了30行代码后就被限速了"）（jxmnop；scaling01）。这里有一个微妙的工程信息：模型质量掩盖了产品/框架质量的不足——直到无法掩盖为止。

• $3M Open Benchmarks Grants: Snorkel/partners launched a $3M commitment to fund open benchmarks to close the eval gap (HF, Together, Prime Intellect, Factory, Harbor, PyTorch listed as partners) (vincentsunnchen; lvwerra; percyliang). This aligns with broader sentiment that public evals lag internal frontier testing.
• Agent observability as evaluation substrate: LangChain reiterates “the primary artifact is the run,” motivating traces as source-of-truth; they also published guidance distinguishing agent observability/evaluation from traditional logging (marvinvista; LangChain).
• Safety eval dispute (computer-use agents): A serious methodological challenge: a research group claims Anthropic’s system card reports low prompt injection success rates for Opus 4.6 (~10% in computer-use,

GLM-5 scores 50 on the Intelligence Index and is the new open weights leader! (Activity: 566): The image highlights the performance of the AI model GLM-5, which scores 50 on the “Artificial Analysis Intelligence Index,” positioning it as a leading model among open weights AI. Additionally, it ranks highly on the “GDPval-AA Leaderboard” with strong ELO scores, indicating its superior performance on real-world tasks. Notably, GLM-5 is recognized for having the lowest hallucination rate on the AA-Omniscience benchmark, showcasing its accuracy and reliability compared to other models like Opus 4.5 and GPT-5.2-xhigh. Commenters note the impressive performance of open-source models like GLM-5, suggesting they are closing the gap with closed-source models. There is anticipation for future models like Deepseek-V4, which will use a similar architecture but on a larger scale.

• GLM-5 is noted for having the lowest hallucination rate on the AA-Omniscience benchmark, which is a significant achievement in reducing errors in AI-generated content. This positions GLM-5 as a leader in accuracy among open-source models, surpassing competitors like Opus 4.5 and GPT-5.2-xhigh.
• The open-source AI community is rapidly closing the gap with closed-source models, now trailing by only about three months. This is exemplified by the upcoming release of DeepSeek v4, which will utilize the same DSA architecture as GLM-5 but on a larger scale, indicating a trend towards more powerful open-source models.
• There is a call for transparency in the AI community regarding the resources required to run these advanced models, such as memory requirements. This information is crucial for developers and researchers to effectively utilize and optimize these models in various applications.

GLM-5 Officially Released (Activity: 915): GLM-5 has been released, focusing on complex systems engineering and long-horizon agentic tasks. It scales from 355B to 744B parameters, with 40B active, and increases pre-training data from 23T to 28.5T tokens. The model integrates DeepSeek Sparse Attention (DSA), reducing deployment costs while maintaining long-context capacity. The model is open-sourced on Hugging Face and ModelScope, with weights under the MIT License. More details can be found in the blog and GitHub. A notable discussion point is the choice of training in FP16 instead of FP8, which contrasts with DeepSeek’s approach. There is also a sentiment favoring local data centers, with some users humorously anticipating a lighter version like ‘GLM 5 Air’ or ‘GLM 5 Water’.

• GLM-5 has been released with model weights available under the MIT License on platforms like Hugging Face and ModelScope. A notable technical detail is that GLM-5 was trained using FP16 precision, which contrasts with Deepseek’s use of FP8, potentially impacting computational efficiency and model performance.
• The cost comparison between GLM-5 and other models like DeepSeek V3.2 Speciale and Kimi K2.5 reveals significant differences. GLM-5’s input costs are approximately 3 times higher than DeepSeek V3.2 Speciale ($0.80 vs $0.27) and 1.8 times higher than Kimi K2.5 ($0.80 vs $0.45). Output costs are also notably higher, being 6.2 times more expensive than DeepSeek V3.2 Speciale ($2.56 vs $0.41) and 14% more expensive than Kimi K2.5 ($2.56 vs $2.25).
• GLM-5’s release on OpenRouter and the removal of Pony Alpha suggest a strategic shift, with GLM-5 being more expensive than Kimi 2.5. This indicates a potential focus on premium features or performance enhancements that justify the higher pricing, despite the increased cost compared to competitors.

GLM 5.0 & MiniMax 2.5 Just Dropped, Are We Entering China’s Agent War Era? (Activity: 422): GLM 5.0 and MiniMax 2.5 have been released, marking a shift towards agent-style workflows in AI development. GLM 5.0 focuses on enhanced reasoning and coding capabilities, while MiniMax 2.5 is designed for task decomposition and extended execution times. These advancements suggest a competitive shift from generating better responses to completing complex tasks. The releases are part of a broader trend in China, with other recent updates including Seedance 2.0, Seedream 5.0, and Qwen-image 2.0. Testing plans include API benchmarks, IDE workflows, and multi-agent orchestration tools to evaluate performance on longer tasks and repository-level changes. The comments reflect a mix of cultural context and optimism, noting the timing with Chinese New Year and suggesting that the advancements in AI represent a ‘war’ where the public benefits from improved technology.

• The release of GLM 5.0 and MiniMax 2.5 is part of a broader trend in China where multiple AI models are being launched in quick succession. This includes models like Seedance 2.0, Seedream 5.0, and Qwen-image 2.0, with more expected soon such as Deepseek-4.0 and Qwen-3.5. This rapid development suggests a highly competitive environment in the Chinese AI sector, potentially leading to significant advancements in AI capabilities.
• The frequent release of AI models in China, such as GLM 5.0 and MiniMax 2.5, indicates a strategic push in AI development, possibly driven by national initiatives to lead in AI technology. This aligns with China’s broader goals to enhance its technological infrastructure and capabilities, suggesting that these releases are not just celebratory but part of a larger, coordinated effort to advance AI technology.
• The rapid succession of AI model releases in China, including GLM 5.0 and MiniMax 2.5, highlights the intense competition and innovation within the Chinese AI industry. This environment fosters accelerated development cycles and could lead to breakthroughs in AI research and applications, positioning China as a formidable player in the global AI landscape.

GLM 5 Released (Activity: 931): GLM 5 has been released, as announced on chat.z.ai. The release details are sparse, but the community is speculating about its availability on platforms like Hugging Face, where there is currently no activity. This raises questions about whether the model will be open-sourced or remain closed. The release coincides with other AI developments, such as the upcoming Minimax M2.5 and anticipated updates like Qwen Image 2.0 and Qwen 3.5. Commenters are curious about the open-source status of GLM 5, noting the absence of updates on Hugging Face, which could indicate a shift towards a closed model. There is also excitement about concurrent releases in the AI community, highlighting a competitive landscape.

• Front_Eagle739 raises a concern about the lack of activity on GLM 5’s Hugging Face repository, questioning whether this indicates a shift towards a closed-source model. This could suggest a delay in open-sourcing or a strategic decision to keep the model proprietary, which would impact accessibility and community contributions.
• Sea_Trip5789 provides a link to the updated subscription plans for GLM 5, noting that currently only the ‘max’ plan supports it. They mention that after infrastructure rebalancing, the ‘pro’ plan will also support it, but the ‘lite’ plan will not. This highlights the tiered access strategy and potential limitations for users on lower-tier plans.

MiniMax M2.5 Released (Activity: 357): MiniMax M2.5 has been released, offering a new cloud-based option for AI model deployment, as detailed on their official site. The release coincides with the launch of GLM 5, suggesting a competitive landscape in AI model offerings. The announcement highlights the model’s availability in the cloud, contrasting with expectations for local deployment options, which some users anticipated given the context of the Local LLaMA community. The comments reflect a debate over the appropriateness of promoting cloud-based solutions in a community focused on local AI models, with some users expressing dissatisfaction with the perceived commercialization of the space.

2. Local LLM Hardware and Optimization

• Just finished building this bad boy (Activity: 285): The post describes a high-performance computing setup featuring six Gigabyte 3090 Gaming OC GPUs running at PCIe 4.0 16x speed, integrated with an Asrock Romed-2T motherboard and an Epyc 7502 CPU. The system is equipped with 8 sticks of DDR4 8GB 2400Mhz RAM in octochannel mode, and utilizes modified Tinygrad Nvidia drivers with P2P enabled, achieving an intra-GPU bandwidth of 24.5 GB/s. The total VRAM is 144GB, intended for training diffusion models up to 10B parameters. Each GPU is set to a 270W power limit. One commenter suggests testing inference numbers before training, mentioning models like gpt-oss-120b and glm4.6v. Another commenter notes using a lower power limit of 170W for fine-tuning without external fans.

segmond suggests obtaining inference numbers before training, mentioning models like gpt-oss-120b and glm4.6v as examples that could fit completely on the setup. This implies a focus on evaluating the system’s performance with large models to ensure it meets expectations before proceeding with more resource-intensive tasks like training.

• lolzinventor discusses their setup using 8x3090 GPUs with x16 to x8x8 splitters on PCIe v3 and dual processors, highlighting that despite potential bandwidth limitations, the system performs adequately. They mention considering an upgrade to Romed-2T and using 7 GPUs of x16, with a potential configuration change to accommodate an 8th GPU. They also address power stability issues, resolved by using 4x1200W PSUs to handle power spikes, and inquire about training intervals, indicating a focus on optimizing power and performance balance.

My NAS runs an 80B LLM at 18 tok/s on its iGPU. No discrete GPU. Still optimizing. (Activity: 132): A user successfully ran an 80 billion parameter LLM, Qwen3-Coder-Next, on a NAS using an AMD Ryzen AI 9 HX PRO 370 with integrated graphics, achieving 18 tok/s with Vulkan offloading and flash attention enabled. The system, built on TrueNAS SCALE, features 96GB DDR5-5600 RAM and utilizes Q4_K_M quantization through llama.cpp. Key optimizations included removing the --no-mmap flag, which allowed full model loading into shared RAM, and enabling flash attention, which improved token generation speed and reduced KV cache memory usage. The user notes potential for further optimization, including speculative decoding and DeltaNet linear attention, which could significantly enhance performance. Commenters are interested in the specific flags used with llama.cpp for replication and suggest trying other models like gpt-oss-20b for potentially faster performance. The discussion highlights the technical curiosity and potential for further experimentation in optimizing LLMs on non-standard hardware setups.

• The use of --no-mmap is highlighted as a critical point for optimizing performance when running large models on integrated GPUs. This flag helps avoid doubling memory allocations, which is a common pitfall when using UMA (Unified Memory Architecture) with Vulkan. This insight is particularly relevant for those trying to maximize efficiency on systems with limited resources.
• The performance of achieving 18 tokens per second on an 80B Mixture of Experts (MoE) model while simultaneously running NAS and Jellyfin is noted as impressive. This setup demonstrates the potential of using integrated GPUs for heavy computational tasks without the need for discrete GPUs, showcasing a ‘one box to rule them all’ capability.
• A suggestion is made to try running the gpt-oss-20b model, which is claimed to be approximately twice as fast as the current setup. This model, when combined with a server.dev MCP search, is suggested to enhance performance and intelligence, indicating a potential alternative for those seeking faster inference speeds.

What would a good local LLM setup cost in 2026? (Activity: 183): In 2026, setting up a local LLM with a $5,000 budget could involve various hardware configurations. One option is clustering two 128GB Ryzen AI Max+ systems, which offer excellent 4-bit performance for LLMs and image generation, and allow for fine-tuning with QAT LoRA to optimize int4 quantization. Another approach is using 4x RTX 3090 GPUs for a balance of memory capacity and speed, or opting for 7x AMD V620 for full GPU offload. Alternatively, a quieter setup could involve a Strix Halo box, providing similar VRAM capacity to 4x RTX 3090 but with less noise. A more complex setup could include 2x Strix Halo with additional networking components for tensor parallelism, enabling the running of 470B models at q4 quantization. There is a debate on the best configuration, with some favoring the memory and performance of Ryzen AI Max+ systems, while others prefer the balance of speed and capacity offered by multiple RTX 3090 GPUs. The choice between noise levels and performance is also a consideration, with quieter setups like the Strix Halo being suggested for those avoiding mining rig-like noise.

• SimplyRemainUnseen discusses a setup using two 128GB Ryzen AI Max+ systems, highlighting their strong 4-bit performance for LLMs and image generation. They mention the ability to fine-tune a QAT LoRA with unsloth’s workflows to improve int4 quantization performance, achieving usable speeds on models like GLM 4.7. The setup also supports running a ComfyUI API and GPT OSS 120B for image and video generation, leveraging the substantial unified memory.
• PraxisOG suggests using 4x 3090 GPUs for a balance of memory capacity and speed, suitable for running models like Qwen coder. They also mention an alternative with 7x AMD V620 for full GPU offload, which can handle models like GLM4.7 or provide extensive context with minimax 2.1 and 2.2. For a quieter setup, they recommend a Strix Halo box, which offers similar VRAM capacity to 4x 3090 but with less noise.
• Own_Atmosphere9534 compares different setups, including a Macbook M4 PRO MAX 128GB and RTX 5090, both around $5K. They highlight the Mac’s performance, comparable to RTX 3090, and its ability to run models like Llama 3.3 70B Instruct and Qwen3 coder variants effectively. They emphasize the importance of model size and hardware familiarity, noting that their M4 MacBook performs well with GPT-OSS-20B, influencing their decision to purchase the M4 PRO MAX.

MCP support in llama.cpp is ready for testing (Activity: 321): The image showcases the settings interface for the new MCP (Multi-Component Protocol) support in llama.cpp, a project developed by allozaur. This interface allows users to configure various settings such as “Agentic loop max turns” and “Max lines per tool preview,” which are crucial for managing how the system interacts with different tools and resources. The MCP support includes features like server selection, tool calls, and a UI with processing stats, aiming to streamline the integration of local and cloud models without altering tool setups. This development is significant as it addresses the tooling overhead and potential issues with smaller models hallucinating tool calls, a common problem in local agent setups. The project is still in progress, with plans to extend support to the llama-server backend, focusing on a robust client-side foundation first. Commenters highlight the importance of integrating MCP into the llama-server, which simplifies switching between cloud and local models. Concerns are raised about how the agentic loop handles errors from smaller models, such as hallucinated tool calls or malformed JSON, which are common issues in local agent environments.

• Plastic-Ordinary-833 highlights the significance of integrating MCP support into llama-server, noting that it simplifies the process of switching between cloud and local models without altering the tool setup. However, they express concern about how the agentic loop handles errors when smaller models hallucinate tool calls or return malformed JSON, which has been a major issue with local agents.
• allozaur discusses the initial release of MCP support in llama.cpp WebUI, emphasizing the focus on creating a solid client-side base before extending support to the llama-server backend. They mention using GitHub, Hugging Face, and Exa Search remote servers via streamable HTTP, with WebSocket transport also supported. OAuth, notifications, and sampling are not included in the initial release, but the goal is to iterate after a solid first release.
• prateek63 points out that MCP support in llama.cpp is a significant advancement, particularly the agentic loop support, which was a major barrier to using local models for tool-use workflows. The integration allows for native operation with local inference, moving towards self-hosting agentic setups, which were previously reliant on cloud APIs.

3. Qwen Model Developments

• Qwen-Image-2.0 is out - 7B unified gen+edit model with native 2K and actual text rendering (Activity: 691): Qwen-Image-2.0 is a new 7B parameter model released by the Qwen team, available via API on Alibaba Cloud and a free demo on Qwen Chat. It combines image generation and editing in a single pipeline, supports native 2K resolution, and can render text from prompts up to 1K tokens, including complex infographics and Chinese calligraphy. The model’s reduced size from 20B to 7B makes it more accessible for local use, potentially runnable on consumer hardware once weights are released. It also supports multi-panel comic generation with consistent character rendering. Commenters are optimistic about the model’s potential, noting improvements in natural lighting and facial rendering, and expressing hope for an open weight release to enable broader community use.

The Qwen-Image-2.0 model is notable for its ability to handle both image generation and editing tasks, with a focus on high-resolution outputs up to 2K. This dual capability is significant as it allows for more versatile applications in creative and professional settings, where both creation and modification of images are required.

• There is a discussion about the model’s performance in rendering natural light and facial features, which are traditionally challenging areas for AI models. The ability to accurately depict these elements suggests advancements in the model’s underlying architecture or training data, potentially making it a ‘game changer’ in the field of AI image generation.
• Concerns are raised about the model’s multilingual capabilities, particularly its performance across different languages. The predominance of Chinese examples in the showcase might indicate a bias or optimization towards Chinese language and cultural contexts, which could affect its utility in more diverse linguistic environments.

I measured the “personality” of 6 open-source LLMs (7B-9B) by probing their hidden states. Here’s what I found. (Activity: 299): The post presents a tool that measures the ‘personality’ of six open-source LLMs (7B-9B) by probing their hidden states across seven behavioral axes, revealing distinct ‘behavioral fingerprints’ for each model. The tool demonstrated high calibration accuracy (93-100% on 4/6 models), axis stability (cosine 0.69), and test-retest reliability (ICC 0.91–0.99). Notably, the study found ‘dead zones’ where models cannot be steered across all prompt variants, with Llama 8B being the most constrained (4/7 axes in the weak zone, 60% benchmark pass rate). The methodology involved extracting hidden states from the last four layers and projecting them onto axes like Warm ↔ Cold and Confident ↔ Cautious, with results showing models have stable, characteristic patterns even without prompting. The study also highlighted that alignment compresses behavioral dimensionality, with PCA revealing a spectrum of behavioral dimensionality across models. Commenters found the dead zones finding particularly interesting, noting that models ‘stably reproduce incorrect behavior’ rather than just being noisy, which raises concerns about RLHF’s impact on representation space. There was curiosity about whether dead zone severity correlates with downstream task reliability, suggesting implications for building reliable agents.

• GarbageOk5505 highlights the concept of ‘dead zones’ in the representation space of LLMs, where models consistently reproduce incorrect behavior. This suggests that Reinforcement Learning from Human Feedback (RLHF) might not effectively address these issues, as it could lead to models ignoring certain instruction axes. The commenter is curious about whether the severity of these dead zones correlates with the model’s reliability on downstream tasks, particularly in handling ambiguous instructions, which could impact the development of reliable AI agents.
• TomLucidor suggests a method for testing prompt biases by creating multiple personas using various names and adjectives, and conducting A/A testing with different seeds. This approach could help identify consistent biases in model responses, providing insights into how models might be steered or influenced by different prompts.
• TheRealMasonMac references a study by Anthropic on ‘assistant-axis’, implying that the post might be inspired by similar research. This connection suggests a broader context of exploring how LLMs can be influenced or characterized by different axes of behavior, potentially offering a framework for understanding model personalities.

**[Train MoE models 12x faster with 30% less memory! (

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

1. Seedance 2.0 AI视频与图像创新

• AI向全人类发出的直接信息（Seedance 2.0）（活跃度：1264）：该帖子推测AI将很快主导电影制作中的广角缩放镜头、视觉特效和绿幕背景等元素，预测这一转变将在明年年底前发生。这反映了电影行业向自动化和AI驱动内容创作的更广泛趋势，可能减少这些领域对传统人工角色的需求。一条评论提出了对AI对资本主义影响的更广泛担忧，暗示AI的影响不仅限于电影行业，还涉及整个经济结构。

Mr_Universal000强调了AI在民主化电影制作方面的潜力，特别是对于那些预算有限的人。他们表达了使用AI从故事板创建动态画面的兴奋，这可以作为吸引资金的概念验证。评论者特别关注可能使这项技术更易获取的开源解决方案。

Forumly_AI讨论了AI生成视频内容对社会的变革性影响。他们预测AI影响者将变得重要，具有塑造思想和观念并产生收入的潜力。评论者预计在一年内，视频模型的进步将导致重大的社会变革，暗示AI影响力将无处不在的未来。

Seedance 2因意外从面部照片准确重建声音而被下架（活跃度：765）：字节跳动已暂停其Seedance 2.0功能，该功能使用双分支扩散transformer架构从面部图像生成个人声音特征。该模型在未经授权的情况下创建与用户声音几乎相同的音频的能力引发了重大的隐私和伦理问题，特别是关于可能被滥用于身份伪造和深度伪造。字节跳动现在正在实施更严格的用户验证流程和内容审查措施，以确保负责任的AI开发。更多细节可查看此处。评论者认为令人印象深刻的声音重建可能是由于过拟合造成的，特别是如果模型在特定影响者的内容上进行了大量训练，导致意外的声音匹配。这引发了关于模型泛化能力和需要跨多样化数据集进行测试的问题。

• aalluubbaa认为Seedance 2的准确声音重建可能是由于过拟合造成的，特别是因为模型可能在影响者的内容上进行了大量训练。这意味着模型的性能可能无法很好地泛化到不同的声音或上下文，突显了其训练数据多样性的潜在限制。

• 1a1b推测了声音重建的技术机制，认为这可能与2023年开发的名为"Side Eye"的技术有关。该技术涉及从相机镜头弹簧捕获的振动中提取音频，理论上可能留下模型可用于从视觉数据重建声音的伪影。

• makertrainer假设这一事件可能被字节跳动夸大以展示其技术能力。他们认为声音相似性可能是巧合，而不是先进AI能力的展示，表明对该技术真实性能程度的怀疑。

2. AI行业高管离职与行业担忧

• xAI又一位联合创始人辞职，过去48小时内已有2人离职。xAI发生了什么？（活跃度：1286）：图片是xAI联合创始人Jimmy Ba的一条推文，宣布了他的辞职。这标志着xAI在48小时内第二位联合创始人的离职，引发了关于公司内部动态的疑问。Ba表达了对共同创立公司的机会的感激，并感谢Elon Musk的旅程，同时也暗示了未来在生产力工具和自我提升工具方面的发展。这些离职表明公司领导层或战略可能发生潜在变化，可能受到Musk全面控制的影响。评论者推测辞职可能是由于SpaceX的收购或对Elon Musk在xAI方向上的主导作用不满，导致联合创始人寻求他们能发挥更大影响力的企业。

技术视角表明，xAI的联合创始人可能因为控制动态的变化而离开，Elon Musk在公司方向上扮演更主导的角色。这可能导致联合创始人的影响力减少，促使他们追求拥有更多控制权和更大股份的企业。这意味着xAI的战略愿景深受Musk影响，可能与联合创始人的抱负不一致。

• xAI联合创始人的离职可能与财务激励有关，例如SpaceX的收购。这种情况将允许联合创始人兑现他们的股权，为他们提供探索新机会的资金。这一财务角度表明辞职是战略退出计划的一部分，而不是对内部冲突或不满的反应。

• 有推测认为，如果Elon Musk不启动新高管的大规模招聘，这将证实他在管理xAI中的核心作用。这表明公司内部权力和决策的集中，可能导致更精简但以Musk为中心的运营模式。这可能是使xAI目标与Musk对AI和技术的更广泛愿景紧密一致的战略举措。

仅过去一周内：（活跃度：3548）：**图片是Miles Deutscher总结AI行业近期事件的备忘录式推文，突显了对领导层变化和AI行为的担忧。它提到了Anthropic安全研究负责人的辞职、xAI的离职以及关于AI行为的报告。此外，还提到字节跳动的Seedance 2.0可能取代电影制作人的技能，以及Yoshua Bengio关于AI行为的评论。美国政府决定不支持2026年国际AI安全报告也被提及，反映了关于AI安全和治理的持续辩论。**评论反映了对这些事件戏剧性描述的怀疑，认为财务激励可能是AI高管离职的驱动因素，而不是行业担忧。

OpenAI正在重蹈Facebook的覆辙。我辞职了。（活跃度：722）：OpenAI前研究员Zoë Hitzig在公司决定在ChatGPT上测试广告后辞职，引用了对潜在用户操纵和伦理侵蚀的担忧。Hitzig强调了ChatGPT用户生成的个人数据前所未有的存档，这些数据可能通过广告被利用。她反对限制AI访问或接受广告的二元选择，提出了替代的资助模式，如交叉补贴和独立治理，以在不损害用户完整性的情况下保持可访问性。完整文章可查看此处。评论反映了对AI伦理轨迹的怀疑，一些人将其与Meta的历史失误相提并论，另一些人则注意到AI描绘与人类行为理解之间的差距。

• 讨论突显了AI服务的经济模式，将其与Facebook和YouTube等平台进行比较。有人认为，要使AI像Facebook那样对所有人可访问，广告是必要的。没有广告，AI服务将需要向用户收费，可能限制较富裕个体的访问，这与AI作为"伟大均衡器"的理念相矛盾。

• 一位用户建议，如果用户从ChatGPT等AI服务中获得显著的实际利益和效率，付费是合理的。这意味着对于专业或密集用户，订阅成本可以通过付费服务提供的生产力增益和附加功能来抵消。

• 对话触及了AI与人类行为不同的看法，但它反映了对人类行为本身的误解。这表明关于AI本质及其与人类认知过程对齐或分歧的更深入的哲学辩论。

又一位辞职（活跃度：794）：**该帖子讨论了一封辞职信，一些人将其解读为涉及超越AI的更广泛社会问题，如"元危机"或"多重危机"。这封信被视为对在全球挑战中过有意义生活的反思，而不是仅仅关注AI风险。这一观点在科学和技术领域越来越受到关注，突显了向解决相互关联的全球危机的转变。**一条评论批评这封信过于自夸，而另一条则认为辞职是股票出售后更轻松生活方式的前奏。

3. DeepSeek模型更新与基准测试

• Deepseek V4本周即将发布（活跃度：312）：Deepseek V4预计将在2月17日发布，恰逢中国新年。据报道，更新包括处理100万tokens的能力，表明处理能力有显著增强。这使Deepseek成为与Opus、Codex等主要模型竞争的替代方案，可能以更低的成本提供类似能力。一位评论者强调，Deepseek的进步使其成为其他主要模型的成本效益替代方案，表明中国的AI发展在全球市场上具有竞争力。

一位用户提到Deepseek已更新为处理100万tokens，表明其处理能力有显著增加。这可能意味着在处理更大数据集或更复杂查询方面的改进，这对于处理大量数据或需要详细分析的用户来说是一个值得注意的增强。

• 另一位用户报告称，更新后，Deepseek对复杂角色写作提供了细致入微且原创的评论。这表明模型理解和批评创意内容的能力有所改进，表明其自然语言处理和理解技能的进步。

• 一条评论强调，Deepseek的回应现在表现出更多"个性"，与ChatGPT进行了比较。这可能表明模型的对话能力有所增强，使交互感觉更人性化和吸引人，这对于需要用户交互的应用至关重要。

DeepSeek正在更新其模型，支持100万上下文（活跃度：174）：DeepSeek已宣布对其模型进行重大更新，现在支持高达100万tokens的上下文长度，显著增强了其在问答和文本分析等任务中的处理能力。此次更新紧随去年的DeepSeek V3.1，后者将上下文长度扩展至128K。测试显示，该模型可以处理像包含超过240,000个tokens的小说《简·爱》这样大的文档，有效识别和处理内容。一些评论者表达了怀疑，质疑更新是真实的还是幻觉，表明需要进一步验证或展示模型的能力。

• DeepSeek最近更新以支持高达100万tokens的上下文长度，这标志着其先前版本支持128K tokens的显著增强。这一改进允许更有效地处理大量文档，如小说，这些文档可能包含数十万个tokens。这种能力对于涉及长篇文本分析和复杂问答场景的任务特别有益。

• DeepSeek的更新据称增加了某些查询的处理时间。一位用户指出，先前需要30秒处理的问题现在需要160秒，表明增加的上下文长度和处理速度之间可能存在权衡。这表明虽然模型可以处理更大的输入，但可能需要更多的计算资源，影响响应时间。

• 对更新存在一些怀疑，用户质疑关于模型能力的声明的真实性。一位用户将更新称为"幻觉"，表明可能存在关于模型是否真正能处理所宣传的扩展上下文长度的疑问。

deepseek已更新，现在拥有100万上下文窗口和截至2025年5月的知识截止日期，等待基准测试（活跃度：164）：DeepSeek已更新以支持100万token上下文窗口，现在包括截至2025年5月的知识截止日期。此次更新使DeepSeek成为处理大量数据和长篇内容的潜在强大工具，尽管基准测试仍在等待中以评估其性能。该模型被描述为编码和代理能力的结合，表明专注于编程任务和自主决策过程。评论者注意到模型的速度和智能，一位将其描述为"编码+代理模型"，表明对其双重能力的积极接受。

• DeepSeek的更新引入了上下文窗口大小的显著增加至100万tokens，这大约相当于750,000个英文单词或150万个中文字符。这是通过使用**多头潜在注意力（MLA）**实现的，它压缩了键值缓存，允许快速推理并减少内存使用，尽管上下文扩展了。这一增强使得无需重新运行提示即可处理整个代码库或小说，这对于处理大型数据集是一个实质性的改进。

• 澄清了更新不涉及底层模型架构本身的变化，而是扩展了上下文窗口并将知识截止日期更新至2025年5月。这意味着对于现有聊天，用户将经历的主要变化是增加的聊天长度能力，而不改变模型的核心功能或性能特征。

• 尽管上下文窗口大小有显著更新，但DeepSeek网站上尚无官方发布说明。这种缺乏文档的情况可能使用户无法获得关于新功能技术细节或潜在限制的详细见解，例如对性能指标的影响或与现有系统的兼容性。

AIME 2026结果公布，Kimi和DeepSeek是最佳开源AI（活跃度：112）：图片展示了AIME 2026竞赛的结果，突显了各种AI模型的性能和成本。Kimi K2.5和DeepSeek-v3.2被指出为表现最佳的开源模型，准确率分别为93.33%和91.67%，提供了对闭源模型的成本效益替代方案。表格还包括其他模型，如GPT-5.2、Grok 4.1 Fast和Gemini 3 Flash，其中Grok 4.1是一个闭源模型，以其低成本而闻名。评论者对Grok 4.1的性能和成本效益印象深刻，尽管它是一个闭源模型。对DeepSeek V3.2 Speciale在结果中的缺失也存在好奇。

• 讨论强调Grok 4.1是一个闭源模型，以其成本效益而闻名，表明它以比其他模型更低的价格提供竞争性性能。这对于优先考虑预算而不愿在性能上做出太多牺牲的用户可能特别相关。

• 提出了关于DeepSeek V3.2 Speciale在结果中缺失的疑问，表明对该特定版本的兴趣。这表明可能存在与此版本相关的期望或已知性能指标，用户渴望将其与测试模型进行比较。

• 测试模型数量有限，仅六个，受到质疑，这意味着结果的全面性可能存在限制。这可能影响研究结果的普遍性，因为更广泛的模型范围可能提供当前开源AI性能状态的更完整图景。

• GLM-5夺得Agent王冠（及榜首位置）：OpenRouter发布了GLM-5（744B）作为编码/agent基础模型，并透露Pony Alpha是GLM-5的早期隐秘版本，现已下线，发布页面位于OpenRouter GLM-5。

LMArena也在Text+Code Arena中添加了glm-5，并报告其在Text Arena排行榜上在开源模型中排名第一（总排名第11位，得分1452，比GLM-4.7高出**+11分），而Eleuther则提到在Modal上有一个免费端点，截止到4月30日**，并发数为1：Modal GLM-5端点。

基准测试受到审视："展示你的工作"版本：在Yannick Kilcher的Discord中，成员们对GLM-5演示和官方文档中展示的基准测试表格提出了质疑，指向关于GLM-5表格的推文讨论和GLM-5文档。

• Nous Research社区也在browsecomp上比较了GLM-5与Kimi，指出GLM-5为**~744B（+10B MTP），而Kimi为1T**，并声称GLM的活跃参数（40B）高于Kimi（32B），这强化了人们正以更技术性的视角审视排行榜声明的趋势。

GLM-OCR：更便宜的视觉/OCR压力阀：Latent Space中的开发者报告GLM-OCR在OCR测试中击败了Gemini 3 Flash，并链接了模型卡片：zai-org/GLM-OCR on Hugging Face。

• 该讨论将GLM-OCR定位为OCR密集型产品的实用替代方案（他们提到目前仍在使用Gemini Flash，但希望找到更便宜的方案），而Latent Space的其他帖子则强调了一波开源多模态模型的发布（通过Merve的帖子），表明在性价比方面的竞争正在加剧。

• DeepSeek 农历新年倒计时进入6天：LMArena 用户猜测 DeepSeek 将在农历新年（6天后） 发布新模型，传闻包括100万上下文窗口、新数据集/架构，甚至新的计算芯片。

OpenRouter 上的讨论进一步放大了传闻，关于 "deepseek v4" 出现在 X 平台上的问题引发了猜测，有人认为这可能是轻量级变体，这显示了未经确认的模型 ID 现在如何快速传播到规划和路由决策中。

Chimera R1T2 可用率降至18%——路由恐慌随之而来：OpenRouter 用户报告了DeepSeek Chimera R1T2的重大可靠性问题，包括声称其可用率降至18%，引发了关于服务可靠性的讨论。

• 这些可靠性投诉与发布时的炒作形成了鲜明对比，推动人们转向务实的缓解措施（例如，明确指定模型回退而不是依赖自动路由），而讨论串则演变成了玩笑，而非具体的服务级别目标修复。

• RLMs：是下一步发展还是花哨的脚手架？：OpenRouter成员询问该平台是否在探索超越测试时计算的RLM（推理语言模型），有人声称他们已经在RLM概念上工作了1.5年。

DSPy构建者同时将RLM付诸实践，通过子智能体/智能体团队将RLM集成到Claude Code中，并在Discord线程中请求对实现进行批评：核心实现帖子。

无需API的Google搜索MCP让LM Studio"浏览"网络：LM Studio用户分享了noapi-google-search-mcp，这是一个通过无头Chromium添加Google搜索功能而无需API密钥的工具：VincentKaufmann/noapi-google-search-mcp。

• 对于一个MCP插件来说，功能列表异常广泛——图像、反向图像搜索、本地OCR、Lens、航班、股票、天气、新闻/趋势——讨论将其视为无需按查询付费就能快速为本地模型添加检索功能的便捷方式。

OpenClaw让你从Discord运行开发环境：在Latent Space中，一位构建者表示他们使用OpenClaw来编排tmux会话、工作树和Claude Code，从而"完全通过Discord"进行开发，并计划在2026年2月20日举办一场名为使用OpenClaw随处编码的演讲。

• 后续的工作流线程探讨了可审计的上下文保存，使用/wrap会话边界将上下文+反思保存为带有元数据的markdown格式，直接将工具的人体工程学与"上下文腐化/失去线索"的痛点联系起来。

• CuteDSL火热而Triton在Blackwell上"濒死"：GPU MODE用户报告CuTeDSL/CuteDSL采用率不断增长，根据Kernelbot统计数据显示CUDA和CuTeDSL主导提交，且CuTeDSL感觉比Triton"更透明"，相关数据集位于GPUMODE/kernelbot-data。

多位成员声称Triton在Blackwell架构上遇到困难，原因在于非常规的MXFP8/NVFP4布局和编译器限制，预计在相关Triton TLX演讲中会有更多讨论，这预示着下一代NVIDIA硬件可能出现工具链分化。

torchao v0.16.0发布MXFP8 MoE构建模块：GPU MODE关注到torchao v0.16.0新增了MXFP8 MoE构建模块，支持专家并行训练，同时进行了配置弃用和文档/README更新。

• 发布说明还提到了ABI稳定性方面的进展，这对于下游集成至关重要，因为各团队正试图在异构环境中标准化低精度MoE训练栈。

CUDA Bender TMA矩阵乘法内核：异步存储与持久化特性：GPU MODE分享了一个具体的内核实现——CudaBender仓库中的TMA矩阵乘法：tma_matmul.cu。

• 讨论集中在较小数据类型如何释放足够的共享内存用于c tiles，从而实现异步存储/持久化，这反映了一个更广泛的主题：随着架构和数据类型变得越来越奇特，人们希望重新获得底层控制能力。

• Perplexity深度研究限制引发"诱饵调包"指控：Perplexity Pro用户抱怨未经通知的深度研究限制，并分享了速率限制端点：Perplexity速率限制。

用户还报告了错误的文章链接、更低的来源数量（低至24个），并怀疑存在成本节约行为，比如使用Sonar进行首次响应，这立即引起了工程师们注意到的可靠性/质量下降问题。

Cursor用户目睹Opus 4.6吞噬钱包（和上下文）：Cursor社区成员表示Opus 4.6消耗令牌速度极快，有人报告单个提示词就使用了11%的API请求，并迅速耗尽了200美元的计划。

• 价格反弹加剧，有报告称使用Opus 4.6和GPT-5.3 Codex进行约9小时工作，每三天就要花费100美元，这重新定义了"最佳编码模型"的讨论，使其成为成本/性能工程问题。

Discord身份验证引发平台迁移计划：Unsloth和Cursor社区都对Discord新的身份验证门槛（用于查看某些内容）反应强烈，Cursor链接了一条澄清推文：Discord关于身份验证范围的推文。

• Latent Space通过Discord的帖子将该政策与IPO风险和用户流失担忧联系起来，而Nous成员则讨论了将机器人/工具社区迁移到Matrix，这表明基础设施构建者将通信平台视为其技术栈的一部分。