The IDE

Underneath the 3D view and the agent, Semantix Studio is an editor. You open a folder, a tree appears, you click a file and it opens. None of that will surprise you.

The one thing worth saying up front: Semantix takes in your whole project when you open it, and after that it knows it. Not the file you have open — the project. Every file is accounted for, and the ones written in a language it knows are read properly: every function, class and constant in them, and which of them reach for which.

That happens once, it takes a moment on a large project, and you watch it happen in the status bar. Almost everything on these pages is a consequence of it having happened.

Because of that: finding things is about names, not folders#

You don't have to remember where something lives. Type part of a name and the folder, the file, or the definition itself comes back — and clicking the definition takes you to it.

Hover a name in the editor and Semantix tells you what it is, its signature, and how many places use it; open the card up and it shows where it's declared and the first few of those places, each one clickable. F12 jumps to the definition. There's no "go to symbol" index to build first and no waiting for a language server to wake up.

The same knowledge puts an error count on files in the tree before you've run anything.

→ Search

Because of that: the agent is working in the project you're looking at#

The agent isn't reading files you paste at it. It's in the same project, with the same map of it, and the window shows you that as it happens: folders unfold as it works, a file it's writing opens and types itself out in front of you, and the tree tidies up after the run ends.

Files it creates appear in your tree without a refresh. So do changes you make in another editor entirely.

→ Watching it work

Because of that: your project has a shape you can look at#

Knowing what a project contains and how it connects is what makes the 3D view possible at all. It's the same knowledge behind the tree and the search box, drawn instead of listed.

→ The 3D view

The part that isn't about any of that#

It is also, plainly, an editor. Tabs, autosave, find and replace, sixteen syntax themes, a real terminal in the bottom panel.

It is a deliberately light one — there is no autocomplete, no code folding, no multi-cursor. It is built for reading a project and changing it, not for replacing the editor you already know. The editor page says exactly where that line falls, rather than leaving you to find it.

Getting started#

Open a folder and give it a moment to read.

• Opening a project — choosing a folder, what gets read, and what's kept where.
• The explorer — the tree, and creating, renaming, moving and deleting.
• The editor — tabs, editing, autosave, and what the gutter tells you.
• Search — what the search box matches, and where to search text instead.
• The terminal — a real shell in your project.
• Panels and layout — the parts of the window and what comes back.