continuedev / continuedev/continue

Multi code-server share the Continue history

Open
#4,691 5 comments 1 reaction 1 assignee View on GitHub

@RomneyDa is already working on this.

Since Mar 17, 2025.

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
Relevant environment info
- OS: ubuntu
- Continue version: 1.1.9
- IDE version: code-server v4.10.1
- Model: Qwen2.5-Coder-1.5B
- config:
  
{
    "models": [
      {
        "title": "Llama CPP",
        "provider": "llama.cpp",
        "model": "Qwen2.5-Coder-1.5B",
        "apiBase": "http://10.222.24.65:8080"
      }
    ],
    "tabAutocompleteModel": {
      "title": "Llama CPP",
      "provider": "llama.cpp", 
      "model": "Qwen2.5-Coder-1.5B",
      "apiBase": "http://10.222.24.65:8080"
    },
    "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": []
  }
  
  OR link to assistant in Continue hub:
Description

In code-server client A, I try to request Continue to write a flask server in python, then I find the same request showed in another code-server client B. As the picture shows

Image

To reproduce

No response

Log output

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.