{"version":"2.1.280","anchor":"file-suggestion-index-now-tracks-and-returns-a-base-director","canonical_anchor":"file-suggestion-index-now-tracks-and-returns-a-base-director","heading":"File suggestion index now tracks and returns a base directory","tier":"internal","area":"Elsewhere","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280\/e\/file-suggestion-index-now-tracks-and-returns-a-base-director","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.280","markdown":"### File suggestion index now tracks and returns a base directory\n\nFile path suggestions (for @-mentions) now also report the base directory they were matched against\n\n**Unclear.** The finding does not say what user-visible effect, if any, this has on file suggestion behavior.\n\n**What**\n\nWhen you type a file path in Claude Code, such as after an `@`-mention, an internal function looks up matching files and paths to suggest. That function used to return just a plain list of matches. It now returns an object with two parts: `items` (the list of matches) and `baseDir` (the directory the matches were resolved against).\n\nRelated to this, the internal function that refreshes the git-based file index (`getFilesUsingGit`) now takes the working directory as an explicit parameter, instead of figuring it out on its own.\n\n**Why**\n\nThis is an internal change to how file suggestions are computed and doesn't change what you type or see when using @-mentions or path completion, but it makes the base directory used for matching explicit and traceable rather than implicit.\n\n- Area: Elsewhere\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}