公开论文雷达

公开 arXiv 研究简报 · 2026-10-01T00:56:33.216727+00:00

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

八篇都在说:信号好看不等于真管用

这批卡片的共同动作是换检验口径。先读《合并不等于验证》那篇,它给的改动最省事——代理交的性能修复PR,合并状态不算证据,自己重跑三次再说。接着读LoLBench,它把代理失败归到代码定位而不是生成,补文件树和API规范能把解决率拉高16到22个百分点。其余按你手上做的是哪类系统往下挑。

推荐阅读顺序

  1. 2609.37985:今天就能改的习惯:别把已合并当性能已验证,30个合并修复里9个无提升或退化。
  2. 2609.37143:决定你怎么投喂代理:瓶颈在定位不在生成,先补目标文件树和接口规范再让它写。
  3. 2609.36783:拦住一条常见捷径:探针能读出代码对错,但照这个方向引导没稳定收益,反向还更差。
  4. 2609.37203:前三篇都在说要查过程,这篇给出怎么查:中间结论先过验证才能当前提。
  5. 2609.31903:同样是门禁,但换成多人协作场景:GitHub加确定性CI,合并前机械核验。
  6. 2609.36595:做机器人或长程任务再读:记忆该存任务状态,不是堆历史画面。
  7. 2609.32491:要把大模型接进符号推理器时读:它给的词汇关系常只对单题成立。
  8. 2609.24348:放最后:六阶段流程和仓库内规范可以参考,但摘录没有评分、样本量和基线。
共性方法
八张卡几乎都在把一个表面信号拆开重测:PR合并状态、最终答案对错、NLI标签、探针读数、保留下来的历史画面。重测之后数字多半掉下来——最强代理解决率14%,23个被拒声称只6个成立,30个合并修复里9个无提升或退化。
关键分歧
发现信号不可靠之后怎么办,两派分得很开。一派加门禁或补输入:LoLBench补文件树和API规范,Proof-R1逐步做UNSAT验证,Choir用CI机械核验,AI-SDLC把约束写进仓库。另一派只报告此路不通:扩散模型探针引导没稳定收益,LLM生成的词汇关系对证明只有中等帮助。
选择准则
按你眼下在信哪种信号来挑:信合并状态读37985;信代理能自己找到代码读37143;想拿内部表征做修复读36783;要搭可审计流程读37203和31903。24348证据只到框架,别拿它当依据。

重点深读(8 / 8 篇)

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

形式化与程序验证 7/30

Explaining Textual Entailment with Lexical Entailments: Using LLMs to Supply Lexical Relations for Formal Proofs

大模型生成词汇解释支撑逻辑证明,效果有限:如果你打算把大模型当词汇知识库接入符号证明器,这条结论直接关系到你的系统设计:测试显示,即便是闭源商用大模型,生成结构化词汇蕴含关系仍然吃力,注入自然逻辑证明器LangPro后对证明成功率的提升只是中等水平。论文构建LEX-NLI数据集,用「生成质量内部评测+证明成功率外部评测」两步检验了这条神经符号管道。

两句看懂

旧评测只看NLI标签对错,不检查LLM是否给出了能支撑该标签的词汇知识;论文让LLM生成结构化词汇蕴含并注入自然逻辑证明器LangPro做形式证明。测试显示,闭源大模型在LEX-NLI生成任务上仍表现吃力,生成的关系常只部分可靠、偏向单题定制而非通用知识,对证明成功率的提升只是中等水平。

核心判断

LLM能为NLI提供可用于形式证明的词汇知识吗?答案是有限。生成的词汇蕴含常不完整或只对单题成立,对LangPro证明成功率的提升只是中等。证据来自LEX-NLI内部评测和LangPro外部证明实验的双重结果。

关键要点

1. 旧假设:NLI标签正确就代表推理合理,但老评测不检查模型是否产出真正支撑标签的结构化词汇知识(如chinchilla⊑small animal),掩盖了「蒙对标签」的风险。 2. 方法与受控检验:人工构建必要且充分的多参考词汇蕴含集LEX-NLI(源自SNLI、SICK的蕴含类问题),先做LLM生成质量的内部评测(按模型家族与规模比较),再把较好模型的输出注入LangPro做外部证明评测。 3. 决定性结果:闭源商用大模型在LEX-NLI上依旧困难,注入后关系常只部分可靠、多为单题定制,证明成功率提升仅为中等——接入符号证明器前必须先做知识质量校验。

证据与结果

数据来自SNLI和SICK中的蕴含类问题,人工标注必要且充分的多参考词汇蕴含集合,构成LEX-NLI测试集。内部评测比较多个LLM按家族与规模生成结构化词汇解释的质量。外部评测挑选表现较好的LLM作为知识库生成器,注入LangPro检验是否足以完成形式证明。结果有两点:闭源商用LLM在LEX-NLI生成上仍困难;证明阶段生成的关系常部分可靠、偏向单题定制,对证明成功率的贡献为中等水平。

打开论文原文
它要解决什么
LLM能否找出NLI推理所需的全部词汇蕴含关系,并让这些关系真正支撑形式化证明?
研究路径
机制分三步。第一步,给LLM一个NLI问题(前提+假设+蕴含标签),要求同时输出推理标签和结构化词汇蕴含集合。第二步,将输出与人工多参考LEX集合比对评分,这是内部评测,按模型家族和规模分析生成质量。第三步,把生成的词汇关系当作知识库条目注入LangPro,运行证明器检查能否构造出完整形式证明,这是外部评测,检验知识的下游可用性。
这对工程意味着什么
第一个行动:把LLM当词汇知识库接入符号证明器之前,先用多参考标注集做内部质量检查,再做下游证明成功率检查,两步都不能省。要避免的捷径:只看NLI标签准确率就判断LLM推理可靠——标签蒙对不代表模型掌握了支撑推理的词汇知识,这是容易被忽略的误导性指标。
证据定位
内部评测显示,即使是闭源商用大模型,在LEX-NLI生成任务上表现仍然吃力。外部评测显示,注入LangPro后,生成的词汇关系往往只部分正确(partially sound),且常常是为单个问题量身定制的答案,而非通用有效的词汇知识,对证明成功率的提升只是中等水平。(筛选维度:形式化验证、可复核评测)
适用边界
边界有三条。只覆盖蕴含(entailment)标签的问题,不含矛盾和中立。只针对结构化词汇蕴含这一种解释形式,不代表其他解释形式的表现。数据来自SNLI和SICK两个来源,规模和覆盖范围受人工标注约束。
方法与英文摘要

论文从SNLI和SICK中筛选蕴含类问题,人工标注必要且充分的多参考词汇蕴含集合,构成LEX-NLI测试集。评测分两步:先让LLM针对「前提+假设+蕴含标签」生成推理标签和结构化词汇解释,与人工多参考答案比对评分(内部评测,按模型家族和规模分析);再挑选表现较好的模型,把其生成的词汇关系当作知识库条目注入自然逻辑定理证明器LangPro,检查能否构造出完整形式证明(外部评测)。

Large Language Models (LLMs) are highly capable of natural language reasoning and appear to store a great deal of lexical knowledge, but it is still unclear how much of this knowledge they actually use when reasoning, and whether they use it in the right way. On the other hand, logic-based Natural Language Inference (NLI) systems provide transparent and formally grounded reasoning, but they need to be supplied with rich lexical knowledge to prove inferences beyond purely logical ones. In this paper, we evaluate whether LLMs can identify all lexical knowledge needed to solve NLI problems and how much this knowledge contributes to proof search in a logic-based NLI system. Our research focuses exclusively on structured lexical entailments (e.g., chinchilla$\sqsubseteq$small animal) as a proxy for structured explanations for NLI problems with an entailment label. First, we curate a dataset for a new task of explaining sentential entailments with a set of lexical entailments. The dataset is used to intrinsically evaluate LLMs on generating structured lexical explanations. Then, we use NLI as an extrinsic evaluation in a simple neuro-symbolic setting, assessing whether LLMs can supply sufficient lexical relations to LangPro, a natural-logic theorem prover for natural language. The results show that the proposed task remains challenging even for hosted proprietary LLMs, and that their contribution to theorem proving is moderate: generated relations are often only partially sound and may be tailored to the specific NLI problem rather than representing generally valid lexical knowledge.

形式化与程序验证 7/30

Choir: An Open Protocol for Distributed Multi-Agent Autoformalization

大规模定理形式化可以不由单一团队承担算力,陌生人用GitHub加确定性门禁就能协作完…:如果你或所在学术组想做大规模自动形式化,却付不起中心化算力账单(Meta FAIR一个项目约3万次agent运行,成本10万至43万美元),这条协议给出一条不用自建算力的复制路径:Choir用开源协议把证明任务发到GitHub,让陌生人各自用自己的LLM订阅认领、证明、提交PR,合并前由确定性门禁机械核验。

两句看懂

现有大规模定理形式化假设单一团队集中运行agent并独自承担算力账单,Meta FAIR一个项目约3万次agent运行、花费10万至43万美元。Choir改用GitHub仓库协调陌生人各自的LLM订阅完成任务,合并前用确定性门禁核验每个提交,并刻意选用与Meta FAIR Atlas库重合的课本讲义以便与中心化结果直接对比。

核心判断

大规模定理形式化可以不靠单一团队集中算力,而是通过GitHub协调陌生人各自的LLM订阅加确定性门禁完成;论文用与Meta FAIR Atlas重合的讲义案例验证协议可运行,但未给出与中心化结果对比的量化数字。

关键要点

1.旧假设:大规模自动形式化必须由单一团队集中调度agent并承担全部算力账单(Meta FAIR约3万次agent运行、10万至43万美元),普通学术组难以复制。2.方法与受控检查:Choir把项目拆成overseer、orchestrator、worker、GitHub Actions确定性门禁四角色,门禁在合并前机械核验定理声明未被篡改且证明通过编译;对照设计选与Meta FAIR Atlas库(26本教材)重合的讲义。3.结果与行动:协议在Yufei Zhao讲义的Lean 4形式化上跑通并公开仓库,但未给出自身量化指标;要做多方可信协作,可复用这套GitHub协调加门禁模式。

证据与结果

测试对象是Yufei Zhao《Probabilistic Methods in Combinatorics》讲义,在Lean 4下形式化,结果仓库公开(yidiq7/ProbMethodCombinatorics);该讲义同时在Meta FAIR Atlas库(26本教材)收录范围内,构成直接对照条件。对照参照为Meta FAIR另一本研究生代数组合教材:约13万行Lean代码、约3万次agent运行、一周时间、成本10万美元(prompt caching)至43万美元(不用)。摘录未给出Choir案例自身的代码行数、通过率或人力投入。

打开论文原文
它要解决什么
大规模定理自动形式化能否不再依赖单一团队的集中算力,而由分散个人的LLM订阅共同完成?
研究路径
orchestrator规划项目并把定理陈述发布为GitHub issue任务;贡献者在issue下评论认领;贡献者用自己的agent和LLM账号在本地证明,从自己fork提交PR;GitHub Actions门禁自动核验被声明的定理陈述是否被篡改、证明是否通过Lean/Isabelle/Rocq编译;门禁通过后orchestrator人工复核并合并。贡献者无仓库写权限,只能评论认领和提交PR。
这对工程意味着什么
第一个行动:复用Choir的GitHub协调加确定性门禁模式来分摊形式化算力成本,让门禁靠机械核验建立信任而非人工审查。要避开的捷径:不要以为门禁通过就能自动合并——论文中merge仍由orchestrator人工复核,跳过这一步会失去审计环节。
证据定位
决定性对比设计:测试案例选Yufei Zhao《Probabilistic Methods in Combinatorics》讲义做Lean 4形式化,同一本讲义也被Meta FAIR的Atlas库(26本教材)收录,使分布式协作结果能与中心化团队结果直接对照;结果仓库公开在GitHub(yidiq7/ProbMethodCombinatorics)。(筛选维度:形式化验证、软件工程方法)
适用边界
摘录仅覆盖单一测试案例(一份讲义的Lean 4形式化),未提供与Meta FAIR中心化结果对比的量化数字(代码行数、通过率、成本),门禁的具体检查规则和失败率也未给出。
方法与英文摘要

协议设四种角色:人类overseer定目标和审计策略,orchestrator agent负责规划、写定理陈述并发布为GitHub issue任务,多个worker贡献者认领任务后在本地用自己的agent和LLM账号证明,从自己fork提交PR,GitHub Actions运行的确定性门禁在合并前重新核验声明未被篡改且证明通过Lean/Isabelle/Rocq编译,最后由orchestrator人工复核合并。全部协调只走issue和PR,不需要中心服务器,贡献者也没有仓库写权限。

AI agents can now formalize entire textbooks and major theorems in proof assistants such as Lean, but current efforts are typically centralized: a single team runs all agents and bears the full computational cost. We introduce Choir, an open protocol for distributed formalization. Choir decomposes a project into tasks that can be completed by independent contributors, each running their own agent with their own LLM subscription, while coordinating entirely through the project's GitHub repository. To support open participation, every contribution is checked by a deterministic gate before merge. Choir supports Lean 4, Isabelle, and Rocq, and is open source and modular, allowing projects to replace individual components or extend the protocol.

形式化与程序验证 7/30

A Lean and Spec-Driven AI-Assisted Software Development Lifecycle for Applied AI Education: The AI-SDLC Approach

六阶段轻量AI-SDLC能把AI编码智能体管回流程,但量化效果暂缺:如果你带团队用AI编程智能体做真实项目,最该担心的不是代码能不能跑,而是需求、架构、测试和实现慢慢散开。这个思路的价值在于把约束写进仓库,用六阶段流程和AGENTS.md、SKILL.md管住智能体;不过本摘录只给出框架和问卷设计,还没有结果数据。

两句看懂

AI编程智能体常能交出可运行代码,但项目推进后需求、架构决策、测试与实现会逐渐脱节,决策依据也变得隐性。论文用六阶段AI-SDLC加仓库内AGENTS.md、SKILL.md把指令层固化下来,并在FHNW课程学生项目中试用;摘录未提供量化结果。

核心判断

六阶段流程加仓库内AGENTS.md/SKILL.md规范,可能有助于遏制需求-架构-测试与实现脱节;当前证据只到框架设计和问卷方法,缺少量化验证。

关键要点

1. 旧问题:智能体产出可运行软件,但需求、架构、测试随项目推进彼此脱节,依据难追溯。 2. 方法:六阶段流程配合AGENTS.md与阶段SKILL.md,用仓库内规范约束智能体,并以课程学生项目和结项问卷做检查。 3. 结果与行动:摘录无评分、样本量或基线对比,不能证明效果;可先采用仓库规范加测试门槛的小范围试点。

证据与结果

验证来自FHNW《AI辅助软件开发》课程的学生团队业务项目,结项后做横截面问卷,题型含闭合量表和开放式问题,覆盖流程支持度、产物可用性、仓库内自我指导感知、AI产出与人工审查互动。摘录未含样本规模、评分结果或对比基线。

打开论文原文
它要解决什么
AI编程智能体生成代码能跑通,但需求、架构、测试为何会逐渐脱节?轻量级流程能否把这些管住?
研究路径
机制是把智能体的自由收进可审查文件:AGENTS.md管全局生命周期,SKILL.md管当前阶段行为,规格、任务状态、架构文档提供上下文。阶段按Bootstrap到Deploy推进,Validate中测试失败会反馈回前序阶段迭代,形成仓库内可追溯的指令层。
这对工程意味着什么
先做一次小试点:为项目写AGENTS.md和阶段SKILL.md,并把测试通过设为进入下一阶段的门槛。要避开的捷径是只靠临时对话提示催进度,不留可审查规范。
证据定位
摘录只描述框架设计和问卷方法,未给出具体问卷评分、样本量或与基线的对比数字。因此可以说它提出了一个可检查流程,但不能据此断定效果优于现有做法。(筛选维度:形式化验证、软件工程方法)
适用边界
样本只来自单一FHNW课程学生团队,反馈依赖自评问卷,缺少独立代码质量或安全性度量;摘录未提供问卷数据,代表性和效果证据有限。
方法与英文摘要

把开发过程切成六个顺序阶段:Bootstrap、Specify、Design、Develop、Validate、Deploy。仓库内放全局AGENTS.md提供生命周期约束,再放阶段专属SKILL.md定义该阶段智能体可做什么;规格、任务状态和架构文档作为上下文依据。场景是FHNW《AI辅助软件开发》课程,学生团队用该流程做业务软件项目,结项后用闭合量表加开放式问题做问卷。

AI coding agents increasingly support software development beyond code completion, including planning, implementation, testing, and repository-level task execution. Their practical use, however, often remains only weakly connected to established software engineering practices. The aim of this work is to develop and evaluate a lightweight, spec-driven lifecycle for governed agentic software engineering. The lifecycle combines established software engineering practices with repository-local guidance through specifications, AGENTS.md, and phase-specific agent skill files. The approach was developed in the context of the FHNW course AI-assisted Software Development and applied by students to business-oriented software use cases. Its educational and practical applicability is explored through a student survey combining closed rating items with open-ended questions. The contribution of this work is a process-oriented framework that enables AI coding agents to operate with bounded autonomy within an explicit, reviewable, and test-oriented software development lifecycle.

形式化与程序验证 6/30

Learning to Prove, Not Just to Answer: Reinforcement Learning from Formal Verification for Natural-Language Logical Reasoning

只看最终答案的强化学习不够,Proof-R1让每步证明先过形式化验证:如果系统要给出可审计的推理链,只奖励“最后答对”会把无效中间步骤也当成功劳;Proof-R1用UNSAT形式化验证门控每一步结论,在ProverQA等三个基准、四种骨干模型上同时提高答案准确率与规则验证率RVR。

两句看懂

结果型强化学习只看最终答案对错,不检查中间结论是否由声明前提推出。Proof-R1用UNSAT验证逐步门控证明状态,在三基准四模型上同时提高准确率和RVR,hard子集证明长度比更接近参考证明的1倍。

核心判断

形式化验证能定义强化学习优化的证明构造过程,而不只是事后打分;支持证据是Proof-R1在准确率与RVR上同时超过Backbone、SFT、GRPO和GoV。

关键要点

1. 旧假设:GRPO只按最终答案给奖励,可能奖励无效或无关步骤。 2. 方法与检查:结构化动作经UNSAT MCFV门控,通过才入证明状态并回溯依赖闭包对齐奖励。 3. 结果与动作:三基准四模型上准确率与RVR同升,hard长度比更接近1倍;给推理链加逐步验证门控。

证据与结果

评测覆盖ProverQA等三个自然语言逻辑推理基准、四种骨干模型;基线含Backbone、SFT、GRPO、GoV;RVR基于schema、语义、规则三类检查;hard子集另看生成证明/参考证明长度比值,用来诊断冗长或残缺。

打开论文原文
它要解决什么
形式化验证能否不止做结果奖励,而是直接定义强化学习要优化的可验证证明构造过程?
研究路径
机制分五步:拆成依赖+结论+谓词规则的动作;用UNSAT MCFV检查依赖且非结论不可满足;只把通过结论写入已验证证明状态;构造候选证明证书图并提取答案支持依赖闭包;用该闭包对齐结果奖励,驱动训练。
这对工程意味着什么
第一步行动:把推理链中间结论接入机器可检验验证门控,再让奖励跟随答案支持依赖闭包。要避免的捷径:不要只因最终答案正确就判定整条推理过程可信。
证据定位
对比对象是Backbone、SFT、GRPO和训练无关agent GoV;指标是答案准确率与RVR。Proof-R1在三个基准、四种骨干模型上两项同时更高;在ProverQA hard子集上,生成证明与参考证明长度比值更接近1倍,对比方法明显偏长或偏短。(筛选维度:形式化验证、可复核评测)
适用边界
摘录中图表文字经OCR混排,具体准确率与RVR数值未能清晰对应到方法名;复现以论文正文表格数字为准,不依赖本摘录图注。
方法与英文摘要

把证明轨迹写成结构化推理动作:依赖、结论、谓词逻辑规则;每个候选动作都做UNSAT-based机器可检验形式化验证MCFV,依赖且非结论不可满足才通过;通过的结论才进入已验证证明状态,再回溯答案支持依赖闭包,把结果奖励对齐到真正支撑答案的依赖。

Large language models (LLMs) are increasingly deployed for natural-language logical reasoning, where the final answer is easy to check but the proof behind it is not. In natural-language logical reasoning, an intermediate conclusion should follow from its premises, and the resulting derivation should support the final answer. Existing methods lack machine-checkable verification of intermediate conclusions and answer-supporting proof dependencies, so they may assign credit to invalid or answer-irrelevant steps. We propose Proof-R1, an RL framework from formal verification that trains LLMs to construct verifiable proofs for natural-language logical reasoning. Proof-R1 admits a generated conclusion into the verified proof state only when the corresponding reasoning action satisfies the proof obligations through UNSAT-based machine-checkable formal verification. Proof-R1 also recovers the answer-supporting dependency closure to trace the proof structure of the final answer and align outcome credit with the proof dependencies. Experiments demonstrate that Proof-R1 improves answer accuracy across three logical reasoning benchmarks and four backbone models and outperforms training-free agents and training-based methods in terms of reasoning-process verifiability.

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

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

LoLBench: Evaluating Coding Agents with Long-Horizon Proposals on Large Software Systems

代理做大型系统改造,卡在找不到代码,不是只会写错代码:如果你的团队想让编码代理直接读长篇增强提案并改大型系统,这个基准说明瓶颈常在前置定位,而不是最后一段生成。LoLBench用100个真实提案任务测试28个代理;最强代理只解决14%,补充参考文件树与API规范后最高到34%。

两句看懂

以往基准多给出详细规格或局部缺陷描述,较少测试代理从长篇增强提案中自行定位改动范围。LoLBench让28个代理跑100个真实提案任务,最强代理只解决14%,补充参考文件树与API规范后最高到34%。

核心判断

编码代理还不能可靠地把长篇提案转成正确实现:28个代理中最强只解决14%,F2P 52.7%;代码定位不全是主要失败原因。

关键要点

1. 旧假设:给足规格或局部缺陷范围,代理失败主要来自实现;但长篇提案要求先自行推导改动范围。2. 方法与对照:100个任务、29个系统、5个领域;提案均约5000词,系统均约240万行,参考PR均改约5500行;对28个代理做全流程评测,并对照提供参考文件树与API规范。3. 结果与动作:最强代理解决率14%、F2P 52.7%;失败主因是代码定位不全;补充文件树与API规范后解决率提高16-22个百分点、最高34%,应先补定位输入再编码。

证据与结果

基准含100个任务,来自29个系统、5个领域,多语言。系统平均约240万行代码,提案平均约5000词,参考PR平均改约5500行。指标是解决率和F2P通过率:最强代理解决率14%,F2P 52.7%;失败分析指向代码定位不全;加入参考文件树与API规范后,解决率提高16-22个百分点,相对提升2.4-17倍,最高34%。

打开论文原文
它要解决什么
面对平均约5000词的增强提案和平均约240万行代码的系统,编码代理能否自己理解意图、定位改动范围并完成正确实现?
研究路径
每个任务给代理一份人类撰写的增强提案,里面有用户意图和高层设计。代理要在约240万行级系统里自己找受影响模块,再生成约5500行级实现。部分实验额外给参考文件树与API规范,用来比较定位辅助前后的解决率;最后用Fail-to-Pass测试和失败归因分析确认瓶颈。
这对工程意味着什么
第一动作:给代理长篇提案前,先补目标文件树与接口规范,再让它进入编码。要避开的捷径:不要靠加长上下文或扩大补丁规模来判断代理能力,这些分数不能说明它真的会定位代码。
证据定位
28个代理中最强者解决率14%,F2P通过率52.7%。失败分析显示主要瓶颈是代码定位不全。补充参考文件树与API规范后,解决率提高16-22个百分点,相对提升2.4-17倍,最高到34%。(筛选维度:形式化验证、可复核评测、软件工程方法)
适用边界
证据只覆盖100个任务、29个系统、5个领域,且都采用增强提案流程的大型项目,例如CPython。对没有正式提案文化或小型项目,结论是否适用未在材料中验证。
方法与英文摘要

LoLBench收集100个任务,覆盖29个软件系统、5个领域,多语言。每个任务配人类撰写的增强提案,平均约5000词;系统平均约240万行代码,参考PR平均修改约5500行。评测让28个代理在相同任务上跑从提案到实现的全流程,并额外对照提供参考文件树与API规范后的效果。

Modern coding agents can deliver increasingly large repository-level changes, and recent benchmarks reflect this by emphasizing long-horizon tasks with large reference implementations. Many benchmarks evaluate coding agents' implementation capability to produce correct code edits from detailed specifications. However, practical modular development tasks also require the perception capability of grounding user intent and high-level design to derive a specification. We introduce LoLBench to evaluate both capabilities through the entire proposal-to-implementation process on large software systems. It is a multilingual benchmark of 100 tasks across 29 software systems in five domains. Each task provides a human-written enhancement proposal with user intent and high-level design. On average, proposals contain about 5,000 words, software systems contain 2.4 million source lines of code (LoC), and implementation pull requests (PRs) change approximately 5,500 LoC. Across 28 agents we evaluated, the best agent resolves only 14% of tasks and achieves a 52.7% Fail-to-Pass (F2P) pass rate. Failure analysis identifies incomplete code localization as a major bottleneck, while providing reference-derived file trees alongside API specifications improves resolved rates by 16--22 percentage points (2.4--17$\times$), reaching at most 34%. These results show that both perception and implementation remain central challenges for coding agents in practical modular development on large software systems. LoLBench is available at https://huggingface.co/datasets/lolbench26/LoLBench.

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

The Editor Has Read-Only Access: Correctness Signals in Diffusion Language Models

扩散代码模型:对错信号可读但难操控:六个扩散语言模型的内部激活可用线性探针区分代码对错,但探针点估计不优于模型自信度,沿探针方向调整激活也未能稳定改善生成代码,反向调整则明显变差。

两句看懂

过去默认模型内部若能读出代码对错,就该能据此直接引导生成更正确的代码。研究在六个扩散语言模型上用线性探针验证读出能力,并在残差流上做引导实验,结果探针可区分对错但引导未带来稳定提升,反向引导反而使代码变差。

核心判断

扩散代码模型内部确实存在可读的正确性信号,但该信号尚不能可靠转化为提升生成的干预:探针可分辨对错,引导实验却未带来稳定提升,反向引导反而变差。

关键要点

1. 以往假设模型内部正确性信号若可读出,就天然可用于干预提升生成质量;本文区分'可读性'与'可控性',两者未必一致,需分别检验探针判别力与引导干预效果。 2. 在六个扩散语言模型(含DiffuCoder-7B)的冻结激活上,用生成代码是否通过测试作标签,训练有监督差均值线性探针;引入小幅语义变异对照以排除探针只学到表面风格;另纳入自回归模型作比较,但非受控架构对照实验。 3. 探针能稳定区分通过与失败样本,但点估计未显示出对模型自身置信度的一致优势;将探针方向加到残差流在测试的引导设置中未带来可靠提升,反方向引导则使代码质量明显下降,统计校准与可复现性仍有限。

证据与结果

评测覆盖六个扩散语言模型,另对DiffuCoder-7B做补充检查,并纳入自回归模型作比较(非受控对照);以生成代码能否通过测试为标签训练探针,并设语义变异对照;比较探针点估计与模型置信度,以及残差流引导前后的代码生成效果;具体数据集规模与数值未在摘录中给出。

打开论文原文
它要解决什么
冻结的扩散代码模型内部是否存在可读的正确性信号,该信号能否转化为提升代码生成质量的干预手段?
研究路径
对六个扩散模型的冻结激活,按生成代码是否通过测试打标签;训练有监督差均值线性探针读出各层表示;以小幅语义变异构造对照,区分正确性信号与表面风格;对比探针点估计与模型自身置信度;将探针方向作为引导向量加到残差流,在去噪步骤中分别测试正向与反向干预。
这对工程意味着什么
工程上可用探针诊断模型是否内部编码了正确性,辅助调试;但不应想当然地把探针方向直接拿来做激活引导以'修复'代码,这类免训练捷径在已测设置中未显示稳定收益,反向调整还会让效果变差。
证据定位
六个扩散模型中探针均能区分通过/失败样本,语义变异对照支持其反映正确性而非风格;但探针点估计并未稳定优于模型自信度,沿探针方向引导未带来可靠提升,反向引导则使性能下降。(筛选维度:置信度与不确定性、可复核评测、软件工程方法)
适用边界
仅覆盖六个扩散模型及DiffuCoder-7B补充检查,自回归模型只作比较非受控实验;作者说明部分统计校准与可复现性仍有限,代码未构成完全冻结的复现环境。
方法与英文摘要

对六个扩散语言模型的冻结激活训练有监督的差均值线性探针,标签为生成代码是否通过测试;以小幅语义变异作对照,排除仅学到表面风格;在DiffuCoder-7B上做补充检查;另引入自回归模型作比较而非受控架构实验;最后将探针方向作为引导向量加到残差流,在去噪步骤中测试正向与反向干预效果。

Diffusion language models generate code by repeatedly updating a partially masked sequence. We ask whether their internal activations encode code correctness and whether that information can improve generation. Across six diffusion models, linear probes distinguish passing from failing attempts, with the strongest reads generally appearing beyond the early layers. Controls using small semantic mutations support a connection to correctness rather than surface style alone. In comparisons with model confidence, probe point estimates offer no consistent advantage. Adding a probe-derived direction to the residual stream does not yield a dependable improvement in the tested steering settings, while the opposite direction degrades performance. We distinguish these observations from claims about statistical significance or a general inability to steer. Supplementary methods, archived results, and code document the tested interventions and the limits of their statistical calibration and reproducibility.

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

Merged, Not Measured: An Empirical Study of Performance Issues Fixed by Coding Agents

代理性能修复:合并不等于验证:对71,677个代理PR中1,262个性能修复问题的实证研究:57%被合并,61%拒绝无理由说明,23个被拒绝声称中仅6个三次重跑后仍成立,30个合并修复中9个无显著提升或退化。

两句看懂

维护者常把代理性能修复PR的合并与否当作收益判断依据,但PR描述很少给出可靠重复测量。作者对23个被拒绝和30个合并修复重新三次运行测量,发现仅6个被拒绝声称成立,9个合并修复无提升或退化、14个在未测试输入上改变行为。

核心判断

答案:合并不能证明代理的性能修复真的有效;接受与否主要取决于代理和仓库的历史记录,而23个被拒绝声称中仅6个、30个合并修复中仅18个经重跑验证达标。

关键要点

1.以往研究要么只看人类性能修复,要么把代理PR的内容与提交者身份混在一起比较,或仅在固定测试环境中测代理速度,没人对代理在真实仓库中提交并被合并的性能修复逐一核实重跑。2.从AIDev v4的71,677个星标超100仓库代理PR中,经文本过滤+语言模型与作者联合编码,筛出582个仓库、6个代理提交的1,262个性能问题,标注每个问题的低效原因、修复范围与测试改动,并对23个被拒绝和30个合并修复做三次重复运行验证。3.57%关闭修复被合并、61%拒绝无说明理由,23个被拒绝声称中仅6个重跑后成立;合并修复删除行占比0.26高于被拒的0.15,但这与编码内容、描述或测试无关;30个合并修复中仅18个达标,9个无提升或退化,14个在未测试输入上改变行为,接受与否更取决于代理与仓库的历史记录而非修复本身。

证据与结果

来源AIDev v4快照(全量约270万代理PR),取星标超100仓库的71,677个PR,筛出582个仓库、6个代理提交的1,262个性能问题。对30个被拒绝声称(23个实际重跑)和30个含测试改动的合并修复做三次重复运行。结果:57%合并、61%拒绝无理由;6/23被拒声称成立;合并修复删除行占比0.26对0.15;18/30合并修复达标,3个未达声称,9个无提升或退化,14个在未测试输入上改变行为;44%问题源于重复计算/冗余数据处理,46%修复属架构级,37%修复改动了测试,11%带性能测试或基准。

打开论文原文
它要解决什么
AI编程代理提交的性能修复PR被合并,是否就证明其声称的加速真实有效?
研究路径
步骤:1)从AIDev v4的71,677个代理PR中用文本过滤初筛;2)语言模型编码后由作者复核确认,得到1,262个性能问题(582仓库、6代理);3)为每个问题标注低效原因、修复范围、是否改测试;4)对23个被拒绝和30个合并修复重新执行,三次运行取结果,比对PR声称的加速是否成立。
这对工程意味着什么
收到代理提交的性能修复PR时,应独立重跑三次以上测量实际收益再合并;不要把“已合并”或“代理过往记录好”当作性能已验证的证据,因为两者都与修复本身是否达标无关。
证据定位
57%关闭修复被合并,61%拒绝无说明理由;23个被拒绝声称重跑后仅6个成立;合并修复删除行占比0.26对0.15;30个合并修复中18个达标,9个无提升或退化,14个对未测试输入改变行为。(筛选维度:可复核评测、软件工程方法)
适用边界
重新执行样本小(23个被拒绝、30个合并),工作负载多为代理自建,仅覆盖6个代理和582个仓库,筛选经语言模型编码可能带入选择偏差。
方法与英文摘要

来源:AIDev v4中71,677个星标超100仓库的代理PR,经文本过滤与语言模型+作者编码筛出582个仓库、6个代理提交的1,262个性能问题;对每个问题标注低效原因、修复范围与测试;重跑23个被拒与30个合并修复(三次运行)验证声称是否成立。

Coding agents open pull requests (PRs) that claim to speed up software, but studies of human performance fixes say little about how maintainers respond to such a fix or whether its claim holds. From the 71,677 agent PRs of AIDev v4, a text filter and codebook coding by language models and by the authors select 1,262 performance issues fixed by six agents in 582 repositories. We code each issue and its tests and re-execute 23 rejected and 30 merged fixes. (1) 57% of closed fixes are merged, 61% of rejections give no stated reason, and only 6 of the 23 re-executed rejected claims held under our three-run pilot on mostly agent-built workloads. (2) Acceptance rises with the agent's track record in the repository (31-37% to 70%) and with the repository's pre-opening merge rate on its other agent PRs (33% to 84%). Merged fixes delete a larger share of the lines they change (0.26 versus 0.15), a difference that holds within agent and within repository, with no such difference detected in the coded content, description, tests or measurements. (3) Repeated computation and redundant data processing cause 44% of the issues, and 46% of fixes are architectural-level. (4) Agents change tests in 37% of fixes and 11% carry a performance test or benchmark; of the 30 merged fixes, 18 met our delivery criterion, 3 fell short of the claim, 9 showed no significant gain or regressed, and 14 change behavior on untested inputs. The outcome tracks the repository's history with the agent rather than the coded content of the fix, and a merge does not show that the fix delivers what it claims.

代码质量与优化(0 篇)

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

UI 与 GUI Agent(0 篇)

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

个人知识与本体(1 篇)

个人知识与本体 4/30

Simple Agentic Memory for Generalist Robot Policies

机器人记忆:保留状态而非画面历史:视觉记忆系统习惯保留或压缩历史画面,但机器人控制还需要画面中不显式存在的交互导出状态,如身份关系、进度、顺序。SimpleARM为冻结策略加一层免训练记忆层,在RoboMME的16个任务、三个策略种子上平均成功率67.17%,超过最强非oracle基线44.51%。

两句看懂

视觉记忆系统长期靠保留或压缩历史画面应对长程操作任务,但单帧画面往往不含身份关系、进度、顺序等交互导出状态。SimpleARM在RoboMME的16项任务、三个策略种子上验证:平均成功率67.17%,超过无记忆基线32.70%和最强非oracle基线44.51%。

核心判断

机器人记忆应维护任务相关的紧凑状态而非单纯保留视觉历史;证据是SimpleARM在RoboMME16任务上67.17%,对比最强非oracle基线44.51%、无记忆基线32.70%,且消融显示状态移除只影响依赖该状态的任务。

关键要点

1.旧假设/评测缺口:长视频与流式视频记忆方法把历史当作观测序列,围绕保留有用视觉证据组织记忆;RoboMME自身的记忆预算研究显示,单纯增加分配给感知历史的token数收益越来越小,说明容量扩大不能解决记忆问题。2.构造/协议:在RoboMME的16个记忆依赖型机器人操作任务上,用冻结VLA策略和三个策略种子评测;SimpleARM流程为指令驱动VLM先给出候选状态规格和检索操作,冻结感知/事件工具在线维护实体-关系绑定、事件进度、有序轨迹等类型化状态,仅在提议子目标的字段依赖历史时触发结构化检索,检索结果经当前画面重新定位后再执行。3.结果/诊断:SimpleARM平均成功率67.17%,高于无记忆基线32.70%和最强非oracle基线44.51%;匹配消融显示机制特异性——移除关系、指代、进度或路线状态分别只让对应依赖该状态的任务成绩大幅下降,其余任务基本不受影响。

证据与结果

基准为RoboMME,含16个记忆依赖型机器人操作任务,要求的历史信息在当前观测中已不可得;每个任务用三个策略随机种子重复评测,报告平均成功率。对比无记忆基线(32.70%)和此前最强非oracle方法(44.51%);SimpleARM达67.17%。匹配消融分别移除关系、指代、进度、路线四类状态,发现损失集中在实际检索该状态用于控制的任务上,其余任务基本不受影响。

打开论文原文
它要解决什么
机器人记忆是否应继续以保留/压缩视觉历史为核心,还是应转向维护交互历史导出的紧凑任务相关状态?
研究路径
执行前:指令条件VLM生成候选状态规格与检索操作。执行中:冻结感知/事件工具维护实体-关系绑定、事件进度、有序轨迹/流程等类型化状态。提出子目标时:仅当某字段依赖历史才触发结构化检索。执行动作前:用当前画面对检索到的实体重新定位(grounding),再交给冻结VLA策略执行。
这对工程意味着什么
给冻结机器人策略加记忆时,按任务拆出需要维护的状态类型(关系/进度/顺序等)并做条件检索与重新定位;单纯加大历史画面保留或压缩预算收益有限,是容易踩的捷径。
证据定位
RoboMME 16任务三策略种子:SimpleARM平均成功率67.17%,超过无记忆基线32.70%与最强非oracle基线44.51%;分别移除关系/指代/进度/路线状态时,仅对应任务成功率大幅下降,其余任务基本不受影响。(筛选维度:可复核评测)
适用边界
仅在RoboMME基准的16个任务、冻结VLA策略和三个随机种子上验证;结论限于该基准定义的记忆依赖型操作任务,未说明是否覆盖真实机器人部署或更大范围任务。
方法与英文摘要

在RoboMME基准(16个需要历史信息、单帧观测已不可得的机器人操作任务)上评测。SimpleARM执行步骤:1)按任务指令,VLM在执行前给出候选状态规格与检索操作;2)冻结的感知与事件工具在线维护紧凑类型化状态(实体-关系绑定、事件进度、有序轨迹/流程);3)仅当提议子目标的某字段依赖历史时才做结构化检索;4)检索到的实体经当前画面重新定位(grounding)后再执行动作。三个策略随机种子重复评测。

Visual-memory systems commonly retain or compress past observations. Robot control additionally requires interaction-derived state that no individual frame may explicitly represent, such as persistent identity relations, accumulated progress, or ordered procedures. We introduce Simple Agentic Robot Memory (SimpleARM), a training-free memory layer for frozen generalist robot policies. From the task instruction, SimpleARM specifies what to monitor; frozen perceptual tools maintain compact typed state online; structured access retrieves that state only when a proposed subgoal depends on history; and current-view grounding resolves recalled entities before execution. We evaluate SimpleARM on RoboMME, a benchmark of memory-dependent robot manipulation tasks that require history information no longer available in the current observation. Across all 16 tasks and three policy seeds, SimpleARM achieves 67.17% mean success, compared with 44.51% for the strongest non-oracle baseline. Matched ablations show mechanism specificity: removing relation, reference, progress, or route state produces large losses where the affected state is retrieved for control, while largely sparing other tasks. These results support a state-based view of robot memory: effective memory for control is not simply retained visual history, but compact task-relevant state derived from the interaction history.

人机协同与对齐(0 篇)

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

本轮分类概览

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

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

近一个季度监测日历

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

近 14 次监测窗口

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

本轮新增候选(13 篇)

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

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

形式化与程序验证 · 6/30 · 2026-09-29形式验证强化学习训练可验证证明以UNSAT形式验证门控中间结论,减少无效步骤归因;细节有限Learning to Prove, Not Just to Answer: Reinforcement Learning from Formal Verification for Natural-Language Logical Reasoning

Large language models (LLMs) are increasingly deployed for natural-language logical reasoning, where the final answer is easy to check but the proof behind it is not. In natural-language logical reasoning, an intermediate conclusion should follow from its premises, and the resulting derivation should support the final answer. Existing methods lack machine-checkable verification of intermediate conclusions and answer-supporting proof dependencies, so they may assign credit to invalid or answer-irrelevant steps. We propose Proof-R1, an RL framework from formal verification that trains LLMs to construct verifiable proofs for natural-language logical reasoning. Proof-R1 admits a generated conclusion into the verified proof state only when the corresponding reasoning action satisfies the proof obligations through UNSAT-based machine-checkable formal verification. Proof-R1 also recovers the answer-supporting dependency closure to trace the proof structure of the final answer and align outcome credit with the proof dependencies. Experiments demonstrate that Proof-R1 improves answer accuracy across three logical reasoning benchmarks and four backbone models and outperforms training-free agents and training-based methods in terms of reasoning-process verifiability.

阅读 arXiv 原文
形式化与程序验证 · 0/30 · 2026-09-29极限语言生成的Lean形式化库覆盖30篇论文的Lean 4库,供人类与AI辅助数学研究;仅摘要说明GenLimitLib: A Formal Library for Language Generation in the Limit and AI-Assisted Mathematical Research

We present GenLimitLib, a source-aligned Lean 4 library for language generation in the limit. Introduced by Kleinberg and Mullainathan at NeurIPS 2024, language generation in the limit studies a theoretical question motivated by LLMs: how to generate valid new strings from observed examples. This young and rapidly evolving field offers a natural testbed for studying large-scale formalization. GenLimitLib contains formal developments for 30 papers. It extracts shared definitions and reusable proof components while preserving paper-specific assumptions and statements, and records relationships across papers. In this way, GenLimitLib provides a concrete and structured view of the literature. We show through mathematical case studies and LLM experiments how our library can support both human mathematical research and AI-assisted research. Our Library: https://github.com/pengzhang91/generation-in-the-limit-lib.

阅读 arXiv 原文

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

软件工程与仓库智能 · 7/30 · 2026-09-29编码代理性能修复的合并与验证分析1,262个性能问题修复,仅少数被拒重跑声明成立;证据限于摘要Merged, Not Measured: An Empirical Study of Performance Issues Fixed by Coding Agents

Coding agents open pull requests (PRs) that claim to speed up software, but studies of human performance fixes say little about how maintainers respond to such a fix or whether its claim holds. From the 71,677 agent PRs of AIDev v4, a text filter and codebook coding by language models and by the authors select 1,262 performance issues fixed by six agents in 582 repositories. We code each issue and its tests and re-execute 23 rejected and 30 merged fixes. (1) 57% of closed fixes are merged, 61% of rejections give no stated reason, and only 6 of the 23 re-executed rejected claims held under our three-run pilot on mostly agent-built workloads. (2) Acceptance rises with the agent's track record in the repository (31-37% to 70%) and with the repository's pre-opening merge rate on its other agent PRs (33% to 84%). Merged fixes delete a larger share of the lines they change (0.26 versus 0.15), a difference that holds within agent and within repository, with no such difference detected in the coded content, description, tests or measurements. (3) Repeated computation and redundant data processing cause 44% of the issues, and 46% of fixes are architectural-level. (4) Agents change tests in 37% of fixes and 11% carry a performance test or benchmark; of the 30 merged fixes, 18 met our delivery criterion, 3 fell short of the claim, 9 showed no significant gain or regressed, and 14 change behavior on untested inputs. The outcome tracks the repository's history with the agent rather than the coded content of the fix, and a merge does not show that the fix delivers what it claims.

阅读 arXiv 原文
软件工程与仓库智能 · 4/30 · 2026-09-29软件测试人员情商访谈研究瑞典16名测试者半结构化访谈得三主题;样本与地域有限Exploring Emotional Intelligence in Software Testing

Background: Emotional Intelligence (EI) is the ability to recognise, understand, and manage one's own and others' emotions. Software testers deliver judgements about colleagues' work under deadlines they do not control, and prior work on emotion in software engineering has mostly studied developers. Aims: To explore how software testers describe the part EI plays in their day-to-day work, in communication and conflict within the team, and in responding to requirements volatility. Method: Semi-structured interviews with 16 software testers in Sweden working in teams that use agile practices, across aviation, automotive, healthcare, IT services, administration, banking and pharmaceuticals, analysed with reflexive thematic analysis informed by Goleman's EI framework. Results: Three themes. Testers described regulating stress under deadline pressure and drawing motivation from recognition, clarity and autonomy; managing the daily delivery of critical findings to colleagues so that trust survives; and responding to requirements change with frustration that turned into decisions about what to leave untested, into advocacy for process change, or into workarounds. Read against developer-focused studies, the themes point to features of the testing role: the work product is a criticism of a colleague's work, success is invisible while failure is attributed, and the tester's window shrinks with every upstream delay. Conclusions: For testers, managing emotions is a constant job requirement. The results highlight that the importance of EI increases when the development process lacks an independent testing phase. The findings also inform implications for teams and, ultimately, for organisations and future research.

阅读 arXiv 原文
软件工程与仓库智能 · 6/30 · 2026-09-29变异测试引导的评分标准生成用突变算子模拟缺陷以检验评分标准敏感性;实验细节未见于摘要Mubric: Mutation Testing-Guided Rubric Generation for LLM Evaluation

Rubric-based evaluation is widely used to assess LLM-based systems by decomposing response quality into task-specific scoring criteria. However, automatically generating rubrics that reliably capture task-specific quality requirements remains challenging. We introduce Mubric, a mutation testing-guided approach to rubric generation. Mutation testing, a classic software testing methodology, evaluates a test suite by injecting faults into programs and checking whether the tests detect them. We draw an analogy between test suites and rubrics: if a rubric captures an important quality requirement, introducing a corresponding defect into an otherwise high-quality response should reduce its score. Mubric first mines common defects from real pairs of preferred and dispreferred responses and abstracts these defects into reusable mutation operators, each specifying how to introduce a particular type of response defect. For a new task, it applies relevant operators to a reference response, checks whether the injected defects reduce response quality, and uses insufficiently penalized defects to refine the rubric. We evaluate Mubric on 703 tasks across four representative domains against six advanced rubric generation methods. Mubric achieves the highest overall evaluation accuracy, outperforming the strongest baseline by 7.48 percentage points.

阅读 arXiv 原文
软件工程与仓库智能 · 8/30 · 2026-09-29AI能否识别似是而非的代码评审1,199实例基准与仓库证据型判定代理Sentinel;证据出自摘要CRJudgeBench: Can AI Detect Plausible but Invalid Code Reviews?

Large language models can generate plausible code-review comments, but such comments may contain technically incorrect claims that mislead developers. We study technical trustworthiness judgment: determining whether a review comment's core technical claims are correct and applicable to the reviewed code in its repository context. Existing code-review benchmarks primarily evaluate review generation, issue discovery, or general comment quality, but do not directly assess whether an agent can determine the technical trustworthy of an individual review comment. To fill this gap, we introduce CRJudgeBench, a benchmark of 1199 instances constructed from real pull requests and expert-verified perturbations, covering both trustworthy and plausible but untrustworthy comments. We further present Sentinel, a repository-grounded agentic judge that actively gathers code evidence to verify review comments before making judgments. Starting from Qwen3-Coder-30B-A3B-Instruct, Sentinel is trained on the CRJudgeBench training split through iterative action-level learning from a privileged teacher. On the 359-instance CRJudgeBench test set, Sentinel achieves 76.60\% accuracy, outperforming GLM-5.3 by 6.13 percentage points and its base model by 19.78 points. These results show that even state-of-the-art general-purpose LLMs struggle to identify untrustworthy comments, while iterative action-level learning substantially improves the accuracy of repository-grounded trustworthiness judgments. Our dataset is available at https://huggingface.co/datasets/dcloud347/CRJudgeBenchmark

阅读 arXiv 原文
软件工程与仓库智能 · 11/30 · 2026-09-29长周期提案级编码代理基准100任务、29个系统,考察从提案到实现两阶段能力;规模数字出自摘要LoLBench: Evaluating Coding Agents with Long-Horizon Proposals on Large Software Systems

Modern coding agents can deliver increasingly large repository-level changes, and recent benchmarks reflect this by emphasizing long-horizon tasks with large reference implementations. Many benchmarks evaluate coding agents' implementation capability to produce correct code edits from detailed specifications. However, practical modular development tasks also require the perception capability of grounding user intent and high-level design to derive a specification. We introduce LoLBench to evaluate both capabilities through the entire proposal-to-implementation process on large software systems. It is a multilingual benchmark of 100 tasks across 29 software systems in five domains. Each task provides a human-written enhancement proposal with user intent and high-level design. On average, proposals contain about 5,000 words, software systems contain 2.4 million source lines of code (LoC), and implementation pull requests (PRs) change approximately 5,500 LoC. Across 28 agents we evaluated, the best agent resolves only 14% of tasks and achieves a 52.7% Fail-to-Pass (F2P) pass rate. Failure analysis identifies incomplete code localization as a major bottleneck, while providing reference-derived file trees alongside API specifications improves resolved rates by 16--22 percentage points (2.4--17$\times$), reaching at most 34%. These results show that both perception and implementation remain central challenges for coding agents in practical modular development on large software systems. LoLBench is available at https://huggingface.co/datasets/lolbench26/LoLBench.

阅读 arXiv 原文
软件工程与仓库智能 · 9/30 · 2026-09-29扩散语言模型的代码正确性信号六模型线性探针可区分通过与否,但引导未见稳定改善;作者提示结论边界The Editor Has Read-Only Access: Correctness Signals in Diffusion Language Models

Diffusion language models generate code by repeatedly updating a partially masked sequence. We ask whether their internal activations encode code correctness and whether that information can improve generation. Across six diffusion models, linear probes distinguish passing from failing attempts, with the strongest reads generally appearing beyond the early layers. Controls using small semantic mutations support a connection to correctness rather than surface style alone. In comparisons with model confidence, probe point estimates offer no consistent advantage. Adding a probe-derived direction to the residual stream does not yield a dependable improvement in the tested steering settings, while the opposite direction degrades performance. We distinguish these observations from claims about statistical significance or a general inability to steer. Supplementary methods, archived results, and code document the tested interventions and the limits of their statistical calibration and reproducibility.

阅读 arXiv 原文

代码质量与优化(1 篇)

代码质量与优化 · 3/30 · 2026-09-29LLM代理能否自主优化科学软件三个计算问题由代理自主优化,人类定范围与验证;结论待全文支撑Is manual software optimization a thing of the past?

Scientific software is increasingly required to process larger datasets while maintaining acceptable execution times. Software optimization traditionally requires substantial expertise in programming, algorithms, and numerical methods. Recent advances in large language models (LLMs) offer the possibility of automating much of this process. We investigate whether LLM-based agents can autonomously achieve substantial performance improvements in scientific software, including mature implementations that have already been extensively optimized by human developers. We tasked an LLM-based agent with optimizing software for three computational problems: t-SNE, single-sample gene set enrichment analysis (ssGSEA), and graphlet counting. Humans defined the scope, correctness criteria, and a verification mechanism, after which the agent worked autonomously, in some cases for several hours. Code maintainers reviewed each resulting implementation and verified its correctness. The optimized implementations were faster in all tested configurations, by up to two orders of magnitude over the fastest existing tools. The improvements included low-level code optimizations, mathematical reformulations, and an entirely new algorithm for graphlet counting. Software optimization can increasingly be delegated to autonomous agents, with the human role shifting from implementing optimizations to deciding which software to optimize, defining objectives, providing verification mechanisms, and ensuring the correctness of the final software. For well-scoped, verifiable problems, we argue that manual software optimization may be a thing of the past.

阅读 arXiv 原文

UI 与 GUI Agent(0 篇)

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

个人知识与本体(4 篇)

个人知识与本体 · 3/30 · 2026-09-29推荐反馈驱动代理记忆演化提出TIDE框架与MEG指标,应对延迟噪声反馈的归因困难;仅摘要信息How Can Recommendation Feedback Evolve Agent Memory?

Content-generation agents continuously receive impressions, clicks, conversions, and negative feedback from recommendation systems, providing real-world outcome signals for memory evolution. However, these signals are delayed and noisy, confounded by audience composition, placement, and recommendation policies, and may result from the combined influence of multiple memories, making accurate attribution difficult. Existing methods rely primarily on immediate feedback or semantic retrieval and therefore struggle to reliably translate recommendation outcomes into memory fitness. To address this challenge, we propose TIDE (Trajectory-Informed Directed Memory Evolution), an external memory evolution framework driven by delayed recommendation feedback. We further introduce Memory Evolution Gain (MEG), which measures the utility improvement of evolved memory over a no memory baseline on strictly future tasks. TIDE treats memory as a capacity-constrained population of experiences: temporal and semantic credit assignment estimates contextual fitness, while responsibility credit distributes outcome signals according to the memories referenced during generation. These signals are then used to reinforce, crossover, mutate, or evict memories. On an e-commerce membership marketing content-generation agent, TIDE achieves a +7.75-percentage-point MEG in offline temporal replay and significantly improves both unique click-through rate (UCTR) and activation rate in an online A/B test. On a delayed-label benchmark, TIDE achieves the lowest mean absolute error (MAE) and root mean squared error (RMSE) and the highest MEG among the compared methods, demonstrating its effectiveness.

阅读 arXiv 原文
个人知识与本体 · 3/30 · 2026-09-29面向代理记忆检索的集合级提升学习以相对无记忆的执行提升学习检索,用EVSI选择探测集;理论假设待验证UpliftMem: Learning Set-Level Uplift for Agent Memory Retrieval

Large language model (LLM) agents reuse external memory to guide new tasks, but effective retrieval requires learning which memory sets improve execution. Such learning relies on costly outcome feedback: ordinary retrieval observes only executed sets, while evaluating alternatives requires additional rollouts. We introduce \textsc{UpliftMem}, which learns memory retrieval from set-level execution uplift relative to the same executor without memory. A theoretical analysis of how retrieval preferences restrict feedback coverage motivates targeted probing of alternative memory sets. Probe selection follows an expected value of sample information (EVSI) criterion, derived in closed form under a correlated Gaussian model, to allocate limited training rollouts according to their expected improvement in local retrieval decisions. The shared scorer is trained with a frozen executor and selects memory sets without test-time probes. Across ALFWorld, WebShop, and BigCodeBench, \textsc{UpliftMem} achieves the best success rates among evaluated baselines on the main evaluation sets. Controlled fixed-store and matched probe budget evaluations further demonstrate improved memory-use decisions and more effective use of execution feedback.

阅读 arXiv 原文
个人知识与本体 · 4/30 · 2026-09-29面向机器人策略的简单代理式记忆免训练记忆层为冻结策略维护类型化状态;在RoboMME上评估,摘要截断Simple Agentic Memory for Generalist Robot Policies

Visual-memory systems commonly retain or compress past observations. Robot control additionally requires interaction-derived state that no individual frame may explicitly represent, such as persistent identity relations, accumulated progress, or ordered procedures. We introduce Simple Agentic Robot Memory (SimpleARM), a training-free memory layer for frozen generalist robot policies. From the task instruction, SimpleARM specifies what to monitor; frozen perceptual tools maintain compact typed state online; structured access retrieves that state only when a proposed subgoal depends on history; and current-view grounding resolves recalled entities before execution. We evaluate SimpleARM on RoboMME, a benchmark of memory-dependent robot manipulation tasks that require history information no longer available in the current observation. Across all 16 tasks and three policy seeds, SimpleARM achieves 67.17% mean success, compared with 44.51% for the strongest non-oracle baseline. Matched ablations show mechanism specificity: removing relation, reference, progress, or route state produces large losses where the affected state is retrieved for control, while largely sparing other tasks. These results support a state-based view of robot memory: effective memory for control is not simply retained visual history, but compact task-relevant state derived from the interaction history.

阅读 arXiv 原文
个人知识与本体 · 0/30 · 2026-09-28按受众授权的持久记忆生命周期记忆条目绑定受众,跨受众复用须显式授权,未决查看者默认失败关闭Audience-Bound Persistent Memory: Authorization Across the Memory Lifecycle

A personal language agent that acts for its owner across private and shared conversations can learn a fact from one audience and later place it in the context it assembles for another. We study authorization before context across the whole memory lifecycle. Each memory item carries the audience present when it was recorded; derived items are partitioned by audience, receive the intersection of their sources' audiences, or are suppressed; an audience widens only by an explicit, object-specific grant; and an item enters a model attempt only when every current viewer belongs to one of its authorized audiences, with unresolved viewers failing closed to public-only. Under explicit identity, provenance and complete-mediation assumptions, this admission is sound and policy-complete on the exact assembled context, enforced by exclusion rather than by model behavior. We realize it in two independently persisted reference architectures, a flat store and a relationship graph, and, descriptively, in a native agent-memory runtime. In a prospectively frozen confirmation over 10,000 multi-party histories, no forbidden item entered any architecture's context, whereas unscoped retrieval exposed forbidden items in 82% of its contexts. Entitled recall matched policy-equivalent baselines exactly and exceeded unscoped retrieval by 0.30 Recall@5, with a Holm-confirmed advantage that grows with distractors. No architecture produced a wrong-principal substitution, but unscoped substitutions were too rare to establish the prespecified joint decision.

阅读 arXiv 原文

人机协同与对齐(0 篇)

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