3D Viewer

Most editors show you a project as a filing cabinet: a tree on the left, tabs across the top. You navigate it by remembering where you put things.

Semantix also draws it as a space. Folders and files become objects hanging in three dimensions, connected by the relationships that actually exist in your code, and you move through it with a mouse. It is the same project the file tree is showing you — just laid out so that shape, distance and thickness carry information a list can't.

This is not a diagram you generate and look at once. It's the view a folder tab opens into, it updates while you work, and when an agent is running you can watch it move through your project in real time.

Where it lives#

The 3D view isn't a mode you switch into. It's what a folder tab shows.

• Click a folder in the explorer, and the tab shows that folder in 3D.
• Click a file, and the tab shows code.

That's the whole rule. There's no 3D/code toggle to hunt for, because they were never two views of the same thing — they're two kinds of tab.

The leftmost tab in the strip is your anchor: a globe icon, no label, and it can't be closed. It's the project root — click it and you're back in the 3D view of the whole project.

One wrinkle worth knowing. Semantix reuses the tab you're standing in rather than opening a new one every time you click something, so if you click a file in the explorer while the globe tab is active, that tab becomes the file. The anchor isn't pinned; it's just the tab pointing at the root.

What a node is#

In the default view you're looking at one folder at a time — its direct contents, not the whole repository at once.

Folders are drawn as folder icons. A folder's size is how many files it holds, so a fat node is a heavy directory and you can spot it without reading a single label.

Files are drawn as small badges — an extruded shield with a file-type icon on its face and the filename floating above it. A file's size is how many symbols it contains: functions, classes, types. A big badge is a big file in the sense that matters, not in bytes.

Out of the box, every file badge shares one look — the same metal shield, distinguished by the file-type icon on its face rather than by colour, and every folder wears the same yellow. That's deliberate: the default view is meant to be legible before you've configured anything.

If you want a project that reads as coloured neighbourhoods — .ts one way, .py another, or the whole project tinted by language — that's what the 3D Editor is for.

There's also a violet node carrying the parent folder's name. That's the way up.

Hovering any node gives you the numbers directly — a folder shows 12 files · 340 symbols, a file shows its language and symbol count.

What a wire is#

Wires are relationships. Two kinds, and it's worth knowing which you're looking at.

Containment — a folder to the things inside it. This is the skeleton that holds the layout together.

Dependency — one thing using another. Imports, calls, type references.

Here is the honest part. In the folder view, these are not colour-coded. Every relationship between two things in view is bundled into a single wire, and what varies is thickness: a thicker wire means more relationships underneath it. Two folders joined by a heavy wire are deeply entangled; a thin one is a passing acquaintance.

That's a deliberate trade — a folder-level view with per-relationship colouring is unreadable noise. When you want to know exactly what depends on what, you don't read the wires at rest, you click a node and let the graph colour it for you.

Two more things wires do: they carry a small arrow showing direction, and relationships pointing at files outside the folder you're looking at are not drawn at all. The view is about this folder.

Opening a folder without leaving#

You can expand a folder in place. Its contents merge into the scene you're already in, sitting alongside the level above rather than replacing it, and you can keep going — building up a view of several folders at once.

The explorer and the 3D root view stay in sync, both ways. Open a folder in the tree and it unfolds in the graph; unfold it in the graph and the tree opens to match. The 3D view wakes up already shaped like your file tree.

One limit worth knowing: that mirror applies to the root view. If you've drilled into a subfolder as its own tab, that tab keeps its own shape and doesn't track the explorer.

Turning it off#

Settings → General → Graph → the 3D graph view checkbox. It's on by default.

Turned off, the 3D viewer is genuinely off — no rendering, no physics, no animation, no WebGL context. Not hidden, not paused. Folder tabs become a quiet empty surface, and everything else in Semantix — explorer, editor, chat, agents — works exactly as before.

The rest of these pages#

• Moving around — mouse, the orientation gizmo, and the camera that remembers where you left it.
• Clicking a node — the glass card, and the X-ray that shows you what depends on a file.
• Finding things — search inside the scene, and the spotlight.
• Watching the agent work — files appearing as ghosts, code landing on glass, and the three follow modes.
• When it's quiet — what the graph does when you stop touching it.
• Big projects and performance — what happens at scale, and the quality ladder you never have to configure.