# Vulnerability Scanner: weekly/cron schedule requires a branch, but UI has no branch picker **URL:** \ **Category:** Bug Reports\ **Tags:** automations, bugbot, security\ **Created:** [August 9, 2026, 11:49am UTC](https://forum.cursor.com/t/vulnerability-scanner-weekly-cron-schedule-requires-a-branch-but-ui-has-no-branch-picker/167809 "2026-08-09T11:49:05Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Netanel](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/netanel/32/107465_2.png) [@Netanel](https://forum.cursor.com/u/Netanel)\ **Post date:** [August 9, 2026, 11:49am UTC](https://forum.cursor.com/t/vulnerability-scanner-weekly-cron-schedule-requires-a-branch-but-ui-has-no-branch-picker/167809/1 "2026-08-09T11:49:05Z")
### 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](http://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](http://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](https://us1.discourse-cdn.com/cursor1/original/3X/3/f/3f6165cf9182e49717bd7b53e2b436864868006b.png) ### 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 ---
**Author:** ![mohitjain](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/mohitjain/32/100229_2.png) [@mohitjain](https://forum.cursor.com/u/mohitjain)\ **Post date:** [August 10, 2026, 11:56am UTC](https://forum.cursor.com/t/vulnerability-scanner-weekly-cron-schedule-requires-a-branch-but-ui-has-no-branch-picker/167809/6 "2026-08-10T11:56:30Z")
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. ---
**Author:** ![Netanel](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/netanel/32/107465_2.png) [@Netanel](https://forum.cursor.com/u/Netanel)\ **Post date:** [August 10, 2026, 12:13pm UTC](https://forum.cursor.com/t/vulnerability-scanner-weekly-cron-schedule-requires-a-branch-but-ui-has-no-branch-picker/167809/7 "2026-08-10T12:13:19Z")
this is the only repo I have. How to proceed from here? ![image](https://us1.discourse-cdn.com/cursor1/original/3X/7/7/771f487c83c1fe8cfac5181467c194f9c9c665ce.png) ---
**Author:** ![Netanel](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/netanel/32/107465_2.png) [@Netanel](https://forum.cursor.com/u/Netanel)\ **Post date:** [August 13, 2026, 9:18am UTC](https://forum.cursor.com/t/vulnerability-scanner-weekly-cron-schedule-requires-a-branch-but-ui-has-no-branch-picker/167809/8 "2026-08-13T09:18:07Z")
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? ---
**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\ **Post date:** [September 12, 2026, 9:18am UTC](https://forum.cursor.com/t/vulnerability-scanner-weekly-cron-schedule-requires-a-branch-but-ui-has-no-branch-picker/167809/9 "2026-09-12T09:18:45Z")
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed. ---
**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\ **Post date:** [September 24, 2026, 10:39pm UTC](https://forum.cursor.com/t/vulnerability-scanner-weekly-cron-schedule-requires-a-branch-but-ui-has-no-branch-picker/167809/11 "2026-09-24T22:39:15Z")
Hey @Netanel, The Vulnerability Scanner no longer requires a branch when only one repository is in scope, so you should now be able to save a weekly or custom cron schedule with just your one repo enabled. Scheduled runs will use the repo’s default branch. Could you give it another try on the Security Agents page and let me know if anything still blocks you? ---
**Author:** ![Colin](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/colin/32/90452_2.png) [@Colin](https://forum.cursor.com/u/Colin)\ **Post date:** [September 24, 2026, 10:39pm UTC](https://forum.cursor.com/t/vulnerability-scanner-weekly-cron-schedule-requires-a-branch-but-ui-has-no-branch-picker/167809/12 "2026-09-24T22:39:23Z")
---
**Author:** ![Netanel](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/netanel/32/107465_2.png) [@Netanel](https://forum.cursor.com/u/Netanel)\ **Post date:** [October 13, 2026, 9:28am UTC](https://forum.cursor.com/t/vulnerability-scanner-weekly-cron-schedule-requires-a-branch-but-ui-has-no-branch-picker/167809/13 "2026-10-13T09:28:01Z")
Confirmed, it works now. Thanks! You can close this. ---
**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\ **Post date:** [October 15, 2026, 9:28am UTC](https://forum.cursor.com/t/vulnerability-scanner-weekly-cron-schedule-requires-a-branch-but-ui-has-no-branch-picker/167809/14 "2026-10-15T09:28:05Z")
This topic was automatically closed 2 days after the last reply. New replies are no longer allowed.