公开论文雷达

公开 arXiv 研究简报 · 2026-07-26T14:47:10.384179+00:00

先看结论和关键数字,再决定要不要读原文。页面只基于公开论文内容生成。

五张卡共识:别信一次通过,看谁在裁定

五张卡分两类:三张打磨评测可信度(WorkBuddy防污染、CoHarden严格测试、MemTools解耦变量),两张提升能力本身(VisualRepair修GUI缺陷、VeriSynth验zkEVM)。共同追问:由谁、按什么标准裁定「通过」,而非只看分数。

推荐阅读顺序

  1. 2607.19843:先立「通过≠正确」的判别视角:F→P会放行根因错补丁,能拒变异补丁才算硬标准,这思路贯穿全组。
  2. 2607.20911:把判别力扩到基准设计:防污染靠逆向改写的构造方式而非保密,且拒报全局均分以免掩盖单域弱项。
  3. 2607.19795:看职责分离的极致:LLM只翻译约束,SMT求解器裁定,去掉修复闭环检测率从91.6%掉到66.3%。
  4. 2607.21404:把评测偏差归因到架构耦合:声明式契约让组件热插拔,数据集与协议正交才能隔离设计变量。
  5. 2607.14075:最后落到具体能力:按图像类型路由工具+多区域自适应缩放,SWE-bench M测试集比基线多修10个。
共性方法
五张卡都拒绝把「跑通或得分」当作正确的证据,而是把生成与裁定分开:CoHarden用变异补丁裁、VeriSynth交给SMT求解器、WorkBuddy靠构造方式防污染并拒报全局均分、MemTools把协议与数据集正交、VisualRepair以测试执行验证补丁。
关键分歧
分歧在信任锚点与目标。WorkBuddy、CoHarden、MemTools指向「让度量可信」,靠构造、变异信号或解耦消除虚高;VisualRepair、VeriSynth指向「把事做对」,靠工具路由加区域缩放或LLM+SMT闭环。前者防自欺,后者提能力。
选择准则
要建基准或评测流水线,先读CoHarden、WorkBuddy、MemTools;要造实际修复或验证系统,读VisualRepair、VeriSynth。两条线都记住:把裁定权交给能拒错的机制,别信单一通过率。

重点深读(5 / 5 篇)

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

Tencent WorkBuddy Bench: A Multi-Domain Coding-Agent Benchmark with Contamination-Resistant Task Construction

多领域编码Agent基准:防污染任务逆向构建:发布四领域编码Agent评测集(代码、前端、办公、安全),任务从真实commit和PR逆向改写为口语请求,提示词不可网搜还原,全套开源可复现。

两句看懂

现有编码Agent基准直接使用issue文本,提示词可被网搜还原导致评测污染;该评测集将真实commit和PR逆向改写为口语请求以规避这一问题。在两套评测harness上完整运行四个领域子集,发布多模型排行榜,全部任务与环境镜像开源可逐项审查。

核心判断

将真实commit/PR逆向改写为口语请求可在完全开源条件下实现防污染;防污染关键在任务构造方式而非数据保密,四领域不报全局均分是另一实质性设计选择。

关键要点

1. 防污染构造机制:将真实commit/PR逆向提取需求后改写为口语角色扮演请求,使提示词与原始issue线程不可对应;防污染不依赖数据保密而依赖改写方式,开源发布不破坏防污染能力。 2. 四领域独立评分设计:代码(仓库级工程)、前端、办公/业务、安全(红蓝对抗)各用不同验证器,子集分不可跨域比较,不报全局均分,避免聚合指标掩盖单一领域失效。 3. 端到端开源可审计:任务目录、环境镜像、评测harness、测试与参考答案全部发布,任何第三方可重跑并逐项核查,是防分数虚报和保证评测可信的必要条件。

证据与结果

在两套Agent harness上运行四个领域全部任务,报告多模型家族排行榜;各子集独立计分,不汇总全局均分;摘要未提供具体通过率数字,证据不足以引用精确指标。任务目录、环境镜像与参考答案全部开源,支持第三方完整复现。

打开论文原文
它要解决什么
如何让公开发布的编码Agent基准同时具备防数据污染能力,而不依赖数据保密?
研究路径
从真实commit、PR或业务场景提取功能需求,将底层issue改写为口语化短请求;改写后提示词与原始线程无文本对应,网搜无法还原。四子集(代码、前端、办公、安全)打包为统一任务目录格式,在相同协议下运行,各使用领域专属验证器评分,并通过数据集版本迭代持续更新防污染能力。
这对工程意味着什么
搭建编码Agent基准时:从真实代码变更逆向构造任务并改写为口语提示;不要认为数据集公开发布必然导致污染——防污染关键在构造方式而非保密,多领域不可简单平均分数。
证据定位
在两套Agent harness上运行四领域全部子集,报告多模型家族排行榜;任务目录、环境镜像、评测harness、测试和参考答案全部开源,第三方可端到端复现。(筛选维度:可复核评测、软件工程方法)
适用边界
摘要未报告具体通过率数字;四子集评分标准不同,模型间跨领域能力无法直接横向比较。
方法与英文摘要

从真实commit、PR或业务场景逆向提取需求,将底层issue改写为口语化角色扮演请求;提示词与原始线程不可对应,网搜无法还原任务背景,防污染依赖构造方式与版本迭代而非保密。

We introduce Tencent WorkBuddy Bench, a multi-domain evaluation suite for coding agents; this report documents its construction methodology, scoring protocol, and a cross-model leaderboard. At its core is a unified evaluation framework for constructing and running distribution-informed coding-agent tasks across four work domains - Code, Web, Office, and Security. Rather than adapting public issue text, every task is reverse-engineered from a real commit, pull request, or business scenario and rewritten as a short, colloquial, role-played request, so that a task's prompt is not recoverable by web-searching the underlying issue, pull request, or commit thread. Because the dataset is released openly - task directories, environment images, evaluation harness, tests, and reference solutions - contamination resistance rests on this construction together with dataset versioning rather than on secrecy. The four subsets - repository-level engineering, front-end development, office and business workflows, and red-/blue-team security - probe complementary facets of real work, each with its own verification style. All are packaged in a uniform task-directory format and run, under a uniform and reproducible protocol, on two agent harnesses (CodeBuddy Code and Claude Code); the full open release makes the benchmark reproducible end to end and directly auditable, since any third party can re-run each task and inspect its content. Because each subset uses a different scoring instrument, scores are not comparable across subsets and the suite reports no suite-wide average. We report a cross-model leaderboard across several model families.

UI 与 GUI Agent 9/30

VisualRepair: Dynamic Tool Calling and Region Focusing for Visual Software Issue Repair

按图像类型动态调工具修复GUI软件缺陷:对含截图、GIF等异质图像的Bug报告,VisualRepair用图像类型感知工具调用(ITTC)与动态区域聚焦(DTRF)两模块,在SWE-bench M测试集比最优基线多修复10个实例。

两句看懂

真实Bug报告含截图、GIF、IDE快照等异质图像,大片无关区域导致MLLM定位偏差;VisualRepair以ITTC按类型路由工具、以DTRF自适应缩放聚焦缺陷区域。在SWE-bench Multimodal基准上,测试集修复196个实例,比最优基线多10个,开发集多11个。

核心判断

对含异质图像的Bug报告,先按图像类型选专属工具链、再自适应缩放定位缺陷区域,测试集修复196个实例,比最优基线多10个,是截至2026年3月SWE-bench M最优。

关键要点

1. ITTC将输入图像分为四类(UI截图、GIF、IDE快照、纯文本),对每类调用定制工具链;GIF需时序帧推理,纯文本需OCR,异类图像走单一流水线会导致语义提取失败,这是以往方法在异质输入上泛化差的直接原因。 2. DTRF在测试阶段枚举多个缺陷候选区域并自适应决定放大(捕获像素细节)或缩小(获取布局上下文),多区域并行探索扩展候选补丁空间,突破单一固定裁剪覆盖不足的瓶颈。 3. 在SWE-bench Multimodal基准上,VisualRepair测试集解决196个实例,比最优基线多10个,开发集多11个;绝对数量差异表明两模块组合带来了实质性增益而非统计噪声。

证据与结果

基准为SWE-bench Multimodal(含视觉上下文的真实GitHub Issue修复任务);VisualRepair测试集修复196个实例、开发集25个;测试集比最优基线+10、开发集+11;评测截至2026年3月。

打开论文原文
它要解决什么
当Bug报告包含截图、GIF、IDE快照等异质图像时,MLLM如何准确理解视觉缺陷并生成有效补丁?
研究路径
ITTC先将输入图像归类为四种(UI截图、GIF、IDE快照、纯文本)并路由到专属工具链;DTRF随后在多个候选缺陷区域执行自适应缩放,放大捕获局部细节、缩小获取上下文,将精炼区域特征输入MLLM生成候选补丁,再经测试执行验证。
这对工程意味着什么
图像类型路由+区域缩放是明确有效的组合(+10测试实例);误导推断:DTRF不是简单裁剪,核心是多候选区域+自适应缩放方向,固定区域单次裁剪无法复现效果。
证据定位
SWE-bench Multimodal测试集修复196个实例、开发集25个,分别比最优基线多10和11个实例,截至2026年3月为该基准最优。(筛选维度:可复核评测、软件工程方法、GUI Agent 方法)
适用边界
摘录未报告各类图像的分类准确率和DTRF区域候选数量,两模块各自的独立贡献无法从现有证据判断。
方法与英文摘要

ITTC将输入图像分四类并按类调用专属工具链;DTRF在多个候选缺陷区域上自适应缩放,精炼定位后输入MLLM生成多样补丁。

Automated Program Repair (APR) has witnessed significant progress with the advent of Large Language Models (LLMs). However, as modern software systems increasingly expose rich graphical user interfaces, effectively leveraging visual information from bug screenshots has become essential for understanding bugs and generating accurate fixes in multimodal scenarios. Real-world issue reports frequently contain heterogeneous visual attachments including UI screenshots, IDE snapshots, GIFs, and text-centric images, each with distinct visual patterns and domain-specific semantics that impose substantial perceptual demands on MLLMs. Furthermore, bug screenshots often contain large expanses of uninformative and bug-irrelevant regions, distracting the model's attention and limiting patch diversity. To address these challenges, we propose VisualRepair, an MLLM-based framework for visual software issue repair comprising two core modules: Image Type-aware Tool Calling (ITTC), which classifies input images and dynamically invokes a tailored tool-calling chain for robust visual interpretation, and Dynamic Test-time Region Focusing (DTRF), which grounds multiple bug-related region candidates and refines them via an adaptive zoom-in and zoom-out strategy to improve fault localization and promote diverse patch generation. Extensive experiments on the SWE-bench Multimodal benchmark demonstrate that VisualRepair consistently outperforms state-of-the-art approaches. VisualRepair resolves 196 and 25 instances on the test and dev sets, respectively, surpassing the best baseline by 10 and 11 instances. These results highlight the effectiveness of type-aware visual understanding and region-focused localization for automated visual software issue repair.

个人知识与本体 8/30

MemTools: A Unified Research Framework for Interoperable Agent Memory

MemTools:智能体记忆研究统一框架:针对智能体记忆系统架构碎片化问题,提出通过声明式数据契约标准化生命周期、解耦评测协议与数据集、统一管理异构记忆表示的研究框架。

两句看懂

现有智能体记忆系统各阶段紧耦合、评测与数据集绑定,导致无法隔离设计变量;MemTools通过声明式契约和正交评测架构解耦这三类问题。跨系统组件替换实验表明,换入组件性能可匹配或超越原生设计,评测协议重配置揭示操作时序对结果有关键影响。

核心判断

智能体记忆研究受阻于架构耦合和评测偏差;MemTools以声明式契约和正交评测协议解决这两个问题,跨系统组件替换实验证实其可行性。

关键要点

1. 生命周期解耦:声明式数据契约标准化记忆形成、存储、检索、演化、利用各阶段接口,匹配引擎自动枚举合法跨系统组合,使组件可互换——此前闭源代码库阻止了这种复用。 2. 评测协议分离:将基准数据集与执行协议正交解耦,同一数据集可运行多种评测工作流,消除执行逻辑差异引入的评测偏差,使性能差异归因成为可能。 3. 异构记忆统一接口:在单一运行时协调符号数据库、神经参数、多模态记录,实验显示异构组合带来互补性能增益。

证据与结果

三类实验验证:跨系统组件集成(替换组件匹配或超越原生性能)、评测协议重配置(揭示操作时序对结果有关键影响)、异构记忆协调(不同表示组合带来互补增益)。摘录未提供具体数值。

打开论文原文
它要解决什么
如何系统隔离智能体记忆设计变量,消除架构耦合带来的评测偏差?
研究路径
MemTools定义覆盖记忆后端、形成、检索、演化、利用五阶段的声明式数据契约;匹配引擎检查字段依赖并枚举合法流水线组合;评测层将数据集与协议正交分离,支持同一数据集多协议运行;统一接口在同一运行时协调符号、神经、多模态三类记忆。
这对工程意味着什么
具体行动:用声明式契约封装记忆模块,使其可跨系统热插拔测试。误区:不要将同一数据集上的性能差异归因于记忆能力本身,执行协议不同会产生系统性偏差。
证据定位
跨系统组件集成实验显示,交换后的组件性能可匹配甚至超越原生设计;评测协议重配置实验证明操作时序对性能有关键影响;异构记忆协调实验显示互补性能增益。(筛选维度:形式化验证、可复核评测)
适用边界
摘录未提供具体性能数字;跨系统兼容性验证的覆盖范围和场景类型未详述。
方法与英文摘要

定义声明式数据契约标准化记忆生命周期各阶段接口;用匹配引擎枚举合法跨系统组合;将数据集与执行协议正交分离;提供统一计算接口管理符号、神经、多模态记忆。

While memory systems are essential for agent architectures, pervasive architectural fragmentation restricts systematic research. Existing implementations typically couple different stages of the memory lifecycle, entangle evaluation logic with specific datasets, and provide limited support for the management of heterogeneous memory types. We introduce MemTools, an interoperability research framework that decouples memory system components from their underlying deployment environments. MemTools standardizes the memory lifecycle through declarative data contracts, enabling the interchangeable assembly of components across different systems. It orthogonally separates benchmark datasets from execution protocols to facilitate controlled assessments. Furthermore, MemTools provides a unified computational interface for coordinating symbolic, neural, and multimodal memory representations within a shared runtime. Empirical evaluations on cross-system component integration, evaluation protocol reconfiguration, and heterogeneous memory coordination demonstrate that MemTools enables systematic isolation and analysis of memory design variables. These findings suggest that MemTools provides a practical and extensible infrastructure for advancing principled research on agent memory.

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

Beyond Fail-to-Pass: Iterative Hardening of Co-Generated Bug Reproduction Tests and Fixes

F→P不够——严格BRT才能驱动正确修复:F→P准则遗漏「宽松」BRT盲区:此类测试通过fail-to-pass却放行错误补丁。CoHarden以变异补丁存活信号迭代加固测试,SWE-bench Verified达69.4%修复率,超最强基线+9.6pp。

两句看懂

F→P测试存在宽松盲区——通过准则却仍放行错误补丁,联合生成还引入测试-修复错误耦合;CoHarden以变异补丁存活信号驱动循环加固,强制测试收敛至严格状态。在SWE-bench Verified评测中,CoHarden达69.4% Resolved,超最强仅修复基线+9.6pp、联合生成基线+7.

核心判断

F→P是BRT质量的必要非充分条件;只有能拒绝变异补丁的严格测试才一致性改善修复成功率;CoHarden以Lax信号收敛,SWE-bench Verified达69.4%,超基线最高+9.6pp。

关键要点

1. F→P有两个具体盲区:宽松BRT仅检查症状消失不约束根因,错误补丁照样通过;联合生成的测试-修复错误耦合使两者同时出错时也能互相掩护——这意味着F→P通过率高并不等于测试具备判别力。 2. CoHarden将测试生成置于修复之前,再用变异补丁(对代码施加小改动的错误候选)检验严格性:若变异补丁通过当前测试则判定为Lax并触发加固迭代,同步更新修复,循环直至无变异补丁幸存——此机制将测试质量从「能否通过F→P」替换为「能否排除合理错误修复」。 3. SWE-bench Verified评测:CoHarden达69.4% Resolved,超最强仅修复基线+9.6pp、最强联合生成基线+7.9pp,跨多个LLM后端和基准集一致复现,表明提升来自框架的Lax收敛设计而非特定模型能力。

证据与结果

基准SWE-bench Verified:CoHarden达69.4% Resolved、78.9% F→P;超最强仅修复基线+9.6pp Resolved、超最强联合生成基线+7.9pp Resolved;实验跨多个LLM后端和SWE-bench系列基准均一致复现提升。

打开论文原文
它要解决什么
满足fail-to-pass的复现测试为何仍会让自动修复系统接受根因错误的补丁?
研究路径
三步迭代闭环:①先生成BRT(无修复信息介入);②对候选修复施加变异生成存活变异补丁;③若存活补丁通过当前测试则判定Lax并触发测试加固,同步更新修复候选;循环至无变异补丁幸存,以Lax回归消除为收敛信号退出。
这对工程意味着什么
可行动:在测试生成或APR管道中加入变异补丁过滤步骤验证测试严格性;要避免的误判:F→P率高不等于测试有效,宽松测试会系统性放行根因错误补丁并虚高修复率指标。
证据定位
SWE-bench Verified上CoHarden达69.4% Resolved、78.9% F→P,超最强仅修复基线+9.6pp、最强联合生成基线+7.9pp,跨多LLM后端一致复现。(筛选维度:可复核评测、软件工程方法)
适用边界
供文摘录未明确列出局限;迭代变异生成引入额外计算开销,收敛轮次与Token消耗的量化数据缺失。
方法与英文摘要

CoHarden先生成BRT再修复,用存活变异补丁检测测试宽松性,反复加固测试与修复,直至测试拒绝所有变异补丁后以Lax信号收敛。

Large language models (LLMs) have made automated program repair (APR) increasingly practical for real-world bugs, but repairing directly from bug reports remains underconstrained. Bug reproduction tests (BRTs) help close this gap by turning a bug report into an executable, bug-specific signal that can guide repair and validate candidate patches. Existing work has therefore studied BRT generation as a core subproblem in APR and mainly evaluates a generated BRT using the fail-to-pass (F->P) criterion, which requires the test to fail on the buggy code but pass on the golden fix. We show that F->P alone is insufficient when the goal of a BRT is to improve downstream repair. In particular, some F->P BRTs are lax, reproducing the observed symptom yet still admitting plausible-but-incorrect patches. We formalize this missing quality dimension by separating F->P BRTs into rigorous and lax ones, and show empirically that only the former consistently improve repair success. We further find that co-generation introduces test--fix error coupling, where the in-trajectory fail-to-pass (F->P) check can pass even when both the generated patch and generated test are wrong. Based on these findings, we propose CoHarden, a co-generation framework that uses the Lax signal as an in-loop convergence criterion. CoHarden first generates a test before any fix, then iteratively hardens the test and fix against surviving mutation patches until the generated test no longer admits Lax regressions. Experiments show that CoHarden reaches 69.4% Resolved and 78.9% F->P on SWE-bench Verified, outperforming the strongest fix-only and cogeneration baselines by +9.6 and +7.9 percentage points in Resolved, respectively, with consistent gains across LLM backbones and benchmarks.

形式化与程序验证 8/30

Towards Automated Formal Verification of zkEVMs Using LLM-Guided Constraint Synthesis

VeriSynth:LLM+SMT闭环自动验证zkEVM:VeriSynth让LLM将Rust zkEVM操作码翻译为Python/Z3约束,SMT求解器负责裁定;在95个注入缺陷的源码级基准上检测率达91.6%,比生产级手写变异测试多发现32个缺陷。

两句看懂

zkEVM的Rust操作码实现含隐式多组件语义,手工编写SMT规约不可持续,VeriSynth让LLM自动合成Python/Z3约束、SMT求解器闭环裁定。在包含95个注入缺陷的首个源码级基准上,VeriSynth检测87个(91.6%),比同类生产级手写变异测试多发现32个。

核心判断

VeriSynth把LLM局限于约束翻译、把正确性裁定权交给SMT求解器,在源码级zkEVM缺陷检测上达到91.6%,比生产级手工测试套件多检测32个缺陷,证明混合架构优于纯LLM和纯手工方案。

关键要点

1. LLM仅作形式化翻译前端,不做正确性判断:将Rust操作码处理器转为候选Z3约束,SMT求解器负责验证;职责分离消除LLM幻觉对验证结论的直接影响,使系统具备形式保证而非统计保证。 2. 验证引导自动修复是核心增益组件:去除该组件后检测率从91.6%骤降至66.3%(降幅25.3个百分点),说明初始LLM生成的约束常含语法或类型错误,需迭代修复才能被求解器执行。 3. 语义分解和检索增强提示进一步提升覆盖:对涉及栈、内存、存储、gas、执行上下文的多组件状态转换进行拆解,并以相关代码片段增强提示,使LLM能处理单次提示无法捕获的隐式依赖。

证据与结果

构建首个源码级zkEVM缺陷基准,含正确实现和注入缺陷的操作码实现共95个缺陷;VeriSynth检测87个(91.6%);生产级手写变异测试检测55个(57.9%);去除自动修复组件后降至66.3%;消融实验确认语义分解和检索增强各自均有独立贡献。

打开论文原文
它要解决什么
如何自动将Rust zkEVM实现转化为可执行SMT约束,检测那些能产生合法ZK证明却语义错误的实现缺陷?
研究路径
读入Rust操作码处理器后,先做语义分解将多组件状态转换拆解为子目标;再用检索增强提示将相关代码片段送入LLM,生成Python/Z3约束;约束经SMT求解器运行;若失败则触发验证引导自动修复,迭代修正语法或类型错误,直到约束可执行并通过求解器检验。
这对工程意味着什么
具体行动:在安全关键VM验证流水线中,可用LLM生成初始约束草稿,但必须加SMT裁定和自动修复闭环才能达到生产可用精度。误导推断:不能认为LLM可独立生成可信形式规约——去掉求解器验证步骤会使检测率下降约25个百分点。
证据定位
在95个注入缺陷的首个源码级zkEVM基准上:VeriSynth检测87个(91.6%),生产级手写变异测试套件检测55个(57.9%);去除自动修复组件后检测率从91.6%降至66.3%;消融实验确认每个组件均不可缺。(筛选维度:形式化验证、可复核评测)
适用边界
基准规模(95个注入缺陷)和覆盖操作码种类未详述;自动修复迭代次数上限和收敛条件未明确分析。
方法与英文摘要

VeriSynth采用LLM作为形式化前端,将Rust操作码处理器翻译为Z3约束;集成语义分解、检索增强提示和验证引导自动修复,构成闭环流水线;SMT求解器负责最终正确性裁定。

Zero-Knowledge Ethereum Virtual Machines (zkEVMs) secure Ethereum rollups by generating zero-knowledge proofs that guarantee off-chain execution correctness. However, subtle implementation bugs (e.g., incorrect gas accounting) can lead to valid proofs certifying semantically faulty states, thereby silently defeating cryptographic guarantees. Formal verification via SMT solvers can prevent this, but is bottlenecked by specification: current zkEVM development practice lacks automated methods to translate Rust opcode handlers into verification models. Current practices rely on unsustainable manual specifications, while LLM-based approaches suffer from hallucination and lack formal guarantees. To address this, we propose VeriSynth, a framework that synthesizes executable Python/Z3 verification models from Rust zkEVM code. VeriSynth enforces a hybrid paradigm: an LLM acts strictly as a formalization frontend to translate code into symbolic constraints, while an SMT solver serves as the correctness arbiter. To handle complex multi-component state transitions, VeriSynth integrates semantic decomposition, retrieval-grounded prompting, and verification-guided auto-repair into a closed-loop pipeline. We evaluate VeriSynth on the first source-level zkEVM verification benchmark, encompassing both correct and faulty opcode implementations. VeriSynth achieves a bug detection rate of over 90%, substantially outperforming direct and conversational LLM baselines, as well as a production-grade handwritten mutation-testing suite. Ablation studies confirm that each pipeline component is critical to the framework's overall effectiveness.

本轮分类概览

同一论文只归入一个最先命中的赛道,避免重复计数。

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

近一个季度监测日历

北京时间。绿色为正常窗口,橙色为部分降级;未运行不等于失败。

2026 年 5 月

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未运行31未运行

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未运行

2026 年 7 月

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未运行2670候选 / 5重点27未运行28293031

近 14 次监测窗口

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

开始时间状态抓取候选重点
07-26 14:52正常99705

候选阅读库(15 篇)

按赛道、评分和日期展开;中文标签用于导航,英文摘要用于核验。

个人知识与本体 · 3/30 · 2026-07-23Agentic Context Management: Solving Agent Memory and Cost by Treating Them as Lifecycle and Architecture Problems

Production AI agents' failures are less often due to an inability to reason well and more often because they cannot manage what is in their reasoning context: conversation histories, large prompts, large tool definitions, and ballooning tool outputs. Agents drown in their own accumulating history while paying a token cost that grows every turn, producing missing recalls within and across conversations. The incumbent response treats this as a storage-and-retrieval problem. We argue that framing is too narrow. Actively managing what an agent holds in mind is a lifecycle, not merely a store: it spans deciding what to remember, extracting and structuring it, choosing the right store per data type, consolidating and forgetting while preserving provenance, deciding what is relevant now, anticipating what is needed next, and compacting context to a budget without losing what matters. In serious production this operates not over a single user but across an organizational scope hierarchy. We name this discipline Agentic Context Management (ACM) and decompose it into five primitives: architecting, ingesting, scoping, anticipating, and compacting & consolidation. We then make the economic case: naive context accumulation grows token cost quadratically in conversation length, crude summarization buys linear cost at the price of an accuracy cliff, and only validated compaction achieves linear cost with preserved fidelity. We describe a reference implementation, Maximem Synap, that realizes the five primitives as a multi-tenant service and reports 92% on LongMemEval and 93.2% on LoCoMo under the configuration detailed in Section 6. We close with dimensions existing benchmarks do not yet capture, latency, token efficiency, and context-rot resistance, and the frontier of decision-level and organization-level context the category points toward.

阅读 arXiv 原文
个人知识与本体 · 8/30 · 2026-07-23MemTools: A Unified Research Framework for Interoperable Agent Memory

While memory systems are essential for agent architectures, pervasive architectural fragmentation restricts systematic research. Existing implementations typically couple different stages of the memory lifecycle, entangle evaluation logic with specific datasets, and provide limited support for the management of heterogeneous memory types. We introduce MemTools, an interoperability research framework that decouples memory system components from their underlying deployment environments. MemTools standardizes the memory lifecycle through declarative data contracts, enabling the interchangeable assembly of components across different systems. It orthogonally separates benchmark datasets from execution protocols to facilitate controlled assessments. Furthermore, MemTools provides a unified computational interface for coordinating symbolic, neural, and multimodal memory representations within a shared runtime. Empirical evaluations on cross-system component integration, evaluation protocol reconfiguration, and heterogeneous memory coordination demonstrate that MemTools enables systematic isolation and analysis of memory design variables. These findings suggest that MemTools provides a practical and extensible infrastructure for advancing principled research on agent memory.

阅读 arXiv 原文
软件工程与仓库智能 · 6/30 · 2026-07-23Information is all you need: Requirements Engineering Quality Reframed

To move beyond this vague appeal to context, this vision proposes a novel holistic theory of requirements engineering (RE) quality. This theory models how information particles, i.e., discrete pieces of domain knowledge, are transferred between roles and artifacts. Since the RE process is ultimately an information transfer, holistic RE quality depends on the properties of information flow, i.e., how effectively and efficiently information is transferred from sources (like stakeholders) to targets (like developers and testers), uniting both artifact- and process-based perspectives on RE quality. In an exemplary simulation of the theory we illustrate why a high-quality specification gets bypassed in an agile context, thereby demonstrating that a simulation can provide actionable insights into calibrating the RE process to optimize the information flow. Beyond organizational applications, we envision that the theory can serve as a coherent theoretical framework for understanding the success or failure of RE processes and artifacts.

阅读 arXiv 原文
形式化与程序验证 · 3/30 · 2026-07-23pAI-Econ-claude: A Gated Human-in-the-Loop Multi-Agent Architecture for AI-Assisted Economic Theory Development

In many social-science research tasks, such as economics, LLM-based agents must produce outputs for which no cheap, task-complete, machine-readable correctness signal exists. This creates a distinctive reliability problem for multi-agent systems: how should generation, critique, coordination, and human judgment be organized when no component can certify the final result? We address this problem through pAI-Econ-claude, a gated, human-in-the-loop multi-agent architecture for AI-assisted economic theory development. Agents coordinate through a shared workspace of inspectable intermediate records; specialized gates diagnose targeted failure modes and recommend loopbacks without certifying correctness; and human checkpoints retain authority over decisions that are costly to reverse. We evaluate the architecture on five matched economic-theory tasks against an ungated baseline. Two evaluators blinded to configuration agreed on all five pairwise rankings, preferring the gated architecture in four tasks and the baseline in one. Mean failure severity fell from 1.58 to 1.16, while overall usefulness rose from 2.60 to 3.10. The largest observed gain occurred when a reality check rejected a false market-structure premise and a proof review prompted revision of a false welfare claim. The negative case shows that scaffolding can also compress an economically important mechanism too aggressively. The results support a bounded claim: gated oversight improves the auditability of AI-assisted economic theory without substituting for formal verification, and the allocation of irreversible human judgment is a more informative design variable than pure agent autonomy. The workflow is publicly available at https://github.com/maxwell2732/pAI-Econ-claude.

阅读 arXiv 原文
个人知识与本体 · 3/30 · 2026-07-23AttriMem: Attribution-Guided Process Feedback for Agent Memory Learning

Effective memory is crucial for LLM agents, yet constructing it effectively remains challenging. A memory-construction policy decides what information to extract, store, update, compress, or discard as interactions accumulate. Heuristic memory methods rely on subjective, task-specific rules, which can misalign with downstream objectives and limit cross-task adaptability. RL-based methods, by contrast, learn from task feedback but mainly use outcome- or module-level rewards. These coarse signals indicate task success but cannot identify which intermediate memory contents support the final answer, creating a fine-grained credit-assignment bottleneck. However, constructing such process feedback is prohibitively difficult because intermediate memory decisions lack unique ground-truth targets, while the appropriate credit varies with the agent's uncertain reasoning trajectory and therefore cannot be specified in advance. We propose AttriMem, an attribution-guided process-feedback framework for learning memory-construction policies with RL. AttriMem augments the global outcome reward with local rewards derived from token-level contributions to the final answer. Experiments on long-horizon dialogue question answering show that AttriMem outperforms retrieval-based, heuristic, and RL-based baselines, generalizes across benchmarks and answer models, stabilizes RL optimization.

阅读 arXiv 原文
软件工程与仓库智能 · 9/30 · 2026-07-23Tencent WorkBuddy Bench: A Multi-Domain Coding-Agent Benchmark with Contamination-Resistant Task Construction

We introduce Tencent WorkBuddy Bench, a multi-domain evaluation suite for coding agents; this report documents its construction methodology, scoring protocol, and a cross-model leaderboard. At its core is a unified evaluation framework for constructing and running distribution-informed coding-agent tasks across four work domains - Code, Web, Office, and Security. Rather than adapting public issue text, every task is reverse-engineered from a real commit, pull request, or business scenario and rewritten as a short, colloquial, role-played request, so that a task's prompt is not recoverable by web-searching the underlying issue, pull request, or commit thread. Because the dataset is released openly - task directories, environment images, evaluation harness, tests, and reference solutions - contamination resistance rests on this construction together with dataset versioning rather than on secrecy. The four subsets - repository-level engineering, front-end development, office and business workflows, and red-/blue-team security - probe complementary facets of real work, each with its own verification style. All are packaged in a uniform task-directory format and run, under a uniform and reproducible protocol, on two agent harnesses (CodeBuddy Code and Claude Code); the full open release makes the benchmark reproducible end to end and directly auditable, since any third party can re-run each task and inspect its content. Because each subset uses a different scoring instrument, scores are not comparable across subsets and the suite reports no suite-wide average. We report a cross-model leaderboard across several model families.

阅读 arXiv 原文
代码质量与优化 · 6/30 · 2026-07-22NVIDIA-labs OO Agents: Native Python Object-Oriented Agents

Traditional agent development is split across prompt templates, tool schemas, callback code, and workflow graphs. We present NVIDIA Object-Oriented Agents (NOOA), a model-agnostic Python framework for building reliable AI agents. NOOA takes a simpler approach: an agent is a Python object. Its methods are the actions the model can take, fields are its state, docstrings are its prompts, and its type annotations are contracts. A method whose code body consists of "..." is completed at runtime by an LLM-driven agent loop, while methods with normal bodies remain standard deterministic Python. This gives developers and agents the same interface, so agent behavior can be tested, traced, refactored, and improved just like other software. This paper makes three contributions. (1) We present the agent-as-a-Python-object programming model and the design principles behind it. Where Python has existing abstractions, we adopt them directly. Agent-specific capabilities--context, events, state rendering, long-term memory, and validated LLM loops--are exposed through simple Pythonic APIs, so both developers and agents share one familiar programming model. (2) We identify six model-facing ideas that NOOA is, to our knowledge, the first to combine on a single surface: typed input/output, pass-by-reference over live objects, code as action, programmable loop engineering, explicit object state, and model-callable harness APIs for context and events. We find the community already converging on several of these ideas--often as experimental or partial features--and present the comparison to encourage further adoption. (3) We demonstrate that current models use this interface effectively, both in targeted capability tests and on agentic and reasoning benchmarks such as SWE-bench Verified and Terminal-Bench 2.0 and ARC-AGI-3.

阅读 arXiv 原文
代码质量与优化 · 3/30 · 2026-07-22Multi-Source and Cross-Scenario Strategy-Guided Code Optimization

Automated code optimization improves program performance by refactoring source code, and recent studies use LLMs to generate optimization patches. The newest approaches are strategy-guided: they summarize strategies from historical optimization commits as static analysis rules, and use these rules to match code locations for LLMs to optimize. However, these approaches have two limitations: (1) the strategies may come from other knowledge sources, such as textbooks and web pages, but the existing approaches cannot utilize them; (2) a strategy may be applicable to different scenarios, e.g., different programming languages, but existing approaches can only formalize strategies for the scenario to which the source commit belongs. To address these limitations, we propose MoST, an LLM-based code optimization framework that integrates multiple knowledge sources across scenarios. MoST uniformly represents items in different knowledge sources as evidence objects, clusters them in a cross-source and cross-scenario manner to identify strategies, and transfers them to the target scenario when necessary for generating static analysis rules. To implement this process, MoST employs a novel self-balanced weighted clustering algorithm to balance evidence objects from different knowledge sources, and a novel example transfer procedure to ensure the quality of the generated rules when transferring across scenarios. On a benchmark containing 151 C/C++, 150 Python, and 50 Rust historical optimization tasks, compared with SemOpt, MoST yields 24.44%-180.00% and 21.88%-37.50% more patches that are exactly the same as or semantically equivalent to developer patches, respectively. When optimizing 15 real-world projects, MoST achieves 19.72%-717.42% maximum improvements and 4.44%-258.17% average improvements for the performance tests in the projects, significantly outperforming SemOpt and Codex.

阅读 arXiv 原文
软件工程与仓库智能 · 8/30 · 2026-07-22Beyond Fail-to-Pass: Iterative Hardening of Co-Generated Bug Reproduction Tests and Fixes

Large language models (LLMs) have made automated program repair (APR) increasingly practical for real-world bugs, but repairing directly from bug reports remains underconstrained. Bug reproduction tests (BRTs) help close this gap by turning a bug report into an executable, bug-specific signal that can guide repair and validate candidate patches. Existing work has therefore studied BRT generation as a core subproblem in APR and mainly evaluates a generated BRT using the fail-to-pass (F->P) criterion, which requires the test to fail on the buggy code but pass on the golden fix. We show that F->P alone is insufficient when the goal of a BRT is to improve downstream repair. In particular, some F->P BRTs are lax, reproducing the observed symptom yet still admitting plausible-but-incorrect patches. We formalize this missing quality dimension by separating F->P BRTs into rigorous and lax ones, and show empirically that only the former consistently improve repair success. We further find that co-generation introduces test--fix error coupling, where the in-trajectory fail-to-pass (F->P) check can pass even when both the generated patch and generated test are wrong. Based on these findings, we propose CoHarden, a co-generation framework that uses the Lax signal as an in-loop convergence criterion. CoHarden first generates a test before any fix, then iteratively hardens the test and fix against surviving mutation patches until the generated test no longer admits Lax regressions. Experiments show that CoHarden reaches 69.4% Resolved and 78.9% F->P on SWE-bench Verified, outperforming the strongest fix-only and cogeneration baselines by +9.6 and +7.9 percentage points in Resolved, respectively, with consistent gains across LLM backbones and benchmarks.

阅读 arXiv 原文
形式化与程序验证 · 8/30 · 2026-07-22Towards Automated Formal Verification of zkEVMs Using LLM-Guided Constraint Synthesis

Zero-Knowledge Ethereum Virtual Machines (zkEVMs) secure Ethereum rollups by generating zero-knowledge proofs that guarantee off-chain execution correctness. However, subtle implementation bugs (e.g., incorrect gas accounting) can lead to valid proofs certifying semantically faulty states, thereby silently defeating cryptographic guarantees. Formal verification via SMT solvers can prevent this, but is bottlenecked by specification: current zkEVM development practice lacks automated methods to translate Rust opcode handlers into verification models. Current practices rely on unsustainable manual specifications, while LLM-based approaches suffer from hallucination and lack formal guarantees. To address this, we propose VeriSynth, a framework that synthesizes executable Python/Z3 verification models from Rust zkEVM code. VeriSynth enforces a hybrid paradigm: an LLM acts strictly as a formalization frontend to translate code into symbolic constraints, while an SMT solver serves as the correctness arbiter. To handle complex multi-component state transitions, VeriSynth integrates semantic decomposition, retrieval-grounded prompting, and verification-guided auto-repair into a closed-loop pipeline. We evaluate VeriSynth on the first source-level zkEVM verification benchmark, encompassing both correct and faulty opcode implementations. VeriSynth achieves a bug detection rate of over 90%, substantially outperforming direct and conversational LLM baselines, as well as a production-grade handwritten mutation-testing suite. Ablation studies confirm that each pipeline component is critical to the framework's overall effectiveness.

阅读 arXiv 原文
形式化与程序验证 · 3/30 · 2026-07-22Neuro-Symbolic AI for Korean Criminal Law: Sentencing Prediction and Document Drafting

The Korean criminal justice system utilizes summary proceedings (guyaksik) to expedite high-volume minor infractions, such as simple driving under the influence (DUI), unlicensed driving, and minor traffic casualties. Although this mechanism improves judicial throughput, processing these cases creates a substantial administrative burden for prosecutors, driving the need for automated systems that can precisely translate unstructured legal text into deterministic statutory outcomes. While recent Large Language Models (LLMs) excel at semantic extraction, their probabilistic nature inherently limits their reliability in Legal Judgment Prediction tasks. Specifically, when confronted with the arithmetic constraints of legal statutes, LLMs can produce hallucinations. Given that legal accountability permits virtually no tolerance for stochastic errors, purely neural architectures remain limited in their direct judicial applications. To address these limitations, we propose a Neuro-Symbolic framework that bridges unstructured legal facts with formal verification. Our architecture restricts the LLM exclusively to semantic extraction, while offloading statutory fine calculations to a Satisfiability Modulo Theories solver. This division of labor reduces hallucination risks during computation. Furthermore, we incorporate a Human-in-the-Loop verification scheme to preserve professional legal oversight. We formalize the 2026 Sentencing Guidelines for Traffic Offenses within this pipeline, demonstrating a deterministic approach to supporting summary indictments.

阅读 arXiv 原文
代码质量与优化 · 6/30 · 2026-07-22PerfAgent: Profiler-Guided Iterative Refinement for Repository-Level Code Optimization

Large language model (LLM) agents now perform well on correctness-oriented repository-level tasks, including SWE-Bench issue resolution and feature implementation in real codebases. However, they still struggle with repository-level code optimization, which requires preserving behavior while improving runtime performance. Passing tests is not enough in this setting; a patch must preserve behavior, implement code optimization, and approach expert speedups. Current agents often miss bottlenecks hidden behind abstraction layers and native extensions, stop after shallow speedups, or insufficiently test the code patches that thus may silently break edge cases. We present PerfAgent, a profiler-guided, verifier-in-the-loop workflow that gives an off-the-shelf coding agent the feedback needed to find real hotspots, improve beyond the first passing patch, and use profiler evidence rather than timing alone to decide what to optimize next. On two challenging optimization benchmarks, GSO and SWE-fficiency-Lite, PerfAgent more than doubles the rate of expert-matching patches over OpenHands with GPT-5.1, improving from 19.6% to 39.2% on GSO and from 26% to 74% on SWE-fficiency-Lite. It also surpasses an oracle best-of-five baseline at substantially lower cost, showing that the gains come from better feedback rather than additional test-time sampling.

阅读 arXiv 原文
UI 与 GUI Agent · 3/30 · 2026-07-20Sidekick: Designing Communication for Effective Multitasking with Computer Use Agents

Computer Use Agents (CUAs) can autonomously execute complex, multi-step tasks within GUIs, enhancing efficiency through parallel multitasking. However, our formative studies with CUA experts and GenAI users indicated that current feedback is primarily text-based, requiring sustained attention to monitor progress and offering limited visibility to trace past GUI interactions. Based on the findings, we developed a prototype system, Sidekick, for communicating CUAs' status with multimodal feedback across different stages of interaction: (i) When CUAs run in the background, Sidekick signals its execution state through ambient cues. (ii) Upon resuming interaction with CUAs, Sidekick provides multimodal summaries of completed actions to support rapid context resumption. (iii) When CUAs operate in the foreground, Sidekick enhances transparency by verbalizing and visualizing the agent's reasoning. A study with 30 participants demonstrated that Sidekick significantly improved multitasking performance with CUAs compared to baseline systems that presented textual feedback either in a typical chat or in an ambient display. Sidekick supported progress awareness, and error and action traceability more effectively. Finally, we demonstrate the promise of Sidekick through several example applications, and discuss implications for long-horizon human-agent collaboration.

阅读 arXiv 原文
UI 与 GUI Agent · 7/30 · 2026-07-16AI Prototyper: A Figma Plugin for Decomposition-Based GUI Prototyping with LLMs

Graphical user interface (GUI) prototyping remains a time-consuming activity that demands both design expertise and considerable manual effort. As GUI prototypes are non-code artifacts that evolve alongside requirements throughout the development cycle, automating their generation is directly relevant to software maintenance and evolution. We present AI Prototyper, an open-source Figma plugin that automates GUI prototyping through a decomposition and retrieval-augmented generation (RAG) pipeline. Given a natural-language description of a desired screen, such as a login page or a product detail card, the plugin decomposes the request into discrete GUI features, retrieves matching components from a custom 32-primitive library, and renders each component as a fully editable Figma layer with auto-layout. The pipeline uses Gemini 2.5 Flash as its LLM back-end and a Node.js Express service. Unlike existing decomposition-based tools, AI Prototyper introduces a human-in-the-loop editing step that lets users review, modify, or extend the generated feature list before rendering, uses a different technology stack and LLM family, and supports multilingual input, producing correctly labelled interfaces in Thai, English, and Mandarin Chinese. In a preliminary evaluation, participants using AI Prototyper completed more prototypes in a fixed time window than those working manually, and expert practitioners rated the AI-generated prototypes higher across nine quality dimensions. A demonstration video is available at https://youtu.be/pRoFAH7MQaE. The source code and component library are available at https://github.com/tongsalangsingha/AI-prototyper-tool

阅读 arXiv 原文
UI 与 GUI Agent · 9/30 · 2026-07-15VisualRepair: Dynamic Tool Calling and Region Focusing for Visual Software Issue Repair

Automated Program Repair (APR) has witnessed significant progress with the advent of Large Language Models (LLMs). However, as modern software systems increasingly expose rich graphical user interfaces, effectively leveraging visual information from bug screenshots has become essential for understanding bugs and generating accurate fixes in multimodal scenarios. Real-world issue reports frequently contain heterogeneous visual attachments including UI screenshots, IDE snapshots, GIFs, and text-centric images, each with distinct visual patterns and domain-specific semantics that impose substantial perceptual demands on MLLMs. Furthermore, bug screenshots often contain large expanses of uninformative and bug-irrelevant regions, distracting the model's attention and limiting patch diversity. To address these challenges, we propose VisualRepair, an MLLM-based framework for visual software issue repair comprising two core modules: Image Type-aware Tool Calling (ITTC), which classifies input images and dynamically invokes a tailored tool-calling chain for robust visual interpretation, and Dynamic Test-time Region Focusing (DTRF), which grounds multiple bug-related region candidates and refines them via an adaptive zoom-in and zoom-out strategy to improve fault localization and promote diverse patch generation. Extensive experiments on the SWE-bench Multimodal benchmark demonstrate that VisualRepair consistently outperforms state-of-the-art approaches. VisualRepair resolves 196 and 25 instances on the test and dev sets, respectively, surpassing the best baseline by 10 and 11 instances. These results highlight the effectiveness of type-aware visual understanding and region-focused localization for automated visual software issue repair.

阅读 arXiv 原文