Relu
View on GitHub

Writing code got fast.
Reading didn’t

A native app for reviewing code: keyboard-driven, with full LSP navigation, and AI only when you ask for it.

Get early access See it in action

A real tool for the volume you ship.

Every team now ships more diff per week than it can comfortably read. That volume is not the problem. Reading it in a browser tab, with no types, no call sites and no way to keep your place, is.

What that volume demands is a real tool: fast, precise, built to help you move quickly, understand a change deeply and see what it actually demands of the codebase. That is what Relu is. The code stays at the center, and the agent digs alongside it.

We do the legwork. You keep the judgment.

Ergonomics

A diff built to be read,
driven by the keyboard.

We learned from the tools that put ergonomics back at the center. The lesson fits in one line: a good shortcut beats a good menu.

Next file, new comment, mark as reviewed: it all happens without leaving the keyboard, in one continuous surface, never losing your place in the diff.

nnext file ccomment vmark as viewed spacenext unviewed file
  • Unified diff, deliberate density
  • A shortcut for every move
  • Per-file review state
  • Comments on a line or a selection

Code navigation

Your language server,
inside the review.

It sounds obvious, yet nobody shipped it. Relu clones a local workspace for every pull request and points your language server at it. You get what your editor gives you: types on hover, go to definition, jump to every call site, right on the diff. No more guessing what that function does.

  • Go to definition, straight from the diff
  • Your LSP, your languages
  • An isolated local workspace per pull request
  • File and code search

A reading assistant

An assistant that reads
and argues back.

Bring your agent into the review. Ask it to explain a part of the codebase you do not know, to hunt the edge case everyone forgot, to argue why this approach over another. It does not flood the review with generic remarks: it gives you something to judge with. Every proposal lands as a draft, anchored to its line, and only exists if you accept it.

  • Explain a change, on demand
  • Hunt edge cases, not noise
  • Any ACP-compatible agent
  • Accept or reject each proposed comment

Workflow

Good code never lands on the first try.

A good pull request takes several rounds: you read, you doubt, you ask for reasons, the author reworks it, you read again. That is where software gets better. Relu is built for those rounds, not for a rubber stamp.

Time spent on one pull request Most of it goes to understanding and challenging

1

Open

Local workspace cloned, LSP attached, diff ready in seconds.

2

Understand

Follow the thread, jump to a definition, mark what you have covered.

3

Challenge

Ask the hard questions, contest the solution, look for the forgotten case.

4

Publish

One batch to GitHub. The author fixes, you pick up at step 2 again.

A careful review takes time, and it should. Relu makes that time pleasant instead of tedious: less hunting, less waiting, more thinking.

Ready to read faster?

Relu is a desktop app for macOS, in early access. Leave your email, we open seats in short waves.

No newsletter. One notification, when your seat opens.