codebase_search tool doesn't handle "." path correctly for current directory searches

[hannesrudolph]

Description

When using the codebase_search tool with path parameter "." (meaning current directory), the search returns no results. This is because the path filtering logic creates an incorrect filter looking for files with pathSegments.0 = ".", but indexed files don't have "." in their path segments.

Steps to Reproduce

1. Use the codebase_search tool with path parameter set to "."
2. Example: <codebase_search><query>any search query</query><path>.</path></codebase_search>
3. The search returns no results even though there are matching files in the workspace

Expected Behavior

When path is "." (or "./" or other current directory representations), the search should return results from the entire workspace without any path filtering.

Actual Behavior

The search returns no results because it creates a filter looking for pathSegments.0 = "." which doesn't match any indexed files.

🔍 Comprehensive Issue Scoping

Root Cause

The issue occurs in src/services/code-index/vector-store/qdrant-client.ts (lines 377-386) where the path is split into segments. When path is ".", it results in ["."] after splitting, creating an invalid filter.

Affected Components

• Primary File:
  • src/services/code-index/vector-store/qdrant-client.ts (lines 377-386): The search method that creates path filters

Proposed Implementation

In the search method of qdrant-client.ts, add a check for current directory representations:

if (directoryPrefix) {
    // Check if the path represents current directory
    const normalizedPrefix = directoryPrefix.replace(/\\/g, '/');
    if (normalizedPrefix === '.' || normalizedPrefix === './' || normalizedPrefix === '') {
        // Don't create a filter - search entire workspace
        filter = undefined;
    } else {
        const segments = directoryPrefix.split(path.sep).filter(Boolean);
        if (segments.length > 0) {
            filter = {
                must: segments.map((segment, index) => ({
                    key: `pathSegments.${index}`,
                    match: { value: segment },
                })),
            };
        }
    }
}

Testing Requirements

• Unit Tests:
  • Test that path "." returns results from entire workspace
  • Test that path "./" returns results from entire workspace
  • Test that path ".\" works on Windows
  • Test that path "./src" correctly filters to src directory
  • Test that existing path filtering still works correctly

Technical Considerations

• Cross-platform compatibility (Windows backslashes)
• No breaking changes to existing functionality
• Minimal performance impact (just a string comparison)

[roomote]

I'm here to help out the maintainers and am going to see if I can fix this issue! 🚀

I can see this is a well-documented bug where the codebase_search tool fails when using "." as the path parameter. The issue is in the path filtering logic in qdrant-client.ts that creates an invalid filter for current directory representations.

I'll work on implementing the proposed fix and add comprehensive tests to ensure it works correctly across platforms. Will keep you updated on progress!

[roomote]

✅ Issue Fixed!

I have successfully implemented a fix for the codebase_search tool's handling of current directory paths.

🔗 Pull Request: #6517

📋 Summary of Changes

Problem: When using codebase_search with path parameter "." (current directory), the search returned no results due to incorrect path filtering logic.

Solution:

• Updated the path filtering logic in QdrantVectorStore.search() to properly detect current directory representations
• When directoryPrefix is ".", "./", "", or similar variations, the filter is now set to undefined to search the entire workspace
• Added cross-platform support for Windows-style paths (".\")

🧪 Testing

• ✅ All existing tests pass (381 tests in code-index service)
• ✅ Added 7 comprehensive test cases covering various current directory scenarios
• ✅ All CI checks pass (compilation, linting, unit tests on Ubuntu/Windows, integration tests)

🎯 Impact

The codebase_search tool now works correctly when searching the current directory with path=".", enabling users to search the entire workspace as expected.

The fix is backward compatible and does not affect any existing functionality - all other path filtering scenarios continue to work exactly as before.