Cursor not working on on auto mode

[Ofir_Rosner]

Describe the Bug

I click submit, and it starts for a second and the stops. Repeat. Repeat. Nothing happens. It says “planning next moves” and then it disappears
throws an error
[error] [Window] i.with is not a function: TypeError: i.with is not a function
at cAt.normalizePath (vscode-file://vscode-app/c:/Users/{user}/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:50:81283)
at SOs.asCanonicalUri (vscode-file://vscode-app/c:/Users/{user}/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:14765:109342)
at hdo.createModelReference (vscode-file://vscode-app/c:/Users/{user}/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:12768:31405)
at xe (vscode-file://vscode-app/c:/Users/{user}/AppData/Local/Programs/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:11815:10228) i.with is not a function
2025-12-16 12:37:37.396 [info] [Window] [Cursor Proclist] Samples written: 0 local processes, 0 remote processes

p.s1
some of the models do work on non max mode

p.s2
Changing the HTTP compatibility mode does not solves to me

p.s3
auto mode do work

Steps to Reproduce

Write anything on any mode (agent/ask/etc.)

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.20 (user setup)
VSCode Version: 1.105.1
Commit: b3573281c4775bfc6bba466bf6563d3d498d1070
Date: 2025-12-12T06:29:26.017Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

[Colin]

Hey there!

Thanks for the report. I want to make sure I understand correctly.

You mentioned “Changing the compatibility mode does solves to me” - does that mean adjusting HTTP compatibility mode resolved the issue for you and Agent mode is now working?

If so, which compatibility mode settings did you use?

If it’s still not working reliably, let us know and we can dig deeper. An essential item to share there would be the Request ID of an affected agent run.

[Ofir_Rosner]

@Colin

HTTP compatibility

was talking about HTTP compatibility and it DOES NOT solve the issues
i edited the main post