Cascade command issues

[grand dagger]

I've been working with this more and it seems the place where it has issues is with the dotnet commands for some reason. not sure why but hope that helps someone diagnose this

[rare edge]

Cascade sometimes running into a blackhole taht the terminal commands or git push jump into hanging hole. It just seems when everytime you close and reopen the conversation, it lost the previous memory in the same conversation but only can be picked up when you asked Cascade to record in the memory.

So, what it means, I had the issue that yesterday running the git push and checking logs successfully using the right command input, but today, as it lost memory, the Cascade/Claude 3.7 went to wrong git command, or requiring more authentication access. Hence it is hanging or timing out.

One clue I found is to find the previous commands with the successful push and then apply again or try back and forth. Sometimes, it finally finding the correct path.

[grand dagger]

thanks for the advice. my issue is a bit different. it will be working away, and like you can see in the screenshots, it runs the command, and the ouput doesn't get directed to the cascade chat, it gets directed to an external terminal window. it sees no output and then you're kinda screwed at that point. the other one is just a script it created but when it executes it, it just hangs.