Saw a claim floating around that backtalk on Windows keeps the console/error window open on a startup failure so it's readable, rather than the window closing immediately. I went looking through main.py and ears.py for this and couldn't find a general mechanism for it -- the closest thing I found is update.bat's pause at the end, but that script is now a deprecated no-op that just tells you to ask your agent to update instead.
Is the "hold the window open on error" behavior real and intentional somewhere in the Windows launch path (maybe in how the setup wizard invokes things), or is this actually just default Windows Terminal/PowerShell behavior getting attributed to backtalk? Want to make sure I'm not missing something in the wizard-driven install path since I only checked the tracked source files.
Saw a claim floating around that backtalk on Windows keeps the console/error window open on a startup failure so it's readable, rather than the window closing immediately. I went looking through
main.pyandears.pyfor this and couldn't find a general mechanism for it -- the closest thing I found isupdate.bat'spauseat the end, but that script is now a deprecated no-op that just tells you to ask your agent to update instead.Is the "hold the window open on error" behavior real and intentional somewhere in the Windows launch path (maybe in how the setup wizard invokes things), or is this actually just default Windows Terminal/PowerShell behavior getting attributed to backtalk? Want to make sure I'm not missing something in the wizard-driven install path since I only checked the tracked source files.