公开论文雷达

公开 arXiv 研究简报 · 2026-08-18T00:56:38.844081+00:00

先看结论和关键数字,再决定要不要读原文。候选只在首次出现时展示;旧候选若后来通过深读门槛,仍会进入重点。

五份评测卡共识:别信单一顶层指标

五张卡横跨记忆后端、GUI代理、代码生成、开源协作与行为建模,却指向同一命题:完成率、吞吐量、Pass@1这类顶层数字会掩盖失败域与噪声。差别在证据硬度——三份有量化对照,两份是标签剖面或概念验证。先读方法最硬、能直接复用的两份。

推荐阅读顺序

  1. 2608.14131:最锋利地重构问题:完成率高不等于安全,失败运行可能在遗留系统留脏状态;引入有效/无效成功失败四类原子性标签。
  2. 2608.13883:匹配协议固定框架只换记忆集成,量化展示宏平均20.5%对13.6%如何掩盖旅行规划四系统SR全为零。
  3. 2608.13884:用账号类型做人机分账,证明33228个PR吞吐21倍/17.9倍增长来自人类,机器人PR占比不足0.2%。
  4. 2608.13742:拆开内容与格式两变量,显示ISO标准化把可读性缺陷密度0.88降到0.69,却拉低错误处理通过率的权衡。
  5. 2608.14352:把轨迹转成带标签马尔可夫链审计行为策略,但仅12台靶机单域概念验证、无定量基线,作思路参考。
共性方法
五张卡都在讲同一件事:单一顶层指标(完成率、吞吐量、Pass@1、任务成功率)会骗人,必须换更能分辨的口径——匹配对照、分域拆解、人机分账、状态原子性、行为建模——才能把真实信号从噪声里分出来。
关键分歧
分歧在证据硬度与测量对象。13883、13742、13884固定变量做量化对照,有具体数字和边界;14131只给四类标签剖面、未公开逐代理数值;14352是单一渗透测试域的概念验证、无定量基线。读时按证据硬度区别对待,别把演示当结论。
选择准则
想要能直接复用的评测协议先读13883与14131;判断AI工具是否真提效读13884;调代码生成提示读13742;14352作行为审计思路参考,勿当量化依据。

重点深读(5 / 5 篇)

形式化与程序验证(0 篇)

本轮没有通过深读证据门的重点论文。

软件工程与仓库智能(2 篇)

软件工程与仓库智能 7/30

Engineering Signals of Human-AI Collaboration in the Agentic Coding Era: A Longitudinal Analysis of 33,228 Pull Requests from vLLM and SGLang with Implications for Biomedical AI Agents and Bioinformatics Pipeline Developmen

AI编程工具普及后,吞吐量暴涨主要来自人类贡献,不是机器人刷量:如果你要判断AI编码工具是否真让团队变快,只看总PR数会把机器人噪声当成人的产出。这个研究用仓库级纵向口径拆解vLLM和SGLang共33228个已合并PR,给出可复核的人机协作信号。

两句看懂

研究回答的是一个实务问题:AI工具到底让团队更快,还是只制造更多自动化痕迹。33228个已合并PR显示,吞吐量21倍/17.9倍增长由人类驱动(机器人PR<0.2%),评论密度增4.2/3.8倍而PR规模稳定,说明变密的是人机协同和审查,不是单个PR变大。

核心判断

高速开源AI基础设施项目中,吞吐量大幅增长主要由人类驱动,机器人PR<0.2%;独立作者数单调上升,反驳贡献集中假设;评论密度约4倍增长而PR规模稳定,说明提升发生在协同和审查密度,而非代码体量膨胀。证据边界是33228个PR的四阶段纵向描述。

关键要点

1. 旧证据多来自个体受控实验,缺少仓库级多阶段纵向数据,也没回答贡献是集中还是扩大。 2. 方法用33228个已合并PR按四个AI工具阶段切片,用账号类型区分人机并抽样复核,用PR规模控制评论密度解释。 3. 结果是吞吐量38→797和42→743个PR/月,机器人PR<0.2%;应同时看机器人占比和PR规模再归因于人类提效。

证据与结果

数据为vLLM 18290个已合并PR(41个月)和SGLang 14938个已合并PR(30个月),合计33228个,来自代码托管平台API及git仓库。四阶段为前自主基线、早期工具扩展、氛围编码主流化、自主编程涌现。关键读数:vLLM吞吐量38→797个PR/月,SGLang 42→743个PR/月,两项目2026年6月均超1100个/月;Era 3中位周期时间1.04天(vLLM)/0.62天(SGLang),P90为16.8/14.3天;独立作者月增+10.1(r²=0.94)/+11.2(r²=0.93),p<0.001;评论密度增4.2/3.8倍,机器人评论占15–20%;PR规模稳定。

打开论文原文
它要解决什么
在高速开源AI基础设施项目里,AI编程工具普及是否推高团队级开发吞吐量?它会不会同时改变贡献结构和代码审查行为,例如贡献集中到少数人,或审查被机器人评论稀释?
研究路径
机制不是模型内部原理,而是度量口径:用Search API拿到全量已合并PR元数据,用git仓库分析补工程指标;用账号类型字段把机器人PR、人类PR、机器人评论、人类评论分开,再对评论子样本人工复核分类。时间轴按四个AI工具里程碑对齐;独立作者数做月粒度OLS回归;周期时间看中位数和P90;用中位变更行数和文件数作为PR规模控制量,排除“评论变多只是PR变大”的路径。
这对工程意味着什么
先把机器人PR占比、机器人评论占比和PR规模加进效能看板,再判断吞吐量增长能否归因于人类。别走只看总吞吐量的捷径;这会把15–20%的机器人评论和少量自动化活动误算成人工效能。
证据定位
吞吐量增长贴近人类驱动结论:vLLM从38增至797个PR/月,21倍;SGLang从42增至743个PR/月,17.9倍;机器人PR占比<0.2%。审查变密但体量不变:评论密度增4.2/3.8倍,机器人评论占15–20%,PR规模跨阶段稳定。贡献面扩大:独立作者月增斜率+10.1(vLLM,r²=0.94)和+11.2(SGLang,r²=0.93),p<0.001。(筛选维度:可复核评测、软件工程方法)
适用边界
这是描述性案例分析,没有对照组;指标变化与AI工具阶段相关,但不能做因果归因。只覆盖vLLM和SGLang两个AI基础设施项目,不能外推到通用开源项目。机器人识别依赖账号类型字段,虽经抽样复核,仍有一定分类误差。
方法与英文摘要

研究抓取代码托管平台Search API和git仓库数据,覆盖vLLM 18290个已合并PR(2023.02–2026.06,41个月)和SGLang 14938个已合并PR(2024.01–2026.06,30个月)。按AI工具里程碑切成四个阶段,用账号类型元数据区分机器人和人类活动,并对评论子集抽样复核。指标固定为7项:PR吞吐量、周期时间、独立作者数、评论密度、合并率、新作者占比、PR规模。

The rapid adoption of AI coding assistants and autonomous agentic development systems has coincided with major changes in the pace and structure of open-source software engineering. Yet empirical longitudinal evidence of these changes at the team level remains limited. We present a descriptive longitudinal analysis of seven engineering metrics: pull request (PR) throughput, cycle time, contributor diversity, PR comment density, merge rate, new-author participation, and PR size. Metrics were computed from all merged PRs in two high-velocity AI infrastructure repositories, vLLM (February 2023-June 2026; 18,290 PRs) and SGLang (January 2024-June 2026; 14,938 PRs). We segment development into four eras aligned with major changes in AI-assisted software development and examine human- and bot-authored activities. Both projects show substantial increases in development velocity and AI-developer collaboration signals. PR throughput increased 21x in vLLM and 17.9x in SGLang, while bot-authored PRs accounted for less than 0.2% of this growth, indicating that the increase was overwhelmingly human-driven. In the latest era, median cycle time was 1.04 days for vLLM and 0.62 days for SGLang, while P90 cycle times reached 16.8 and 14.3 days, respectively. Monthly unique authors increased steadily in both projects, suggesting broader contributor participation. PR comment density increased 4.2x in vLLM and 3.8x in SGLang, with bot comments contributing an estimated 15-20% of the increase. In contrast, PR size remained relatively stable across eras. Overall, AI-assisted development is associated with higher throughput, broader contributor participation, and increased AI-developer collaboration signals in high-velocity open-source software development.

软件工程与仓库智能 6/30

ATLAS: Discovering Agent Strategies through LLM-Guided Abstraction and Automata Learning

从轨迹学习LLM智能体行为有限状态模型:当前对LLM智能体的评估只看任务成功率和执行轨迹,无法揭示其内部策略。ATLAS以LLM引导的语义抽象加自动机学习,将智能体轨迹转化为可解释的带标签马尔可夫链模型,在渗透测试12台漏洞靶机的案例中验证了高层策略的可识别性。

两句看懂

直接分析执行轨迹无法揭示LLM智能体在多步任务中采用的高层策略,ATLAS以LLM引导抽象加自动机学习将轨迹转化为带标签马尔可夫链。在12台漏洞靶机渗透测试案例中,学到的模型暴露了原始轨迹难以发现的行为策略并支持了跨模型符号知识迁移。

核心判断

LLM智能体的交互轨迹可通过语义抽象和自动机学习自动转化为可解释有限状态模型,从而揭示高层策略和失败环路;证据来自12台漏洞靶机渗透测试案例及跨模型知识迁移演示。

关键要点

1. 现有评估只记录任务成功率和执行轨迹,缺乏对智能体本身行为策略的显式建模,导致比较、监控和验证难以实施;LLM决策复杂度使手工建模不可行,已记录轨迹作为行为信息来源长期被忽视。 2. ATLAS三步构建:原始轨迹收集→LLM引导语义抽象(将噪声动作与观察归并为高层类别)→自动机学习(推断带标签马尔可夫链);受控因素为抽象粒度与模型构造算法;在12台漏洞靶机渗透测试场景上部署验证。 3. 学到的马尔可夫链可识别原始轨迹难以发现的高层利用策略和失败环路,并演示从前沿大模型到紧凑语言模型的符号知识迁移;当前覆盖仅限单一渗透测试领域的概念验证规模,未提供定量对比基线。

证据与结果

数据来自LLM渗透测试智能体与12台漏洞靶机的交互轨迹;评估为定性分析:检验学到的马尔可夫链是否暴露原始轨迹难以识别的高层策略、决策点、成功路径和失败环路;同时演示前沿大模型向紧凑语言模型的符号知识迁移,以及通过模型变换生成简洁行为说明;论文定位为概念验证,未提供定量对比基线或数值指标。

打开论文原文
它要解决什么
如何从LLM智能体的交互轨迹中自动恢复紧凑且可解释的行为模型,以支持策略分析、可解释性审计和跨模型知识迁移?
研究路径
基础模型对每条原始动作和环境观察执行语义分组,将相似条目映射为有限高层标签;抽象后的标注轨迹输入自动机学习算法,推断带标签马尔可夫链;链上状态对应行为类别,转移概率捕获随机决策;最终模型支持概率模型检验、模型变换及跨模型符号知识迁移。
这对工程意味着什么
若需审计LLM智能体在多步任务中的行为策略,可用该流程将轨迹转化为马尔可夫链以定位失败环路和策略偏差;勿将高任务通过率误认为策略可理解,通过率掩盖了智能体实际路径的分布差异。
证据定位
在12台漏洞靶机渗透测试案例中,学到的马尔可夫链模型暴露了原始轨迹难以识别的高层利用策略和失败环路;另演示了从前沿大模型到紧凑语言模型的符号知识迁移。(筛选维度:可复核评测、软件工程方法)
适用边界
概念验证仅在渗透测试领域12台靶机上执行,单一任务类型限制了域外泛化能力;论文未提供定量对比基线,策略发现效果的客观度量依据不足。
方法与英文摘要

数据来自LLM渗透测试智能体在12台漏洞靶机上产生的交互轨迹。流程三步:一、收集智能体与环境的原始交互轨迹;二、用基础模型对原始动作和观察做语义抽象,将相似条目归并为有限高层类别;三、以抽象轨迹为输入执行自动机学习,推断带标签马尔可夫链作为行为模型。模型支持概率模型检验、模型变换和符号知识迁移。

Large Language Model (LLM)-based agents are increasingly used for complex tasks such as software testing and cybersecurity assessment. While these agents demonstrate impressive capabilities, their behavior is difficult to understand, explain, and analyze. Existing evaluations focus mainly on task success and execution traces, offering limited insight into the strategies employed by the agent. We present ATLAS (Automata Learning for Agent Trajectory Analysis and Strategy Discovery), an approach for recovering interpretable behavioral models from agent trajectories. ATLAS combines trace abstraction with automata learning to infer finite-state models that capture observed agent-environment interaction strategies. These models provide human-interpretable insights and support automated analyses of recurring behaviors, decision points, successful task-completion paths, and failure loops. As a proof of concept, we apply ATLAS to trajectories generated by an LLM-based penetration-testing agent. The resulting models expose high-level behavioral strategies for exploiting vulnerable machines that are difficult to identify from raw execution traces alone. We discuss how learned behavioral models can support explainability, model-guided exploration, auditing, and analysis of agentic systems. We further demonstrate symbolic model-based knowledge transfer from powerful frontier models to compact language models. In addition, we show how model transformations can derive concise explanations of agent behavior in a penetration-testing case study comprising 12 vulnerable machines. ATLAS highlights a new opportunity for model-driven engineering: transforming agent trajectories into explicit behavioral models that enable systematic understanding and analysis of otherwise opaque AI agents.

代码质量与优化(1 篇)

代码质量与优化 6/30

Does ISO-Grounded NFR Specification Improve LLM Code Generation? A Comparison of Rich and Structured Interventions against a Natural-Language Baseline

ISO标准化NFR规格能降低静态缺陷,但会降低错误处理通过率:你给LLM写代码生成提示时,非功能需求(NFR)常常只写一行短语。这个实验说明:把NFR扩展成符合ISO/IEC 25010的详细描述,能把Performance NFR的可读性缺陷密度从0.88降到0.69,并让多次生成的输出更稳定;但功能正确性没有可靠提升,错误处理的ET-Pass@1反而下降。

两句看懂

实践中LLM代码生成的NFR往往只写一行短语,本研究把它替换成ISO/IEC 25010标准化的详细描述或JSON,在HumanEval上用每条件10个提示变体做配对检验。结果是Performance NFR可读性缺陷密度从0.88降到0.69、提示敏感性下降,但功能正确性未可靠提升,错误处理ET-Pass@1反降,prose与JSON差距仅|δ|≤0.023。

核心判断

ISO标准化的NFR内容能改善静态质量指标并降低提示敏感性,但不能可靠提升功能正确性,错误处理ET-Pass@1甚至下降;语义内容比序列化形式更重要,NL-rich与JSON差距|δ|≤0.023就是证据。

关键要点

1. 旧做法的问题:NFR只用一行短语指定,这类规格已知会拉低Pass@1并增大跨提示变体的标准差,但没人分清是内容丰富化的作用还是格式(prose vs JSON)的作用,工程师不知道该优化内容还是格式。 2. 方法与受控检验:HumanEval/HumanEval-ET上设三组配对条件,固定单一模型快照,四类NFR各做10个提示变体;静态质量用per-10-LOC缺陷密度,正确性用Pass@1/ET-Pass@1,鲁棒性用跨变体STDEV,配对非参数检验;基线与干预存在时间差(2026年4-5月 vs 6月)。 3. 决定性结果与行动:NL-rich使Performance可读性缺陷密度从0.88降到0.69,四类NFR静态质量全部改善、STDEV下降,但Pass@1未可靠提升、错误处理ET-Pass@1下降(防御性编码与精确输出基准冲突);prose与JSON差距|δ|≤0.023,应优先把NFR内容标准化,而不是改格式。

证据与结果

基准:HumanEval测功能正确性,HumanEval-ET用扩展测试集、判得更严。四类NFR:性能效率、错误处理、代码异味、可读性。每条件10个提示变体,固定单一模型快照,三组配对比较(NL-simple vs NL-rich、NL-simple vs Structured、NL-rich vs Structured)。关键数字:Performance NFR可读性缺陷密度0.88→0.69(NL-rich);NL-rich与Structured正确性差|δ|≤0.023;错误处理NFR的ET-Pass@1下降,原因是防御性编码模式与精确输出基准存在张力。基线在2026年4-5月收集,干预条件在2026年6月执行,没有同期重跑。

打开论文原文
它要解决什么
把NFR从一行短语扩展成ISO/IEC 25010标准化的详细内容,能否提升LLM代码生成的功能正确性与非功能质量?prose和JSON两种写法差异大吗?
研究路径
为每个HumanEval任务构造三类提示:一行NFR短语、ISO/IEC 25010对应质量特征的详细自然语言段落、同一ISO内容序列化的JSON。功能任务描述和模型快照固定不变,每个条件生成10个提示变体;每题记录Pass@1、ET-Pass@1和per-10-LOC静态质量缺陷密度,用跨变体STDEV衡量鲁棒性,用配对非参数检验比较三组差异。这样内容(丰富 vs 简单)和形式(prose vs JSON)两个变量被分开检验。
这对工程意味着什么
第一步行动:把你的NFR提示改写成ISO标准化的质量特征描述,用来降低缺陷密度、稳定多次生成的输出。要避开的捷径:别以为把提示改成JSON格式就能提质——格式不是关键变量;同时对错误处理类NFR保持警惕,标准化描述可能引入防御性编码,反而拉低精确输出基准的通过率。
证据定位
Performance NFR的可读性缺陷密度在NL-rich下从0.88降到0.69,四类NFR的静态质量缺陷密度全部下降,跨变体STDEV缩小;但错误处理NFR的ET-Pass@1下降;NL-rich与Structured的正确性差距只有|δ|≤0.023。(筛选维度:形式化验证、可复核评测)
适用边界
基线与干预条件存在时间差(基线2026年4-5月,干预2026年6月,未同期重跑);实验只覆盖HumanEval类编程任务和四类NFR;模型固定为单一快照,结论对其他模型的泛化性未验证。
方法与英文摘要

基准用HumanEval和HumanEval-ET。设三组提示条件:NL-simple(一行NFR短语基线)、NL-rich(ISO/IEC 25010对应质量特征的详细自然语言段落)、Structured(同一ISO内容序列化成JSON)。覆盖四类NFR:性能效率、错误处理、代码异味、可读性。每个条件做10个提示变体,固定单一模型快照,用配对非参数检验比较。度量包括Pass@1、ET-Pass@1、per-10-LOC静态质量缺陷密度和跨变体STDEV。

In LLM-based code generation, Non-Functional Requirements (NFRs) are often specified as terse one-line phrases. We ask whether grounding those specifications in ISO/IEC 25010 Quality Model, either as rich natural-language prose (NL-rich) or as structured JSON (Structured), improves code generated on HumanEval/HumanEval-ET compared to a RobuNFR-style one-line baseline (NL-simple). We evaluate four NFRs (performance, error handling, code smell, readability) with ten prompt variations per condition under a fixed model snapshot and paired non-parametric analysis. Primary finding: ISO-grounded enrichment improves static quality proxies (unreadability density falls across all four NFRs (e.g., Performance 0.88 -> 0.69 for NL-rich)) and reduces sensitivity to prompt wording, but does not reliably improve functional correctness; for error handling, extended-test pass rate decreases, suggesting tension between defensive coding patterns and exact-output benchmarks. Secondary finding: when ISO content is held constant, NL-rich and Structured differ negligibly in correctness (|delta| <= 0.023), indicating that semantic content matters more than JSON-vs-prose format. Practitioners should invest in standard-grounded NFR content rather than serialization form. A fully traceable replication package is provided.

UI 与 GUI Agent(1 篇)

UI 与 GUI Agent 8/30

LegacyWorld: Atomicity-Aware Evaluation of GUI Agents for Legacy Workflows

遗留GUI代理测评只看完成率不够:失败运行必须不留脏状态:如果你要把computer-use代理放进医疗、行政或企业遗留系统,完成率高不代表安全:一次失败或“名义成功”的运行可能已经把无效状态写进业务记录。LegacyWorld的价值在于把原子性纳入测评,用28个Windows遗留工作流检查代理是否既完成任务,又不留下脏状态。

两句看懂

现有computer-use基准不检查失败运行是否在遗留系统中留下无效持久状态;该工作对28个Windows工作流引入原子性测评,把每次运行标记为有效成功、无效成功、有效失败、无效失败四类。跨6个托管代理的测评显示,有效完成、安全失败与非原子副作用是三种独立操作剖面,录屏生成提示词与手写提示词在完成率和状态有效性上存在可观察差异。

核心判断

在遗留GUI工作流中,有效完成、安全失败与非原子副作用是三种独立操作剖面;只看完成率无法捕捉状态污染风险。该结论来自6个托管代理在28个Windows工作流上的四类原子性标签测评。

关键要点

1. 旧假设只问“任务是否完成”,不验证失败或名义成功是否留下无效持久状态;在医疗或行政记录里,这会静默污染数据。 2. 方法把28个Windows工作流合同化,固定初始/目标状态与任务专属验证器,在独立虚拟机运行后合并代理上报与独立状态验证;对照手写提示词和录屏生成提示词。 3. 结果是6个托管代理呈现三种独立剖面:有效完成、安全失败、非原子副作用;工程上应把状态验证器和原子性验收测试列为上线门槛。

证据与结果

评测对象是28个Windows GUI工作流,由医疗、行政、企业等域专家识别与审核,含状态变更型与外部接地型两类任务;外部接地任务在生产或暂存系统完成设计验证,全部执行在隔离虚拟机中。指标不是单一成功率,而是有效成功、无效成功、有效失败、无效失败四类标签。对比条件是专家手写提示词与录屏生成提示词,样本为6个托管computer-use代理。主要发现是三种操作剖面相互独立,两种提示来源在完成率与状态有效性上有可观察差异;公开摘录未提供逐代理具体数值。

打开论文原文
它要解决什么
当前computer-use代理执行遗留GUI工作流时,能否在不产生无效持久状态的前提下完成任务?把专家手写提示词换成从录屏自动生成的提示词,会不会改变完成率与状态有效性?
研究路径
机制关键是“合同化+独立验证”。专家先把工作流写成任务合同,明确自然语言指令、初始状态、目标状态、运行时参数、返回值模式和任务专属验证器。每次运行放在独立虚拟机,结束后不只看代理自称结果,还合并独立状态验证,输出四类原子性标签。录屏生成提示词时只抽取操作步骤正文,初始/目标状态与验证器保持固定,避免把录屏误认为正确性oracle。
这对工程意味着什么
第一步先给每条遗留工作流补状态验证器和原子性验收测试,再谈代理上线;因为完成率只衡量最终结果,检不出失败运行留下的无效持久状态。要避开的捷径是把demo通过当作部署判据:demo成功不等同于失败安全。
证据定位
跨6个托管代理,有效完成、安全失败与非原子副作用呈现三种相互独立的操作剖面;这说明单一完成率不能覆盖状态污染风险。录屏生成提示词与手写提示词在完成率和状态有效性上产生可观察差异。公开摘录未给出逐代理具体数值,因此不能引用更细的排名或差距。(筛选维度:可复核评测、GUI Agent 方法)
适用边界
基准规模为28个工作流,集中在Windows GUI遗留类场景;任务由特定域专家识别,样本代表性受参与专家领域覆盖限制;公开摘录未提供逐代理具体数值,无法评估定量边界与跨系统泛化范围。
方法与英文摘要

基准包含28个Windows GUI工作流,来自医疗、行政、企业等域专家识别与审核,覆盖遗留及遗留类应用。每条工作流被编码成任务合同:自然语言指令、初始状态、目标状态、运行时参数、返回值模式和任务专属验证器。每次测评在独立虚拟机运行,结束后合并代理上报结果与独立状态验证,打出四类标签:有效成功、无效成功、有效失败、无效失败。对照条件是专家手写提示词与录屏生成提示词;录屏只提供操作步骤正文,初始/目标状态与验证器固定不变。共测评6个托管computer-use代理。

Legacy and legacy-like enterprise systems often remain difficult to modernize because critical workflows expose limited programmable interfaces and still require manual GUI interaction. This paper reports a pre-deployment evaluation study motivated by the development of legacy-use, an industry-oriented framework for automating such workflows with multimodal LLM agents. During framework development, domain experts helped identify stateful workflows where successful demos are not sufficient: a failed agent run may still leave persistent invalid changes in business or healthcare records. We therefore evaluate computer-use agents using atomicity: a run should either complete the intended workflow correctly or fail without unintended persistent side effects. We construct a domain-expert-informed benchmark of 28 Windows GUI workflows, each specified with an initial state, goal state, and task-specific validator. We compare expert-crafted prompts with prompts generated from screen recordings of expert golden-path executions. Across six hosted computer-use agents, our results show that useful completion, safe failure, and non-atomic side effects are distinct operational profiles. We conclude that workflow capture, state validators, and atomicity-aware acceptance tests should be first-class requirements for AI-based legacy workflow automation.

个人知识与本体(1 篇)

个人知识与本体 8/30

MemoryLake on MemoryArena: A Matched Study of Agent Memory Backends

四系统匹配对比揭示记忆后端效能边界:MemoryArena框架下,MemoryLake与Mem0、向量RAG及长上下文在五领域做匹配系统对比。数学SR 9/40、物理12/20居首;旅行规划所有系统SR均为零,购物仅长上下文1/150。宏平均SR 20.5%对最优对照13.6%,但样本量有限,置信区间重叠,无显著性检验。

两句看懂

多数记忆基准只测后验召回而非跨会话任务完成;MemoryArena引入有序子任务闭合循环,本研究在此框架下对四种记忆后端做匹配对比。固定框架与模型别名,仅记忆集成不同;MemoryLake在数学(9/40)、物理(12/20)、渐进检索SR最高,宏平均20.5%对最优对照13.6%,但旅行规划四系统SR均为零,置信区间重叠。

核心判断

在相同框架与模型下,MemoryLake在三个领域SR最高、宏平均20.5%对最优对照13.6%;来自MemoryArena匹配对比,但样本有限、置信区间重叠,不支持跨基准最优或因果优势声明。

关键要点

1. 既有召回基准(LoCoMo、LongMemEval等)只测信息能否被检索,不验证跨会话行动依赖;MemoryArena以有序子任务构成闭合循环,早期子任务输出成为后期前提或约束,要求记忆后端支持端到端多步完成而非单次召回。 2. 匹配协议将四系统固定在同一框架、gpt-5-mini别名与评分代码下,仅记忆集成为受控变量;每个后端捆绑写入、检索、整合、预算与提示组装,属系统级对比而非表示层消融,也非资源匹配实验,结论不可推广至成本维度。 3. MemoryLake在数学(9/40)、物理(12/20)、渐进检索(4/20)SR最高,宏平均20.5%对最优对照13.6%;旅行规划四系统SR均为零,购物最高仅长上下文1/150;样本量有限、置信区间重叠、无配对显著性检验,结论为有界点估计,不支持跨基准最优声明。

证据与结果

MemoryArena五领域:数学40样本、物理20、购物150、渐进检索20(另有全量221条仅MemoryLake独立运行,不作基线对比);旅行规划样本量原文未明确列出。主指标为端到端SR;辅助指标:旅行软过程分、购物步骤匹配。关键数字:数学9/40、物理12/20、渐进检索4/20均为MemoryLake最高;旅行规划四系统SR=0;购物长上下文1/150最高,MemoryLake第三。宏平均SR 20.5%对13.6%。评分依赖GPT法官;置信区间重叠,无配对显著性检验。

打开论文原文
它要解决什么
在相同智能体框架和模型别名下,结构化多轨记忆后端在跨会话多步任务中的端到端成功率是否优于向量RAG和长上下文方案?
研究路径
MemoryLake维护三类并行轨道:已确认结论、支撑证据、可复用经验,各轨道采用不同留存策略。写入时按类分轨存储,检索时跨轨查询,整合与预算控制决定进入提示的内容。对照系统:Mem0托管记忆、text-embedding-3-small向量块RAG、长上下文平铺历史轨迹;四系统记忆集成之外共享所有组件。
这对工程意味着什么
按任务类型分域评估记忆后端SR,避免仅用宏平均掩盖全系统失败域(如旅行规划SR=0);匹配协议能有效隔离后端差异,但资源消耗不匹配时比较结论不可直接推广。
证据定位
MemoryLake在数学(9/40)、物理(12/20)、渐进检索(4/20)SR最高;旅行规划四系统SR均为零;购物长上下文1/150最高、MemoryLake排第三。宏平均SR:MemoryLake 20.5%对最优对照13.6%,置信区间重叠。(筛选维度:置信度与不确定性、可复核评测)
适用边界
样本量有限(数学40、物理20、购物150、渐进检索20),置信区间重叠,无配对显著性检验;未做资源匹配对比;评分依赖GPT法官存在偏差风险;渐进检索221条全量运行不作基线对照,结论有界于本研究共享评估集。
方法与英文摘要

基准:MemoryArena五领域(数学40样本、物理20、旅行规划、购物150、渐进检索20)。四系统共享同一智能体框架、gpt-5-mini模型别名、任务样本与评分代码,仅记忆集成不同:MemoryLake结构化多轨、Mem0、text-embedding-3-small向量RAG、同模型长上下文。每个后端捆绑写入、检索、整合、预算与提示组装,属系统级对比而非表示层消融。

Most agent-memory benchmarks test post-hoc recall, whereas MemoryArena evaluates whether memory supports interdependent, multi-session task completion. We compare MemoryLake, a structured multi-track memory backend, with Mem0, text-embedding-3-small vector RAG, and a long-context control across all five MemoryArena domains. The systems share the same agent framework, requested gpt-5-mini model alias, task samples, and scoring code; the memory integration is the intentionally changed component. Because each backend bundles write, retrieval, consolidation, budgeting, and prompt-assembly choices, the study is a matched system-level comparison, not a representation-only ablation or a cost-matched experiment. On the shared evaluation sets, MemoryLake has the highest observed success rate (SR) in mathematics (9/40), physics (12/20), and progressive retrieval (4/20). Every system has zero SR in travel planning, and web shopping yields a single bundle-level success (long context, 1/150); MemoryLake ranks third on both the travel soft process score and shopping step match. Following MemoryArena's suite-level convention, a post-hoc equal-weight average over the five SRs is 20.5% for MemoryLake versus 13.6% for the best comparator. These are point estimates: sample sizes are modest, confidence intervals overlap, and we do not report paired significance tests. A separate MemoryLake-only run over all 221 progressive queries yields a failure-counted SR of 26.7% (59/221) and is not a baseline comparison. The results support a workload-dependent view of memory backends and an observed lead among the four evaluated systems on the shared sets; they do not establish benchmark-wide state of the art or a causal advantage of representation structure.

人机协同与对齐(0 篇)

本轮没有通过深读证据门的重点论文。

本轮分类概览

同一论文只归入一个最先命中的赛道,避免重复计数;“新增候选”只统计首次展示的论文。

赛道新增候选重点
形式化与程序验证00
软件工程与仓库智能32
代码质量与优化11
UI 与 GUI Agent21
个人知识与本体11
人机协同与对齐00

近一个季度监测日历

北京时间。绿色表示有可阅读的新候选,灰蓝表示已监测但无新增,橙色表示部分降级;“无记录”不等于失败。

2026 年 6 月

1无记录2无记录3无记录4无记录5无记录6无记录7无记录8无记录9无记录10无记录11无记录12无记录13无记录14无记录15无记录16无记录17无记录18无记录19无记录20无记录21无记录22无记录23无记录24无记录25无记录26无记录27无记录28无记录29无记录30无记录

近 14 次监测窗口

仅展示公开源的聚合运行状态,不含提示词、全文或个人数据。

本轮新增候选(7 篇)

按赛道、评分和日期展开;中文标签用于导航,英文摘要用于核验。已展示过的旧候选不会每日重复。

形式化与程序验证(0 篇)

本轮该赛道没有候选论文。

软件工程与仓库智能(3 篇)

软件工程与仓库智能 · 6/30 · 2026-08-14ATLAS:抽象与自动机学习发现智能体策略结合轨迹抽象与自动机学习,从智能体轨迹推断可解释状态模型,支持分析成功路径与失败循环ATLAS: Discovering Agent Strategies through LLM-Guided Abstraction and Automata Learning

Large Language Model (LLM)-based agents are increasingly used for complex tasks such as software testing and cybersecurity assessment. While these agents demonstrate impressive capabilities, their behavior is difficult to understand, explain, and analyze. Existing evaluations focus mainly on task success and execution traces, offering limited insight into the strategies employed by the agent. We present ATLAS (Automata Learning for Agent Trajectory Analysis and Strategy Discovery), an approach for recovering interpretable behavioral models from agent trajectories. ATLAS combines trace abstraction with automata learning to infer finite-state models that capture observed agent-environment interaction strategies. These models provide human-interpretable insights and support automated analyses of recurring behaviors, decision points, successful task-completion paths, and failure loops. As a proof of concept, we apply ATLAS to trajectories generated by an LLM-based penetration-testing agent. The resulting models expose high-level behavioral strategies for exploiting vulnerable machines that are difficult to identify from raw execution traces alone. We discuss how learned behavioral models can support explainability, model-guided exploration, auditing, and analysis of agentic systems. We further demonstrate symbolic model-based knowledge transfer from powerful frontier models to compact language models. In addition, we show how model transformations can derive concise explanations of agent behavior in a penetration-testing case study comprising 12 vulnerable machines. ATLAS highlights a new opportunity for model-driven engineering: transforming agent trajectories into explicit behavioral models that enable systematic understanding and analysis of otherwise opaque AI agents.

阅读 arXiv 原文
软件工程与仓库智能 · 3/30 · 2026-08-14重思自动程序修复:复杂度、定位与成本实证分析缺陷复杂度、故障定位、推理设置与成本如何影响LLM修复性能Rethinking Automated Program Repair: The Impact of Bug Complexity, Fault Localization, and LLM Cost-efficiency

Background: Software bugs remain a critical challenge in development, necessitating effective Automated Program Repair (APR) techniques. While Large Language Model (LLM)-based APR systems have shown promise, prior studies primarily focus on overall repair effectiveness. The effects of bug complexity, fault localization, reasoning settings, and repair cost-effectiveness remain insufficiently explored. Aims: This study presents a comprehensive empirical analysis of LLM-based APR, focusing on how repair performance is shaped by bug complexity, fault localization, reasoning settings, and costs. Method: We evaluate two APR techniques (ChatRepair and CodeCorrector) using three LLMs (DeepSeek, GPT, and Llama), and examine their performance across diverse levels of bug complexity and localization strategies through a multi-dimensional empirical framework and statistical analysis. Results: Although structurally complex bugs and imprecise fault localization make repair more challenging, LLM-based APR techniques still achieve competitive repair effectiveness. Imprecise fault localization can substantially enlarge the performance gap between APR techniques. Furthermore, higher-cost LLMs and stronger reasoning settings do not consistently yield better cost-efficiency, revealing a nontrivial trade-off between repair effectiveness and computational cost. Conclusions: Over 50% of moderately complex bugs can be repaired by low-cost LLM-based APR techniques. The repair effectiveness gap between APR techniques becomes larger as fault localization becomes less precise. GPT-5 repairs 7 and 39 more complex bugs than DeepSeek-V4-pro and DeepSeek-V3.2, respectively; whereas the total repair cost of DeepSeek-V3.2 shows the best cost-efficiency performance.

阅读 arXiv 原文
软件工程与仓库智能 · 7/30 · 2026-08-14智能体编码时代人机协作的工程信号对vLLM与SGLang共33,228个合并PR的纵向分析,观察吞吐、周期、多样性等七项工程指标Engineering Signals of Human-AI Collaboration in the Agentic Coding Era: A Longitudinal Analysis of 33,228 Pull Requests from vLLM and SGLang with Implications for Biomedical AI Agents and Bioinformatics Pipeline Developmen

The rapid adoption of AI coding assistants and autonomous agentic development systems has coincided with major changes in the pace and structure of open-source software engineering. Yet empirical longitudinal evidence of these changes at the team level remains limited. We present a descriptive longitudinal analysis of seven engineering metrics: pull request (PR) throughput, cycle time, contributor diversity, PR comment density, merge rate, new-author participation, and PR size. Metrics were computed from all merged PRs in two high-velocity AI infrastructure repositories, vLLM (February 2023-June 2026; 18,290 PRs) and SGLang (January 2024-June 2026; 14,938 PRs). We segment development into four eras aligned with major changes in AI-assisted software development and examine human- and bot-authored activities. Both projects show substantial increases in development velocity and AI-developer collaboration signals. PR throughput increased 21x in vLLM and 17.9x in SGLang, while bot-authored PRs accounted for less than 0.2% of this growth, indicating that the increase was overwhelmingly human-driven. In the latest era, median cycle time was 1.04 days for vLLM and 0.62 days for SGLang, while P90 cycle times reached 16.8 and 14.3 days, respectively. Monthly unique authors increased steadily in both projects, suggesting broader contributor participation. PR comment density increased 4.2x in vLLM and 3.8x in SGLang, with bot comments contributing an estimated 15-20% of the increase. In contrast, PR size remained relatively stable across eras. Overall, AI-assisted development is associated with higher throughput, broader contributor participation, and increased AI-developer collaboration signals in high-velocity open-source software development.

阅读 arXiv 原文

代码质量与优化(1 篇)

代码质量与优化 · 6/30 · 2026-08-13ISO规范的非功能需求能否改善代码生成以ISO/IEC 25010丰富NFR可改善静态质量并降低提示词敏感性,但功能正确性提升不确定Does ISO-Grounded NFR Specification Improve LLM Code Generation? A Comparison of Rich and Structured Interventions against a Natural-Language Baseline

In LLM-based code generation, Non-Functional Requirements (NFRs) are often specified as terse one-line phrases. We ask whether grounding those specifications in ISO/IEC 25010 Quality Model, either as rich natural-language prose (NL-rich) or as structured JSON (Structured), improves code generated on HumanEval/HumanEval-ET compared to a RobuNFR-style one-line baseline (NL-simple). We evaluate four NFRs (performance, error handling, code smell, readability) with ten prompt variations per condition under a fixed model snapshot and paired non-parametric analysis. Primary finding: ISO-grounded enrichment improves static quality proxies (unreadability density falls across all four NFRs (e.g., Performance 0.88 -> 0.69 for NL-rich)) and reduces sensitivity to prompt wording, but does not reliably improve functional correctness; for error handling, extended-test pass rate decreases, suggesting tension between defensive coding patterns and exact-output benchmarks. Secondary finding: when ISO content is held constant, NL-rich and Structured differ negligibly in correctness (|delta| <= 0.023), indicating that semantic content matters more than JSON-vs-prose format. Practitioners should invest in standard-grounded NFR content rather than serialization form. A fully traceable replication package is provided.

阅读 arXiv 原文

UI 与 GUI Agent(2 篇)

UI 与 GUI Agent · 8/30 · 2026-08-14从GUI动作推断用户意图的智能体基准首个通过连续意图-动作轨迹评估主动移动智能体的基准,含72,511条意图与70万+动作Act2Intention: A Benchmark For Developing Active Mobile Agents Through Inferring User Intention from GUI Actions

Mobile GUI Agents powered by multimodal large language models (MLLMs) show promise in human-computer intelligence. However, current research primarily focuses on reactive task execution while lacking a comprehensive understanding-prediction-execution process for user intentions, which are the core requirements of active agents. In this paper, we propose the Act2Intention framework that builds an active mobile agent by integrating understanding, predicting user intentions, and executing decisions. First, we construct the Act2Intention Bench through data collection and validated generation, comprising 72,511 intentions and over 700,000 actions across 52 apps, thereby establishing the first benchmark for evaluating proactive agents via continuous intention-action trajectories. We further develop the Act2Intention Agent, achieving proactive services through Proactive-oriented Intention Understanding, Personalized Proactive Intention Prediction, and Experience-guided Intention Execution. Experimental results show that supervised fine-tuning on Act2Intention Bench yields absolute improvements of +32.0 Acc-S, +10.25 Acc-S, and +6.9 SSR points over non-fine-tuned counterparts under the same agent framework for intention understanding, prediction, and execution, respectively. This success underscores the necessity and value of the Act2Intention Bench, which establishes a standardized platform for developing and evaluating proactive agents and consequently paves the way for research on intention-driven human-computer interaction.

阅读 arXiv 原文
UI 与 GUI Agent · 8/30 · 2026-08-14遗留工作流GUI智能体的原子性评测要求GUI智能体要么完整完成任务、要么不留下持久副作用,基于28个Windows工作流评测LegacyWorld: Atomicity-Aware Evaluation of GUI Agents for Legacy Workflows

Legacy and legacy-like enterprise systems often remain difficult to modernize because critical workflows expose limited programmable interfaces and still require manual GUI interaction. This paper reports a pre-deployment evaluation study motivated by the development of legacy-use, an industry-oriented framework for automating such workflows with multimodal LLM agents. During framework development, domain experts helped identify stateful workflows where successful demos are not sufficient: a failed agent run may still leave persistent invalid changes in business or healthcare records. We therefore evaluate computer-use agents using atomicity: a run should either complete the intended workflow correctly or fail without unintended persistent side effects. We construct a domain-expert-informed benchmark of 28 Windows GUI workflows, each specified with an initial state, goal state, and task-specific validator. We compare expert-crafted prompts with prompts generated from screen recordings of expert golden-path executions. Across six hosted computer-use agents, our results show that useful completion, safe failure, and non-atomic side effects are distinct operational profiles. We conclude that workflow capture, state validators, and atomicity-aware acceptance tests should be first-class requirements for AI-based legacy workflow automation.

阅读 arXiv 原文

个人知识与本体(1 篇)

个人知识与本体 · 8/30 · 2026-08-14跨五域匹配对比智能体记忆后端在MemoryArena五域与多种记忆后端对比,MemoryLake在数学、物理等任务成功率最高MemoryLake on MemoryArena: A Matched Study of Agent Memory Backends

Most agent-memory benchmarks test post-hoc recall, whereas MemoryArena evaluates whether memory supports interdependent, multi-session task completion. We compare MemoryLake, a structured multi-track memory backend, with Mem0, text-embedding-3-small vector RAG, and a long-context control across all five MemoryArena domains. The systems share the same agent framework, requested gpt-5-mini model alias, task samples, and scoring code; the memory integration is the intentionally changed component. Because each backend bundles write, retrieval, consolidation, budgeting, and prompt-assembly choices, the study is a matched system-level comparison, not a representation-only ablation or a cost-matched experiment. On the shared evaluation sets, MemoryLake has the highest observed success rate (SR) in mathematics (9/40), physics (12/20), and progressive retrieval (4/20). Every system has zero SR in travel planning, and web shopping yields a single bundle-level success (long context, 1/150); MemoryLake ranks third on both the travel soft process score and shopping step match. Following MemoryArena's suite-level convention, a post-hoc equal-weight average over the five SRs is 20.5% for MemoryLake versus 13.6% for the best comparator. These are point estimates: sample sizes are modest, confidence intervals overlap, and we do not report paired significance tests. A separate MemoryLake-only run over all 221 progressive queries yields a failure-counted SR of 26.7% (59/221) and is not a baseline comparison. The results support a workload-dependent view of memory backends and an observed lead among the four evaluated systems on the shared sets; they do not establish benchmark-wide state of the art or a causal advantage of representation structure.

阅读 arXiv 原文

人机协同与对齐(0 篇)

本轮该赛道没有候选论文。