Launching today

MergeWarden

Launching today

The change-control gate for AI-agent pull requests

1 follower

The change-control gate for AI-agent pull requests

1 follower

Visit website

AI coding agents open PRs all day. Who checks they stayed in bounds? MergeWarden is a checkout-free GitHub Action and CLI that gates AI-agent PRs against your repo's boundaries: declared scope, agent-control-plane drift (AGENTS.md,mcp.json), and workflow permission escalation. No checkout, no LLM, deterministic replayable evidence. See what it catches in one command, no token or repo: npx mergewarden demo. Built after scanning 2,204 merged agent PRs: zero declared their scope. MIT.

Free

Launch tags:Developer Tools•Artificial Intelligence•GitHub

Launch Team

Framer AI AgentsDesign and publish professional sites with AI

Promoted

Hunter

📌

Hi Product Hunt 👋 I'm Jinhyuk, maker of MergeWarden. Coding agents (Devin, Copilot, Codex, Claude Code, Cursor) now open and merge pull requests at scale. But when an agent PR lands, a reviewer has exactly what they'd have for a human PR: the diff. The agent knew precisely what task it was given — none of that intent survives into the PR in a form anything can check. So I scanned 2,204 recently merged agent PRs to see what actually happens. 0 of 2,204 declared a machine-checkable scope. Of the ones that touched CI workflows, ~13% escalated GitHub Actions permissions, and 3.9% edited the files that steer future agents (AGENTS.md, .mcp.json). MergeWarden is the change-control gate I built for exactly this: a checkout-free GitHub Action + CLI that checks each agent PR against your repo's boundaries — declared scope, agent-control-plane drift, and workflow permission escalation. It never checks out PR code, never calls an LLM, and every finding is deterministic and replayable. MIT-licensed. Try it on any public PR without installing anything: npx mergewarden scan owner/repo#123 Would love your feedback — especially on false positives and which boundaries you'd want checked. Happy to answer anything about the data or the detection rules.

Report

4d ago

Forum Threads

p/mergewarden

•

3d ago

We scanned 2,204 merged AI-agent PRs. Zero declared what they intended to change.

I spent a couple of weeks scanning merged pull requests opened by coding agents Devin, GitHub Copilot's coding agent, Codex, Claude Code, and Cursor across public repositories. 2,204 of them, read-only through the GitHub API, no LLM judgment anywhere, just deterministic checks.

The number that stuck with me: zero of the 2,204 declared, in any machine-checkable form, what they intended to change. Not "most didn't" zero.

Of the 349 that touched CI workflows or package manifests, 12.9% escalated workflow permissions and 17.5% added unpinned actions. 3.9% edited the files that steer every future agent run (AGENTS.md, CLAUDE.md, .mcp.json).

Most of those are probably fine. That is sort of the point: nobody declared them, so nobody can tell the difference without reading every diff by hand.

View all