Repository Intelligence

The Repository Intelligence dashboard reads your repository once and keeps a live index of it — the files, the symbols, the imports and the history — so every coding session is briefed from a map of your actual codebase instead of answering blind.

The index

The first time you open it, the index builds itself in the background. The dashboard shows the build in progress — how many files it has found, what phase it is in (finding files, reading symbols, resolving imports, mining history, writing the index) and how long it has left. Once it is ready it keeps itself current as your code changes.

The header always shows where the index stands: the state (READY, INDEXING, REBUILDING or ERROR), the commit it was built from, when it was last indexed, and the size of the index — files, symbols and database size — so you can see exactly what the agent has to work from.

What it gives you

• Overview — the state of the index and the health of the repository at a glance.
• Knowledge Graph — modules and files drawn as a graph of imports and co-changes, with a search box that finds a file or symbol and shows its neighbourhood. Click a file to see the module it lives in, the files it imports and the files it changes together with.
• Discovery — a replay of what each task actually discovered while it worked: which files it briefed itself on, in order, as it explored the repository.
• Hotspots — the files that change most and are touched by the most code: churn, commits in the last 90 days and top owners, so you can see where the risky code lives.

Why it matters

When the agent can see the shape of your repository — what depends on what, what changes together, which files are the hot ones — its answers and edits are grounded in the real structure of your code rather than a guess. The graph and hotspots also give a developer a way in: start at a hot file, follow the imports, understand the neighbourhood before touching it.

Keeping it current

The index updates itself as you work. When it needs a full refresh — after a failed incremental update, for instance — the dashboard offers Rebuild index, which rescans the whole repository (about a minute on a typical codebase).

Next steps

• Engineering Trace — what the agent did during a session.
• What is AETHER Coder — the panel these views live in.