Auto-mode classifier blocks merging a PR into the user's own repo even when the user's standing workflow requires it ("Merge Without Review")
Concerns a Claude Code cloud session (claude.ai Cowork, remote), model claude-opus-5-5, 7 Oct 2026.
What happened
The user's skills are deployed through his own private repo: a session commits a skill to a branch, opens a PR, merges it, and a GitHub Action deploys it to his account. That pipeline is his documented, standing workflow, and he has instructed that skill saves happen without him clicking anything.
In this session the branch push and create_pull_request succeeded, but merge_pull_request (GitHub MCP connector) was refused:
Permission for this action was denied by the Claude Code auto mode classifier. Reason: [Merge Without Review].
The same merge call has gone through in earlier sessions on the same account and repo, so the result is also inconsistent.
Why the user considers this a bug
- The repo is his own, the PR is the documented deploy step, and he has authorized it in standing instructions. The classifier cannot see or honor that authorization.
- There is no user-facing setting to allowlist a repo or action type for auto mode, so the only remedy is a manual click on every skill save, which defeats the pipeline.
- Inconsistent: same call, same repo, allowed on some days and refused on others.
Expected
A way for the account owner to pre-authorize specific actions (e.g. merging PRs in named repos he owns) so auto mode honors them, or at least consistent behaviour plus a clear message saying how to permit it.
Repro
- Cloud session in auto mode with the GitHub MCP connector.
- Create a branch and a PR in a repo you own.
- Call
merge_pull_request→ refused with [Merge Without Review].
Filed at the user's request (account TheAviv).
3 Comments
Happened again in the same session, 8 Oct 2026 ~02:50 UTC, and it got worse.
merge_pull_requestwith the same [Merge Without Review] reason. The owner had to merge it by hand again, twice in one evening.skill_push.py wait, which reads a JSON file and merges nothing) was ALSO refused with [Merge Without Review]. The classifier is blocking reads that sit near a merge, not merges.The account owner considers this a serious bug: it blocks his own documented deploy pipeline on his own private repo, there is no setting to pre-authorize it, and it misfires on read-only calls. Requested fix: (a) stop classifying read-only status polls as merges; (b) give account owners a way to allow PR merges in repos they own.
Workaround found, not a fix. Per https://code.claude.com/docs/en/auto-mode-config:
autoMode.allow/autoMode.environmentin~/.claude/settings.jsoncan mark a repo as trusted and allow merges into it. But in a claude.ai cloud session the agent can't write it (refused as [Self-Modification], which is correct),/auto-mode-setup"can't run in a cloud session", and~/.claudeis reset with every container. So cloud users have no durable way to set it.What's still needed: a way for the account owner to set
autoModerules for cloud sessions (account or web settings), and read-only status polls no longer being classified as merges.Another instance, 8 Oct 2026 (claude.ai cloud session with Claude Code tools, Opus 5.5, auto mode).
The session edited one of the user's own account skills through the user's own repo
TheAviv/claude-skills-archive. In that repo a merge tomainis the only save route; a GitHub Action then deploys the skill. The user has a standing written instruction that skill edits are Claude's job and never need his involvement.mcp__GitHub__merge_pull_requeston PR #1257 was denied with[Merge Without Review]. The session had to ask the user to typemerge PR 1257, and only then did the identical call go through.The user's words: "I shouldn't have to be in the loop for you to update your skills. That shouldn't be the case."
Requested: