When agent-merge is engaged in a Pull Request, it responds to any comment fro...
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 2.1k
- Forks
- 157
- PR merge metrics
- No merged PRs in 30d
Description
When agent-merge is engaged in a Pull Request, it responds to any comment from any user, at least in Enterprise settings. I have not tested it in public settings.
This poses a big security risk: If a user leaves agent-merge engaged in a public open source project, malicious actors could use it to instruct the users' Copilot App session to do basically anything they want, including introducing malicious code, merging the PR and even trigger a release.
agent-merge should introduce deterministic repository permissions checks and block any execution from users that don't have write/contributor permissions.
| Field | Value |
|---|---|
| App version | 1.1.17 |
| OS | macOS 26.6.2 |
| Theme | GitHub |
| Path | /chat |
| Tenure | Week 2 |
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how agent-merge handles Pull Request comments in Enterprise settings and where repository permissions are evaluated. Reproduce the behavior with a user lacking write or contributor permissions, then verify that unauthorized comments cannot trigger execution while permitted users still can.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- authorization, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100