VSC WSL Agents Unable to Access Index and WSL - No Output Logs And Others

[Sh3rfire]

Before submitting your bug report

• I believe this is a bug. I'll try to join the Continue Discord for questions
• I'm not able to find an open issue that reports the same bug
• I've seen the troubleshooting guide on the Continue Docs

Relevant environment info

- OS: Windows 10
- Continue version:0.8.66
- IDE version:
- Model:
- config.json:

Description

Environment

• VSCode running in WSL
• Windows 10/11 [please specify]
• Continue.dev version: 0.8.66
• WSL: Ubuntu [22.04]

Core Issues

1. Competing Processes

   • Continue.dev seems to run separate processes in Windows and WSL
   • Results in file locking issues and configuration conflicts
   • Get "EBUSY: resource busy or locked" errors when trying to access index.sqlite
   • Although indexing completes, claude is unable to access the indexed files
   • Missing continue options in right click menu

2. Configuration Path Conflicts

   • Config button routes to Windows path even when running in WSL
   • Setting CONTINUE_CONFIG_PATH and CONTINUE_INDEX_PATH doesn't resolve
   • The workaround from Windows WSL, File hyperlinks in search results not opening files #2253 (setting remote.extensionKind) only partially works

3. Inconsistent Functionality

   • No logging output in either environment
   • Files don't show as indexed
   • Right-click context menu options missing
   • Features work inconsistently between Windows/WSL environments

Attempted Solutions

1. Environment Variables:

   CONTINUE_CONFIG_PATH="/home/turbo/projects/CopyBot/.continue/config.json"
   CONTINUE_INDEX_PATH="/home/turbo/projects/CopyBot/.continue/index"

2. VSCode Settings:

   {
     "remote.extensionKind": {
       "Continue.continue": [
         "workspace"
       ]
     },
     "continue.enableDebugLogs": true
   }

3. Installation Combinations:

   • WSL-only installation
   • Windows-only installation
   • Both installations
   • Complete uninstall/reinstall cycles
   • Clearing all configuration and starting fresh

Expected Behavior

• Continue.dev should work consistently in WSL environment
• Configuration and indexing should respect WSL paths
• Features should work consistently regardless of installation location
• Clear logging and debugging capabilities

Actual Behavior

• Competing processes between Windows/WSL
• File locking issues
• Inconsistent functionality
• No logging output
• Configuration path conflicts

Impact

• Unable to use Continue.dev effectively in WSL environment
• Significant time spent troubleshooting (approximately 50 hours)
• Basic functionality compromised

Additional Context

[Any other specific details about your setup or attempts]

Questions for the Team

1. Is the dual-process behavior (Windows/WSL) intended?
2. What's the recommended setup for WSL users?
3. How should logging and indexing work in WSL environment?

Would the team consider adding specific WSL installation and configuration documentation?

To reproduce

Install wsl extension. Install continue extension. Run index.

Log output

I am not generating any output logs.