Model connections

A model connection combines a provider, endpoint, credential, default model, and supported protocol. Tasks select a configured connection; credentials are never returned to browser clients after they are saved.

The selected provider receives the context required for each model call. Review Data flow and privacy boundaries before connecting a private repository, and confirm the provider or gateway's retention, training, residency, and deletion policy.

Add a connection

Open Settings → Personal → Models & providers, choose a provider, and enter the fields supplied by your provider or administrator. Give the connection a recognizable name such as Production OpenAI or Internal gateway.

Use the connection test before saving. A successful test confirms authentication and protocol compatibility; it does not grant a Task additional filesystem, command, or network permissions. The test makes a real request to that endpoint and may therefore appear in provider or gateway logs.

Select a model for a Task

Choose the connection and model when creating a Task. Existing Tasks keep their explicit selection so changing a global default does not silently change a resumable workflow. If a saved connection is removed, Kairo Code asks you to select a valid replacement before the next turn.

Keep credentials private

WARNING

Treat provider keys as secrets. Enter them only in the Desktop connection form, never in a Task, repository file, screenshot, or support message. Kairo Code does not reveal a saved credential back to the Desktop client.