Where does the bug appear (feature/product)?
Bugbot / Security Review Agent
Describe the Bug
There is currently no way to understand where BugBot costs are coming from. Billing shows a breakdown per model and “usage on demand”, but it’s very hard to tell which PRs, repos, or automations are actually driving that spend. We’re experimenting with multiple models and switching between them, which makes this even harder to track. Since we can’t see where the cost originates, we’ve had to reduce our BugBot usage, which is blocking our review workflow. We’d like a dedicated usage/billing view (similar to the existing BugBot GitHub billing section) that shows cost per model, per PR, and ideally per automation or per repo, so we can understand and optimize spend without having to guess.
Steps to Reproduce
- Enable BugBot on a GitHub org/repo and let it review multiple PRs over a billing period.
- Use several different models for BugBot reviews (or switch models over time).
- Go to Cursor billing / usage dashboard and try to determine which specific PRs, repos, or automations generated the BugBot spend.
- Notice that only an aggregate breakdown per model and general “usage on demand” is available, with no way to trace cost back to a specific PR, repo, or automation.
Expected Behavior
Expected: A dedicated usage/billing view for BugBot (in the dashboard or GitHub billing section) that shows cost broken down per model, per PR, and ideally per automation/repo, so we can identify which PRs, repos, or automations are driving spend and optimize model choice and automation triggers accordingly. Even a coarse per-repo/per-automation breakdown would be a big improvement over the current aggregate view.
Operating System
MacOS
Version Information
N/A – this relates to the BugBot billing/usage dashboard on cursor.com, not a specific IDE/CLI version. Accessed via Chrome on macOS.
For AI issues: which model did you use?
N/A - not tied to a specific model, applies to all models used with BugBot
Additional Information
This is a feature request more than a bug: the underlying billing data likely exists on Cursor’s backend (since the GitHub billing section already shows some breakdown), but it’s not surfaced granularly enough in the BugBot/GitHub billing UI. Filing here as our team can’t move forward with heavier BugBot adoption until we can see where cost is coming from.
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor