LectureRechercheRadarCadre d'investissement
Connexion / Inscription
← Retour à la lecture
ActualitésSujet · AI代理代码范围蔓延Matériel4 min de lectureRédaction DisconfirmAI

Scope Creep in AI Agents: CodeRabbit Founder Harjot Gill and OpenCode’s Ryan Vogel on Why Deciding What to Keep Is Harder Than Generation

When AI produces two hundred pull requests a day, even if all are reviewed, whether the changes are necessary remains an open question. Gill and Vogel explain how scope creep occurs, how reference points counter it, and under what conditions this approach is effective.

2026-11-17 04:00 GMT+8

When AI agents can produce two hundred pull requests (PRs) a day or pile up six hundred pending changes for review at once, the core issue facing engineering teams is no longer whether the code has bugs, but whether these changes should exist at all. CodeRabbit founder Harjot Gill and OpenCode maintainer Ryan Vogel discussed this issue on The Merge podcast. Their consensus is that while AI-written code is useful, the harder part is deciding what to merge, what to push back on, and what to drop.

This judgment problem has an easily overlooked starting point: the problem takes shape before the code exists. Vogel gave the example of a kitchen to-do app—assign the task to an agent, and it will first add a database, then a caching layer, then more infrastructure. Each step individually does not look wrong, but the application ends up far more complex than a simple to-do list requires. Vogel pointed out that without an external reference point, every decision provides justification for the next, and the project can drift off course even while each step appears productive.

To combat this creep, Vogel and Gill each approached from different stages. Vogel’s method involves having the agent output an architecture plan first, which humans then challenge by identifying unnecessary parts; simultaneously, he runs a separate agent to compare intermediate outputs against the original requirement direction. Gill, drawing from CodeRabbit’s practice, added another dimension: review should not just look at diffs, but read changes in the order they were built. CodeRabbit divides review into three layers—the bottom layer consists of data and schema changes, the middle layer covers functions, business logic, and API routes, and the top layer includes the interface and its tests. Schema changes explain why an API behaves differently, and API changes explain what the interface now needs to handle. Reviewing in this order allows humans to check the assumptions connecting various parts, rather than guessing from filenames.

Connexion / Inscription
LectureRechercheRadarCadre d'investissement

But sequence alone is not enough; evidence is also required. Gill mentioned hallucination issues encountered early on by CodeRabbit: when models are forced to give answers, they fabricate them. The team’s solution was to provide an escape hatch—for situations with insufficient information, the model could ask questions, investigate further, or write a script to verify its hypotheses. This reduced the hallucination rate. In the review process, the same discipline means treating a suspected bug as something to be tested, rather than immediately turning it into a comment requiring developer action. The recipient of the review feedback can inspect how the conclusion was reached, run the check, and question its assumptions. Scripts themselves may still be incorrect or incomplete, but their value lies in making part of the claim verifiable.

This approach has a clear boundary of applicability. Gill pointed out that agents are best suited for tasks with clear completion conditions, such as adapting a working integration to another platform—because both the agent and the reviewer have concrete results to check. Open-ended design work requires more frequent human decision-making because the desired outcome is still taking shape while the agent runs. In other words, the premise for reference points to be effective is that you already know where you are going; if the destination itself is changing, the reference point loses its anchoring function.

Finally, both Gill and Vogel emphasized the handoff issue. The handoff from agent to developer receives most attention, but the handoff between people is equally important. Code alone does not show why a certain approach was chosen, what was tried and abandoned, which choices were deliberate, and which were merely defaults. Vogel’s team shares the full session logs behind changes, allowing colleagues reviewing the code to also see the prompts and the decisions that produced them. Gill mentioned CodeRabbit’s collaborative memory, where one developer’s review feedback influences subsequent reviews. Both methods allow the next person to see what was attempted and what still needs validation. Not every change deserves the same level of scrutiny—a small interface change that can be rolled back in minutes carries completely different consequences compared to a change on a mature code path relied upon by many people, and review effort should reflect this difference.

Sources

  • coderabbit.aiCodeRabbit↗
Sujet

AI代理代码范围蔓延

当 AI 编码代理一天生成数百个拉取请求时,真正的瓶颈不再是代码生成速度,而是决定哪些变更值得合并。CodeRabbit 创始人 Harjot Gill 与 OpenCode 的 Ryan Vogel 指出,“范围蔓延”——即代理在修复 B…

5 étapes1 piècesMis à jour 2026-11-19 18:32

Comment on en est arrivé là

  1. 2025-10-09NVIDIA 发布博客《从助手到对手》,揭示攻击者如何利用 Cursor 等代理式工具的系统提示弱点,通过 GitHub Issue 注入恶意指令实现远程代码执行,强调了限制代理自主性和隔离不可信数据的重要性。developer.nvidia.cn ↗
  2. 2026-04-20Cloudflare 工程团队分享其内部大规模应用 AI 代码审查的经验,采用基于 OpenCode 的编排系统,通过多个专业化代理协同工作来减少噪音并提高审查效率,同时强调插件化架构以支持不同 VCS 和模型。blog.cloudflare.com ↗
  3. 2026-10-04Athenode 发布文章探讨如何遏制 AI 代理的范围蔓延,建议在请求中明确划定“超出范围”的文件,并要求代理将发现的问题记录在单独的列表中而非直接修改,以保持变更的最小化。athenode.com ↗

Ce qui reste non résolu

  • 如何在保证代码质量的前提下,量化评估“过度工程化”带来的技术债务成本?
  • 现有的静态分析工具能否有效识别由 AI 代理引入的隐蔽性范围蔓延(如细微的逻辑重构)?
  • 随着代理自主性的提高,人类开发者在代码审查中的角色将如何从“逐行阅读”转变为“架构验证”?
Lire le sujet complet →
Continuer la recherche →