A second look before merge. Lookover reviews your GitHub pull requests with Claude and ChatGPT, on the subscriptions you already pay for.

It runs on your own computer and posts its review on the pull request. Your coding agent can take it from there: wait for the review, fix what it found, push, and ask again until nothing is left.

Website · Docs · Changelog · Report a bug

Lookover is in 0.x: it works, and it changes. What it doesn't do yet is below.

What it does

• Reviews each pull request you open, when it is ready for review. Optionally after every push, when you comment /lookover review, or when you click "Review now" in the app.
• Finds, then confirms. One AI looks for problems, the other checks each one before it is posted. Use Claude, ChatGPT or both.
• Posts at most one review a round on GitHub: its findings on the lines of the diff, its status at the end of the pull request's description, kept up to date, and a check on each commit with its findings in a form a program can read.
• Reads the threads on the next round. A finding you fixed is verified, and lookover wait resolves its thread; a finding is never posted twice; a reply you wrote is answered.
• Follows your rules: REVIEW.md, AGENTS.md and CLAUDE.md, read from the default branch.
• Shows what is happening in an app in your browser: the queue, each review and its rounds, each AI and its sign-in, the logs, and the settings.

What you need

• A Claude subscription (Pro or Max) with the claude CLI, a ChatGPT subscription (Plus or Pro) with the codex CLI, or both. Install them; Lookover's setup signs you in to each.
• git and the gh CLI on your PATH.
• Node.js 18 or later and npm, to install Lookover.
• A GitHub account. Lookover reviews the repositories of your personal account, or of an organisation you belong to.
• Windows, macOS or Linux, on x64 or arm64 (Windows: x64).

Install

npm install -g lookover

npm installs the one executable your platform needs and puts lookover on your PATH. Nothing runs at install: there is no install script, so --ignore-scripts changes nothing.

First run

lookover start

Lookover starts in the background and opens in your browser. Close the terminal whenever you like: it keeps running, and starts again each time you log in (Settings turns that off).

The setup takes a few minutes, one step at a time:

1. AI. Sign in to Claude, Codex or both.
2. GitHub. Sign in with GitHub: enter the code Lookover shows on GitHub's page, then install Lookover Dev on your account or your organisation and pick the repositories it may see. Lookover posts its reviews as you, each comment opening with Lookover's wordmark.
3. Repositories. Pick the ones to review.
4. First review. Pick an open pull request, or preview a review that posts nothing.
5. Your coding agent. Install the skill, below.

The other commands:

| Command | What it does | |---|---| | lookover open | Opens the app with a new one-time link. --no-open prints the link instead | | lookover status | Running or stopped, its address, data folder and version. Exit 0 running, 3 stopped | | lookover stop | Stops it | | lookover help | Every command and its options |

To update, stop it first: on Windows the running program holds its file open.

lookover stop
npm update -g lookover
lookover start

The agent loop

A coding agent that pushes to a pull request can run the review loop itself:

lookover wait       # asks for a review of the pushed commit, waits for it
lookover feedback   # the findings waiting on you, each with its thread
lookover reply F3 wont-fix "The value is checked by the caller."

lookover wait exits 0 when there is nothing to fix and 3 when there is; 4 means a person is needed. lookover reply answers a finding: fixed, wont-fix, disputed, deferred or question. The next round reads the answer.

Setup's last step, or Settings › Your coding agent, installs the lookover-review-loop skill for Claude Code and Codex. It teaches the agent the loop, and calls Lookover by its full path, so the agent needs nothing on its PATH. Then tell your agent: "Get pull request #12 through Lookover's review: fix what it found and push."

What it doesn't do yet

• GitHub only (github.com). No GitLab, Bitbucket or GitHub Enterprise Server.
• Subscriptions only, through the claude and codex CLIs. No API keys, no other AI.
• Your own pull requests. Another author's pull request is reviewed when you ask, by Claude alone. A fork's is never reviewed by itself: ask with /lookover review, and Claude reviews it.
• On your computer only. No server mode yet.
• Windows is where Lookover is used day to day. macOS and Linux pass each release's tests and a start on a real runner, and have had little use beyond that.
• No Alpine and other musl Linux: Lookover's Linux executables need glibc.
• No signed executables in 0.x. npm's provenance says where each one was built.
• A console window flashes for a moment at login on Windows, while Lookover starts.
• A post that fails can't be retried from the app yet.
• A hand edit to a settings file counts from the next start.

How releases are made

• Built and tested on every supported platform: Windows, macOS and Linux, including an install from npm and a real start on each release's runners.
• No runtime dependencies or install scripts in the npm packages: a small launcher and the executable for your platform.
• Published to npm with provenance. GitHub releases are immutable, with build attestations and checksums for the executables.

See the latest release for downloads and verification commands, and the security policy for how Lookover ships.

Security

• What runs where. Lookover runs on your computer, as you. It reviews with the official claude and codex CLIs, signed in through their own flows: Lookover never reads your subscription's tokens. It talks to GitHub, and to nothing else: no telemetry, no server of ours. On GitHub it acts as you, through Lookover Dev, the App you sign in to: its token reaches only what both you and the App may reach. Lookover reads your organisations from your own gh when it is signed in as you.
• What the AI may do. Each review runs in a read-only sandbox, on a checkout of the pull request. On Windows, Codex's sandbox isn't elevated: accepted because Codex reviews only your own changes. Hooks, MCP servers and settings that a pull request brings are turned off. No GitHub token reaches the model.
• No private key. Lookover Dev has none: none was ever generated, and nobody holds one. An organisation that installs it trusts the lookover-dev account on GitHub, which could make one (what that means).
• What it posts. The review, its line comments, its status in the description and the check, on the pull request it reviewed. Your teammates see your review written by you, each comment opening with Lookover's wordmark, and a Lookover check. In the description Lookover rewrites only its own part, after your text. As you, when your coding agent runs them: lookover wait's /lookover review comment and the threads it resolves once settled (fixed, withdrawn or dismissed), and lookover reply's answers on a thread. Secrets in a known shape are taken out of what it posts and of its logs.
• What it keeps. Everything is in one data folder on your computer: the reviews, the settings, the logs. Your sign-in with GitHub is encrypted there, and the key that opens it is in your system's credential store. With no credential store (on some Linux systems), it is kept unencrypted in a file only you can open.
• Forks are never reviewed by themselves, so a stranger's code doesn't reach an AI unless you ask.

Found a vulnerability? Please report it privately, as SECURITY.md says, never in a public issue.

Remove it

1. In Settings › Your coding agent, "Remove the skill".
2. In Settings, turn off "Start at login".
3. lookover stop, then npm uninstall -g lookover.
4. Delete Lookover's entry in your system's credential store: its name is key.entry in github/sign-in.json, in the data folder (lookover status names the folder); a data folder an earlier version set up with an App of your own also holds one in github/app.json. With "kept": "file" there, there is no entry: the secret is a file in that folder.
5. Delete the data folder.
6. On GitHub, under Settings › Applications › Authorized GitHub Apps, revoke Lookover Dev.

Contributing

Bugs and ideas are welcome in issues. To build Lookover or send a change, read CONTRIBUTING.md.

Everyone taking part follows the code of conduct.

Licence

MIT, © 2026 Samuel Asensi.