Clicking a node
The glass card that opens on a file, and the X-ray that shows you what breaks if you change it.
Clicking is the main verb in the 3D view. One click flies the camera in, opens a card of information about the thing you clicked, and colours the graph to show what that thing is connected to.
The second of those is the one worth learning properly. It answers a question that is genuinely hard to answer in a file tree.
What depends on this#
When a node is focused, the graph lights up its blast radius in two colours:
- Amber — the things that depend on it. These are what break if you change this file.
- Teal — the things it depends on. These are what it needs to work.
The lighting reaches three hops out, fading as it goes, so you see not just the immediate neighbours but the second and third ring behind them. Only the first hop carries moving particles, which keeps the direct relationships readable inside the wider glow.
Containment is deliberately excluded. A file being inside a folder isn't impact — it tells you nothing about what happens if you edit it. Only real code relationships light up.
This is the "should I touch this?" instrument. Click a file you're about to refactor, and the amber is your morning.
The lighting recomputes as the scene changes, so expanding a folder while a node is focused folds those new files into the radius if they belong there.
The card#
A dark glass panel appears beside the node, carrying what Semantix knows about it.
The header is the file's icon and name — folders get a trailing slash. Below that, up to four sections:
META — the language, or directory for a folder. For a file whose language Semantix doesn't
recognise, you get the extension instead: toml, lock.
SYMBOLS — how many functions, classes and types are in it.
ACTIONS — the three most recent things an agent did to this file: wrote · 12s ago,
edited · 3m ago, read · 1h ago. If nothing has touched it, it reads idle.
HISTORY — a longer list, up to eight. It only appears once the file has actually been written or edited.
Note
These two sections are an agent's log, not the file's. They record what agents did during
this session — your own edits in the code editor, changes made outside Semantix, and git history
never appear here. A file you rewrote by hand five minutes ago still reads idle.
Tip
The HISTORY rows are clickable. Click one and the chat jumps to that exact change — the message and the diff where it happened.
That's the shortest path from "why does this file look like this" to the conversation that made it that way. You're standing in the project, you see a file that surprises you, and two clicks later you're reading the reasoning.
The two buttons#
The card header carries a small dark pill with up to two icon buttons.
Expand in place (a +, folders only) — unfolds the folder's contents into the scene you're
already in, without leaving it. Use this to build up a view of several folders at once.
Drill (a </> glyph) — goes into the thing:
| You drill | You get |
|---|---|
| A folder | That folder as its own 3D tab |
| A file | That file open in the code editor, in a new tab |
Drilling a closed folder opens it first, so you always land on something with contents.
How the card goes away#
It isn't a window — there's no close button, no title bar, and you can't drag or resize it. It's attached to the node. Four things dismiss it:
- Click empty space.
- Move the camera — any tumble, zoom or pan.
- Fly far enough away. The card fades as you retreat and lets go entirely once you're well clear of it.
- Turn away — it hides when the node it's anchored to leaves the screen.
The card is also transparent to the mouse, which is easy to miss and genuinely useful. Only its two buttons and its history rows take clicks; everywhere else, your click passes straight through the glass to the scene behind it. The node stays draggable and clickable with its own card sitting on top of it, and you can grab something behind a card without moving the card out of the way.
Only one at a time#
Focusing is single-selection: one card, on the node you last clicked. The exception is an agent at work, which opens its own cards on the files it's touching — up to three at once. That's Watching the agent work.