continuedev / continuedev/continue
Installing vsCode plugin causes loss and/or erratic connection to remote SSH vsCode session.
Open
@RomneyDa is already working on this.
Since Mar 10, 2025.
ide:vscode
kind:bug
needs-triage
os:linux
- Dominant language
- TypeScript
- Stars
- 36k
- Forks
- 5.4k
- PR merge metrics
- No merged PRs in 30d
Description
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: Fedora-41 / Linux
- Continue version: v1.0.3 (release version) and v1.1.7 (pre-release version)
- IDE version: v1.98.0 (vsCode)
- Model: All models (cloud-hosted and ollama-self-hosted)
config:
{
"models": [
{
"title": "qwen2.5-coder:32b",
"model": "qwen2.5-coder:32b",
"provider": "ollama",
"apiBase": "http://192.168.0.12:11434"
},
{
"title": "qwen2.5:32b-instruct",
"model": "qwen2.5:32b-instruct",
"provider": "ollama",
"apiBase": "http://192.168.0.12:11434"
},
{
"title": "gemma2:27b",
"model": "gemma2:27b",
"provider": "ollama",
"apiBase": "http://192.168.0.12:11434"
}
],
"embeddingsProvider": {
"title": "nomic-embed-text",
"model": "nomic-embed-text",
"provider": "ollama",
"apiBase": "http://192.168.0.12:11434"
},
"tabAutocompleteModel": {
"title": "qwen2.5-coder:32b",
"model": "qwen2.5-coder:32b",
"provider": "ollama",
"apiBase": "http://192.168.0.12:11434"
},
"contextProviders": [
{
"name": "code",
"params": {}
},
{
"name": "docs",
"params": {}
},
{
"name": "diff",
"params": {}
},
{
"name": "terminal",
"params": {}
},
{
"name": "problems",
"params": {}
},
{
"name": "folder",
"params": {}
},
{
"name": "codebase",
"params": {}
}
],
"slashCommands": [
{
"name": "share",
"description": "Export the current chat session to markdown"
},
{
"name": "cmd",
"description": "Generate a shell command"
},
{
"name": "commit",
"description": "Generate a git commit message"
}
],
"data": []
}
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Assessment
This issue has not been assessed yet.