Common issues

Common issues

This section highlights frequent challenges, errors, or obstacles you may encounter while using the Code Companion.

Keyboard shortcuts not resolving

If your keyboard shortcuts are not resolving, you may have other commands that are taking precedence over Code Companion shortcuts. You can see if this is the case, and change your shortcut mappings, in the configuration of your IDE.

• VSCode keyboard shortcuts docs
• JetBrains keyboard shortcut docs

Will Code Companion work on a remote SSH configuration or with my WSL?

Yes. Make sure the remote machine whitelists the following endpoints over port 443:

https://api.genai-pltfmc2-prod.eu3.k8saas.thalesdigital.io
wss://api.genai-pltfmc2-prod.eu3.k8saas.thalesdigital.io
https://genai-platform.azure-api.net
https://login.microsoftonline.com

If your firewall requires IP allowlisting, ensure these IP addresses are accessible over port 443:

98.64.59.203
98.64.16.231

If your remote SSH server or your WSL does not have access to these endpoints, you can use a workaround to execute your Code Companion extension on your host computer:

Add the following to your settings.json file:

"remote.extensionKind": {
    "thalesgroup.continue": ["ui"]
}

I installed Code Companion, but don’t see the sidebar window

By default the window is on the left side of VS Code, but it can be dragged to right side as well, which we recommend in our tutorial. In the situation where you have previously installed Code Companion and moved it to the right side, it may still be there. You can reveal Code Companion either by using cmd/ctrl+L or by selecting the button in the top right of VSCode to open the right sidebar.

Indexing issues

If you are having persistent errors with indexing, our recommendation is to rebuild your index from scratch. Note that for large codebases this may take some time.

This can be accomplished using the following command: Continue: Rebuild codebase index.

I received a “Codebase indexing disabled - Your Linux system …” notification

We use LanceDB as our vector database for codebase search features. On x64 Linux systems, LanceDB requires specific CPU features (FMA and AVX2) which may not be available on older processors.

Most features will work normally, including autocomplete and chat. However, commands that rely on codebase indexing, such as @codebase, @files, and @folder, will be disabled.

For more details about this requirement, see the LanceDB issue #2195 .

How do I reset the state of the extension?

The extension stores it’s data in the ~/.continue directory (%USERPROFILE%.continue` on Windows).

If you’d like to perform a clean reset of the extension, including removing all configuration files, indices, etc, you can remove this directory, uninstall, and then reinstall.

Request approval needed at sign in

Sometimes when signing in a request for approval needs to be sent. This is an error and should not happen.

To overcome this problem, you need to clear your browser’s cache and cookies:

• Chrome users
• Edge users

Code Companion doesn’t load my models

If models, context providers or any custom settings aren’t behaving as expected, it is most likely due to incorrect or outdated configuration arguments in the ~/.continue/config.json directory.

We recommend seeing this page for instructions on how to migrate your configuration settings to the newest format.

Or making a complete reset of your configuration file may also resolve the issue.

I’m having troubles using Code Companion under WSL

On JetBrains

Many issues usually come from IntelliJ’s handling of WSL paths, specifically due to how the WSL environment is launched from within the IDE.

To resolve the issue, in the IntelliJ menu, close your current project and then open it by typing the following path in the Windows File Explorer popup:

\\wsl$\your_wsl_name\your_folder_path

instead of:

\\wsl.localhost\your_wsl_name\your_folder_path

This ensures IntelliJ correctly maps the WSL file system.

Why do I see a C1 banner when using code companion?

There’s a few reasons you may see a C1 data classification banner when using code companion:

1. You have unknown models configured

   • If you configured local models or tried to use any mix of already available models + your own local models.

   • Code companion will, by default, only show a higher security level than C1 when the models used are the ones provided by TDP.

2. You have an issue when loading models

   • If you’ve been modifiyng your config files (.YAML or .JSON) to add models or other, double-check for typos or unsupported syntax, otherwise, remove the whole .continue directory to force a clean reset of your configuration, see this section and/or the config documentation for more details.