DeepSeek 测试 Super-agent 分离路由与编程工作
AI 总结
据一篇评论文章报道,DeepSeek 发布了一个名为 Super-agent 的原型,由一个会话路由请求,独立工作会话负责编程。在每次约含 300 条消息和 20 个工作请求的模拟中,每种配置运行五次;路由与工作分离方案的中位和 p95 完成时间分别为 12.4 分钟和 15.7 分钟,中性提示的单会话基线则为 20.4 分钟和 29.5 分钟。报道中的 47% p95 降幅难以单独归因于架构拆分:基线在五次运行中从未调用子智能体工具,而委派优先提示将中位耗时降至 13.8 分钟,但 p95 仍为 29.0 分钟。每次运行的缓存读取量从 610 万增至 2320 万 token,但这不等同于总支出。工作目录并非操作系统沙箱,命令以用户的操作系统账户运行。
深度见解
该原型为多会话编码智能体设计提供了具体思路,而基线、缓存读取量和沙箱限制等注意事项表明,在采用该模式前需要审慎评估其延迟表现。
| DeepSeek published a prototype of what it calls a Super-agent: one session routes incoming requests, separate worker sessions do the coding. The interesting part is the ablation, not the architecture diagram. In a simulation of roughly 300 messages and 20 work requests per run, five runs per configuration, the router-and-worker setup finished at 12.4 min median and 15.7 min p95. The single-session baseline with a neutral prompt sat at 20.4 and 29.5 min, so about a 47% cut at the tail. Caveat: that baseline never once called its subagent tool across the five runs. A delegation-first prompt brought it to 13.8 min median, with p95 unchanged at 29.0. The cost side is the part I would want before adopting the pattern: 23.2M cache-read tokens per run against 6.1M. Cache reads are not total spend, but 3.8x is not noise. Also worth noting: worker directories are not a sandbox. Commands run as your own OS user. submitted by /u/docdavkitty [link] [comments] |