Looking at the logs, this appears to be a network connectivity issue rather than a bug in Cursor itself. Your requests are successfully reaching Cursor servers, but the connection is being interrupted before the response completes.
Next time this happens to you, could you try running Network Diagnostics a few times to see if there’s an error that appears?
I’ve gotten to the point where I can consistently reproduce this when a command with a lot of output is piped to Select-Object -First 50. This happens in the final command run related to your Request ID before the agent crashes. I’ve reported this as a bug.
As a workaround, you can try manually editing the command to remove 2>&1 | Select-Object -First 50, but this isn’t a great fix.