Where connections live
Connections are stored as thellmConnections array in the config file (~/.synti/config.json). Their secrets are held separately in the encrypted credential store and referenced by slug.
Connection fields
Provider types
Auth types
How a session picks a connection
When you send a message, Synti resolves the connection in this order:- Session connection — locked in after the session’s first message.
- Workspace default — the default set for the active workspace.
- Global default —
defaultLlmConnectionin the config. - First connection — the first entry in the list, as a fallback.
A session locks to its connection after the first message so a conversation stays coherent on one model. To use a different provider, start a new session.
Managing connections
Open Settings → AI to add, edit, delete, and validate connections. From there you can:- Set the global default and per-workspace defaults.
- Validate that a connection actually reaches its provider.
- Toggle per-model image support for custom endpoints without editing JSON.
- Choose mid-stream behavior per connection.
synti-cli connections — see the CLI reference.
Mid-stream behavior
If you send a message while the agent is still responding, the connection decides what happens:queue— hold the new message until the current turn finishes. Default for Anthropic.steer— inject the message into the turn in progress to redirect it.
Custom endpoint capabilities
Foropenai_compat connections, declare what the endpoint supports per model — for example contextWindow and supportsImages — so Synti sizes requests and enables images correctly. See API Providers.
Related
API Providers
Base URLs, model IDs, and custom endpoints.
Credentials
Where each connection’s key is encrypted.
Config File
The file that holds the connections array.
Environment Variables
Supply provider keys at launch.