[Requests and ideas] In Agent Merge, would be great to have options to shape how the agents behave.
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 153
- PR merge metrics
- No merged PRs in 30d
Description
**Mood:** 😊
**Category:** Requests and ideas
In Agent Merge, would be great to have options to shape how the agents behave.
e.g. some projects might want Agent Merge to automatically resolve conversations (current default behaviour), while others might only want to fix and leave a coment.
This could be achieved e.g. with a .github/agent-merge.yml file with config flags the skill use to shape its behaviour
---
| Field | Value |
| --- | --- |
| App version | 1.0.16 |
| OS | macOS 26.5.1 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Week 8 |
Contributor guide
Research direction
Start with the Agent Merge behavior described in the issue and determine where its current automatic conversation resolution is controlled. Define the configuration flags for .github/agent-merge.yml, including whether conversations are resolved or only commented on. Done means the selected repository configuration reliably shapes Agent Merge behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100