Feature request for product/service
Describe the request
Summary
Add a self-serve way for team admins (and individual users, where applicable) to remove or hide specific repositories from the “All Repositories” filter on the Usage Analytics dashboard (cursor.com/dashboard/analytics).
Current behavior
The repository filter on the dashboard is auto-populated from git activity detected across team members’ machines (Cursor 1.5+). Any repo with a resolvable origin remote that sees Cursor usage shows up in the dropdown — including:
Stale repos the team no longer maintains
Forks, experiments, scratch repos, and one-off clones
Repos that belong to a different org but were briefly opened in Cursor
There is currently no UI control to remove a repo from this list. The only documented options are:
GitHub/GitLab app repo selection — controls Cloud Agents/Bugbot scope, not analytics
Enterprise repository blocklist — blocks access, not analytics attribution
Privacy Mode — team-wide, not repo-specific
Ref: Usage Analytics docs
Problem / use case
Signal-to-noise — stale repos dilute meaningful team metrics (AI Share of Committed Code, Agent Edits, etc.). When I filter “All Repositories,” I want to see my team’s work repos, not my weekend project.
Privacy — Some developers don’t want repo names visible to team admins in the analytics dropdown, even if the metrics themselves are harmless.
Reporting accuracy — When leadership reviews adoption or ROI, irrelevant repos skew perception. Admins currently have no way to curate the view.
Onboarding / offboarding hygiene — Repos from departed team members or deprecated projects linger with no cleanup path.
Proposed solution
Ideally a combination of:
Admin-side repo management in the dashboard:
Under Team Settings → Analytics (or similar), a list of repos with a “Hide from analytics” toggle per repo.
Bulk hide/unhide and a search filter.
Hidden repos are excluded from the dropdown, charts, and aggregate metrics (or optionally just the dropdown — see option 3).
User-side opt-out:
Granularity options:
Hide from view (cosmetic — still counted in totals)
Exclude entirely (remove from totals and charts)
Admins choose which mode per repo.
Audit trail:
Show who hid/excluded a repo and when, so admins can review.
Alternative / lighter-weight version
If a full management UI is too much scope, even a simple “Remove from list” right-click/kebab action on each repo in the dropdown — gated to team admins — would solve 80% of the pain.
Related / prior art
GitHub Insights lets org owners archive/hide repos from org-level reporting.
Linear, Datadog, and most analytics tools allow admins to curate which entities appear in dashboards.
Impact
Cleaner dashboards → better exec reporting and adoption storytelling
More trust from devs that work won’t leak into team views
Reduced support load — currently the only path is emailing Cursor support to request manual removal, which isn’t documented anywhere
Thanks for considering! Happy to share more context or mock up screens if useful.
Operating System (if it applies)
Windows 10/11