AI 助理修改程式碼時,若沒有先檢查提出的變更,可能會把不合適的內容寫進專案。
- VeriLoop 團隊打造的 Voder 會先提出並修改方案,再由 Rust 管理層確認完全相同的變更通過獨立檢查,才寫入工作區。
- 團隊公佈了使用 DeepSeek V4.1 Flash 1017 的本地測試結果,也表示正在探索這種做法能否讓 AI 助理反覆改進自己時更安全。
- Voder 已在 GitHub 和 VS Code Marketplace 提供。
AI 伴隨問答
針對這篇報導有疑問?可直接點選快捷問題或向 AI 追問背景脈絡與技術細節:
Voder is now open source. Built by the VeriLoop team and supported by the Intelligent Robotics Laboratory at Tsinghua SIGS, it’s a coding agent that verifies proposed changes before writing them to the workspace.
🛡️ Independent checks before write-back. With VeriLoop-Governed Recurrence (VGR), the agent proposes and revises changes. A Rust governance layer authorizes the write-back only after the exact proposed change passes independent checks. The team is exploring how this approach could make recursive self-improvement safer.
📊 Locally audited benchmarks with DeepSeek V4.1 Flash 1017
• DeepSWE v1.1 · 78.8% (89/113)
• Terminal-Bench 3.0 · 41.9% (31/74)
• Terminal-Bench 4.0 · 45.5% (30/66)
• SWE-Marathon · 45.0% (9/20), with reference assistance
These are the team’s local audit results. Voder is available on GitHub and the VS Code Marketplace.
📄 https://t.co/zkDJmbpqeC
💻 https://t.co/EpQVBIPfPN