Indexing and Status

Indexing turns a repository into the map an agent needs before it can improve the system coherently: files, packages, symbols, call edges, metrics, scores, and recent Git history. Run it at the start of the loop and again after each patch so rankings reflect the current codebase.

Example

Index TypeScript

Builds the local structural map for Redux and records the files, symbols, calls, scores, and history signals.

terminal

$ agide index . --exclude website --exclude docs --exclude examples

indexed 31 package(s), 176 symbol(s), 196 call(s), 0 impl(s); 0 metric(s) computed; 0 dropped
recent churn: 40 commit(s) scanned, 477 file(s) signaled
historical quality: 202 snapshot(s) analyzed
scored 153 symbol(s)
prepared searchable code context

31 files indexed

153 symbols available

57 call edges

1 history snapshots

Status confirms the current folder resolves to an indexed project and that the data is ready for ranking, graph inspection, and patch review.

Example

Check index health

Confirms the current folder is indexed and reports the query-ready counts.

terminal

$ agide status

agide project status: ready
  last indexed at: 1780362648
  next: query with `agide search`, `agide rank`, or `agide query`
  packages indexed:     31
  files indexed:        31
  symbols indexed:      153
  call edges indexed:   57
  type edges indexed:   0
  history snapshots:    1