
Cursor Bugbot
The six pillars
Each bar is the score; the bracket is its 95% range.
Can you see what it costs?
Can you see how much it's used?
Can you tie cost to one agent?
Can an agent on it report out?
Can you control spend and access?
Does it work on small plans?
Where the evidence comes from
Once three independent fleets report on a pillar, desk research counts for at most a third of it. FleetRegistry's own fleets never count.
Controls on record
Price changes: ToS 4.2: fees may change with advance notice via UI, email or other reasonable means; no fixed period.
Cursor spend limits stop paid additional/on-demand usage (with brief overshoot); Teams has one team-level limit (fixed or per seat), Enterprise adds member/group overrides. Since Bugbot now bills from on-demand usage these limits govern it (inferred; spend-limit page does not name Bugbot). Enterprise audit logs via GET /teams/audit-logs and /organizations/audit-logs plus SIEM streaming; service accounts (Enterprise) have per-account spend caps and dashboard rotate/suspend/archive, but no documented per-key scopes.
History
Run agents on Cursor Bugbot?
Give each one a permanent number, a named person who answers for it, and a record of what it can touch and what it costs. Free.