KoboldCpp has no automatic updater. To update, download the new file and use it instead of the old one.
- If you haven't yet, save your settings: click Save Config in the launcher. It writes a
.kcppsfile. - Click Update in the launcher, or go to the latest release. Update only opens that page in your browser.
- Download the same file you use now, for example
koboldcpp.exe. See Release files if you are unsure. - Replace the old file with the new one. On Linux and macOS, run
chmod +xon the new file. - Start it and load your settings with Load Config.
Your models are separate files and stay where they are.
Which version you have
Section titled “Which version you have”The launcher's window title shows it:
KoboldCpp v….--versionon its own prints the version and exits:Terminal ./koboldcpp --version
Why update
Section titled “Why update”New model architectures need a newer KoboldCpp. If a model fails with unknown model architecture, update first.
Your settings
Section titled “Your settings”A .kcpps config holds your launch settings. You can load it three ways:
- Load Config in the launcher
- drag the
.kcppsfile onto the exe (Windows) --config mysettings.kcppson the command line
Configs saved by older versions can keep old settings; see Config files (.kcpps).
Old file names
Section titled “Old file names”The file names changed in the past, and the old names no longer exist. If a script downloads koboldcpp_cu12.exe or a similar name, update it; see old file names.
Colab and Docker
Section titled “Colab and Docker”- Colab: the notebook downloads the latest release every time it runs.
- Docker: the image downloads the latest KoboldCpp when the container starts, unless
KCPP_DONT_UPDATE=trueis set. The image itself only changes when its Docker setup changes; when it does, get it withdocker pull koboldai/koboldcpp.
Advanced: rolling builds
Section titled “Advanced: rolling builds”Rolling builds are updated automatically and may be unstable. For stability and proper support, use the official releases.
Advanced: source builds and Termux
Section titled “Advanced: source builds and Termux”koboldcpp.sh: after pulling the new source, run./koboldcpp.sh rebuild. See Build from source.- Android (Termux): re-running the setup script does not rebuild an existing install. See Android.