[BUG] Per-workspace codebase-indexing control from Roo is not exposed; checkbox changes global state

[Wisdawn]

Problem

Zoo Code’s Codebase Indexing popover exposes only an “Enable Codebase Indexing” checkbox. The checkbox behaves globally: disabling it while one large workspace is open also leaves indexing disabled when another unrelated workspace is opened.

There is no visible “Enable indexing for this workspace” control.

Expected behavior

Zoo should retain Roo Code’s previously implemented per-workspace indexing behavior:

• codebase indexing may remain globally available;
• individual workspace folders can enable or disable indexing independently;
• the choice persists for each folder across restarts;
• disabling indexing for one folder does not alter other folders;
• an active indexing operation can be stopped.

Roo Code implemented this in PR #11456 using folder-keyed workspace state such as:

codeIndexWorkspaceEnabled:<folder-uri>

The PR also added a visible “Enable indexing for this workspace” toggle and a global “Auto-enable indexing for new workspaces” default.

Actual behavior

In the current Zoo Code build:

1. Open workspace A.
2. Open the Codebase Indexing popover.
3. Untick “Enable Codebase Indexing.”
4. Open workspace B.
5. The checkbox remains unticked.

Re-enabling it in workspace B similarly enables it when returning to workspace A.

The control therefore appears to be bound to the global indexing feature state rather than the inherited per-folder state.

Impact

Large workspaces can begin embedding automatically even when indexing is inappropriate for that project.

In my case, opening a large repository caused nomic-embed-text through Ollama to sustain approximately 75–100% GPU activity indefinitely. I need indexing enabled for ordinary development projects but disabled for occasional work involving very large repositories or asset-heavy directories.

The only current alternatives are to:

• toggle indexing globally whenever switching workspaces;
• disable the entire Zoo Code extension for that workspace;
• exclude every file through an ignore file;
• maintain separate VS Code profiles.

None is equivalent to the per-folder control Roo already provided.

Relevant inherited implementation

Zoo’s code appears still to contain per-workspace-related handlers or state, including names such as:

toggleWorkspaceIndexing
setWorkspaceEnabled
codeIndexWorkspaceEnabled

Please verify whether the Code Index popover was accidentally connected only to the global codebaseIndexEnabled state during the Zoo transition or subsequent UI changes.

Success criteria

• The indexing popover exposes a distinct per-workspace-folder toggle.
• Disabling indexing in folder A does not disable it in folder B.
• The choice survives VS Code reloads.
• An active scan stops when the folder is disabled.
• Global indexing configuration and provider settings remain available independently.
• Multi-root workspace folders retain separate indexing states.