PRBee
PRBee logo
Free beta · macOS on Apple silicon

Your pull requests keep moving
while you do something else.

PRBee runs your AI coding agent, Claude Code or Codex, over your pull requests: it reviews them, answers review threads, fixes red builds and conflicts, and keeps branches up to date, on your Mac, within the hours and the budget you set.

curl -fsSL https://github.com/muratatak77/prbee/releases/latest/download/install.sh | bash

Paste it into Terminal. It checks the download against its SHA-256 and installs PRBee.app. Run it again to update. Prefer a disk image? Download the .dmg (beta builds are not notarized yet, so macOS asks you to allow it under System Settings > Privacy & Security).

What it does

Finds the work

Pull requests waiting on your review, and every one you opened, drafts included, read straight from GitHub.

Reviews

Reads the diff and posts findings on the lines they are about, on your colleagues' PRs and on your own.

Answers threads

Fixes what reviewers asked for on your PRs, commits, pushes and replies in each thread.

Fixes red builds and conflicts

Triages a failing CI run, fixes what is the branch's fault, and resolves rebase conflicts.

Checks before anything leaves

Pushes, signed commits, merges and shared CI files are decided by fixed rules in the app, not by the agent.

Stays inside your limits

Working hours, jobs per hour and per-job cost ceilings, with tokens and dollars tracked for every job.

You decide how far it goes

LevelWhat it does
WatchFinds the PRs and writes reviews to disk. Posts nothing.
Review and replyPosts its reviews and answers review threads. Changes no code, pushes nothing.
Review, reply and fixAlso resolves conflicts, fixes failing CI and syncs branches that are behind, so it pushes commits to your branches.

Merging is a separate switch, off by default.

Getting started

  1. Run the install command above. PRBee opens in your browser and starts at login.
  2. Pick the agent: Claude Code or Codex, signed in with its own account or an API key.
  3. Let it check git and the GitHub CLI gh; it installs what is missing.
  4. Point it at a clone of your repository. It works in its own worktree beside it, so your checkout is never touched.
  5. Choose the GitHub account it acts as, and the level above.

Where your data goes