Codebase indexing qdrant docker compose can not start indexing

[FabianHertwig]

App Version

3.19.5

API Provider

OpenAI

Model Used

N/A

🔁 Steps to Reproduce

Setup codebase indexing with a docker compose file like described here: https://docs.roocode.com/features/experimental/codebase-indexing

version: '3.8'
services:
  qdrant:
    image: qdrant/qdrant
    ports:
      - "6333:6333"
    volumes:
      - qdrant_storage:/qdrant/storage
volumes:
  qdrant_storage:

Go to codebase indexing settings and configure and save them.

💥 Outcome Summary

I expected I could start indexing, but the start indexing button is grayed out. There is a hint to save the settings to start indexing.

📄 Relevant Logs or Errors (Optional)

In the Roocode output there is this line


[CodeIndexManager] Error during background CodeIndexManager configuration/indexing: Cannot create services: Code indexing is not properly configured

[dosubot]

Hi @FabianHertwig! I'm Dosu and I’m helping the Roo-Code team.

The "start indexing" button stays grayed out when Roo Code thinks the codebase indexing setup is incomplete. Based on the docs, you need to make sure all required fields are filled and saved: enable "Enable Codebase Indexing" in the Experimental settings, enter your OpenAI API key and select a model, and set the Qdrant URL (should be http://localhost:6333 for your Docker setup). After saving, the button should become active if everything is correct docs.

If the button is still grayed out, double-check that your Qdrant container is running and accessible on port 6333 (try visiting http://localhost:6333 or running curl http://localhost:6333). If Qdrant isn’t reachable, Roo Code will not let you start indexing docs.

If you’ve confirmed all settings and Qdrant is running but still see the error, try restarting Roo Code after saving the settings. There are no known bugs in 3.19.5 matching this symptom in the docs. If you have more logs or see a specific error in the Roo Code output, sharing that could help narrow it down.

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}   

[FabianHertwig]

So I have restarted Cursor and the start indexing button was no longer grayed out. But when clicking it nothing happened and there was no output in the Roocode output.
I then ran the Developer: Reload Window command and then the indexing started and I saw the progress bar.

Seems to me like there might be an issue with the UI updating correctly.

[FabianHertwig]

Also I would recommend adding the QDRANT__SERVICE__API_KEY to the env section of the docker file, otherwise it is really confusing on what to put in the Qdrant key section in the settings. I think there even was some default value.

    image: qdrant/qdrant
    container_name: qdrant
    ports:
      - 6333:6333
    environment:
      QDRANT__SERVICE__API_KEY: mysecretpassword
    volumes:
      - qdrant_storage:/qdrant/storage

[daniel-lxs]

Hey @FabianHertwig,

Can you share a screenshot of your settings? Basically if any require setting is missing the indexing service won't start.

[FabianHertwig]

@daniel-lxs I now had this issue a second time in another project. The correct values from earlier were set, but only after a Developer: Reload Window the indexing started.

[C-F4]

I am also having this issue with all proper configurations being correct and my containers properly initialized. Possibly an error with the roo code UI not updating the status?

[hannesrudolph]

This is a problem was caused by settings not being properly saved, should be fixed now. Let us know if you still have issues with it.