How-to

How to review a pull request without sending code to the cloud

Last updated 2026-06-18 · Outlier v1.11.469

What you need first for “how to review a pull request without sending code to the cloud”

Apple Silicon Mac, macOS 12 or later, the unified-memory minimum that the chosen tier requires (6 GB for Nano, 12 GB for Lite, 24 GB for Core / Code / Vision, 32 GB for Plus). Internet is required only for the one-time model download.

Steps

1. Copy the diff. git show HEAD or fetch the PR locally.
2. Paste into Outlier in Code mode. The system prompt is tuned for code-first review.
3. Ask for a single axis at a time. Bug surface, then style, then perf.
4. Save the rendered review to your PR description. No part of the diff has left the Mac.

What is the specific thing to know about this guide?

For PR review, the Code tier’s default 64K context window is wider than Core’s 32K, which matters for long diffs. Both share the same weights, so answer quality is identical.

What can go wrong with this guide?

• Diffs over 1000 lines may exceed Code’s default 64K context if the repo files are also pasted.
• The review is only as good as the prompt’s axis; ask for one thing per turn.

How does this guide differ from the cloud equivalent?

Cloud PR review tools transmit the diff. Outlier’s Code mode keeps it on the Mac, which matters when the diff has untested mitigations or unreleased features.

For PR review, the Code tier’s default 64K context window is wider than Core’s 32K, which matters for long diffs. Both share the same weights, so answer quality is identical.

What does this guide not claim about “how to review a pull request without sending code to the cloud”?

For PR review, the Code tier’s default 64K context window is wider than Core’s 32K, which matters for long diffs. Both share the same weights, so answer quality is identical.

This guide does not claim feature parity with cloud-side workflows for “how to review a pull request without sending code to the cloud”. Specifically, the product surface in v1.11.469 covers chat, file attachment, the local agent loop, project scoping, and the model picker. Cross-device sync, team workspaces, and shared session history are out of scope and are not on the v1.9 backlog either.

How does Code-tier context width compare to Core?

Code defaults to 64K context against Core’s 32K, with both capped at 256K. The two share the same safetensors and produce identical answer quality; the difference is the chat template and decoding configuration. For PR review on diffs over 500 lines, Code’s wider default keeps the whole diff plus the relevant surrounding code addressable in a single turn.

Where does this guide fit in the rest of the lineup?

For a 500-line diff, Code’s 64K default context holds the diff plus surrounding source. For longer diffs, paste the diff alone and reference the surrounding files by name; Outlier loads them via the project chip if needed.

One unique number

4 steps, zero network requests after the model is downloaded. Asking along a single axis at a time (correctness, then style, then perf) holds quality better than a single ‘review this’ ask.

Download Outlier for Mac

Requires Apple Silicon (M1, M2, M3, or M4) — Intel Macs are not supported. macOS 12+.