Thanks for the clarification. Yes, the error Serialization error in aiserver.v1.StreamUnifiedChatRequestWithTools is a known bug related to an int32 overflow. The team is working on a fix.
Temporary workarounds:
- Create a new chat - after the error appears, the current chat gets “broken,” but a new chat should work
- Restart Cursor - if a new chat doesn’t help
- Avoid PowerShell pipelines with truncation (on Windows):
- Don’t use
| Select-Object -First Nwith external commands - This can cause exit code -1, which triggers the bug
- Don’t use
Related topics for the same issue:
- Serialization error
- Cursor Agent gets stuck in “Connection failed” loop after PowerShell output-truncation pipeline; local protobuf serialization fails (invalid int 32: 4294967295)
Let me know if creating a new chat helps.