Feature: Per-Workspace Codebase Indexing Control

[VooDisss]

Problem Description

Currently, the codebase indexing feature in the RooCode VS Code extension is controlled by a single global setting. When enabled, it automatically starts indexing all open workspaces upon VS Code launch. This can lead to high GPU usage, especially for users who work with multiple VS Code windows simultaneously (e.g., 10+ windows). It becomes difficult to identify which VS Code instance is causing the high resource consumption.

This is problematic for users who only need indexing for specific projects and want to keep it disabled for others to conserve system resources.

Proposed Solution

Introduce a per-workspace setting for codebase indexing that overrides the global default. This would allow users to:

1. Set a global default for indexing: For example, have indexing disabled globally.
2. Enable or disable indexing for individual workspaces: A user could then enable indexing for a specific workspace, and that setting would persist for that workspace across sessions.

This would provide a more granular control over resource usage and a better user experience for developers working on multiple projects.

Technical Context

Based on an analysis of the codebase, the core of the indexing feature resides in the src/services/code-index/ directory.

• CodeIndexConfigManager (src/services/code-index/config-manager.ts) is responsible for loading the indexing configuration. It currently reads from the global state, and this would need to be modified to also read from workspace-level settings.
• CodeIndexManager (src/services/code-index/manager.ts) is a singleton that manages the indexing process for each workspace. It would need to be updated to use the new workspace-specific configuration.
• CodeIndexOrchestrator (src/services/code-index/orchestrator.ts) is responsible for the actual indexing and file watching. Its behavior is driven by the configuration provided by CodeIndexConfigManager.

The proposed changes would primarily involve updating CodeIndexConfigManager to first check for a workspace-specific setting, and if one is not found, to fall back to the global setting. This would allow for the desired override behavior.

Impact

This feature would greatly improve the user experience for developers who work on multiple projects simultaneously, by giving them more control over resource usage. It would also make the RooCode extension more efficient and less intrusive for users who do not need indexing on all their projects.

[roomote]

I'm exploring a potential implementation for per-workspace codebase indexing control. I'll work on adding the ability to override the global indexing setting at the workspace level as described. Will open a PR to share progress.

[roomote]

I have successfully implemented the per-workspace codebase indexing control feature as requested.

Implementation Summary

✅ Pull Request Created: #7512
🔗 #7512

What was implemented:

• Added workspace-specific storage support to ContextProxy
• Updated CodeIndexConfigManager to check workspace settings before global settings
• Added UI controls in the Code Index settings to enable workspace-specific overrides
• Added all necessary message handlers and types for workspace-specific settings
• Updated tests to support the new functionality

How it works:

1. Users can enable a "Override for this workspace" toggle in the Code Index settings
2. When enabled, they can control indexing for that specific workspace independently
3. Each workspace maintains its own indexing state
4. Workspace settings take precedence over global settings

CI Status:

• ✅ Unit tests (Ubuntu & Windows) - Passing
• ✅ Integration tests - Passing
• ✅ Code compilation - Passing
• ✅ Code analysis - Passing
• ⚠️ Translation check - Failed (only English translations added, other languages need updating)

The translation check failure is expected as I only added the English translations. The other language files would need to be updated by translators.

This implementation allows users with multiple VS Code windows to control GPU usage by enabling/disabling indexing per workspace as needed.

[NaccOll]

Good idea. I often clone open source projects to gain more knowledge. The global index switch makes me build a codebase index for each project, but that is not necessary. I only need to turn on the codebase index for the projects I contribute to.