FAQ

Yes — pick Ollama as the provider. The CLI then talks only to http://localhost:11434 (or whatever you’ve configured); no API key is required and no diff leaves your machine.

CommitBrief itself never makes outbound network calls beyond the provider you chose. There is no telemetry endpoint, no auto-update check, no analytics beacon.

Yes. The secret scanner ships eight built-in patterns for common token formats, and guard.secret_patterns lets you layer your own regexes on top — handy for internal or company-specific credentials:

guard:
  secret_patterns:
    - name: Acme Internal Token
      pattern: 'acme_[A-Za-z0-9]{32}'

Your patterns are additive: the built-ins always run and can’t be disabled or shadowed (use guard.secret_scan: false to turn the scanner off entirely). An invalid regex aborts the review before any provider call, naming the offending entry, so a typo can’t silently disable a check. Only the line number and pattern name are ever reported — never the matched text.

This key is config-file only; hand-edit config.yml (or your init/setup output) rather than commitbrief config set. See Safety and cost.

No. The baseline (.commitbrief/baseline.json) is per-developer and gitignored — .commitbrief/ is auto-added to .gitignore on first write, so the file is never committed and never propagates.

That means CI has no baseline file and reviews the full diff, and the next reviewer’s checkout has no baseline (or their own) either. There’s no shared baseline to bake a bug into, so a baseline can only quiet repeat noise for you — it can’t lower the bar for anyone else.

Inline // commitbrief-ignore: reason suppressions do live in the code, but they carry a mandatory reason that lands in the diff the reviewer reads, so they’re never a silent override either. See Signal control.

CommitBrief is a Go CLI that runs LLM-powered code reviews on git diffs — staged, unstaged, or any historic range git diff understands via the commitbrief diff <args> subcommand (single commit, branch vs target, PR-style three-dot range, etc.). It runs locally; the only network egress is to the provider you chose.

It is not a SaaS, a dashboard, a GitHub App, or a bot. There is no account, no server-side state, and no telemetry.

Ten providers ship as of v1.4.0 — seven HTTPS API backends plus three subprocess wrappers around host CLI tools. Use whichever fits your billing and trust model.

API providers (need an API key, billed per-token):

• Anthropic (default): best output quality on code review tasks in our experience; ephemeral prompt caching makes repeat runs cheap.
• OpenAI: comparable quality; automatic prompt caching at ≥1024-token prefixes.
• Gemini: largest free-tier context windows (2 M with 2.5 Pro). Good when your COMMITBRIEF.md is unusually large.
• DeepSeek / Mistral / Cohere: OpenAI-compatible endpoints driven through the same SDK — no extra dependency. Low-cost (DeepSeek), EU-hosted and code-tuned (Mistral codestral), or the Cohere command family. Structured output is prompt-driven with graceful degrade.
• Ollama: zero cost, zero network egress, runs on your own GPU. Best for SOC2-restricted repos or air-gapped environments.

CLI-tool-backed providers (no API key, reuse existing subscription):

• claude-cli: drives your locally-installed Claude Code (claude) binary as a subprocess. Auth + billing handled by your Claude Code subscription. Output is pre-formatted plain text — no --json or --fail-on severity gating.
• gemini-cli: same idea against Google’s Gemini CLI (gemini).
• codex-cli: same idea against OpenAI’s Codex CLI (codex), run non-interactively under its read-only sandbox. Added in v1.3.0.

Run commitbrief setup to configure any of the seven API providers interactively, or invoke a CLI-backed one directly with commitbrief --cli claude / --cli gemini / --cli codex.

The flaky-test detector is a deterministic pre-pass that flags timing-dependent and unseeded-random anti-patterns in your changed test files. It’s on by default for API providers. To turn it off:

commitbrief --staged --no-flaky          # per-run
commitbrief config set review.flaky false  # persistently

Disable it if a CI layer already handles flake detection, or if your test code legitimately uses these patterns. Note that flaky findings are first-class — they render alongside the model’s findings and count toward --fail-on, so silencing them also drops them from CI gating. See Flaky-test detector.

Two ways, both true removals (a dropped finding no longer counts toward --fail-on or appears in --json):

• Baseline a whole repo’s existing findings so only new ones surface from then on:

  commitbrief --update-baseline   # record current findings

  The baseline lives in a user-private, gitignored .commitbrief/baseline.json. Findings are fingerprinted by file + severity + title (not line), so they survive code drift.

• Suppress one specific finding inline, with a reason the next reviewer can read:

  const id = rows[0].id; // commitbrief-ignore: list is non-empty here

  Use commitbrief-ignore[high]: … to scope the drop to one severity.

This is stronger than --min-severity, which only hides findings from the view — they still count toward CI gating. See Signal control.

It depends on your provider’s per-token pricing and the size of the diff plus your COMMITBRIEF.md. Run any command with --verbose to see the actual token counts and cost for that run.

Two CommitBrief features keep cost low:

1. Local response cache. Re-running on an identical diff (same provider, model, language, schema) is a disk read — zero token spend. The verbose footer prints Saved: $X for cache hits.
2. Provider prompt caching. Anthropic, OpenAI, and Gemini all discount repeated input prefixes. CommitBrief structures the prompt to maximize cache hit rate; the verbose footer reports provider cached: N tokens.

commitbrief compress can additionally shrink your COMMITBRIEF.md itself (see --level light|balanced|aggressive).