Settings

Route: /settings

The Settings page configures the active project’s integrations, model keys, and developer tooling. The tab is persisted in the URL (?tab=).

Tabs

General

Notifications, Sentry config, the default LLM model, and the deduplication threshold for report clustering.

BYOK (API keys)

Configure Anthropic and OpenAI-compatible API keys for the project’s LLM pipelines. Keys are stored encrypted in Supabase Vault.

Key	Used by
Anthropic API key	`fix-worker`, `classify-report`, `pdca-runner`, `judge-batch`
OpenAI-compatible key	`fix-worker` (fallback), `test-gen-from-report`

After saving, only the last four characters are shown.

Firecrawl

Optional web research provider. When configured, enables the Research page and powers the drift-walker crawl:

Field	Description
Firecrawl API key	Your BYOK key from firecrawl.dev
Firecrawl base URL	Optional self-hosted endpoint override

Health

Live connection status for all configured integrations. Shows the same provider probe data as the Integration health page, scoped to this project. Also includes the SDK reference (your VITE_MUSHI_API_KEY for SDK configuration) and a pipeline smoke test button.

Dev tools

Debug logging flag and other local-only developer flags for this project. These settings are never sent to the SDK or end users.

Changing a key

Open the BYOK tab.
Paste the new key and click Save.
Navigate to Integration health → Probe now to verify the new key works.

Do not paste a Supabase service_role key here. That key bypasses all row-level security and must only be used server-side. These BYOK fields are for third-party AI/integration providers only.

Integration health — verify keys with live round-trip tests
Storage — configure BYO object storage
SSO — SAML/OIDC identity provider registration
Organization members — manage access and roles