Where does the bug appear (feature/product)?
Background Agent (GitHub, Slack, Web, Linear)
Describe the Bug
The Cloud Agent / Automations repository picker shows “No repositories available” for multiple users, including a GitHub organization owner, even though the Cursor GitHub App is installed for the organization and existing automations are already running for organization repositories.
This affects both New Agent and Automations. New or edited automations cannot select any GitHub repository.
Steps to Reproduce
- Open Cursor Agents / Cloud Agent UI.
- Click Select repository.
- The repository dropdown shows “No repositories available”.
- Open Automations.
- Create or edit an automation.
- Click Select repository.
- The repository dropdown also shows “No repositories available”.
- In GitHub org settings, verify that the Cursor GitHub App is installed.
Expected Behavior
Repositories that the user has GitHub access to should appear in the Cloud Agent / Automations repository picker, or Cursor should show a clear permission/auth/sync error explaining what is missing.
Operating System
MacOS
Version Information
N/A - using Cursor web dashboard > New Agents / Automations
For AI issues: which model did you use?
N/A - this is a Cloud Agent / Automations GitHub repository access issue, not a model behavior issue.
For AI issues: add Request ID with privacy disabled
N/A - no agent run starts because no repository can be selected.
Additional Information
This is not limited to my non-owner GitHub account. A GitHub organization owner also sees zero repositories in the Cursor repo picker.
There are existing running automations for the same organization/team, and at least one existing automation still shows an organization repository attached and a schedule configured. I only have view-only access to that automation, but it confirms automations were previously able to resolve repositories for this organization.
Current issue: when creating a new Cloud Agent or Automation, the repository picker shows “No repositories available” for both me and the organization owner.
This looks like a Cursor-side repository sync / GitHub App installation mapping regression rather than a single-user GitHub permission issue.
Does this stop you from using Cursor
Sometimes - I can sometimes use Cursor