On an Individual Cursor plan with no team (dashboard/members only shows “Create team”), my Bugbot GitHub installation for casper7995 keeps flipping to:
Badge: “Team Managed”
Message: “Only team admins can modify installation settings and enabled repositories.”
I cannot change installation settings even though I own the repos. It briefly works after disconnect/reconnect, then the Team Managed lock returns by itself.
Disconnect GitHub in Integrations and/or uninstall the Cursor GitHub App, then reconnect.
Bugbot works briefly (or lock clears).
Without creating a team, the “Team Managed” lock returns again.
Expected Behavior
On an Individual plan with no team, Bugbot should not show “Team Managed” or require team admin. I should be able to manage my own GitHub installation and enabled repositories. The team association should not reappear after reconnect.
Thanks for the clear report, and sorry for the trouble.
You’ve diagnosed this correctly: it’s a bug on our side, not your setup. An old, canceled team still linked to your account is being attached to your Bugbot GitHub installation, and that’s what triggers the “Team Managed” lock even though you’re on an individual plan with no active team.
Two things worth knowing:
Disconnecting and reconnecting, or reinstalling the GitHub App, won’t resolve it. The old team gets reattached automatically when the installation is recreated, which is the “it comes back by itself” behavior you’re seeing. I’d hold off on further reinstalls for now, since they won’t hold and can reset your enabled repositories.
This one needs a fix on our side. There isn’t a reliable workaround in the meantime, so it will need our bug fix to fully clear. We’ve logged it with the team, and I’ll follow up here as soon as there’s progress.
Totally understand, and thanks for bearing with us.
While the cloud PR reviews are locked, you can still run Bugbot locally in Cursor, which doesn’t depend on the stuck GitHub installation:
In the agent, run /review-bugbot (or /review) to review your branch changes before pushing.
Or use the “Review Changes” button in the Source Control panel.
This works on your Ultra plan and needs Cursor 3.7+, so your build is good. It reviews local changes rather than the PR, but it’s a solid bridge in the meantime. More detail: Bugbot | Cursor Docs
On the cloud side, the lock comes from an old canceled team still attached to your installation. We’ll keep you apprised of any updates here for this bug.
Hi @argarcia-ottersoft We’re working on it! It will be a generalized solution, so we shouldn’t need your info at this time. I’ll follow up with any updates here.