Agent Merge: Pull request gets merged directly without following configured monitoring/checks first

Version: 1.139.0-insider (user setup)
Commit: f44f55cde0c1ff6c834bad0bb46397bc48711da8
Date: 2026-09-15T08:49:29-07:00
Electron: 42.10.0
ElectronBuildId: 15109253
Chromium: 148.0.7778.280
Node.js: 24.18.1
V8: 14.8.178.38-electron.0
@github/copilot: 1.0.84-5
@github/copilot-sdk: 1.0.13
OS: Windows_NT x64 10.0.26200

- Feature (e.g. agent/edit/ask mode): Agents/Agent Merge
- Selected model (e.g. GPT 4.1, Claude 3.7 Sonnet): GPT-5.6 Terra
- Logs:
```
Agent Merge is enabled for agents/admin-imports-fix-search-dropdown. It will wait for a pull request on this branch, then monitor it.

It will ask the agent to address new pull request review comments.
It will ask the agent to fix failing CI checks.
It will ask the agent to resolve merge conflicts and update the branch when it falls behind.
Replies it posts will identify Agent Merge as the source.
After each update, it will wait for new CI results and review comments.
When the pull request is ready, Agent Merge will merge it automatically.
It will choose an available merge method automatically.
10:51 AM

Agent Merge merged pull request #1898.
10:52 AM
```

Steps to Reproduce:

1. Make committable changes
2. Use the Create PR button
3. Configure Agent Merge and enable all review options
4. Create PR or send PR message to chat
5. PR gets merged immediately without configured/expected monitoring

# Root cause
The session’s Agent Merge monitor was active independently of that repository workflow. After the PR-creation turn ended, it made a direct merge API action using the session’s authenticated identity rather than waiting for:

- the repository’s pending or failing CI states,
- the Copilot review request to complete,
- unresolved review threads, or
- branch-protection-required checks.