Skip to content

Configure a remote provider

Item Current behavior
Default Local (Ollama), with an empty API key.
Valid values ollama or openai-compatible; an External API needs an HTTPS base URL (or explicit localhost development URL), API key, model name, and separate endpoint authorization.
Existing sessions Local session data is unchanged. Future generation can use the newly selected provider.
New actions Explicitly authorized summaries and session chat use the chosen provider configuration. Embeddings stay local.
Storage The API key is stored in macOS Keychain; the authorization policy is in the encrypted database.
Privacy External API can transmit transcript, prompt, question, chat-history, and retrieved context.
Restart None.
  1. Open Settings and select External API under AI Provider.
  2. Enter the provider base URL, API key, and chat model name.
  3. In Privacy & Data, authorize this endpoint; a changed origin must be authorized again.
  4. Test with non-sensitive content before using production recordings.
  5. Select Local (Ollama) to return future generation to the local runtime.

The application accepts HTTPS endpoints, except explicit localhost development endpoints, and does not follow provider redirects. Review the endpoint, transport, retention, and provider support before relying on a provider that calls itself OpenAI-compatible.