index_file
Re-index one file after editing. 9ms unchanged, 153ms changed. Enables real-time coding workflows.
What it does
Re-indexes a single file after a change without a full repo walk. 9ms for unchanged files, 153ms for changed files — vs 3-8s for a full folder reindex.
Why agents need this
When an agent makes a code change and wants to immediately see updated analysis, index_file makes that possible in real-time. Full folder reindex would make live coding workflows impractical.
Always use index_file after editing a file. Never use index_folder for single-file changes.
Related tools
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.