Automations Save resets selected non-default branch to main (Cloud Environment repo)

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cloud Agent (GitHub, Slack, Web, Linear)

Describe the Bug

On cursor.com/automations, I can search and select a non-default branch
(epic/<epic-name>). Clicking Save immediately resets the branch
field to main (the GitHub default). A reload still shows main.

Same result in the web editor and the IDE.

This causes the agent to not be able to open a PR to the desired branch because base_branch is main

Steps to Reproduce

Open the automation → select a non-default branch → Save → field snaps to the default branch → reload still default.

Expected Behavior

Save keeps the selected branch; cron runs fork from it.

Operating System

MacOS

Version Information

IDE: 3.16.29
Web

Does this stop you from using Cursor

No - Cursor works, but with this issue

7

Where does the bug appear (feature/product)?

Cloud Agent (GitHub, Slack, Web, Linear)

Describe the Bug

hey, in cursor automations when I select it to run on another branch and then hit “save” it goes back to the main branch

thus i think making it not possible to run cursor automations on a branch. it previously worked so i think it maybe or recent bug!

Steps to Reproduce

Go to automation in cursor (ide or cursor.com)
select a branch say for example “evals”
hit save
branch goes back “main”

Expected Behavior

stays on the selected branch when save is hit

Operating System

MacOS

Version Information

cursor ide version 3.17.8

Does this stop you from using Cursor

No - Cursor works, but with this issue

10

Hey all, thanks for the report!

This is a known issue we’re already tracking, when the repository has a Cloud Environment configured, the branch you pick in the automation editor isn’t kept after Save, which is why it snaps back to main.

We’re working on a fix now! In the meantime, a workaround is to tell the agent which branch to use directly in the automation’s prompt (e.g. “check out the evals branch first and base all work on it”) — the agent will switch branches at the start of the run.