Post-execution delay where agent remains in “running command” state after output is already returned

@Leland_Hepworth, glad the sleep issue is gone.

About the agent using PowerShell commands when cmd is the default terminal, that’s a known bug. The agent doesn’t always correctly detect which shell is active, so it may send PowerShell commands.

As a temporary workaround, you can add something like this to your project-level .cursor/rules:

When running terminal commands, always use cmd.exe syntax, not PowerShell. The default shell is Command Prompt.

This won’t guarantee a 100% fix, but it should reduce the number of wrong PowerShell calls.

Thanks for the link to the sleep thread, it’s helpful for tracking.