Project
The Re-index button — when to press it, what it touches, and what it never touches.
Settings → Project. One section, Index, with one row: Re-index project.
Re-index project#
One button, no confirmation. It throws away the map Semantix has of your project and builds a new one from what's on disk right now.
Reach for it when the IDE seems to be looking at an older version of your project — most often after you've changed files with the app closed, pulled a branch outside the IDE, or done a large move or rename. Semantix watches for changes while it's running, but it can't see anything that happened while it wasn't.
It's also the blunt fix for search returning something that isn't there any more, a hover card quoting a line that's moved, or the graph showing files you deleted.
What it touches: only the index — the derived map of your code. It reads your project; it never writes to it. Nothing in your source folder is touched, created or deleted. Your settings, open tabs, panel layout, saved cameras and conversations are all stored separately and come through untouched.
While it runs: the button reads Indexing… and a thin progress bar crosses the top of the
content area. On a large project this takes a while. When it lands, the row's hint reads
Done — N files indexed.; if it fails, the error prints there instead, in red.
Note
Search and the graph have nothing to answer with until it finishes. That gap is real — the old index is cleared before the new one exists.
You can switch to another Settings page, or another tab, while it runs; it keeps going, and the
Project page still shows Indexing… when you come back, because Settings pages stay loaded once
you've opened them. Don't press the button a second time — you'd start a second re-index on top
of the first.
When it's finished, your file tree refreshes, so files added or removed while the IDE was closed appear and disappear, and search and the graph answer from the new map.
Note
If a re-index genuinely fails, run it again before doing anything else. The old index is cleared before the new one is built, so a failed run leaves you with an incomplete one.
There's no menu item and no shortcut for this — but it isn't the only thing that rebuilds the index. Restoring a checkpoint from the chat re-indexes as part of the restore, and opening a project for the first time indexes it automatically.