Internal error on your end

Support Bug Reports
,
1

Where does the bug appear (feature/product)?

Somewhere else…

Describe the Bug

Request ID: 1b7f2d36-c05f-4016-a885-d7630b01c59c
[internal] serialize binary: invalid int 32: 4294963248
NTe: [internal] serialize binary: invalid int 32: 4294963248
at tpf (vscode-file://vscode-app/c:/Users/joese/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9097:38348)
at Xmf (vscode-file://vscode-app/c:/Users/joese/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9097:37251)
at gpf (vscode-file://vscode-app/c:/Users/joese/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9098:5088)
at yva.run (vscode-file://vscode-app/c:/Users/joese/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9098:9098)
at async Wyt.runAgentLoop (vscode-file://vscode-app/c:/Users/joese/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34198:57104)
at async ngc.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/joese/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34247:7835)
at async ngc.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/joese/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34247:8576)
at async OTe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/joese/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9172:14624)
at async Xi (vscode-file://vscode-app/c:/Users/joese/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:32996:3808)

Steps to Reproduce

cant proceed with anything

Expected Behavior

just says your servers are expecting an unexpected error keeps occuring

Operating System

Windows 10/11

Version Information

Version: 2.4.28 (user setup)
VSCode Version: 1.105.1
Commit: f3f5cec40024283013878b50c4f9be4002e0b580
Date: 2026-02-03T00:56:18.293Z
Build Type: Stable
Release Track: Default
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.26200

Additional Information

Request ID: 13cf8daa-d4da-4fe6-888c-a2d6145cb409
[internal] serialize binary: invalid int 32: 4294963248
NTe: [internal] serialize binary: invalid int 32: 4294963248
at tpf (vscode-file://vscode-app/c:/Users/joese/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9097:38348)
at Xmf (vscode-file://vscode-app/c:/Users/joese/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9097:37251)
at gpf (vscode-file://vscode-app/c:/Users/joese/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9098:5088)
at yva.run (vscode-file://vscode-app/c:/Users/joese/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9098:9098)
at async Wyt.runAgentLoop (vscode-file://vscode-app/c:/Users/joese/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34198:57104)
at async ngc.streamFromAgentBackend (vscode-file://vscode-app/c:/Users/joese/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34247:7835)
at async ngc.getAgentStreamResponse (vscode-file://vscode-app/c:/Users/joese/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:34247:8576)
at async OTe.submitChatMaybeAbortCurrent (vscode-file://vscode-app/c:/Users/joese/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:9172:14624)
at async Xi (vscode-file://vscode-app/c:/Users/joese/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:32996:3808)

Does this stop you from using Cursor

Yes - Cursor is unusable

3

Hey, thanks for the report. This is a known issue on Windows. It happens when the Agent runs commands in the terminal and gets an incorrect exit code that can’t fit into an int32 during serialization.

Try switching from PowerShell to Command Prompt:

  • Fully close Cursor
  • Open Settings Ctrl+,
  • Find terminal.integrated.defaultProfile.windows
  • Set it to “Command Prompt” instead of PowerShell
  • Restart Cursor

Honestly, this workaround doesn’t always help, especially with long commands. If it doesn’t work, let me know.

Related threads:

4

A post was merged into an existing topic: Connection Error - Serialize Binary