bug remote ssh VS code

[chemquantsdev]

Before submitting your bug report

• I've tried using the "Ask AI" feature on the Continue docs site to see if the docs have an answer
• I'm not able to find a related conversation on GitHub discussions that reports the same bug
• 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:
- Continue version:
- IDE version:
- Model:
- config:
  

  
  OR link to agent in Continue hub:

Description

📧 Issue Report: Remote-SSH Configuration Context Error

Subject: Critical Bug: Remote-SSH Extension Confuses Local/Remote Config Context After Agent Reinstallation

---

Hello Continue Team,

I am experiencing a critical issue when using the Continue extension in a VS Code Remote-SSH environment. The extension is failing to correctly recognize the remote workspace context and is defaulting to local settings, despite the remote agent being active.

🐛 Observed Symptoms

1. Configuration Context Error: The model selector dropdown and configuration menu in the Continue sidebar consistently show the option "local config" (instead of correctly identifying the remote workspace configuration).

2. Configuration Link Incorrect: When I click the gear icon to edit the configuration, VS Code opens the local machine's ~/.continue/config.yaml file, rather than the remote machine's ~/.vscode-server/data/VsCodeExtensions/continue.continue-1.2.10-linux-x64/... path or the remote workspace's .continue/config.yaml.

3. Specific Model Error (Now Resolved): Initial attempts to use an Anthropic model via Vertex AI in the working (internal) agent config failed with an HTTP 400 region error, which has since been mitigated by changing the region to global in the primary config.

💻 Environment Details

Component | Detail -- | -- VS Code Version | (Please specify your VS Code version, e.g., 1.94.2) Continue Extension Version | 1.2.10 (Based on logs) Host OS | (e.g., Ubuntu 22.04 LTS) Client OS | (e.g., Windows 11 / macOS) Connection Method | VS Code Remote-SSH

🛑 Troubleshooting Steps Performed (Critical)

I have performed a full, deep cleanup to eliminate local and remote caching, forcing a fresh installation. The issue persists.

1. Fixed Corrupted Index: Identified and resolved SQLITE_ERROR: no such table: chunks and Neon module: assertion left == right failed errors by manually deleting the remote cache:

   Bash

   # Run on Remote Host
   rm -rf /path/to/workspace/.continue/index
   rm -rf /path/to/workspace/.continue/agent
   

2. Reinstalled Extension Components: The issue began when I mistakenly uninstalled the local UI component, so I performed the following:

   • Uninstalled the extension locally.

   • Manually deleted the entire remote extension folder: rm -rf ~/.vscode-server/extensions/continue.continue-*

   • Reinstalled the extension locally.

   • Killed the VS Code Server (Remote-SSH: Kill VS Code Server on Host...) and reconnected.

3. Configuration Verified: The primary configuration file, .continue/config.yaml, exists and is structurally valid in the root of the remote workspace.

Conclusion: Even after a complete local and remote clean reinstall, the local UI component of the extension fails to switch context when connected via Remote-SSH and continues to look for configuration files and display settings as if it were a purely local workspace.

Please investigate the context-switching logic used by the Continue UI component when the extension host is running remotely.

Thank you for your time.

To reproduce

No response

Log output