Watching the agent work
Files appear as ghosts before they exist, code lands on glass, and the camera follows — or doesn't, if you'd rather it didn't.
This is the part of the 3D view that isn't decoration.
When an agent works on your project, it does so in a place you can see. Files it creates appear before they exist. Files it edits show you the code arriving. The folders it's working in unfold and the ones it isn't fold away, so the scene narrows to where the work is happening.
You can read an agent's whole turn without reading a word of its output.
What a write looks like#
The agent decides to write a file. In the graph, all at once:
The folders unfold toward it. The path down to that file opens, level by level. Everything irrelevant closes. The scene prunes itself to the work.
A ghost appears. If the file doesn't exist yet, a translucent node hangs itself off the parent folder, faint and half-there. It is a file that is going to exist. It is not on your disk yet.
Its wire starts throbbing, pulsing on a heartbeat with particles running down it toward the node — the visual of something being fed.
The node turns into a card, and the code lands on it. The badge and its label step aside, and the file becomes a pane of glass with the actual text the agent is writing projected across it, syntax-highlighted, scrolling. Bolts of light crackle over the surface with each burst.
Writes are anchored to the bottom — you watch the tail, the way you'd watch a terminal. Reads are anchored to the top, because when something is being read you want the beginning of the file.
Then it resolves. A tick in the card header on success, a cross on failure. On success the ghost holds until Semantix has actually seen the file land on disk, then solidifies into a real node and its wire flashes bright. On failure the ghost dissolves and the graph looks as if it never happened.
The card lingers a moment and fades. Up to three can be open at once, so a burst of writes reads as three panes lighting in sequence rather than a flicker you miss.
What a read looks like#
Quieter, and it depends on how many files.
One file — the camera flies into it, the same ride as clicking it yourself, and the file's text is cast onto its glass for about five seconds. Long enough to see what it looked at.
Several files at once — they all light up in the spotlight colours and the camera pulls back to frame the whole set. No text is cast; you get the shape of what it reached for, not the contents.
Deletions get a single particle down the wire, no flash, and the node disappears from the scene. The graph is telling you the truth about your project as it changes, not celebrating it.
The rhythm of a turn#
On Visual follow — the default — a turn has a shape you can watch. At the start the view returns to the whole project, seen wide. It dives into each file as the agent reaches it. At the end it pulls back out again.
Sky view, dive, sky view. Once you've watched it a few times you can tell how wide a turn was without reading the transcript — how far it dove, how many folders it opened, how much of the project it lit on the way.
Note
That opening move does more than move the camera: it takes the view back to the project root. If you had drilled into a folder, sending a message returns you to the top and you'll need to drill back in.
It only happens in Visual follow, and only for the conversation you're looking at — an agent working in another conversation won't reset your view.
At the end of a turn the folders fold back down to a single open path, so the scene doesn't accumulate. That one happens in every follow mode, camera or no camera.
The three follow modes#
You control how much of this reaches you. The follow control sits in the chat input bar, and has three states:
| Mode | What it does |
|---|---|
| Visual follow (3D camera) | The camera flies to what the agent is touching. The default. |
| Editor follow (open agent's file) | No camera. The agent's file opens in your editor instead, streaming as it's written. |
| Follow off | Neither. |
Important
"Follow off" turns off the camera, not the graph. Ghost nodes, glowing wires, the cards and the code projection all still play in every mode — including off.
That's on purpose. The setting is about whether the app is allowed to move you, not whether the project is allowed to show you what's happening in it. If you want to keep the graph as a live status board while you work undisturbed, that's exactly the combination.
What "off" does stop, besides the camera: the file explorer no longer reveals the agent's files as it works, and the view no longer returns to the project root between turns.
Editor follow has one extra rule: it only follows agents working in the conversation you're actually looking at. A background agent in another conversation won't yank your editor around.
The graph updates as work lands#
New files appear as nodes without the scene rebuilding. Deleted files vanish. Existing nodes are briefly held in place while new ones arrive, so a burst of file creation doesn't detonate the layout you've arranged.
This is worth saying plainly: the 3D view is not a snapshot you refresh. It's the current state of the project, and it changes underneath you while you're looking at it.