GitLab Merge Request Review Agent with OpenClaw
The line doing the most work here forbids things: approving, merging, closing or reopening, pushing a commit, and resolving somebody else's thread. One note per qualifying event and the occasional Slack line is the whole of its output. OpenClaw is a straightforward harness to run inside a boundary drawn that clearly.
Watch it work before it's live
Run a staged conversation — no account needed. The agent handles it for real while a simulated world answers its tool calls; nothing touches real accounts, and nothing is actually sent.
Add idempotency keys to the refunds endpoint
Open@fatima.zahra
Adds an Idempotency-Key header to POST /refunds and stores the key against the refund for 24 hours, so a retried request returns the original refund instead of issuing a second one. Migration adds one table and a unique index. Twelve files, 340 lines added, 46 removed. Unit and integration tests included, pipeline green on the head commit. Closes issue 2841.
Set up in minutes
Using this template drops you into a guided setup. It asks exactly this, nothing else:
Connect GitLab
One sign-in. The agent acts through your account, scoped to what this template uses.
Connect Slack
One sign-in. The agent acts through your account, scoped to what this template uses.
Review checklist
What a merge request has to satisfy on this project in your own words, which of those items block a merge, and what you want asked of the author when an item cannot be judged from the diff alone.
Runs on OpenClaw
Preselected for this page — connect your OpenClaw account during setup, or switch to NoClick's built-in models with one click.
Watch it handle a test run
A staged conversation against a simulated world — then it’s live.
Why OpenClaw for this agent
It cannot ship anything
Nothing merges because software liked it. The note is evidence a reviewer reads, and your approval rules are left exactly as they were.
Enforce it at the token
If instruction alone is not enough for you, give it a role that can comment on merge requests and cannot merge them, and the limit stops depending on the agent.
Before you fork
Which parts of the merge request can it change?
None of them. It creates notes and reads everything else. Labels, assignees, milestones, the title, the branch and the merge button all sit outside its reach, and it will not resolve a thread somebody else opened. The only thing it can get wrong is the content of a note, which a reviewer answers in a reply.
Run it with a different agent
Put GitLab Merge Request Review Agent to work on OpenClaw
Free to start. Guided setup, a test run against staged conversations, and it's live.