Vulnerability Scanner: weekly/cron schedule requires a branch, but UI has no branch picker

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Bugbot / Security Review Agent

Describe the Bug

Where does the bug appear (feature/product)?

Bugbot / Security Agents / Vulnerability Scanner (cursor.com dashboard)

Describe the Bug

Changing a Vulnerability Scanner trigger to a weekly schedule or custom cron shows:

The “Every week” trigger needs a branch selected.

Repo scope is already set (e.g. NetanelH2/mentor, 1/1 enabled). Configure → Manage repositories only lets you enable/disable orgs/repos — there is no branch field anywhere (not on the trigger row, not in Manage repositories, not when editing a custom cron).

So the form validates that a branch is required, but never exposes a control to set it. Saving is blocked no matter what.

Regular Automations docs say scheduled runs need repo and branch — that picker exists for normal automations, but is missing on the managed Vulnerability Scanner page.

Steps to Reproduce

  1. Open Security Agents → Vulnerability Scanner on cursor.com
  2. Ensure Repo scope has at least one repo enabled
  3. Set trigger to Every week (or Custom schedule cron, e.g. 0 3 * * 1)
  4. Click Configure under Repo scope → only org/repo enable UI; no branch
  5. Try to Save

Expected Behavior

Either a branch picker on the schedule trigger / single-repo settings (e.g. default to main), or don’t require a branch if repo scope + default branch is enough.

Actual Behavior

Validation error blocks save; no UI path to select a branch.

Operating System

macOS

Version Information

Cursor Web App (Security Agents / Vulnerability Scanner)

Does this stop you from using Cursor

No — but it blocks configuring a weekly Vulnerability Scanner schedule.

Steps to Reproduce

Creating a new Vulnerability Scanner

Expected Behavior

Created.

Screenshots / Screen Recordings

image.png
image.png980×1090 67.8 KB

Operating System

MacOS

Version Information

Version: 3.15.13
VS Code Extension API: 1.128.0
Commit: db56c26fed834fb7fd3e85a82d5acd0b393b9dc0
Date: 2026-08-08T01:41:56.624Z
Layout: Agent Window
Build Type: Stable
Release Track: Nightly
Electron: 40.10.3
Chromium: 144.0.7559.236
Node.js: 24.15.0
V8: 14.4.258.32-electron.0
xterm.js: 6.1.0-beta.291
OS: Darwin arm64 25.6.0

Does this stop you from using Cursor

No - Cursor works, but with this issue

6

Hey there! Thanks for the report - that isn’t intended on your end.

Workaround: in Repo scope → Configure, enable at least two repos (a throwaway under the same org is enough if you only have one), then Create Agent again. Or use the generic New Automation editor, which still has a branch picker.

We’ve let the team know and this is an issue we’re tracking. I’ll post here when there’s an update.

7

this is the only repo I have.
How to proceed from here?

image
image1406×556 28 KB

8

Hey, still blocked on this.

I only have one repo, so enabling two repos isn’t an option. Is there another way to set the branch, or should I use a generic automation instead?