General

Six small sections. Everything on this tab is remembered per project — including, unusually, whether the 3D view is on.

Three font sizes, not one#

The IDE has three type scales and this tab holds all three. Each runs from 10 to 24, with a reset link that appears only once you've moved it.

They aren't quite independent: the editor's size stands alone, but the chat's is a zoom applied on top of the interface size, so raising Interface makes the conversation bigger too.

Interface — the app chrome: the explorer, tabs, menus, panels, status bar. Default 14. This is the one that makes the whole IDE bigger or smaller.

Editor — the code canvas only. Default 13. Changing it re-flows the open file immediately; your cursor, selection, scroll position and undo history all survive.

Chat — the conversation. Default 15.

The typeface is a separate matter from the size, and it isn't here: both the interface font and the code font are set in the theme editor.

→ The theme editor

Editor theme#

Sixteen syntax themes for the code canvas — nine dark, seven light. One Dark by default.

This colours your code only. The rest of the IDE keeps the app theme, so picking a light editor theme inside a dark IDE gives you exactly that: a light page in a dark frame. If you want the whole interface to change, that's the theme editor.

Chat: the emoji picker#

Off by default. Turning it on adds a 😊 button to the composer's action row, beside the new-chat and history buttons, opening a small searchable picker with a recently-used row. Purely a composer convenience.

Memory#

Four switches deciding how much the assistant recalls between conversations on its own: a master — Memory reflexes in chat — and three under it for Time awareness, Prompt recall and Self-recall (mirror). All four are on by default.

They shape what memory does. Whether it happens at all is decided one tab over, in Privacy — until Semantix Memory is on there (and Local only off), this section is inert, and it says so at the top rather than letting you toggle things that can't run.

→ Memory — what each switch changes · Privacy — the consent switch

Graph: turning the 3D view off#

On by default. Turning it off unmounts the 3D viewer completely — no rendering, no physics, no animation, no GPU work at all. It's the switch to reach for on a laptop that's getting hot, or when you simply want a plain editor.

Files still open in the code view exactly as before. What changes is what you see when you open a folder or the project overview: with 3D off, the centre of the window is blank. There's no message and no button to turn it back on — come back here.

Two smaller things go quiet with it: the orientation gizmo, and the agent's habit of showing you what it's reading by lighting up and flying to nodes as it works. If you turn 3D off, the agent stops pointing at things.

The 3D scene also disappears while the theme editor is open, which is normal and not this setting.

→ The 3D viewer

Re-index project#

One button, no confirmation. It throws away the map Semantix has of your project and builds a new one from what's on disk right now.

Reach for it when the IDE seems to be looking at an older version of your project — most often after you've changed files with the app closed, pulled a branch outside the IDE, or done a large move or rename. Semantix watches for changes while it's running, but it can't see anything that happened while it wasn't.

It's also the blunt fix for search returning something that isn't there any more, a hover card quoting a line that's moved, or the graph showing files you deleted.

What it touches: only the index — the derived map of your code. It reads your project; it never writes to it. Nothing in your source folder is touched, created or deleted. Your settings, open tabs, panel layout, saved cameras and conversations are all stored separately and come through untouched.

While it runs: the button reads Indexing…, a thin progress bar crosses the top of the content area, and the status bar counts files as they're read, then resolves cross-file relations, then reports how many files and symbols it found. On a large project this takes a while.

You can close Settings while it runs; it keeps going. You just won't see the Done — N files indexed line when it lands.

When it's finished, your file tree refreshes, so files added or removed while the IDE was closed appear and disappear. An already-open 3D graph may still show the old shape until you switch channels or reload the window.

There's no menu item and no command for this — but it isn't the only thing that rebuilds the index. Restoring a checkpoint from the chat re-indexes as part of the restore, and opening a project for the first time indexes it automatically.