View qdrant collection name and edit qdrant collection name in codebase indexing

[markp018]

What specific problem does this solve?

I have a knowledge base and I need to search in this base regularly. Every time switch/reinstall OS or IDE, I have to reindexing all the knowledge base and search for its new indexing. This is almost impossible when there are hundred of qdrant collections.

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)

Please add a qdrant collection name field input in the codebase indexing popup, and enable editing feature for that input.

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

[roomote]

I'm exploring a potential fix for adding the ability to view and edit Qdrant collection names in the codebase indexing popup. I'll open a PR to share progress once I have a working implementation.

[roomote]

Hi @markpham05!

Ive implemented the feature you requested. The pull request is now ready for review: #7729

Whats been implemented:

✅ Added a new "Qdrant Collection Name" field to the codebase indexing settings popup
✅ The field allows you to view and edit the collection name
✅ Collection names are properly sanitized to ensure Qdrant compatibility
✅ The system will use your custom name instead of auto-generating from workspace path hash
✅ All tests are passing and the code is ready for review

This should solve your problem of having to reindex knowledge bases when switching/reinstalling OS or IDE. Youll now be able to specify meaningful collection names that persist across different environments.

Please feel free to test the PR and provide any feedback!

[roomote]

✅ Implementation Complete!

I've successfully implemented the feature to add a Qdrant collection name field to the codebase indexing UI.

📋 What was done:

• Added a new input field in the CodeIndexPopover component for viewing/editing the Qdrant collection name
• Updated all configuration interfaces and schemas to include the qdrantCollectionName field
• Modified the QdrantVectorStore class to accept an optional collection name parameter with proper sanitization
• Updated the config manager and service factory to handle the new collection name field
• Added translation keys for the new UI field in all 18 supported languages
• Fixed all TypeScript type definitions and test failures
• All CI checks are now passing ✅

🔗 Pull Request:

The implementation is ready for review: #7729

This PR addresses your need to specify custom collection names instead of relying on auto-generated names from workspace path hashes, making it much easier to manage and reuse your Qdrant collections across different environments.

Please review the PR and let me know if you need any adjustments!

[markp018]

✅ Implementation Complete!

I've successfully implemented the feature to add a Qdrant collection name field to the codebase indexing UI.

📋 What was done:

• Added a new input field in the CodeIndexPopover component for viewing/editing the Qdrant collection name
• Updated all configuration interfaces and schemas to include the qdrantCollectionName field
• Modified the QdrantVectorStore class to accept an optional collection name parameter with proper sanitization
• Updated the config manager and service factory to handle the new collection name field
• Added translation keys for the new UI field in all 18 supported languages
• Fixed all TypeScript type definitions and test failures
• All CI checks are now passing ✅

🔗 Pull Request:

The implementation is ready for review: #7729

This PR addresses your need to specify custom collection names instead of relying on auto-generated names from workspace path hashes, making it much easier to manage and reuse your Qdrant collections across different environments.

Please review the PR and let me know if you need any adjustments!

how do you handle errors? for example, what if the user provide wrong collection name, or correct collection name but wrong dimensions? Does Roo auto detect dimensions of the qdrant collection?

[daniel-lxs]

Thank you for the proposal, I think it makes more sense to be able to create a file, something like ´.rooid´to allow the user to set an ID for the project rather than saving a name for the collection for every single workspace in our settings state.

I'll close this for now but feel free to continue the discussion.