公开论文雷达

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

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

五张卡片:先读带数字的,再读方法蓝图

五张卡片多在对抗"表面通过"信号。CoHarden、VeriSynth、VisualRepair给出可核实数字,WorkBuddy、MemTools全文摘录缺失、只凭构建逻辑声称。建议先读有数字和开放资产的,把无数字的当方法参考,不要当已验证结论。

推荐阅读顺序

  1. 2607.19843:先建立心态:F→P通过不等于修复正确,且给出69.4%等可核实数字,是理解其余卡片的判断底座。
  2. 2607.19795:接着看具体机制样板:LLM只做翻译、SMT做仲裁,91.6%检出且比手写测试多32个,数字可对照。
  3. 2607.14075:再看能力侧:图像类型路由加区域缩放,测试集超基线10个实例,最独立自足,可直接评估借鉴。
  4. 2607.20911:当方法蓝图读:逆向构造抗污染任务的思路值得参考,但摘录为空、无分数,别横向比较子集。
  5. 2607.21404:最后当基建读:用数据契约隔离评测变量、做消融,无量化数字,价值在排噪不在直接涨分。
共性方法
多数卡片都在质疑"表面通过":F→P通过、搜索可还原原始issue、手写测试、评测环境耦合都可能制造假象。共同做法是把可审计的构造、变异、仲裁或隔离机制摆在信任之前,用做法本身而非保密或结论来支撑。
关键分歧
证据强度分两档:VisualRepair超基线10个实例、CoHarden 69.4%、VeriSynth 91.6%均可核实;WorkBuddy与MemTools全文摘录缺失,只凭构建逻辑声称。抗错手段也分构造改写、变异信号、SMT仲裁、变量隔离四路,路径互不相同。
选择准则
若要立刻可复现可审计,先读带具体数字和开放资产的CoHarden、VeriSynth、VisualRepair;WorkBuddy、MemTools当方法蓝图看,别把其声称当已验证结论。

重点深读(5 / 5 篇)

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

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

抗污染多域编程智能体评测基准:从真实commit和PR逆向构建任务提示,覆盖代码、前端、办公、安全四域,提示无法通过搜索原始issue还原,以构建方式而非保密实现抗污染,全套资产开放复现。

两句看懂

针对编程智能体评测的数据污染问题,将真实commit和PR逆向改写为口语化提示,使搜索原始issue无法还原任务内容。在两个智能体harness上跨多个模型家族运行排行榜,但全文摘录缺失,具体分数无法核实。

一句话结论

评测任务从真实代码提交逆向生成并改写,搜索原始PR或commit无法还原提示;抗污染性依赖构建方式而非数据保密,版本控制替代秘密性。

关键结果

在两个智能体harness上跨多个模型家族运行,各子集独立报告排行榜;因各子集采用不同评分工具,分数不可跨子集比较,不设全套平均分。全文摘录为空,无具体模型分数、任务数量或子集规模数据可引用。

打开论文原文
它要解决什么
如何构造无法通过搜索原始PR或commit还原的编程智能体评测任务,在开放发布条件下保持抗污染性?
它怎么做
每个任务从真实commit、PR或业务场景提取功能意图后改写为简短口语化角色扮演请求;四子集(仓库级工程、前端开发、办公流程、红蓝安全)各用独立验证方式;任务打包为统一目录(含环境镜像、测试和参考答案)并在统一可复现协议下运行;以版本控制代替数据保密维持抗污染性。
下一步怎么用
适合在设计编程智能体内部评测集时参考其逆向工程任务构建流程;避免误认为各子集分数可横向比较——论文明确不报告全套平均分。
证据来自哪里
全文摘录为空,无具体分数;摘要描述在两个智能体harness上跨多个模型家族运行并报告排行榜,但无数字可引用。(筛选维度:可复核评测、软件工程方法)
别过度解读
全文摘录为空,任务数量、子集规模和具体分数均不可知;抗污染效果仅凭构建逻辑声称,未见实证检验。
方法与英文摘要

从真实commit、PR或业务场景提取功能意图,改写为简短口语化角色扮演提示;四子集各用独立验证方式;所有任务打包为统一目录格式,在统一可复现协议下运行。

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

视觉软件缺陷修复框架VisualRepair:提出VisualRepair框架,用图像类型感知工具调用与动态区域聚焦两模块,解决GUI缺陷报告中异构视觉输入难题,在SWE-bench多模态基准测试集超最优基线10个实例。

两句看懂

VisualRepair针对GUI缺陷报告中UI截图、GIF、IDE快照等异构视觉输入,设计类型感知工具调用(ITTC)和动态区域缩放聚焦(DTRF)两模块。在SWE-bench Multimodal测试集上解决196个实例,超最优基线10个,开发集超基线11个。

一句话结论

按图像类型动态选择工具链、加缺陷区域自适应缩放,使MLLM在GUI软件修复任务中测试集解决率超最优基线10个实例,说明视觉类型感知和区域聚焦是有效突破口。

关键结果

基准:SWE-bench Multimodal(软件Issue修复任务,含GUI截图等视觉附件);测试集解决196个实例、开发集25个;对比最优基线,测试集+10个、开发集+11个;系统为MLLM驱动的generate-and-validate流程;实验完成于2026年3月。

打开论文原文
它要解决什么
如何让MLLM有效理解GUI缺陷截图中的异构视觉内容并精确定位缺陷区域以生成正确补丁?
它怎么做
ITTC先将输入图像分为四类:UI截图、动态GIF(需时序推理)、IDE代码快照、纯文本图(需OCR),再针对每类动态调用不同工具链提取视觉语义;DTRF在全图中定位多个缺陷候选区域,通过缩放放大精化边界、缩放缩小恢复上下文,最终输出多样化候选补丁交由测试验证。
下一步怎么用
适合在处理多类型截图的GUI自动修复或视觉测试回归流水线中评估;不要认为单一通用提示足以处理截图/GIF/IDE快照,图像类型感知路由是不可省略的前提步骤。
证据来自哪里
SWE-bench Multimodal测试集解决196个实例、开发集解决25个,分别超过最优基线10和11个实例(实验截至2026年3月)。(筛选维度:可复核评测、软件工程方法、GUI Agent 方法)
别过度解读
仅在SWE-bench Multimodal评测,对GIF时序推理和OCR细节描述有限;跨项目泛化能力及各模块单独贡献未充分验证。
方法与英文摘要

ITTC模块将图像分为UI截图、GIF、IDE快照、纯文本图四类并调用对应工具链;DTRF模块定位多个缺陷候选区域后执行自适应缩放精化,增强定位精度和补丁多样性。

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通过声明式数据契约将记忆生命周期各阶段解耦,并将评测协议与数据集正交分离,支持符号/神经/多模态记忆统一管理。跨系统组件集成实验显示组合组件与原生设计持平或更优,隔离评测逻辑后发现操作时序是影响性能的关键变量。

一句话结论

记忆组件耦合和评测协议绑定是系统间研究结论不可复现的根因;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:迭代加固缺陷复现测试与修复:F→P标准不足以评估BRT质量:宽松测试通过F→P却仍接受错误补丁。CoHarden以Lax信号为内循环收敛判据迭代加固测试与修复共生成,SWE-bench Verified达69.4%解决率。

两句看懂

超越F→P:迭代加固缺陷复现测试与修复。F→P标准不足以评估BRT质量:宽松测试通过F→P却仍接受错误补丁。CoHarden以Lax信号为内循环收敛判据迭代加固测试与修复共生成,SWE-bench Verified达69.4%解决率。

一句话结论

F→P是必要但不充分的BRT质量标准;共生成中测试-修复错误可相互耦合形成假阳性;只有严格BRT(拒绝所有变异错误补丁)才能持续提升修复成功率。

关键结果

基准:SWE-bench Verified;指标:Resolved率与F→P率。CoHarden:69.4% Resolved、78.9% F→P。超最强fix-only基线+9.6pp(Resolved),超最强共生成基线+7.9pp(Resolved)。实验覆盖多个LLM主干与多个基准集以验证一致性。

打开论文原文
它要解决什么
F→P通过的BRT中存在宽松测试吗?共生成时测试与修复的错误如何相互掩盖并导致修复率虚高?
它怎么做
三阶段:①测试优先——在任何修复前独立生成BRT;②变异检测——生成候选补丁并运行变异测试,将仍被接受的变异补丁标记为Lax回归;③加固收敛——以Lax信号反馈给测试生成器,迭代强化断言,直至所有变异补丁均被拒绝。核心约束:测试与修复不同步迭代,切断错误耦合回路。
下一步怎么用
下一步先核验实验设置与对照基线;不要只凭摘要中的结论判断它可复现。
证据来自哪里
SWE-bench Verified:69.4% Resolved、78.9% F→P;超最强fix-only基线+9.6pp、超最强共生成基线+7.9pp;多LLM主干和基准集均有一致增益。(筛选维度:可复核评测、软件工程方法)
别过度解读
全文摘录缺失;无法评估迭代收敛代价、变异补丁生成开销及在非SWE-bench场景的泛化能力。
方法与英文摘要

CoHarden:先独立生成BRT,再用变异补丁检测Lax测试,以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

LLM引导约束合成自动验证zkEVM:zkEVM中的细微语义错误(如gas计费错误)可令零知识证明通过但语义有误。VeriSynth让LLM将Rust代码翻译为Python/Z3约束、SMT求解器仲裁,95个注入缺陷中检出87个(91.6%)。

两句看懂

VeriSynth以LLM为翻译前端将Rust操作码转为Python/Z3符号约束,再由SMT求解器判定正确性,形成闭环流水线。在95个注入缺陷的zkEVM基准上检出87个(91.6%),比生产级手写变异测试套件多检出32个。

一句话结论

LLM翻译加SMT求解器仲裁的混合流水线在zkEVM基准上检出率达91.6%,比生产级手写测试套件多发现32个缺陷。

关键结果

在首个源码级zkEVM缺陷基准(95个注入缺陷,含正确和错误操作码实现)上评测,检出87个(91.6%),生产级手写变异测试套件仅检出55个。消融:去掉自动修复后检出率从91.6%降至66.3%;检索增强与语义分解各提供独立增益。

打开论文原文
它要解决什么
如何将Rust编写的zkEVM操作码实现自动转化为可执行SMT验证模型,替代不可扩展的人工规约?
它怎么做
语义分解将复杂操作码拆为可逐一翻译的子组件;检索增强提示从已有规约中取相关样本减少幻觉;验证驱动自动修复检测Z3模型的语法/类型错误后反馈LLM重生成直到可执行;SMT求解器最终裁定约束与被测实现是否一致。
下一步怎么用
适合在Rust安全关键代码项目中评估此验证流水线;不要误以为LLM在此框架中承担推理判断——它仅作翻译前端,推理由SMT求解器完成。
证据来自哪里
在95个注入缺陷基准上检出87个(91.6%),比生产级手写变异测试套件(检出55个)多32个;消融显示去掉自动修复后检出率降至66.3%。(筛选维度:形式化验证、可复核评测)
别过度解读
仅在95个注入缺陷的小规模基准上评测,跨操作码复杂交互缺陷的覆盖能力未验证。
方法与英文摘要

LLM将Rust操作码翻译为Python/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 原文