Skip to content
Sign in

Self-hostable AI code review for GitHub

Code review on the AI subscription you already pay for

Gecco reviews your GitHub pull requests using your ChatGPT subscription or an OpenAI-compatible endpoint you run. Host it yourself if you like. Either way, every finding is checked against the source before it reaches you.

Sign in

What makes Gecco different

  • Your subscription, not an API bill

    Connect a ChatGPT subscription, or point Gecco at an OpenAI-compatible endpoint you run. Gecco has no model of its own to bill you for.

  • Self-host it

    Run the dashboard, the review workers and the database on your own machine or server, with PostgreSQL or the built-in database.

  • Your keys stay with your installation

    Model sign-ins and GitHub credentials are kept by the Gecco installation that uses them. Your code goes only to the model provider you connect.

acme/billing #412

Support partial refunds

Finished with limits

1 medium1 low11 of 12 files reviewed

Summary

Lets customers refund part of an order, and moves refund math into one shared helper.

Added

A partial refund option on the order page.

Changed

Refund totals come from the shared helper.

Fixed

Refund emails show the right currency.

Medium

Refund total ignores partial captures

src/billing/refund.ts:88-94
Why it matters
A partly captured order is refunded its full authorized amount.
When it happens
Any refund on an order captured in more than one payment.

Suggested change

const total = sum(order.captures.map((c) => c.amount));
Illustrative example. The repository, code and findings are made up.

How it works

Three steps to your first review.

  1. Connect your repositories

    Your GitHub repositories connect through the Gecco GitHub App. Then connect the subscription reviews should run on.

  2. Choose what to review

    Switch on automatic reviews and publishing for each repository you want Gecco to look after.

  3. Reviews arrive on your pull requests

    New pull requests are reviewed when they open, and again on new commits if you want. The review lands where your team already works.

On the pull request itself

With publishing on, reviews are posted next to your team’s own comments and checks.

  • A review comment

    Merge confidence from 1 to 5 with a one-line reason, then each finding with its severity and location.

  • Summary by Gecco

    Optional, when your installation turns it on: Gecco adds to the pull request description what the change is for, then what it added, changed, fixed and removed.

  • A Gecco check

    Shows in the checks list while Gecco reviews, then reports the outcome in its title.

  • Ask in a comment

    Mention your Gecco app in a pull request comment to ask for a review, for example @gecco-sh review on gecco.sh. Gecco reacts with 👀 when the review starts.

Reviews you can check

Gecco shows its working, so you can decide quickly what to fix.

  • Findings you can act on

    Each finding names the file and line, why it matters and when it happens, with a suggested change when the fix is small.

  • Checked against the source

    Verifier agents re-read the cited code and try to disprove candidate findings, most severe first. Findings the source contradicts are dropped.

  • Clear about what it read

    Every review says how much it covered, such as 11 of 12 files reviewed, and why the rest were left out. Confidence is capped when it could not see everything.

  • Review your way

    Rules tell reviewers what to check, and where, for a workspace or one repository. Review profiles choose the model and reasoning effort.

  • One place for every review

    A dashboard with your pull requests inbox, review history and a full review page for each run.

  • From your terminal too

    The Gecco CLI reviews staged or uncommitted changes, a branch or a pull request, with JSON output for scripts and coding agents.

Try Gecco on your next pull request

Connect a repository and your subscription, and the next pull request gets a review.

Sign in