Unable to use Jetbrains gateway.

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: host: Ubuntu 24.04, client: Windows 11
- Continue version: v0.0.86
- IDE version: Jetbrains IntelliJ 2024.3.1
- Model: Claude Sonnet 3.5

Description

When I open a project through Jetbrains gateway, I can't get the file list in Continue.

To reproduce

1. Install continue plugin in host.
2. Install continue plugin in client.

Log output

...
[info] Starting Continue core...
[2025-01-28T03:31:27] [info] Starting Continue core... 
[2025-01-28T03:31:27] Setup 
[2025-01-28T03:31:27] [binary] Core started 
[2025-01-28T03:31:28] (node:64460) ExperimentalWarning: The Fetch API is an experimental feature. This feature could change at any time
(Use `continue-binary --trace-warnings ...` to show where the warning was created) 
[2025-01-28T03:31:35] error when indexing:  Error: Failed to generate embeddings for 401 chunks with provider: A::all-MiniLM-L6-v2::500: Error: `local_files_only=true` or `env.allowRemoteModels=false` and file was not found locally at "C:\snapshot\continue\binary\models/all-MiniLM-L6-v2/tokenizer.json".
[2025-01-28T03:31:35] Indexing failed with error:  Error: Failed to generate embeddings for 401 chunks with provider: A::all-MiniLM-L6-v2::500: Error: `local_files_only=true` or `env.allowRemoteModels=false` and file was not found locally at "C:\snapshot\continue\binary\models/all-MiniLM-L6-v2/tokenizer.json". j0e.getEmbeddings, async j0e.computeRows, async j0e.update, async cGA.indexFiles, async cGA.refreshDirs, async hGA.refreshCodebaseIndex
[info] Starting Continue core...
[2025-01-28T06:31:37] [info] Starting Continue core... 
[2025-01-28T06:31:37] Setup 
[2025-01-28T06:31:37] [binary] Core started 
[2025-01-28T06:31:37] (node:69712) ExperimentalWarning: The Fetch API is an experimental feature. This feature could change at any time
(Use `continue-binary --trace-warnings ...` to show where the warning was created)