Claude Code Can Now Auto-Merge Your PRs — Here's Why That's Not Enough

Claude Code just shipped auto-fix and auto-merge. Your AI agent can now monitor PRs in the background, fix CI failures, and merge once all checks pass — without you touching a thing. This is a genuinely exciting development. But after building governance tooling for AI-generated code, I think teams need to understand what this does and doesn't solve before enabling it across their repos. What Claude Code Auto-Merge Actually Does The workflow is straightforward: Claude Code opens a PR It monitors CI check status in the background If CI fails, auto-fix attempts to resolve the failure Once all checks pass, auto-merge lands the PR You can literally walk away, start a new task, and come back to a merged PR. For developer velocity, this is a huge win. The Assumption Worth Questioning The auto-merge logic is: CI passes → safe to merge. But is that true? Consider two PRs that both have green CI: PR A: Bump express from 4.18.2 to 4.21.0. One file changed. All tests pass. PR B: Add JWT authentic