executing-plans
executing-plans
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available
setupInstall, verify, configure, and launch the local speech-to-text server.
Independent GitHub snapshot · Automated classification · Original documentation governs
Use this sub-skill when the user needs to prepare a local checkout for first launch or recovery: create the environment, install runtime dependencies, verify ffmpeg/ffprobe, place or download models, choose CPU vs CUDA, interpret set.ini, and start the server safely.
/api or /v1/audio/transcriptions request detailsFor those topics, use transcription. For shared launch failures and broader runtime issues, use the root troubleshooting guide.
ffmpeg / ffprobe checksmodels/ layout and model download expectationsset.ini startup keys and device selectionreferences/install-and-launch.mdreferences/configuration.mdreferences/troubleshooting.md../../scripts/check-runtime.pyscripts/check-cuda.pyscripts/launch-server.pyreferences/install-and-launch.md for the normal install and launch path.references/configuration.md when the user asks about set.ini, model selection, or CPU/CUDA toggles.../../scripts/check-runtime.py --repo-root <checkout> before launch.scripts/check-cuda.py only when CUDA is expected or needs diagnosis.scripts/launch-server.py --repo-root <checkout> to start the app from the current checkout.references/troubleshooting.md, then hand off to transcription only after the server is reachable.start.py launches a Flask + gevent server, starts a background update check and transcription worker, and opens the browser automatically.WhisperModel(device=sets.get('devtype'), download_root=<project>/models) and does not pass temperature or cuda_com_type into WhisperModel.temperature, while devtype still selects CPU vs CUDA.set.ini exposes cuda_com_type, but the current observed runtime path does not consume it during model creation.