Codebase indexing error state and inability to save settings

[benzntech]

App Version

v3.25.6

API Provider

Google Gemini

Model Used

gemini-embedding-001

Roo Code Task Links (Optional)

No response

🔁 Steps to Reproduce

1. Open the Roo Code extension settings.

2. Locate the "Codebase Indexing" section. 3. Uncheck the "Enable Codebase Indexing" box.

3. Attempt to save the settings. The save action fails.

4. An error message appears stating "Error - Indexing requires an open workspace folder." and the Ul doesn't visually update to reflect that the indexing is disabled. 6. The "Status" section continues to show the same error, even when the feature is meant to be disabled.

5. The system also appears to be invoking a function related to indexing even when the feature is explicitly turned off, which is causing the error.

6. To successfully save the settings, you must first enter some random text into the "API Key" field, then uncheck the "Enable Codebase Indexing" box and then save. 9. The setting is enabled by default in new workspaces.

💥 Outcome Summary

The "Enable Codebase Indexing" checkbox, when unchecked, does not save its state correctly. The UI shows a persistent error message and doesn't visually update. The system appears to invoke a function related to indexing even when the feature is explicitly turned off. A workaround is required to save the setting, which involves entering text into another field and then unchecking the box.

📄 Relevant Logs or Errors (Optional)

Cannot save code index settings: No workspace folder open

[roomote]

Hi! I'm here to help out the maintainers and am going to see if I can fix this issue. The problem appears to be that the codebase indexing settings are not saving correctly when trying to disable the feature, especially when no workspace folder is open. I'll investigate the code and work on a fix!

[roomote]

I've created a pull request to fix this issue: #6665

The fix allows users to disable codebase indexing even when no workspace folder is open. The key changes are:

• Modified the settings save handler to allow disabling the feature without a workspace
• Updated status handlers to only show workspace-required errors when the feature is enabled
• Clear error status when the feature is disabled

The PR is currently running through CI checks.

[daniel-lxs]

Closing as duplicate of #6660