@echo off

cd /d "%~dp0.."

if exist "ai-visualizer\" if not "%1"=="hands" (

echo face: starting

start "agent face" cmd /c "cd ai-visualizer && run.bat"

)

if exist "barehands\" if not "%1"=="voice" (

echo hands: starting

start "agent hands" cmd /c "cd barehands && run.bat"

)

if exist "backtalk\" (

echo voice: starting in this window. Close it to hang up.

cd backtalk

rem Self-repair: reconcile the voice line's packages before launch

rem (fast when current; heals a half-installed environment).

rem

rem Its output is deliberately NOT hidden. This used to run quiet with

rem everything sent to nul, so a first run downloaded a few hundred

rem megabytes behind a completely blank screen. There is no way to tell

rem that apart from frozen, and people reasonably assumed the worst.

echo voice: checking packages. The FIRST run downloads a few hundred MB

echo and can take several minutes. It is not stuck.

uv sync --inexact

rem Stop HERE if the packages could not be installed. This used to fall

rem through to the launch and then blame backtalk's log for a failure

rem that happened before backtalk ever ran, sending people to a healthy

rem log file with nothing in it to find.

if errorlevel 1 (

echo.

echo The voice line's packages could not be installed, so it never

echo started. The reason is in the output above.

echo.

echo This happened during setup, BEFORE the voice ran, so there is

echo nothing about it in backtalk\logs\backtalk.log.

echo.

pause

exit /b 1

)

uv run python -m backtalk.main

rem A clean goodbye exits 0 and the window may close. An error exits

rem nonzero, and the window HOLDS so the message can be read.

if errorlevel 1 (

echo.

echo The voice line stopped with an error. The message is above.

echo The log lives in backtalk\logs\backtalk.log

pause

)

)