The Studio agent
Say what you want changed — the theme, a setting, a task — and the Studio agent does it, or tells you where it lives. What it can touch, what it asks first, and what it will never change for you.
Most of Semantix is pages of settings, and most people never want to learn where everything is. The Studio agent is the other road: say it in plain words, and it changes it or takes you there.
"Make the theme warmer." "Increase the editor font size." "Turn the 3D graph off." "Run my nightly task now."
It is not the chat you code with. That one works in your project's files. This one works on the Studio itself — its look, its settings and its tasks — and never touches your code.
Opening it#
Press Ctrl+Shift+P (Cmd+Shift+P on a Mac). It works from anywhere, even while you're typing in
the editor or the terminal. The same keys close it, as do Esc and the ×. You can rebind it in
Keybindings, where it's called Toggle Studio agent.
It opens as a card over the IDE: Studio agent at the top, a box that reads Ask Studio anything, or tell it what to change…, and, before you've said anything, What should we change? with a few suggestions to start from. Clicking a suggestion fills the box; it doesn't send.
Enter sends, Shift+Enter starts a new line. You can paste or drop pictures too, up to four a message — a screenshot of a look you like, say.
At the top: Maximize / Restore, New conversation once there's something to clear, and Stop speaking while it's reading an answer aloud.
What it needs#
You signed in to Semantix, and a model of yours to run on. It uses the Primary you set under Settings → Studio → Semantix's own models — your Claude Code sign-in, or any API-based model you've connected — and falls back to the Secondary. With neither set, it says so before spending anything, and names the place to fix it.
Every question is a model turn on your account or key, like any other chat.
What it can do#
Themes. Ask for a new look and it first shows you a concept — a name, a mood, the palette as swatches, the two fonts — and stops to ask. Say yes and it paints the whole theme: interface colours, code colours, fonts, even small amounts of per-region CSS. Small tweaks ("a bit more contrast on comments") skip the concept and go straight on.
What it paints is a draft, like an edit you make by hand on the Theme tab: it's live, but nothing is saved until you choose to keep it. The agent never saves a theme for you. It also checks its own work for readable contrast and tells you about any pair that falls short.
Settings. It can read and change almost any setting: the 3D graph, the explorer, the memory walker's pace, every remappable shortcut, glass and depth, speech. The change goes through the same rules as when you make it by hand, so a value out of range is refused, and it tells you why.
Note
Glass — opacity, depth, shadow, the overlay — is a setting, not part of the theme. Discarding a theme draft doesn't undo a glass change the agent made.
Tasks. It can list your tasks, read one, read what a run did, create a task, and edit, enable or disable one. Those happen at once — you're the one asking. Two things it always asks first, with a card in the conversation: Delete and Run now. Decide on the card, or in the Task Manager; either settles it in both places.
Taking you there. "Where do I set my model?" — it opens the page, as a tab. If the card is maximized and covering it, it says to press Restore.
Showing numbers. Ask how something's going and it can answer with a small chart or table instead of a paragraph.
Answering from the docs. Ask how something works and it searches these docs.
Speaking. With speech on, it can say a short line aloud before it writes, or read its whole answer, whichever you chose.
What it won't do#
- Change your privacy settings. Local only and memory are never changed on anyone's behalf. It can tell you what they're set to, and where to change them yourself.
- Touch your code or files. That's the chat panel's job.
- Build an agent flow for you. It can explain how to build one on the canvas — see Agents — but it has no way to draw one.
- See your screen. It knows the colours it set, not how they look. It reports contrast by the numbers; if something looks wrong, tell it, or show it a screenshot.
- Fetch anything from the web into a theme. Per-region CSS may only use pictures already inside Studio.
What it remembers#
The conversation lives only until you press New conversation or restart: it isn't saved. What it learns about you — that you like dark themes, that your tasks run at night — goes to its memory, if memory is on, so a later conversation can start from it.
One question at a time: while it works, Send becomes Stop. Closing the card doesn't stop a turn that's running.
Where it is now#
Note
The Studio agent is new. It works on the Studio's look, settings and tasks today. The empty state suggests building a flow; for now that gets you directions, not a flow. Where something on these pages is marked coming, it means exactly that.