[BUG] Disable automatic full-workspace indexing: Multi-Root Workspaces cause local LLM DoS/Timeouts

[thomas-mindruptive]

I am using VS Code with a Multi-Root Workspace containing multiple projects. When I start indexing, Roo Code immediately attempts to index every single root folder in the workspace simultaneously.
This creates a massive spike in batch requests. Since I am using a local provider (Ollama) on consumer hardware (AMD Ryzen, running on CPU/iGPU), the provider cannot handle the concurrent load from multiple project scanners.

It's challenging to identify the files being indexed, because there is, as far as I have seen, no "live-file-indicator" nor a log output.
If there were, the problem would be immediately visible.

Roo-Cline: 3.39.1

Version: 1.107.1 (user setup)
Commit: 994fd12f8d3a5aa16f17d42c041e5809167e845a
Date: 2025-12-17T14:15:14.850Z
Electron: 39.2.3
ElectronBuildId: 12895514
Chromium: 142.0.7444.175
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.26200

ollama + quadrant run as local (non docker) processes

Ollama models: nomic-embed-text and nomic-embed-code.

I currently have to manually create .rooignore files containing * in every project folder I am not working on to prevent Roo Cline from killing my local Ollama instance. This is a tedious workaround and defeats the purpose of a workspace.

Context (who is affected and when)

Happens to users when they start indexing or restart VSC, and it automatically starts indexing.

Reproduction steps

• Open VSC with workspace file that contains multiple folders.
• Enable indexing (ollama + qadrant)
• Indexing starts and shows "0/N blocks" without ever increasing "0"
• After a few minutes, the indexing dialog log shows:

Fehler während des ersten Scans: Indexing failed: Verarbeitung des Batches nach 3 Versuchen fehlgeschlagen: Ollama Einbettung fehlgeschlagen: Ollama API-Anfrage fehlgeschlagen mit Status 400 Bad Request: {"error":"do embedding request: Post "[http://127.0.0.1:63812/embedding\](https://www.google.com/url?sa=E&q=http%3A%2F%2F127.0.0.1%3A63812%2Fembedding%5C)": read tcp 127.0.0.1:63826-\u003e127.0.0.1:63812: wsarecv: Eine vorhandene Verbindung wurde vom Remotehost geschlossen."}

• and dev console:

log.ts:460   ERR [Extension Host] Ollama embedding failed: AbortError: This operation was aborted
    at node:internal/deps/undici/undici:14900:13
    at processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async globalThis.fetch ...
    at async Dze.createEmbeddings (...\extension.js:924:19344)

log.ts:460   ERR [Extension Host] [DirectoryScanner] Error processing batch (attempt 1) in workspace c:\dev\pure\pure-svelte: Error: Verbindung zum Embedder-Dienst fehlgeschlagen.

Expected result

Indexes only the current project (not index entire workspace) or at least warns "workspace with many files..." or provides a config seeting "do not index entire workspace"

Actual result

Indexes entire workspace with all included folders. Does not indicate which files are indexed.

Variations tried (optional)

No response

App Version

3.39.1

API Provider (optional)

Google Gemini

Model Used (optional)

gemini-3-flash-preview

Roo Code Task Links (optional)

No response

Relevant logs or errors (optional)

Indexing dialog:

Fehler während des ersten Scans: Indexing failed: Verarbeitung des Batches nach 3 Versuchen fehlgeschlagen: Ollama Einbettung fehlgeschlagen: Ollama API-Anfrage fehlgeschlagen mit Status 400 Bad Request: {"error":"do embedding request: Post "[http://127.0.0.1:63812/embedding\](https://www.google.com/url?sa=E&q=http%3A%2F%2F127.0.0.1%3A63812%2Fembedding%5C)": read tcp 127.0.0.1:63826-\u003e127.0.0.1:63812: wsarecv: Eine vorhandene Verbindung wurde vom Remotehost geschlossen."}

Dev console:
log.ts:460   ERR [Extension Host] Ollama embedding failed: AbortError: This operation was aborted
    at node:internal/deps/undici/undici:14900:13
    at processTicksAndRejections (node:internal/process/task_queues:105:5)
    at async globalThis.fetch ...
    at async Dze.createEmbeddings (...\extension.js:924:19344)

log.ts:460   ERR [Extension Host] [DirectoryScanner] Error processing batch (attempt 1) in workspace c:\dev\

[roomote]

I've analyzed this issue and here's my proposed implementation plan:

Root Cause Analysis

The issue is in extension.ts where all workspace folders start indexing simultaneously during extension activation:

if (vscode.workspace.workspaceFolders) {
    for (const folder of vscode.workspace.workspaceFolders) {
        const manager = CodeIndexManager.getInstance(context, folder.uri.fsPath)
        if (manager) {
            // All folders start indexing in parallel
            void manager.initialize(contextProxy).catch((error) => {...})
        }
    }
}

Each CodeIndexManager instance independently calls startIndexing(), causing concurrent embedding API requests that overwhelm local providers like Ollama on consumer hardware.

Proposed Solution

1. Add a new setting: codebaseIndexAutoStart (boolean)

• Default: true (backward compatible)
• When false: Indexing will not start automatically on extension activation/VSCode restart
• Users can manually start indexing through the indexing settings popover

2. Add a new setting: codebaseIndexMaxConcurrent (number)

• Default: 1 (sequential indexing - one folder at a time)
• Controls how many workspace folders can be indexed simultaneously
• Value of 1 prevents DoS on local embedding providers
• Users with powerful hardware/cloud providers can increase this value

3. Implement a sequential indexing queue in extension.ts

• Create a simple queue system to manage concurrent indexing
• When one folder finishes indexing (reaches "Indexed" state), start the next folder
• Respect the codebaseIndexMaxConcurrent limit

4. Add configuration UI in CodeIndexPopover.tsx

• Add checkbox for "Auto-start indexing on extension load"
• Add dropdown/input for "Maximum concurrent indexing operations"

Files to modify:

1. src/extension.ts - Add indexing queue with concurrency control
2. src/services/code-index/config-manager.ts - Add new config options
3. webview-ui/src/components/chat/CodeIndexPopover.tsx - Add UI for new settings
4. src/shared/ExtensionMessage.ts / types - Add new config fields
5. Relevant test files

This approach:

• Maintains backward compatibility (default behavior unchanged for single-folder workspaces)
• Gives users full control over indexing behavior
• Prevents local provider overload by default in multi-root workspaces
• Is minimally invasive to the existing codebase

Please mention @roomote in a comment saying that you approve this plan, and I'll proceed with the implementation.

[ArchimedesCrypto]

@roomote Looks good to me. Approved. Ensure your test cases cover edge cases as well.

[roomote]

Thanks for the approval! I will now proceed with the implementation. I will ensure test cases cover edge cases as requested. Starting work on the changes now.

[roomote]

Opened a PR with my attempt at addressing this: #10612

The PR adds:

• Auto-start indexing setting to disable automatic indexing on workspace open
• Maximum concurrent indexing setting to limit parallel indexing (default: 1 for sequential)
• UI controls in the Code Index popover (checkbox and slider)
• Unit tests covering the new functionality

Feedback welcome!