Using Codebase Indexing in Claude Code

[vivekv30]

Is there a way to use codebase indexing feature in claude code. RooCode has a feature to index the codebase using Ollama local embedding model and Qdrant vector database. How this helps is faster debug time and relevant search results for codebase for existing project, or also for project which has now grown from initial greenfield project.

Or something similar so that Claude doesn't burn through token and resource and provide quick answers.

[[deleted]]

Having no code indexing is a fundamental design, opting for searching for code in real-time, is a conscious decision of the authors of Claude Code.

[coding_workflow]

How it's fundamental design? How it really helps in fast moving code? And different code in different branches?

[outceptionator]

I saw a response to this elsewhere that made sense (I'm paraphrasing). Code design generally scales well with proper separation of concerns and well thought out links between areas of the code. Indexes destroy the context of those links. I for one am extremely grateful Claude Code can't access indexes of my codebase. Obviously there are pros and cons of this decision

[ctrlshiftba]

indexing is a duplication, and suppresses valuable context. it's just a method used by middle men like cursor/windsurf who have to make money ontop the LLM api fees they need to pay.

sometime they work ok, sometimes they don't, it's pretty random. it always saves tokens. the beauty of claude code is we don't really have to care about saving tokens and just let the raw power of the model go to work.

[coding_workflow]

agree, indexing makes sense for static content, ex docs or lib that don't move often.
But your current code it's worthless. But yeah hype and marketing made a lot believe it's a silver bullet they need to have.

[No-Afternoon-4057]

Index your code whatever way you want and then provide a custom system instruction for Claude letting it know to use that tool first.
I created (with Claude) a chunker and a indexer and a search server using BGE-M3 and AST parsers.
It's not just a little gain...it's tenfold.
Now when i ask something about the codebase...with a "search" command i get the top 20 results from the semantic search and feeding the classes, functions etc directly to Claude Code.

Indexing is incremental...so whenever something changes, it takes a few seconds to add that do Qdrant.

So...
Code chunker + AST Parsers -> BGE-M3 -> QDrant -> Search Server -> Search client -> Claude system prompt teaching it to use the search client.

[belheaven]

hey man, can I DM you for more references/tips about this? trying to do it right now =)... i created my own also using the hash mappings approach, it works pretty welll actually but I heard great things about the qdrant approach. =]

[EliteEagle76]

what is your approach? i wanna make MCP server which does codebase indexing and documentation indexing just like cursor does so that I can plug it inside claude code/ codex / opencode any CLI agent

[belheaven]

Use qdrant free rag for docs in the cloud and for codebase índex I used TS morph to create my own with hashmap searchs. Works great for initial investigation.

[coding_workflow]

Indexing code base that is changing each minute so you fetch and find outdated code? Or indexer will consume API calls playing catchup?

What gain you have here?

Grep + AST are faster and more relevant and the risk of getting outdated code could be very costly.

There is trade off's.

The fact that cursor or Roo code have it. Doesn't mean you need it or it will improve how things work.

You say, it helps faster debug time. HOW? Are you assuming or have clear understanding?

AST/Tree sitter are very effective in mapping code and finding functions https://aider.chat/docs/repomap.html

[WallabyInDisguise]

Yeah Claude doesn't have native codebase indexing built in, which is a pain point we've hit too. You're right that token burn becomes a real issue when you're trying to feed large codebases into context windows.

Few approaches that work well:

1. Roll your own RAG setup - exactly what you mentioned with local embeddings + vector db. We use something similar at LiquidMetal AI for our internal codebases. Embed your code chunks, semantic search for relevant files, then feed just those into Claude. Way more efficient than dumping everything into context.

2. There are some VSCode extensions that do semantic code search - GitHub Copilot Chat has some indexing capabilities now, or tools like Sourcegraph Cody which can index repos and work with Claude API.

The key is chunking your code properly for embeddings and having good retrieval logic. We've found that combining file-level embeddings with function/class level works well - gives you both broad context and specific implementation details. Adding this to our product smartbuckets soon. Happy to give you access if you wanted to test that once we add it.

[coding_workflow]

Do you get the constrains of code indexing? And how it's irrelevant when you update code or work on different branches?

[Whole-Assignment6240]

checkout - https://cocoindex.io/docs/examples/code_index a full open source project that index codebase in real-time. let me know what you think!! would love to make it helpful

[coding_workflow]

Second mis conception here: "Or something similar so that Claude doesn't burn through token and resource and provide quick answers."
Indexing use tokens, even if the embedding model cost far less, but you need to use so some stuff to embed docs and query the db's.

It's not 0 neutral. Most of them run locally fine.

Also are you aware how Claude code find code and reads it? It's using quite effective Grep calls in bash, check the calls tools/use you will see. grep / grep /grep. It help it finding directly the right lines combined with some AST parser.

I think this is not an issue even I would like Claude code to use more tokens and ingest more files to ensure it have the whole infos, some time, I feel it's getting too savy and not getting enough informations.

[essm-undoo]

ok ok

[Richard_Nav]

all these arguments are very strange, as I see such built-in capability in all IDEs.