Deterministic naming for Codebase Indexing Qdrant collections #7940
Description
What specific problem does this solve?
RooCode’s Codebase Indexing currently creates a Qdrant collection per workspace based on the absolute file path.
This leads to two issues:
-
Git worktree
Each worktree uses a different path, causing RooCode to treat them as separate workspaces and create separate collections. This means that indexes built in one worktree cannot be used in another, resulting in duplicated work and storage. -
Sharing between developers
Developers working on the same repository may have different local paths, leading to separate collections for the same codebase. This prevents teams from sharing a single, consistent index.
Why this matters
Without a stable collection name, every path variation produces a separate index. This leads to duplicated indexing runs, extra storage usage, and a reduced ability to rely on previously indexed context across worktrees or developers.
Ideal Outcome
A way to deterministically set the Qdrant collection name for a given workspace. If this value could be persisted in the repository, it would enable consistent indexing across worktrees and developers.
Additional context (optional)
No response
Roo Code Task Links (Optional)
No response
Request checklist
- I've searched existing Issues and Discussions for duplicates
- This describes a specific problem with clear impact and context
Interested in implementing this?
- Yes, I'd like to help implement this feature
Implementation requirements
- I understand this needs approval before implementation begins
How should this be solved? (REQUIRED if contributing, optional otherwise)
No response
How will we know it works? (Acceptance Criteria - REQUIRED if contributing, optional otherwise)
No response
Technical considerations (REQUIRED if contributing, optional otherwise)
No response
Trade-offs and risks (REQUIRED if contributing, optional otherwise)
No response