Run an ingest
By the end of this page your application will have its first graph version, and you will know when to re-run.
Prerequisites
- An application with at least one source (Attach sources).
- Admin or Developer role.
What an ingest does
It acquires each repository, inventories every file, parses the code it understands, runs the framework detectors, assembles the result into a graph, and embeds the code into a searchable index. One completed ingest writes one version.
Run it
Choose Full or Incremental
| Mode | What it does | Use it |
|---|---|---|
| Full | Reads and re-embeds everything. | The first time, and after changing a source or a model. |
| Incremental | Compares file hashes against the last version and re-embeds only what changed. | Every other time. |
An unchanged repository costs no embedding calls at all on an incremental run, which is what makes keeping the graph fresh affordable.
Click Ingest
The button stays disabled until at least one source is attached, and says so on hover.
Watch it run
The card shows a live log while the job works. It reads “Waiting for log lines…” until the first arrives.
A running job can be Cancelled. Nothing partial is kept — a version is only written when a job completes.
Read the result
When it finishes you get a version number, and the screen offers four places to go: Explore the graph, Search the code, Cross-repo links and Versions.
The history table
Every job is listed, whatever its outcome:
| Column | What it tells you |
|---|---|
| Status | Whether it completed, failed or was cancelled |
| Mode | Full or Incremental |
| Started · Duration | When, and how long it took |
| Nodes | How many things the graph ended up with |
| Chunks written | How much was embedded — near zero on an incremental run where little changed |
Chunks written is the number to watch. An incremental run that writes as many chunks as a full one means the hashes all changed, which usually means a reformat, a line-ending change, or a different branch.
Ingest embeds code, which consumes credits. Incremental runs are what keep that cost small — an unchanged repository re-embeds nothing. See Pricing & credits.
When to re-run
- After a meaningful merge, so agents are not reasoning about last month’s code.
- Before a piece of analysis work, so the answer reflects what is deployed.
- Not on every commit. A graph version is a snapshot, and having hundreds of near-identical ones makes the version history harder to read than it is worth.
Common issues
- Ingest is disabled — No source is attached.
- The job fails immediately on a private repository — The credential name does not match a configuration, or its token cannot read that repository.
- It finishes with very few nodes — The repository is mostly in a language with no symbol parser. You still get the file inventory and infrastructure detectors. See Overview.
- An incremental run re-embeds everything — Every file hash changed. Check for a reformat, a line-ending change, or that the branch is the one you expect.
- The graph is empty afterwards — The job stopped before the inventory stage. Read its log in the history.