Configure a remote provider
Setting contract
Section titled “Setting contract”| Item | Current behavior |
|---|---|
| Default | Local (Ollama), with an empty API key. |
| Valid values | ollama or openai-compatible; an External API needs a non-empty base URL, API key, and model name. |
| Existing sessions | Local session data is unchanged. Future generation can use the newly selected provider. |
| New actions | Summaries, session chat, and some embedding paths use the chosen provider configuration. |
| Storage | Provider fields are stored in synthezia-settings in webview local storage. |
| Privacy | External API can transmit transcript, prompt, question, chat-history, and retrieved context. The API key is not in Keychain. |
| Restart | None. |
Configure an External API
Section titled “Configure an External API”- Open Settings and select External API under AI Provider.
- Enter the provider base URL, API key, and chat model name.
- Test with non-sensitive content before using production recordings.
- Select Local (Ollama) to return future generation to the local runtime.
The current application accepts a non-empty base URL but does not enforce HTTPS. Review the endpoint, transport, retention, and the fixed remote embedding-model requirement before relying on a provider that calls itself OpenAI-compatible.

