Indexing No native equivalent

index_folder

Index a local folder with mtime-based incremental skip. Full reindex 57s → incremental 10s (5.6× faster).

What it does

Indexes a local folder with mtime-based incremental skip — unchanged files are skipped automatically. On a 778-file repo: full reindex 57s → incremental 10s (5.6× faster).

When to use

  • First-time indexing of a codebase
  • After major restructuring (or use invalidate_cache first)
  • Don’t use if repo already in list_repos — file watcher auto-updates
  • Don’t use after editing one file — use index_file instead (9ms vs 3-8s)

Related tools

index_file index_repo list_repos invalidate_cache

Benchmark note

This benchmark compares CodeSift against the closest practical native workflow an agent would use for the same task. For some tools, that baseline is a direct shell equivalent such as rg or find. For AST-aware, graph-aware, and LSP-backed tools, the baseline is a multi-step workflow rather than a strictly identical command. Results should be read as agent-workflow comparisons: token cost, call count, and practical context efficiency.