# Crewreview > A free, open source crew of AI agents that reviews pull requests and answers the reviews on yours: fixes, replies, resolves. Runs on your computer with Claude Code, Codex, Kiro or any ACP agent, on GitHub and GitLab. Version 0.14.2. Free software (AGPL-3.0). Source: https://github.com/Quost/crewreview Made by Pururucos, https://pururucos.com.br ## What it does - Reviewer: Several read-only lenses in parallel, a verifier that tries to prove them wrong, and a fixed rule for the verdict. Correctness, security, architecture, tests and UI lenses; add your own in the repository. Every finding points at a real file and line, or it's dropped. Reads the description, the discussion, CI and what changed since its last review; never repeats a point already made. Posts one review with inline comments, from your account. - Attendant: On your pull requests, it answers each comment: fixed, replied, declined, or left to you. Works in its own worktree, never in your clone. Runs your checks before pushing; commits with your identity and signature, never force-pushes. Replies, resolves fixed threads and asks reviewers to look again. The polish loop: review, fix, review again, before you ask a person. - Dashboard: undefined undefined undefined - Hosts: GitHub and GitLab (cloud and self-managed). - Harnesses: Claude Code and Codex CLI (review and attend), Kiro CLI (review), any Agent Client Protocol agent or custom CLI after a conformance test. - Runs on macOS, Linux and Windows as a CLI, a background service and a local dashboard. Interface in English, Brazilian Portuguese, Spanish, German and Simplified Chinese. ## Safety - Read-only, proven: Reviewers can't write or run commands; a canary test proves it on your machine, per harness version. - No tokens for agents: Your git host token stays with Crewreview. Agents get a filtered environment; Crewreview posts and pushes. - Only trusted voices: Only people who can push to the repository steer the attendant. Everyone else is ignored. - Sensitive files wait: Changes to CI, secrets, deployment or the crew's own rules always wait for your approval. - Nothing leaves but to your harness: No server, no account, no telemetry. Code goes only where the harness you picked sends it. - Signed updates: Updates install only with a valid signature from the release key built into your binary. ## Install - Desktop app (macOS, Windows, Linux): https://crewreview.pururucos.com.br/#start, or the latest release: https://github.com/Quost/crewreview/releases/latest (Crewreview-macos-arm64.dmg, Crewreview-macos-x64.dmg, Crewreview-windows-x64-setup.exe, Crewreview-linux-x64.AppImage and .deb/.rpm, the same for linux-arm64). It bundles the crew and keeps it running from the menu bar or tray. - Command line, macOS or Linux: curl -fsSL https://crewreview.pururucos.com.br/install.sh | sh (Homebrew: brew tap Quost/crewreview https://github.com/Quost/crewreview && brew trust quost/crewreview && brew install Quost/crewreview/crewreview) - Command line, Windows (PowerShell): irm https://crewreview.pururucos.com.br/install.ps1 | iex (Scoop: scoop bucket add crewreview https://github.com/Quost/crewreview; scoop install crewreview/crewreview) ## Using it with a team - Each developer installs it and links the team's repositories, or a whole GitHub organization or GitLab group (crewreview repo add https://github.com/acme, with --include/--exclude name filters); reviews post from their own account, with the coding agent plan they already have. No server, no seats, no shared API key. - A commit that already has a Crewreview review on the host is skipped, whoever's crew wrote it, so several people can run it on the same repository. - Shared rules live in the repository: .crewreview/lenses/.md replaces or adds a lens, and the crew follows AGENTS.md, CLAUDE.md and CONTRIBUTING.md, all read from the base branch. - The language of review comments is set per repository (commentLanguage). - Working alone: GitHub doesn't let you approve your own pull requests, so a repository can post its reviews as a second account. The app walks through it (Repositories → Post reviews as → Set it up step by step): the person creates the account and types one sign-in code; the app checks it, invites it with write access, signs it in to gh, switches gh back, accepts the invitations and sets the repositories. By hand: crewreview repo set --account my-bot (signed in to gh), or env:VARIABLE with its token. Approvals from that account count; everything else runs as you. - Or one bot account reviews for the whole team from a shared machine: a Docker image built from the signed release binary, with the dashboard reached over SSH. Guide: https://github.com/Quost/crewreview/blob/main/docs/team-machine.md ## Setting it up for someone (for AI agents) 1. Install the command line tool (above). Explain each command before running it. 2. Run crewreview doctor. It needs git, at least one coding agent signed in (Claude Code, Codex or Kiro) and gh (GitHub) or glab (GitLab) signed in. If something is missing, tell the user how to fix it and wait. 3. Ask which repositories to watch, or whether to link a whole organization or group (every repository in it, new ones too). Link each in inbox mode, so nothing is posted without approval: crewreview repo add --attend inbox. Never switch a repository to auto unless the user asks. 4. Keep it running and open the dashboard: crewreview service install, then crewreview ui. 5. Connect it to the user's coding agents: crewreview mcp setup prints the steps for each. Claude Code: /plugin marketplace add Quost/crewreview, then /plugin install crewreview@crewreview. ## Commands - crewreview doctor --conformance: prove each harness's read-only and write-scope locks on this machine. - crewreview local: review the current branch; nothing is posted. - crewreview repo add [--mode inbox|auto] [--attend off|inbox|auto] [--polish on]: link a repository. - crewreview review / crewreview attend : run one now. - crewreview inbox [show|approve|discard] : what waits for approval. - crewreview run / ui / service install / update: the daemon, its dashboard, start with login, signed updates. ## Not included No hosted service, no account, no telemetry. It doesn't merge pull requests and never force-pushes.