Configure AI provider

Guided Review calls your LLM account. There is no Guided Review cloud that holds your key or rewrites diffs for you. That design is spelled out in Privacy & data.

You need a provider before your first review. GitHub auth is separate and only required to submit a review — see Connect GitHub.

Supported providers

OpenAI and Grok share the same client shape; Anthropic uses its own streaming endpoint. Structured output for the review plan is enforced with a shared JSON schema so behavior stays consistent across backends — see How a review plan works.

We’ll keep adding more providers — request one on the repo, or open a PR that adds yours. Also covered in the FAQ.

Set your API key

1. Open the extension Options page (after install).
2. Choose a provider.
3. Paste an API key from that provider’s console.
4. Save.

Keys are stored in chrome.storage.local and are only used from the background service worker when annotating a review or testing the connection. Content scripts never hold the key for outbound LLM calls.

Pick a model

Select a model available on your account. Prefer a model that handles long contexts well if you review large PRs — Guided Review chunks oversized diffs by file (~60k characters per chunk) so no single call is expected to swallow an entire monorepo change set, but each chunk still benefits from a capable model.

Models currently listed in Options (ids can change as providers ship or retire models):

If a stored model disappears from the catalog, Options falls back to that provider’s default.

Test connection

Use Test connection on the options page. That runs the same provider path as a lightweight health check and surfaces user-safe error messages if the key, model, or network path fails.

If the test fails, step through Troubleshooting → Provider and API key.

Where settings live

Session resume behavior: Your first review → Resume later and Troubleshooting.

Next. Your first review · How a review plan works · Privacy & data