[GH-ISSUE #212] start_command error when launching SillyTavern + Extra on Windows #132

New issue

Closed

opened 2026-10-15 18:04:50 +00:00 by bsakaguchi · 0 comments

bsakaguchi commented

2026-10-15 18:04:50 +00:00

Owner

Originally created by @Greanibak on GitHub (Dec 29, 2023).
Original GitHub issue: https://github.com/SillyTavern/SillyTavern-Extras/issues/212

Hello guys,

With SillyTavern 1.11.1 'release' (736223a8), I encountered a bug when launching SillyTavern Extras using launcher.bat, specifically with command 3. The CMD window would open but then end with an error related to the start_command not being defined. I noticed that the SillyTavern launcher.bat was sourcing the modules.txt not from the "SillyTavern-extras" folder but from the SillyTavern root folder. Moreover, even the modules.txt in the SillyTavern folder doesn't seem to work on Windows, as it lacks the "start_command" at the beginning, as well as the server.py. The parsing intended by the code doesn't seem to function.

I resolved this on my end by editing the modules.txt file in the root folder and adding the complete API server launch command with the start_command:
start_command=python server.py --enable-modules=chromadb --listen (in my case, I only want listen and chromadb).

Did I miss something on my end, or is this a problem encountered by others as well? Thank you.

Originally created by @Greanibak on GitHub (Dec 29, 2023). Original GitHub issue: https://github.com/SillyTavern/SillyTavern-Extras/issues/212 Hello guys, With SillyTavern 1.11.1 'release' (736223a8), I encountered a bug when launching SillyTavern Extras using launcher.bat, specifically with command 3. The CMD window would open but then end with an error related to the start_command not being defined. I noticed that the SillyTavern launcher.bat was sourcing the modules.txt not from the "SillyTavern-extras" folder but from the SillyTavern root folder. Moreover, even the modules.txt in the SillyTavern folder doesn't seem to work on Windows, as it lacks the "start_command" at the beginning, as well as the server.py. The parsing intended by the code doesn't seem to function. I resolved this on my end by editing the modules.txt file in the root folder and adding the complete API server launch command with the start_command: start_command=python server.py --enable-modules=chromadb --listen (in my case, I only want listen and chromadb). Did I miss something on my end, or is this a problem encountered by others as well? Thank you.

bsakaguchi closed this issue

2026-10-15 18:04:50 +00:00