Studio
The composer's emoji picker, and the two model seats Semantix uses for its own work — which is the one setting on this page that actually matters.
Settings → Studio. Two sections. The first is a convenience; the second decides which
model does Semantix's own thinking behind your back, so it's the one to read.
Both are remembered per machine, across every project.
Composer: the emoji picker#
Emoji picker, off by default. Turning it on adds an emoji button to the strip that rides along
the top edge of the chat composer — the same strip as New chat and Chat history — opening a
small searchable picker with a recently-used row. Purely a composer convenience.
Semantix's own models#
Semantix does work of its own that isn't a reply to you: it reads your conversations and files what is worth keeping into memory, it writes the hand-off note a new session starts from, and it brings old conversations into memory when you ask it to. That work needs a model, and that model is not the one you're chatting with. It's whatever sits in these two seats.
Primary — does the thinking. This is the model the memory walker runs on after each turn, the one that writes hand-off notes, and the one bulk ingest uses.
Secondary — the context carrier. A cheaper model for moving context around. It's the fallback when Primary can't run.
Both pickers are the same searchable model picker the chat uses, with one difference: they only offer API-key models — your custom models and the catalogue of any provider you've connected. Claude Code and the other installed coding agents aren't on the list, because Semantix has to call this model itself, from the background, with no session of yours open.
Leave both empty and memory does nothing. With Semantix Memory switched on in Privacy and no seat set, the walker refuses each turn and says so once per conversation in the transcript, as a warning notice titled Memory; the ingest page's button stays disabled with Needs one of your own API-key models first. The seats are the first thing to set once you turn memory on.
→ Memory · The walker and bulk ingest
Note
Pick models you're comfortable running on your data. Everything the walker reads — your messages, the agent's replies, the tool results you've allowed memory to see — goes to the Primary seat's provider, under that provider's key.
Note
A seat is global on purpose: one Primary for every project on this machine. It used to be per-project, which produced a new project that quietly had no seat at all.
What isn't here#
The chat's own model — the one that answers you — is chosen per conversation in the composer's
picker. Font sizes, once on this page, are on the Theme tab under Typography and Code.