Credentials

miu-cr is bring-your-own-key. You supply an LLM API key via an environment variable or a flag; it lives in memory only for the duration of the call. It is never written to disk, the SQLite history, or anywhere else — and never a subscription token.

Supplying a key

export ANTHROPIC_API_KEY=...                                      # Anthropic
export ANTHROPIC_BASE_URL=https://api.z.ai/api/anthropic \
       ANTHROPIC_AUTH_TOKEN=$ZAI_API_KEY                          # GLM via z.ai
export OPENAI_API_KEY=...                                         # OpenAI-compatible

Or pass per-run flags (which override the matching env var):

miucr review --staged --api-key "$MY_KEY"
miucr review --staged --auth-token "$ZAI_API_KEY" --base-url https://api.z.ai/api/anthropic

See Providers for the full resolution matrix per provider.

What is never persisted

• API keys and auth tokens (--api-key, --auth-token, ANTHROPIC_API_KEY, OPENAI_API_KEY, ZAI_API_KEY, …).
• Base URLs supplied via --base-url.

The SQLite history stores review records only — anchored findings and run stats. Credentials are not part of that record.

Output redaction

Both the CLI envelope and the MCP tool outputs are scrubbed before they leave the process:

• Credential-named JSON fields (anything matching password, secret, token, api_key, auth_token, …) are replaced with ***.
• Credential-bearing URLs and key=value assignments are redacted.
• Finding prose is exempt — rationale and suggested_patch may legitimately quote token-like example text, so they survive the scrub intact.

Local state

The SQLite review history is a local file. The project .gitignore excludes *.db and state.db so review state — and the code it references — is never committed. Treat the history database as local-only.