[GH-ISSUE #124] Support unpacked KoboldCpp in custom shortcut / updater #66

Open
opened 2026-10-15 18:06:41 +00:00 by bsakaguchi · 0 comments
Owner

Originally created by @playful1510 on GitHub (Jan 1, 2026).
Original GitHub issue: https://github.com/SillyTavern/SillyTavern-Launcher/issues/124

Have you searched for similar requests?

Yes

I like that ST can update Kobold, but I also like to unpack Kobold to a folder to decrease boot time. When I update Kobold using ST-Launcher, it only updates the .exe file, leaving the unpacked filed alone. Also, when using the :start_koboldcpp custom shortcut, it only launches the kobold exe and not the unpacked launcher.

Describe the solution you'd like

I would imagine it's possible to fetch the newest kobold exe to a temp folder, and then run it with the '--unpack' command to output to the dev-koboldcpp folder. This would unpack only the -launcher exe, but if the packed exe would be needed/wanted, that could be moved to the dev-koboldcpp folder afterwards. When removing the koboldcpp.exe as part of the update process, an error will be thrown if the folder isn't cleared before unpacking, hence the need to use a temp folder.

Describe alternatives you've considered

No response

Additional context

No response

Priority

Low (Nice-to-have)

Is this something you would be keen to implement?

Maybe

Originally created by @playful1510 on GitHub (Jan 1, 2026). Original GitHub issue: https://github.com/SillyTavern/SillyTavern-Launcher/issues/124 ### Have you searched for similar requests? Yes ### Is your feature request related to a problem? If so, please describe. I like that ST can update Kobold, but I also like to unpack Kobold to a folder to decrease boot time. When I update Kobold using ST-Launcher, it only updates the .exe file, leaving the unpacked filed alone. Also, when using the :start_koboldcpp custom shortcut, it only launches the kobold exe and not the unpacked launcher. ### Describe the solution you'd like I would imagine it's possible to fetch the newest kobold exe to a temp folder, and then run it with the '--unpack' command to output to the dev-koboldcpp folder. This would unpack only the -launcher exe, but if the packed exe would be needed/wanted, that could be moved to the dev-koboldcpp folder afterwards. When removing the koboldcpp.exe as part of the update process, an error will be thrown if the folder isn't cleared before unpacking, hence the need to use a temp folder. ### Describe alternatives you've considered _No response_ ### Additional context _No response_ ### Priority Low (Nice-to-have) ### Is this something you would be keen to implement? Maybe
Sign in to join this conversation.
No description provided.