can you please fix it already? i have this bug for 1 month already. People are complaining about it since April(at least). I can’t use cursor guys. How do you suppose i will continue to purchase Your Product if i can’t use it? If there is no any stalling or artifacts into console - then it’s serrialization (Request ID: 6cc79f43-094c-457c-ae13-56291aef2255
ConnectError: [internal] Serialization error in aiserver.v1.StreamUnifiedChatRequestWithTools
at vscode-file://vscode-app/h:/cursor/resources/app/out/vs/workbench/workbench.desktop.main.js:7246:383704 ). How can i not think that this is kind of artificial restriction. Just say that there is no real “unlimited auto” - that would be okay. But not these (as i feel right now) artificial limitations by bugs. You have made so great product, but these micro bugs are ruining everything. How can they exist 180+ days, i dont understand
Steps to Reproduce
just chat with agent
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Thanks for reporting this. I understand the frustration with these persistent issues.
For the serialization error in agent chat, could you please run network diagnostics?
Go to Cursor Settings → Network → Run Diagnostic
Share results
For the terminal artifacts (“qc” or ‘с’ characters appearing):
What exact actions trigger this? (specific commands, terminal usage patterns?)
Screenshots would be helpful
Does this happen in Cursor’s integrated terminal only? Or in normal terminal as well?
Also worth trying: You’re on a pre-release version (1.8.0-pre.15.patch.0). Could you test on the stable release to see if issues persist? Settings → Beta → Default
1)netDiagnostics - all is ok everywhere. Agent - [2025-10-09T08:42:35.183Z] Starting stream [2025-10-09T08:42:35.184Z] Pushing first message [2025-10-09T08:42:36.325Z] Response: ‘foo’ in 1141ms [2025-10-09T08:42:36.827Z] Pushing next message [2025-10-09T08:42:37.488Z] Response: ‘foo’ in 1163ms [2025-10-09T08:42:37.989Z] Pushing next message [2025-10-09T08:42:38.846Z] Response: ‘foo’ in 1358ms [2025-10-09T08:42:39.353Z] Pushing next message [2025-10-09T08:42:40.208Z] Response: ‘foo’ in 1362ms [2025-10-09T08:42:40.711Z] Pushing next message [2025-10-09T08:42:41.350Z] Response: ‘foo’ in 1142ms [2025-10-09T08:42:41.350Z] Result: true.
about “qc” and ‘с’ - when terminal stalls and you manually press Shift+ Cancel, or, sometimes, when agent skipping terminall comands itself. Ain’t used Cursor CLI much - but haven’t seen it there yet. At screenshot - it was ok when i skipped. after this ‘q’ - terminal went itself to the new string. But it was very ok when You made that you can’t write into agent’s terminal - so there weren’t any artifacts that prevent next agent’s execution.
