Serialize binary :invalid int 32:3212222

Support Bug Reports
,
3

Hey, thanks for the report. This is a known Windows issue related to how PowerShell returns exit codes. Your error shows a different number (3221225477 instead of the usual 4294967295), but the root cause is the same: int32 overflow during serialization.

Try switching to Command Prompt:

  1. Fully close Cursor
  2. Open Settings with Ctrl+,
  3. Find terminal.integrated.defaultProfile.windows
  4. Set it to “Command Prompt” instead of PowerShell
  5. Restart Cursor

This workaround doesn’t always help (especially with long commands), but it’s worth trying.

If it doesn’t help, please share:

  • Your Cursor version (Menu → About Cursor → Copy)
  • What command the Agent tried to run right before the error

The bug is logged and lots of users have hit it. Main thread with updates: Connection Error - Serialize Binary. You can subscribe there to follow the news.