Skip to content

Conversation

@Mihir-Mavalankar
Copy link
Contributor

PR Details

  • When the triage-signals-v0 feature flag is enabled, replace the "Where should Seer stop?" dropdown with two simpler toggles:
    • Auto-open PR: Controls whether Seer automatically opens PRs (off=code_changes, on=open_pr)
    • Hand off to Cursor: Enables Cursor cloud agent handoff at root cause
  • The toggles are mutually exclusive - enabling one disables the other.
  • Screenshots:
    • Screenshot 2025-11-24 at 2 08 09 PM
    • Screenshot 2025-11-24 at 2 07 52 PM
  • Will rebase after this one merged

@Mihir-Mavalankar Mihir-Mavalankar self-assigned this Nov 24, 2025
@github-actions github-actions bot added the Scope: Frontend Automatically applied to PRs that change frontend components label Nov 24, 2025
@roaga
Copy link
Member

roaga commented Nov 24, 2025

I think they shouldn't be mutually exclusive. Rather the "auto-open PR" toggle should control whether any coding agent, Seer or Cursor, can open a PR or not

@Mihir-Mavalankar
Copy link
Contributor Author

Mihir-Mavalankar commented Nov 24, 2025

I think they shouldn't be mutually exclusive. Rather the "auto-open PR" toggle should control whether any coding agent, Seer or Cursor, can open a PR or not

This is to stick to the current behaviour. Currently they are mutually exclusive since "Hand off to Cursor" and "Open PRs" are different options in the dropdown.
Plus @jennmueng has another PR to make cursor Open PRs permission separate. I agree though that having two open PRs toggles can be confusing.
Tagging @Dhrumil-Sentry too. Should we combine both the Open PRs toggles?

@Mihir-Mavalankar
Copy link
Contributor Author

@ryan953 This is the PR to add the Open PR and cursor toggles to the project level Seer options.

…gnals-v0

When the triage-signals-v0 feature flag is enabled, replace the "Where should
Seer stop?" dropdown with two simpler toggles:

- Auto-open PR: Controls whether Seer automatically opens PRs (off=code_changes, on=open_pr)
- Hand off to Cursor: Enables Cursor cloud agent handoff at root cause

The toggles are mutually exclusive - enabling one disables the other.

Changes:
- Add handleAutoOpenPrChange and handleCursorHandoffChange handlers
- Add autoOpenPrToggleField and cursorHandoffToggleField field definitions
- Update fields array to show toggles (flag on) or dropdown (flag off)
- Add initialData for new toggle states
- Add tests for toggle visibility and preference updates
@Mihir-Mavalankar Mihir-Mavalankar merged commit 1b4efba into master Dec 1, 2025
48 checks passed
@Mihir-Mavalankar Mihir-Mavalankar deleted the open-pr-cursor-toggles branch December 1, 2025 18:24
jerryzhou196 pushed a commit that referenced this pull request Dec 1, 2025
…gnals-v0 [feature flagged] (#103932)

## PR Details
+ When the triage-signals-v0 feature flag is enabled, replace the "Where
should Seer stop?" dropdown with two simpler toggles:
+ Auto-open PR: Controls whether Seer automatically opens PRs
(off=code_changes, on=open_pr)
+ Hand off to Cursor: Enables Cursor cloud agent handoff at root cause
+ The toggles are mutually exclusive - enabling one disables the other.
+ Screenshots: 
+ <img width="2151" height="1167" alt="Screenshot 2025-11-24 at 2 08
09 PM"
src="https://github.com/user-attachments/assets/02a960f1-3963-40ff-888e-a64346ac9e13"
/>
+ <img width="2068" height="1118" alt="Screenshot 2025-11-24 at 2 07
52 PM"
src="https://github.com/user-attachments/assets/165d5bc6-cd18-4f43-a88b-f8c36185da49"
/>
+ Will rebase after [this
one](#103730) merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Scope: Frontend Automatically applied to PRs that change frontend components

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants