Connecting a provider
Where the keys go, what the app does with them, and what it deliberately does not check.
Everything on this page lives in Settings → Models, which holds four sections in order: your default model, your saved keys, your configured models, and memory.
If you are using the Claude lane, you can skip most of this — that lane asks for no key at all.
Saving a key#
Saved API keys → Add API key. Three fields:
Provider — Together AI or OpenRouter.
Label — optional. A name for you, so that two keys from the same provider are tellable apart.
API key — the secret itself.
Important
The key does not go into the app's database. It goes into your operating system's own keychain — macOS Keychain, Windows Credential Manager, or the Linux secret service. The app's own note says it: Keys stay on this computer in the native system keychain. Saved secrets are never displayed again.
"Never displayed again" is literal. You can replace a key; you cannot read one back.
Deleting a key is refused while a configured model is still using it. Remove the model first.
Configuring a model#
A saved key says how to pay. A configured model says what to run. You need both.
Models → Add model:
Provider — the same two.
Model ID — the exact name the provider uses for it, typed by hand.
Display name — optional, what you will see in pickers. Defaults to the model ID.
API key — either one of your saved keys, or a manual key kept private to this one model configuration.
Warning
Nothing here is checked against the provider when you save it. The app does not confirm the model ID exists, and does not test the key. A typo in either is accepted quietly and shows up later, as a failed message.
If a companion cannot answer on a model you just added, the model ID is the first thing to re-read.
There is no base-URL field, and no custom headers. The endpoints for both providers are built in.
Connecting memory#
The last section, Semantix Memory, is not about models — it is what memory runs on.
Paste your Semantix token and press Connect. Like the provider keys, it is held in the system keychain, and like them it is not verified at the moment you save it — the first recall is what proves it.
Note
This connection is what memory depends on: Recall only runs while a token is connected. Disconnect and the companion keeps talking, but stops remembering.
Underneath it sit the memory switches — the master, the sleeper, and the recall reflexes.
→ Recall · The sleeper