wrong coding for Chinese on Windows11

Before submitting your bug report

• I've tried finding an answer on the Continue docs site
• 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: Windows11 LTSC
- Continue version: 2.0.0
- IDE version: 1.136.1
- Model: ollama qwen3:8B
- config:
  
name: 本地 Ollama 配置
version: 1.0.0

models:
  # 主力对话模型
  - name: Qwen3 8B
    provider: ollama
    model: qwen3:8b
    apiBase: http://localhost:11434
    roles:
      - chat
      - edit
      - apply

  # 代码自动补全
  - name: Qwen3 8B (Autocomplete)
    provider: ollama
    model: qwen3:8b
    apiBase: http://localhost:11434
    roles:
      - autocomplete

# 嵌入模型（代码库索引，可选）
embeddingsProvider:
  provider: ollama
  model: nomic-embed-text
  apiBase: http://localhost:11434

tabAutocompleteModel:
  name: Qwen3 8B (Autocomplete)
  provider: ollama
  model: qwen3:8b
  apiBase: http://localhost:11434

contextProviders:
  - name: code
  - name: docs
  - name: diff
  - name: terminal
  - name: problems
  - name: folder
  - name: codebase

slashCommands:
  - name: edit
    description: 编辑选中代码
  - name: comment
    description: 添加代码注释
  - name: test
    description: 生成测试用例
  - name: commit
    description: 生成 Git commit 信息
  
  OR link to agent in Continue hub:

Description

The path is displayed as c%3A instead of C: This is essentially a bug in the Continue utility's URI path over-encoding on Windows, causing @file to fail to read the Continue configuration file, and the model cannot read the file.

To reproduce

No response

Log output

No source file or test is named. Start by reproducing the @file configuration lookup on Windows 11 with the supplied Continue, IDE, and Ollama setup, then trace where the URI path becomes c%3A instead of C:. Done means the configuration file opens correctly through @file and the Windows drive path is not over-encoded.