Managing providers 

Adding a provider 

1. Navigate to AI > Setup > Providers.
2. Click Add Provider.

3. Fill in the required fields:

   Identifier

   A unique slug for programmatic access (e.g., openai-prod, ollama-local).

   Name

   A display name for the backend (e.g., OpenAI Production).

   Adapter Type

   Select the provider protocol. Available adapters: openai, anthropic, gemini, ollama, openrouter, mistral, groq, azure_openai, custom, and the decision adapters typesafe and decision_sidecar (Decision service).

   API Key

   Your API key. Stored securely via nr-vault envelope encryption. Leave empty for local providers like Ollama.

4. Optionally set the endpoint URL, organization ID, timeout, and retry count.
5. Click Save.

Setting the key from the command line 

An unattended install cannot operate the wizard. nrllm:provider:set-key does the same job for a provider record that already exists, reading the key from STDIN:

printf '%s' "$OPENAI_API_KEY" | \
    vendor/bin/typo3 nrllm:provider:set-key openai

The key is never accepted as an argument — that would put it in the process list and the shell history. A terminal is refused rather than read, so a provisioning script fails visibly instead of hanging on a prompt.

Running it again for the same provider replaces the stored key and keeps the identifier, so anything already referring to that identifier — including providers.openai.apiKeyIdentifier in the extension configuration, which the speech and image services read — keeps working. See ADR-124.

Testing a connection 

After saving a provider, click Test Connection to verify the setup. The test makes an HTTP request to the provider API and reports:

• Connection status (success or failure).
• Available models (if the provider supports listing).
• Error details on failure.

$GLOBALS['TYPO3_CONF_VARS']['HTTP']['allowed_hosts'][] = 'ollama';

Ollama model-list fallback 

If fetching Ollama's model list fails, its adapter returns a small predefined list for the model picker. These entries do not confirm that those models are installed or that the endpoint is reachable. The connection test still reports an unreachable endpoint as a failure.

The adapter attempts a diagnostic warning when it uses that list. A failure while writing the warning does not prevent the fallback list from being returned.

Editing and deleting providers 

• Click a provider row to edit its settings.
• Use the Delete action to remove a provider. Models linked to a deleted provider become inactive.