Incremental codebase indexing #11

New issue

Open

opened 2026-04-07 20:22:15 +00:00 by austin · 0 comments

austin commented

2026-04-07 20:22:15 +00:00

Owner

Implement the indexing lifecycle: initial scan, persistent storage, and incremental updates.

On first run, walk the project directory and index all Python files
Store the index to disk (under .localcode/) so subsequent runs are fast
Track file modification times; on startup, re-index only changed files
Support a file watcher mode for re-indexing on save (optional, for long-running sessions)
Respect .gitignore and a configurable exclude list (skip venvs, node_modules, etc.)
Progress reporting for the initial index build (will be wired to the TUI later)

The index needs to be fast enough that startup feels instant on projects with a few hundred files.

Implement the indexing lifecycle: initial scan, persistent storage, and incremental updates. - On first run, walk the project directory and index all Python files - Store the index to disk (under `.localcode/`) so subsequent runs are fast - Track file modification times; on startup, re-index only changed files - Support a file watcher mode for re-indexing on save (optional, for long-running sessions) - Respect .gitignore and a configurable exclude list (skip venvs, node_modules, etc.) - Progress reporting for the initial index build (will be wired to the TUI later) The index needs to be fast enough that startup feels instant on projects with a few hundred files.