Multi-repo Automations not saving repo selection

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cloud Agent (GitHub, Slack, Web, Linear)

Describe the Bug

I’m trying to select 4 repositories for a single Cursor Automation. I see that by default the repo picker is in single repo mode, so I click the “Select Multiple” button in the dropdown, and then search for all 4 of my repos (from the same organization). They show visible in that picker, so I press the save button on the automation, and I get the “Saved successfully” toast message. At that point though, the selected repository visually shows “Select repository” AND I can’t trigger a test run because it says I haven’t selected any repositories.

Steps to Reproduce

  1. Go to an automation
  2. Click the repository dropdown and then click the “Select Multiple” button in the dropdown
  3. Select 4 repos from the same organization
  4. Press the save button on the automation, and see that the “Saved successfully” toast appears
  5. Refresh the page and see that the selected repository visually shows “Select repository”. This is the bug

Operating System

MacOS

Version Information

N/A (we’re talking about the Automations view in the Cursor dashboard

Does this stop you from using Cursor

Yes - Cursor is unusable

6

Hey there!

What’s happening: when a multi-repo environment that an automation uses gets saved to the team, the automation’s link to that environment isn’t carried over, so the picker falls back to “Select repository” and test runs get blocked — even though the save reported success. We’ve seen this pattern before, and I’ve logged your case with the team.

To get you unblocked now:

  1. Open the automation and, in the repository picker, select the multi-repo environment that already holds your four repos - the team one created when you saved to the team - then Save.
  2. Refresh once and confirm the four repos stick and the test run is allowed.

Going forward, set the multi-repo environment up as a team environment first (Cloud Agents → Environments), then point the automation at it - rather than saving an environment to the team while an automation is already using it, which is what clears the selection.

Give that a try and let me know if the selection sticks after a refresh - happy to dig in further if anything’s still off.

7

The environment wasn’t listed in the repository picker for me. I created a brand new environment from scratch though, and then a brand new automation after that and that new environment is now visible in the picker. That appears to have resolved the issue with saving, thank you.