今天，我们发布了 Bugbot 迄今为止最大规模的一系列改进。
Bugbot 现在的运行速度提升了 3 倍以上，成本降低了 22%，并且每次审查能多发现 10% 的漏洞。实际上，90% 的 Bugbot 运行现在都能在三分钟内完成。
更快、更便宜、更全面的 Bugbot 能让您更早发现问题，更快合并代码。
在推送代码前运行 Bugbot
现在，您可以在推送代码前，使用 `/review` 命令运行 Bugbot 和安全审查。`/review` 会提示您选择要运行哪些智能体，或者您也可以直接使用 `/review-bugbot` 和 `/review-security` 命令。
这是在推送代码前发现并修复问题的绝佳方式。
`/review` 命令还能与 GitHub 和 GitLab 上的 Bugbot 同步。如果您运行了 `/review`，然后使用相同的差异（diff）打开一个 PR，Bugbot 会识别出来，跳过此次审查，并留下一条评论，说明它已经审查过该差异。
该功能在 Cursor 3.7+ 版本及 cursor.com/agents 上可用，CLI 支持即将推出。
仅审查 PR 中的新增内容
默认情况下，每次推送更改时，Bugbot 都会重新审查整个 PR。这可能会对之前已经审查并批准的代码产生新的标记。现在，您可以配置 Bugbot，使其仅审查自上次审查以来的新增内容，从而将反馈集中在您的最新更新上。
我们是如何实现的
这些性能提升得益于工具链的改进以及我们在训练 Composer 2.5 方面取得的进展，该模型现在为 Bugbot 提供支持。我们的模型训练工作是未来持续改进 Bugbot 的一部分。
Bugbot 遵循模型屏蔽列表。如果您的组织选择不使用 Composer 2.5，Bugbot 将自动回退到下一个最佳可用模型。速度和性能可能因您的配置而异。
了解更多
在此处试用 Bugbot，并阅读 Bugbot 文档以了解更多信息。
Bugbot 现在可通过学习规则实现自我改进
Michael Zhao
使用 Bugbot Autofix 闭环代码审查流程
Jon Kaplan
团队版定价改进
Today we're shipping our biggest set of improvements yet to Bugbot.
Bugbot is now over 3x faster to run, 22% cheaper, and finds 10% more bugs per review. In practice, 90% of Bugbot runs now finish in under three minutes.
A faster, less expensive, more thorough Bugbot allows you to find issues sooner and merge code faster.
Run Bugbot before you push
You can now run Bugbot and Security Review with /review before pushing code. /review prompts you to choose which agents to run, or use /review-bugbot and /review-security directly.
This is a great way to catch and fix issues before pushing the code.
/review also syncs with Bugbot on GitHub and GitLab. If you run /review and then open a PR with the same diff, Bugbot recognizes it, skips the review, and leaves a comment noting it has already reviewed that diff.
Available in Cursor 3.7+ and on cursor.com/agents, with support in CLI coming soon.
Only review what's new in your PR
Bugbot by default re-reviews the entire PR every time a change is pushed. This can result in new flags on code it had already reviewed and approved. You can now configure Bugbot to only review what's new since the last review, keeping feedback focused on your latest updates.
How we got here
These performance gains are made possible by harness improvements and progress we've made training Composer 2.5, which now powers Bugbot. Our model training work is one part of how we will continue to improve Bugbot over time.
Bugbot respects model block lists. If your organization has opted out of Composer 2.5, Bugbot will automatically fall back to the next best available model. Speed and performance can vary depending on your configuration.
Learn more
Try Bugbot here and read the Bugbot docs to learn more.
Bugbot now self-improves with learned rules
Michael Zhao
Closing the code review loop with Bugbot Autofix
Jon Kaplan
Improvements to Teams Pricing