Installing vsCode plugin causes loss and/or erratic connection to remote SSH vsCode session.

[nmvega]

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": []
}

[nmvega]

Hello Friends:

First, thank you for this vsCode extension.

Searching first for a similar issue, this issue appears to be what I ran into this weekend:

• Occupying bandwidth when using remote SSH server #1771

I'm hoping to rejuvenate interest in this issue because, while Continue works before SSH crashes, it doesn't work for very long (with the SSHconnection crashing or vsCode constant "scanning" for something), and I'd really love to useContinuewithvsCodepointed to a remotely servedvsCodeandOllama`.

Thank you. =:)

[EthraZa]

I guess I'm having the same issue. I had to uninstall it, unfortunately.

• Using PopOS Linux 24.04 or Windows 11.
• Remote connection hangs and it's needed to manually close the window and reopen vscode,
• it happens every 10 to 20 minutes,
• does not matter if I'm typing or not.
• It started to happens by the last week of December, 24.

[Xboooo]

Yes, I have the same issue. I'm using Windows 11 locally with Ubuntu 24.10 LTS remotely, and whenever I use continue.dev, it causes my remote SSH to malfunction.

Continue - Codestral, Claude, and more v1.0.5
Remote - SSH v0.119.0

[MrDasix]

I am also having this problem with Windows 11 Localy and linux in the server using Continue 1.0.7

[Patrick-Erichsen]

Hi folks, I ran Continue via SSH for a while today on my macOS machine but was unable to repro. It seems like almost everyone here is on a Windows machine, so I believe the issue is likely isolated to Windows.

The next time anyone experiences this, mind checking the logs for anything interesting? Both our logs, and the VS Code logs, which can be accessed using the Main output (see screenshots

[EthraZa]

I'am on Linux

$ cat /etc/lsb-release
DISTRIB_ID=Pop
DISTRIB_RELEASE=24.04
DISTRIB_CODENAME=noble
DISTRIB_DESCRIPTION="Pop!_OS 24.04 LTS"

I had 4 months looking a lot at the logs searching for a reason for the freezings, changed parameters on the VSCode and SSH server and client and the only way I discovered the Continue.dev was the problem, was searching the Internet and finding this thread, and by disabling Continue I verified this was the cause.

Also, this thread have 2 Linux (including op) and 2 Windows and 1 mac, I guess the conclusion is that maybe, it does no occur on mac. But I guess it's more probable it is some kind of bad interaction between Continue and other extensions.

[Patrick-Erichsen]

😬 apologies for the rough experience. In the future you might find the built in VS Code extension bisect to be helpful when narrowing things down.

[EthraZa]

😬 apologies for the rough experience. In the future you might find the built in VS Code extension bisect to be helpful when narrowing things down.

I realise now that I may sounded rough and it is not my intention. I did not mean Continue.dev is the bad extension, I'm just thinking that it may had a bad time interacting with some other extension we have installed. I will take a look at the bisect link and if I find something helpful I came back to report.

[amritter]

Hi folks, I ran Continue via SSH for a while today on my macOS machine but was unable to repro. It seems like almost everyone here is on a Windows machine, so I believe the issue is likely isolated to Windows.

The next time anyone experiences this, mind checking the logs for anything interesting? Both our logs, and the VS Code logs, which can be accessed using the Main output (see screenshots

Hi. I also have this Issue and can contribute some Information. My local machine runs macOS 15. With Ollama running locally on my Mac. In the past I had a Windows 11 machine, I connected to via Remote SSH. Now I am running a dev container on a Debian Host via Remote SSH. In both cases I had an intermittent SSH connection. The problem seems to be worse on my new setup. Found continue vscode plugin to be the source of the issue after completely wiping my vscode installs (local and remote). When reinstalling the continue plugin the issue appeared again, so I had to uninstall.

I've installed again to check the logs. What I see is that Extension host exits regularly. But other than that I don't see any unusual or continue related logs in "Main" or anywhere else.

2025-09-04 08:47:55.002 [info] Extension host with pid 14510 exited with code: 0, signal: unknown.
2025-09-04 08:54:30.252 [info] Extension host with pid 14545 exited with code: 0, signal: unknown.
2025-09-04 08:54:31.253 [error] Extension host with pid 14545 still exists, forcefully killing it...
2025-09-04 08:54:58.640 [info] Extension host with pid 14688 exited with code: 0, signal: unknown.

Please advise, if I can provide anything else.