Watching the agent work
Files appear as ghosts before they exist, code lands on a card, 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 sky lights what it reads.
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 sky, all at once:
The folders unfold toward it. The path down to that file opens, level by level, exactly as if you'd opened it in the explorer. Nothing else closes.
A ghost appears. If the file doesn't exist yet, a translucent orb hangs itself beside the parent folder, faint and half-there. It is a file that is going to exist. It is not on your disk yet.
The orb beats. With every burst of text the orb flashes and its bolts run outward — the visual of something being fed.
A card docks on it, and the code lands. The card's live section is labelled writing (or
editing), and the actual text the agent is writing scrolls across it, syntax-highlighted.
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. The label turns to wrote or edited. On success the ghost holds until
Semantix has actually seen the file land on disk, then becomes a real orb. On failure the ghost
dissolves and the sky looks as if it never happened.
A finished card lingers a moment and fades. Up to three can be open at once, so a burst of writes reads as three cards lighting in sequence rather than a flicker you miss.
What a read looks like#
Quieter, and it depends on what the agent did.
One file — the camera flies in front of it, the same ride as clicking it yourself, and the file's text is cast onto its card for about five seconds. Long enough to see what it looked at.
Several files at once, or a search — each hit is struck from its folder and lights as the bolt lands, the rest of the sky sinks, and the camera rises over the whole set. No text is cast; you get the shape of what it reached for, not the contents.
A folder listing — the camera turns to face the folder, and the folder and everything the listing found light up together, with a strike out to each entry.
Deletions and new files the watcher notices get a single beat on the nearest visible orb, and the node appears or disappears from the scene. The sky 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 flown into a folder, sending a message returns you to the top.
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.
Nothing folds at the end of a turn. Whatever the agent opened stays open until you close it — one folder at a time, or all at once with Collapse All Folders on the sky's right-click menu.
The three follow modes#
You control how much of this reaches you. The follow control sits in the strip above the chat input, 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 sky. Ghost orbs, strikes, 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 sky as a live status board while you work undisturbed, that's exactly the combination.
What "off" also stops: the file explorer no longer reveals the files the agent reads (it still reveals what it writes), and the view no longer returns to the project root between turns.
Both the camera and the editor follow only the conversation you're actually looking at. A background agent in another conversation lights its nodes and pops its cards, but won't move your camera or your editor.
Your hand wins. Drag the sky during a turn and the agent stops steering the camera for that step; the pointer merely resting on the scene doesn't. The light plays regardless.
The sky updates as work lands#
New files appear as orbs without the scene rebuilding. Deleted files vanish. Existing orbs are held in their seats while new ones arrive beside their kin, so a burst of file creation doesn't detonate the layout you were looking at.
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.