{"version":"2.1.280","anchor":"file-search-index-gains-filename-only-matching-arrays","canonical_anchor":"file-search-index-gains-filename-only-matching-arrays","heading":"Fuzzy file search can now match on filenames separately from full paths","tier":"internal","area":"File Search","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/file-search-index-gains-filename-only-matching-arrays","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### Fuzzy file search can now match on filenames separately from full paths\n\nFile search indexing now tracks filenames separately so matches can target just the filename\n\n**Unclear.** The finding shows the new arrays being added but not yet how they change actual search results or ranking.\n\n**What**\n\nThe index Claude Code's fuzzy\/path file search uses now records extra per-entry information about just the filename (the last segment of a path), not only the full path. Alongside the existing whole-path arrays (`lowerPaths`, `charBits`, `pathLens`, `matchPositions`), it now also tracks `nameStarts` (where each filename begins within its path), `nameCharBits` (a bitmask of the lowercase letters used in just the filename), and `nameMatchPositions`.\n\n**Why**\n\nThis lets file search match and score based on the filename alone rather than only the whole path, which should make it easier to find a file by name even when it's buried deep in a long path.\n\n- Area: File Search\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}