First-run indexing with progress #30

New issue

Open

opened 2026-04-07 20:24:59 +00:00 by austin · 0 comments

austin commented

2026-04-07 20:24:59 +00:00

Owner

Wire up the indexing lifecycle to the interactive session.

On first run in a project: detect no existing index, trigger full index build
Display progress via Rich (file count, current file, elapsed time)
On subsequent runs: load existing index, detect changed files, re-index incrementally (should be near-instant for small changes)
Index storage under .localcode/ in the project root
Add .localcode/ to the suggested .gitignore entries

This is the bridge between the indexing system (milestone 2) and the interactive session. The user should see the index build happen and understand that subsequent starts will be faster.

Wire up the indexing lifecycle to the interactive session. - On first run in a project: detect no existing index, trigger full index build - Display progress via Rich (file count, current file, elapsed time) - On subsequent runs: load existing index, detect changed files, re-index incrementally (should be near-instant for small changes) - Index storage under `.localcode/` in the project root - Add `.localcode/` to the suggested .gitignore entries This is the bridge between the indexing system (milestone 2) and the interactive session. The user should see the index build happen and understand that subsequent starts will be faster.