Agent Merge UI Improvement Suggestions
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 153
- PR merge metrics
- No merged PRs in 30d
Description
Agent Merge UI Improvement Suggestions
After enabling 'Agent Merge', I often want to _only_ have 'Merge pull request' checked with the others unchecked. Trying to uncheck the other items first ends up disabling 'Agent Merge' as soon as the last item is unchecked. In order to turn on 'Merge pull request' only, you have to check it first, and then uncheck the other items.
It's also disconcerting that when I enable 'Agent merge' those other items are checked by default. Will I turn them off fast enough before it starts to take action?
I recommend:
1. Have an 'Apply' button to apply the agent merge options
2. Do not functionally enable agent merge until the user has turned it on, selected which features they want enabled, and clicked Apply
3. Ensure the UI allows me to turn off all items and then turn one on without dismissing the popup
---
| Field | Value |
| --- | --- |
| App version | 1.1.3 |
| OS | Windows 10.0.26200 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Week 3 |
Contributor guide
Research direction
Start at the Agent Merge options popup from the /chat entry point and reproduce the sequence of unchecking every option, then selecting only “Merge pull request.” Done means the popup supports choosing options without dismissing or activating the agent prematurely, and an Apply action commits the selection; no files or tests are named in the issue.
Written by the indexing model from the issue text.
Assessment
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 56/100