A tool for text search with pre indexing the repo especially non dotnet code elements like XML, configs, settings etc

[kri-kan]

Another issue I felt that can make this repo more reliable is, every project will end up having a lot of non dotnet code files, bet it XML, configs, settings, json, html, css etc.,
LLMs can be instructed to do text search on these files, but if the indexing proces can ingest and index these effectively be it plain text or RAG, a tool that can answer search queries with file names can reinforce the LLMs inference with a wider clarity.

[bbajt]

Thanks for raising this — it's a reasonable need, and you're right that repos are full of meaningful non-code files (config, XML, JSON, etc.).

The reason it's not a quick "yes" is a design one: CodeMap is deliberately a semantic index — it's built from the Roslyn compilation and scoped to .NET symbols, call graphs, and architectural facts. That focus is exactly what keeps the index small and the results precise (and what drives the 90%+ token savings). Ingesting every .xml / .json / .config / .html / .css file as plain text or embeddings would bloat the index considerably and dilute that precision — and for a lot of that content, plain text search is something agents already do well with grep / ripgrep, which don't need a pre-built index.

Worth knowing what exists today: code.search_text does regex search across the indexed source, so C#/VB/F# text is already covered — the gap is specifically arbitrary non-source files.

So the honest position: I'm not going to add blanket "index all file types" right now, precisely to avoid that bloat. If there's a real need it's more likely to land as a scoped, opt-in feature — e.g. you nominate specific globs (appsettings*.json, **/*.csproj) rather than everything — so the cost stays proportional to the value. If you can share the concrete case (which file types, and whether you need semantic/RAG search or just "which file contains this string"), that'd help me judge whether the scoped version is worth building.

Keeping this open as the tracker for it - it's a valid ask!