返回 2026-08-25 编辑版
发现与解读中文优先 · EN 原文开源项目

Einsia 发布:SWE Refactor Bench 评估代码 Agent 的整仓迁移能力

对编码代理的最终测试不是本地编辑—— 这是整个回购协议的演变,目前,生存率为 5.4%。 今天我们要发布的是SWERefactor Bench,长期、全存储库软件堆栈迁移的基准。 编码代理越来越擅长修复错误。 但他们能否重构整个系统,C→Rust,Maven→Gradle,POSIX → WebAssembly? 我们跨项目构建了 20 个真实迁移,包括SQLite、zlib、libsodium 和GraphHopper。 520 次运行。只有 28 名选手通过了全部 3 个阶段。13/20任务没有人解决。 系统规模的迁移仍然是开放的。 全面解析👇GitHub:[https://github.com/Einsia/SWE-重构工作台] 论文链接:[https://arxiv.org/abs/2608.23564] Einsia网站:[https://lab.einsia.ai/swe-refactor-bench/]

查看英文原文

The ultimate test for coding agents isn't local editing— it's whole-repo evolution, and right now, the survival rate is 5.4%. Today we’re releasing SWE Refactor Bench, a benchmark for long-horizon, whole-repository software stack migration. Coding agents are getting very good at fixing bugs. But can they refactor an entire system, C → Rust, Maven → Gradle, POSIX → WebAssembly? We built 20 real migrations across projects, including SQLite, zlib, libsodium, and GraphHopper. 520 runs. Only 28 survived all 3 stages. 13/20 tasks were solved by nobody. System-scale migration is still wide open. Full breakdown 👇 GitHub: [https://github.com/Einsia/SWE-Refactor-Bench] Paper Link: [https://arxiv.org/abs/2608.23564] Einsia Website: [https://lab.einsia.ai/swe-refactor-bench/]

The ultimate test for coding agents isn't local editing— it's whole-repo evolution, and right now, the survival rate is 5.4%. Today we’re releasing SWE Refactor Bench, a benchmark for long-horizon, whole-repository software stack migration. Coding agents are getting very good at fixing bugs. But can they refactor an entire system, C → Rust, Maven → Gradle, POSIX → WebAssembly? We built 20 real migrations across projects, including SQLite, zlib, libsodium, and GraphHopper. 520 runs. Only 28 survived all 3 stages. 13/20 tasks were solved by nobody. System-scale migration is still wide open. Full breakdown 👇 GitHub: [https://github.com/Einsia/SWE-Refactor-Bench] Paper Link: [https://arxiv.org/abs/2608.23564] Einsia Website: [https://lab.einsia.ai/swe-refactor-bench/]

代码 Agent 的裁判从短任务通过率走向整仓迁移、可重生成任务和生产静默失败

为什么值得看

Agent 评估正在形成一条更接近真实交付的链路:任务能否长期完成、基准能否持续有效、生产失败能否被发现,以及运行底座是否安全。

最强反方

两项基准虽有论文或任务资产,实际覆盖面仍待复现;Agnost 与 Vetta 的生产改善和成本数字是发布方口径,安全风险来自独立简报汇总而非本期事故统计。

原始出现与传播对照

1 条出现 · 本次 AIHOT 未精确命中

发现与解读

对编码代理的最终测试不是本地编辑—— 这是整个回购协议的演变,目前,生存率为 5.4%。 今天我们要发布的是SWERefactor Bench,长期、全存储库软件堆栈迁移的基准。 编码代理越来越擅长修复错误。 但他们能否重构…

对编码代理的最终测试不是本地编辑—— 这是整个回购协议的演变,目前,生存率为 5.4%。 今天我们要发布的是SWERefactor Bench,长期、全存储库软件堆栈迁移的基准。 编码代理越来越擅长修复错误。 但他们能否重构整个系统,C→Rust,Maven→Gradle,POSIX → WebAssembly? 我们跨项目构建了 20 个真实迁移,包括SQLite、zlib、libsodium 和GraphHopper。 520 次运行。只有 28 名选手通过了全部 3 个阶段。13/20任务没有人解决。 系统规模的迁移仍然是开放的。

查看英文原文

The ultimate test for coding agents isn't local editing— it's whole-repo evolution, and right now, the survival rate is 5.4%. Today we’re releasing SWE Refactor Bench, a benchmark for long-horizon, whole-repository software stack migration. Coding agents are getting very good at fixing bugs. But can they refactor an entire system, C → Rust, Maven → Gradle, POSIX → WebAssembly? We built 20 real migrations across projects, including SQLite, zlib, libsodium, and GraphHopper. 520 runs. Only 28 survived all 3 stages. 13/20 tasks were solved by nobody. System-scale migration is still wide open. Full breakdown 👇 GitHub: [https://github.com/Einsia/SWE-Refactor-Bench] Paper Link: [https://arxiv.org/abs/2608.23564] Einsia Website: [https://lab.einsia.ai/swe-refactor-bench/]

The ultimate test for coding agents isn't local editing— it's whole-repo evolution, and right now, the survival rate is 5.4%. Today we’re releasing SWE Refactor Bench, a benchmark for long-horizon, whole-repository software stack migration. Coding agents are getting very good at fixing bugs. But can they refactor an entire system, C → Rust, Maven → Gradle, POSIX → WebAssembly? We built 20 real migrations across projects, including SQLite, zlib, libsodium, and GraphHopper. 520 runs. Only 28 survived all 3 stages. 13/20 tasks were solved by nobody. System-scale migration is still wide open. Full breakdown 👇 GitHub: [https://github.com/Einsia/SWE-Refactor-Bench] Paper Link: [https://arxiv.org/abs/2608.23564] Einsia Website: [https://lab.einsia.ai/swe-refactor-bench/]

直接发布标题Einsia@EinsiaAI打开该层出处 ↗

The ultimate test for coding agents isn't local editing— it's whole-repo evolution, and right now, the survival rate is 5.4%. Today we’re releasing SWE Refactor Bench, a benchmark for long-horizon, whole-repository software stack migration. Coding agents are getting very good at fixing bugs. But can they refactor an entire system, C → Rust, Maven → Gradle, POSIX → WebAssembly? We built 20 real migrations across projects, including SQLite, zlib, libsodium, and GraphHopper. 520 runs. Only 28 survived all 3 stages. 13/20 tasks were solved by nobody. System-scale migration is still wide open. Full breakdown 👇 GitHub: [https://github.com/Einsia/SWE-Refactor-Bench] Paper Link: [https://arxiv.org/abs/2608.23564] Einsia Website: [https://lab.einsia.ai/swe-refactor-bench/]

来源
X @_akhaliq · x-akhaliq
证据角色
x_project_network
时间状态
known
用户判决
未判
查看该来源原文raw/x-akhaliq.json5432628dd3480a4584a931c45377b3b8c2acf368ad8cfbcb4605ff9228dbe846
Cluster IDevt_040a902121a602aec7494cc6精确去重依据canonical_url事件状态未判