continuedev / continuedev/continue

.continuerc.json not overriding config.json for Android Studio

Open
#3,892 1 comment 0 reactions 1 assignee View on GitHub

@RomneyDa is already working on this.

Since Jan 29, 2025.

area:autocomplete kind:bug needs-triage os:mac
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: Mac OS
- Continue version: 0.0.86
- IDE version: Android: AndroidStudio2024.1
- Model: _
- config.json:
Description

Expected:
I use two auto complete configs: follows:

"tabAutocompleteModel": {
    "title": "Qwen Tab Autocomplete Model",
    "model": "qwen2.5-coder:1.5b-base",
    "provider": "ollama",
    "apiBase": "https://192.168.185:11434/",
    "requestOptions": {
      "headers": {
        "verifySsl": "false"
      },
      "caBundlePath": "/Users/sid/.ssh/truenas_npm_continue_dev.pem",
      "clientCertificate": {
        "cert": "/Users/sid/.ssh/truenas_npm_continue_dev.crt",
        "key": "/Users/sid/.ssh/truenas_npm_continue_dev.key",
        "passphrase": "XXXX"
      }
    }
  }

OR

 "tabAutocompleteModel": {
    "title": "Mixtral Autocomplete Model",
    "provider": "mistral",
    "model": "codestral-latest",
    "apiKey": "XXXXX"
  },

I've tested the latest version of the plugin with VSCode version: 1.96.4 and using the latter in .continuerc.json override works as evidenced by idea's prompt logs as well as looking at my local GPU usage on my machine at vpn.itissid.me

To reproduce
  1. Open/Create a random Android Studio proeject.
  2. Create two tabAutocompleteModel configs
  3. Add one config to config.json and the other to .continuerc.json
  4. Observe prompt logs when you type.

Expected:
Prompt logs show the tab auto complete model being used is one in .continue.json
Actual:
Prompt logs show that the tab auto complete model being used is the one in config.json.

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.