Local AI Toolkit

Code search is not text search

Contents · Русская версия

A file is not sliced into equal slabs of text. It is taken apart by declaration — class, method, function — and each of those gets its own chunk, with its name, its signature and its exact lines. A declaration too long for one chunk — 6,000 characters with its header — is cut into overlapping parts numbered like [1/3]. That is why a hit reads OrderCloser.CloseAsync, or one numbered part of it, rather than a line that happened to match in the middle of somebody else’s method.

One thing the index cannot see: a file you have edited but not saved. Navigation can still answer for it, but only when an agent hands over the buffer’s text — there is no such path from the command line, and language servers stay off until you enable them.


← What the command line gets · Contents · With a cloud agent: what stops costing tokens →