Summary
Cursor now lets Teams admins and individual users change how much reasoning Bugbot uses during pull request reviews. The new settings add default, high, and natural-language custom modes so customers can trade off review depth, cost, and latency.
What changed
Cursor added configurable effort levels for Bugbot PR reviews.
Why it matters
This exposes the quality versus cost tradeoff directly inside AI code review instead of leaving review behavior as a fixed black box. It also suggests that reasoning-depth controls are becoming a product surface in automated developer workflows.
Evidence excerpt
Cursor says Bugbot now supports default, high, and custom effort modes, and that high effort finds more bugs per run at higher cost and latency.