Troubleshooting

Jolt doesn't see my repo

If Jolt cannot detect your git repository, or if you encounter issues with git operations, here are some troubleshooting steps:

Changing your git remote URL (origin)

If your repository's URL changes (e.g., it's renamed, moved to a different organization, or migrated to a new Git hosting service), update the remote URL in your local Git repository. This ensures that git pull, git push, and other remote operations point to the correct location.

This is particularly important if Jolt is interacting with your repository via local Git operations, as an outdated remote URL can lead to errors.

To update your origin remote (the typical default name for your primary remote repository), open your terminal or command prompt in your local repository directory and use the following command:

git remote set-url origin NEW_GIT_URL

Replace NEW_GIT_URL with the new HTTPS or SSH URL of your repository. For example: git remote set-url origin git@github.com:new-organization/new-repo-name.git

You can verify that the URL has been updated by running:

git remote -v

Check that the output shows the new URL for origin.

Git SSH aliasing

If you're using SSH aliases in your Git configuration (typically defined in ~/.ssh/config), Jolt may not be able to resolve repository URLs that use these aliases. SSH aliases allow you to use custom hostnames for Git operations, but Jolt needs to understand how these aliases map to Git hosting services.

On the welcome screen in the desktop app or IDE extensions, you can add git SSH aliases to the Jolt configuration. Once added you will be prompted to restart the Jolt extension to apply the changes.

Windows Subsystem for Linux (WSL)

If you are using Jolt with Windows Subsystem for Linux (WSL), there are a few important considerations to ensure it works correctly:

Visual Studio Code

Jolt works best with the latest version of the WSL remote extension from Microsoft. If you have problems detecting a git repo, ensure Jolt is running as a WSL extension so that Jolt can access your local codebase.

"remote.extensionKind": {
  "jolt.bridge": ["workspace"]
},

JetBrains IDEs

If you are using a JetBrains IDE (like IntelliJ IDEA, WebStorm, PyCharm, etc.) with WSL, you will need to access the repository folder via a mapped network drive or a network path. Network paths for WSL typically start with \\wsl$\ (for accessing the WSL distribution's file system from Windows) or //wsl$/ (sometimes used within WSL or for certain tools).

For example, if your WSL distribution is named 'Ubuntu' and your project is in your WSL user's home directory at ~/my-project, the Windows path would be \\wsl$\Ubuntu\home\your_wsl_username\my-project.

Open your project in the JetBrains IDE by:

1. Using the File > Open menu.
2. Navigating to the WSL path (e.g., by typing \\wsl$\ into the address bar of the file dialog).
3. Selecting your project folder.

Alternatively, you can map the WSL path to a network drive in Windows and then open it from the IDE using the mapped drive letter.

General

Prerequisites

Jolt requires the following minimum versions of git and node to be installed on your system when using the IDE extensions, plugins, or Jolt desktop:

• Git 2.20+: Download Git from git-scm.com.
• Node.js 20+: Download Node.js from nodejs.org.

Update not appearing in Cursor or Windsurf

IDEs forked from VSCode, like Cursor and Windsurf, have a known issue where their marketplaces lag behind the official VSCode marketplace. New versions of Jolt may take time to appear. Follow the steps outlined here to get the latest version of our extension.

Switching teams or organizations

If you need to switch between teams, move to a different organization, or resolve team-related access issues, contact support at support@usejolt.ai for assistance.