FAQ
Short answers to the questions that come up most about running Diffgazer.
These are the questions people ask most often, with a link to the page that covers each one in full.
Does my code leave my machine?
Only when you ask for a review, and only to the model provider you chose. Diffgazer runs an embedded server on your own machine and never relays anything through a service we run, so your source and your API keys stay off our infrastructure. But a review request is not empty: it carries your diff and the prompt built around it straight to your provider, under your own account and that provider's data policy. Your code never leaves before that; setup itself can make a model-catalog lookup that carries no code. See Privacy and security for how that holds up layer by layer.
Which providers can I use?
Nine hosted API products are selectable: Google Gemini, Z.AI, OpenRouter, DeepSeek, Qwen International, Moonshot Open Platform, MiniMax International, Ollama Cloud, and OpenCode Zen. Each takes your own key, either stored by Diffgazer or read from the environment variable that product is bound to. The Providers reference lists the credential kind, endpoint, and enablement gate for each one, and Environment variables lists the reference names.
Can I run Diffgazer in Docker or on a server?
No. Diffgazer is a local binary that opens a browser tab on your own machine, so there is no headless server mode to deploy. The repo does ship Dockerfiles and reverse-proxy notes for the project's own sites (the docs, landing, and registry), but those are not the review CLI. Install the published CLI where you work and run diffgazer from inside a repository.
How do I change the port?
Set the PORT environment variable before you launch. It defaults to 3000 for the API server, and the value must be an integer from 1 to 65535. The Server reference covers the embedded server and the variables that shape how it runs.
Is the terminal UI ready?
Not yet. The terminal UI is a beta and still incomplete, so web mode is the default and the full-featured way to review. Try the TUI with diffgazer --tui if you want to, but expect gaps until it leaves beta. See Terminal UI for what works today.
Where is my config stored?
Globally, under ~/.diffgazer: settings in config.json, credential references in secrets.json (literal keys go to the OS keyring or separate 0600 files), and per-project trust records in trust.json. Each repository you review also gets a small .diffgazer/project.json inside it that pins a stable id for trust to point at. You can move the global directory by setting DIFFGAZER_HOME; the full layout is in Configuration.
Still stuck?
If something is broken rather than just unclear, work through Troubleshooting for the common failures and their fixes.