Exafunction
In cascade occasionally Terminal commands freeze with no signs of recovery
Sometimes cascade will wait at a prompt forever waiting for something to happen. sometimes an empty command prompt sometimes when it encounters an unexpected command prompt.
At the command prompt the best work around I have found is to send the command -1 to the cascade powershell. At an application prompt I have found <CTRL>+C to break the prompt usually leads to the LLM seeing the application prompt and dealing with it properly.
When running terminal commands can the LLM be required to specify a timeout, and the terminal command could return a message to the LLM that the timeout was encountered, review the output and either increase the timeout or try another command.
It may be fixed now, or my rules work around it, but the cascade conversations used to ignore the command output, even when errors happened.