GitHub PR Review Agent with Codex

Three headings, one comment, a fixed verdict word against each checklist item, and a hard list of things it may not do: approve, merge, label, assign. The shape is decided before the run begins, and the work is fetching the pull request, its files, its commits and its existing reviews, then filling that shape in. Codex is at home in bounded API work of exactly this kind.
Loading preview…
Free to start · guided setup · switch agents any time.

Live demo

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.

Stream tile responses instead of buffering the whole body

Open

opened by @marijke-devos

Replaces the buffered writer in the tile handler with a streaming encoder, so a 40MB vector tile stops sitting in memory before the first byte goes out. Nine files, 214 lines added, 118 removed, all under internal/tiles. Adds a benchmark showing peak memory falling from 96MB to 11MB on the Jakarta extract, plus table tests for the partial write path. The description links issue 402 and states the wire format is unchanged.

What you'll need

Set up in minutes

Using this template drops you into a guided setup. It asks exactly this, nothing else:

  1. Connect GitHub

    One sign-in. The agent acts through your account, scoped to what this template uses.

  2. Connect Slack

    One sign-in. The agent acts through your account, scoped to what this template uses.

  3. Review checklist

    What a pull request has to satisfy in this repository, put the way you would explain it to somebody reviewing here for the first time: which items are hard blockers, which paths you treat as sensitive, and what you want asked when the diff alone cannot settle one.

  4. Runs on Codex

    Preselected for this page — connect your Codex account during setup, or switch to NoClick's built-in models with one click.

  5. Watch it handle a test run

    A staged conversation against a simulated world — then it’s live.

A considered pairing

Why Codex for this agent

READ, VERDICTS, ASKS, always

The same three parts arrive in the same order on every pull request, so a reviewer learns where to look once. Concrete output shapes are what this harness is most dependable on.

GitHub is ordinary ground

Pulling a pull request, its commits, its files and its reviews, then posting a single issue comment, is plain integration work. Nothing in the loop asks the harness to be inventive.

Good to know

Before you fork

Our pull requests touch four hundred files across a monorepo. What then?

GitHub returns changed files in pages and the agent judges what it was handed, so on a very large diff plenty of items resolve to cannot tell with a reason attached instead of to a verdict. That is intended behaviour rather than a shortfall. Monorepo teams usually narrow the bar down to the paths they genuinely gate on.

Other editions

Run it with a different agent

claude-codeClaude CodeopencodeopenclawhermesMore Codex agents

Make it yours

Put GitHub PR Review Agent to work on Codex.

Free to start. Guided setup, a staged test run, and a workflow you can change at every step.