Rejudge

Independent review before your agent acts.

$ npm install -g rejudge
GitHub npm 
Rejudge
Fresh · read-only
does this migration need a lock?
  gpt-5.5 (judge)        0. thinking     01s weighing the two objections
    ⎿ deepseek-v4-pro  ✓  done (35s | 6 tools)
    ⎿ mimo-v2.5-pro    ✓  done (41s | 4 tools)
    ⎿ gpt-5.4            2. read         03s db/migrate/0142_add_index.sql
Total 52s
Three reviewers read the code on their own. The judge waits for them, then answers.

Why

The agent that just wrote the code is the worst candidate to review it. It checks its own reasoning with the model that produced it, so a mistake made while writing survives the reading.

Asking one other model helps — until that model is confidently wrong. You get a fluent second opinion with nothing to weigh it against, and no signal about which parts are actually contested.

Rejudge runs several models that never see each other's work, then makes one of them account for the disagreement. What comes back is either agreement worth trusting or a dissent worth reading.

How it works

Several reviewers, then a judge who can question them

Your agent asks a question Model X writes its conclusion Model Y writes its conclusion Model Z writes its conclusion Judge compares the findings Answer based on all findings + Run ID to resume Your agent asks a question Model X writes its conclusion Model Y writes its conclusion Model Z writes its conclusion Judge compares the findings Answer based on all findings + Run ID to resume
Every reviewer gets the same request and works without seeing the others. The judge compares their answers and goes back with follow-up questions when they disagree.

Install

Three steps to the first review

01 Install the CLI

Node 22.19 or newer. The package ships prebuilt, so Bun is needed only to build from source.

npm install -g rejudge

02 Configure the panel

Create .rejudge/config.json in the project you want reviewed. Two reviewers minimum, and every model carries a reasoning level — minimal low medium high xhigh.

{
  "reviewers": [
    "opencode-go/deepseek-v4-pro@high",
    "opencode-go/mimo-v2.5-pro@high",
    "opencode-go/minimax-m3@high"
  ],
  "judge": "opencode-go/glm-5.1@high"
}

A project config wins over the global one at ~/.config/rejudge/config.json. Credentials stay in the environment; the CLI never stores a key.

03 Ask

rejudge "does this migration need a lock?"
git diff | rejudge "review this change"
rejudge --resume <run-id> "what about the rollback path?"

The answer owns stdout; progress, configuration, and the run id go to stderr, so redirecting the answer keeps it clean. Inside Pi the same package registers a native rejudge tool plus the /rejudge and /rejudge-diff workflows.