Chat

The agent panel — on the left by default — is where you work with the agent. It looks like a chat, and the first thing to understand is that it isn't one.

A chatbot answers from what you paste into it. This agent works inside your project. It reads your files, searches the index, runs your type-checker, writes and edits code, and runs commands — on your machine, in the project you have open. The conversation is the interface; the work is the point.

Almost everything else on these pages follows from that one difference.

Because of that: who is allowed to change your files matters#

An assistant that can delete files is a different proposition from one that can only talk. Semantix has a permission gate for exactly that: reading and searching happen freely, and everything that writes, deletes, moves or runs a shell command can stop and ask you first, naming the tool and showing the target.

How much it asks is yours to set, with one chip next to Send: Manual asks before every write, delete and command; Edits lets the agent save and edit files freely and run harmless commands, asking for the rest; Full runs everything and asks only for critical commands and deletes. A delete, or a command that could destroy something — rm, sudo, a force-push — asks in every mode.

The gate is the same on every model, Claude Code included: its writes, edits and shell commands go through the same card, and its turns get the same Restore point.

→ What the agent can do

Because of that: you can watch it work#

If the agent is editing real files, you should be able to see it happen rather than read a summary afterwards.

So the file it's writing can open in a tab and type itself out; the 3D view of your project lights up the nodes it touches and flies the camera to them; and a line above the message box narrates the current step. Every tool it calls leaves a card in the transcript with a clickable filename, so checking its work is one click, not a search.

→ Watching it work

Because of that: one conversation is often not enough#

Real work runs in parallel — one agent on a migration, another on a bug, a third answering a question. Chat mode shows you one conversation at a time in the side panel. Runs mode slides that panel away and turns every open conversation into a floating card over your project, all live at once, driven by a single command bar. HUD mode puts one conversation straight onto the glass over the 3D view.

Same conversations, same history. A different way of looking.

→ Runs mode

The part that isn't about the agent#

Your conversations are stored on your own disk, in a database that lives outside the project folder so a reindex can't take it with it. Semantix does not keep a copy of your chat history on a server unless you switch cloud backup on yourself — it's off by default.

The turns themselves do go out, because that's what running a model means. Where they go depends on which model you picked: a Claude Code conversation goes through your own Claude login; a model from a connected provider or a custom endpoint goes to that provider with your key.

→ Conversations and history

Getting started#

You need to be signed in — the panel says so if you aren't — and you need a project open, because the tools work on one.

Type in the box at the bottom, press Enter. Drag a file onto the box from the explorer to point at something specific, paste an image to show it something, type / to reach your saved commands.

• Your first conversation — sending, reading a turn, and finding your way around a long one.
• The composer — attachments, slash commands, choosing the model, the permission mode and the context ring.
• What the agent can do — the tool list and the permission gate.
• Watching it work — the indicator, follow modes, and what stopping actually stops.
• Runs mode — floating cards, arranging them, and what persists.
• Conversations and history — tabs, history, replay, hand-off, and where it's all stored.