app/concepts
Concepts
How Diffgazer works locally and what leaves your machine when a provider review runs.
Read this section before the mode guides: it explains how a review actually runs, where your code and keys live, and what is sent to your chosen model provider when a review starts.
In this section
- How it works — the single global binary, the local server it starts, and the two ways you read a review.
- The review pipeline — what happens between your working changes going in and structured issues coming back inline.
- Providers and models — why Diffgazer is provider-agnostic and how bring-your-own-model and keys fit in.
- Privacy — what stays on your machine, what leaves it, and why there is no dashboard to upload to.