Auto/Composer 2.5 emitting few tokens / only thinking

My agent stopped working, both new and old, everything is absolute.
My agent stopped working, both new and old, everything is absolute. I give requests to do this or that action, he says okay, I’m doing it, and he doesn’t do anything, just keeps silent.
При этом мои кредиты списываются, мол он выдаёт мне много символов, но их нет

I encountered the same problem:

Request ID:c2531d43-7f6a-4da5-8de6-9da9fcf0f83a

Version: 3.5.17 (system setup)
VSCode Version: 1.105.1
Commit: d5b2fc092e16007956c9e5047f76097b9e626ca0
Date: 2026-05-20T02:43:31.559Z
Layout: editor
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.26200

Yes, I see the same behavior

UPD - It seems like it was fixed, but what about the loans that were spent, which in fact were not spent?

I have the same issue, all hangs. no response. New agents, new workspaces, restart the app. Nothing seems to help.

The application seems to burn tokens without responding.

Cursor Support where are you?

Burned Tokens where are they???

The problem has not been solved, it still does not work =)

Still broken for me

Every attempt to check tokens are thrown in the fire

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

What is going on?

Steps to Reproduce

In normal chat, switching the model after this situation still encounters the issue

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 3.5.17
VSCode Version: 1.105.1
Commit: d5b2fc092e16007956c9e5047f76097b9e626ca0
Date: 2026-05-20T02:43:31.559Z (1 天前)
Layout: glass
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Darwin arm64 24.6.0

For AI issues: which model did you use?

auto/compose 2.5/kimi

For AI issues: add Request ID with privacy disabled

33dc7241-8dcf-4293-8e26-42c3a6564299

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, from the screenshot I can see a chat where the agent didn’t finish the icon migration on the first try. From the report it’s not clear what the bug is. Is this a complaint about the model’s answer quality, or is there a specific error or system failure?

Can you clarify:

  1. What exactly “doesn’t work”? Do you see an error message, or does the agent just do a poor job on the task?
  2. Does this happen only in Auto mode, or with all models too Sonnet, GPT-5, etc?
  3. Please share a recent Request ID from a chat where the issue reproduced right top of the chat > Copy Request ID. The one in the report didn’t show up in the logs, so it might be a conversation ID.

From the logs, your requests over the last 24 hours ran normally, so without more details it’s hard to tell if this is a technical bug or just the model not handling the task well. If it’s the second, try Plan Mode or a stronger model Sonnet 4.6 or Opus 4.7 for complex migrations.

I agree with your viewpoint.

Yes, definitely an issue happening. Agents are not working this morning; agents provide a single response as if they are working, but then immediately stop.

Hi all,

Thanks for the reports. We’re investigating the issue.

Please share a Request ID if you have one for an affected chat – it will help us a lot!

5b95cc28-2c66-4f35-9657-da6717481392
51c8085b-6e87-4cb1-86e2-e90f00ccf4fd
cloud agents are working, but not local if that helps

2800fbe6-9094-4b0f-9626-f413d8e76d55
This problem has wasted a lot of my balance.

  1. After this request, he completely stopped working in other chats and in this one, everywhere, he doesn’t execute commands, gives a short answer and that’s it.“I’m going to do it” and it doesn’t go, it just hangs.

    Everywhere, I use everything

    It started after the request, and judging by the thread, I’m not the only one with this problem, as if the server went down.

39e22724-5cbc-4726-887d-560c08fbf9fe

2026-05-21 11:53:47.851 [error] ConnectError: [unavailable] Error

at jBe (/Applications/Cursor.app/Contents/Resources/app/extensions/cursor-always-local/dist/main.js:2:2408194)

at /Applications/Cursor.app/Contents/Resources/app/extensions/cursor-always-local/dist/main.js:2:2415798

at next (/Applications/Cursor.app/Contents/Resources/app/extensions/cursor-always-local/dist/main.js:2:2415809)

at process.processTicksAndRejections (node:internal/process/task_queues:103:5)

at async /Applications/Cursor.app/Contents/Resources/app/extensions/cursor-always-local/dist/main.js:2:2442462

at async /Applications/Cursor.app/Contents/Resources/app/extensions/cursor-always-local/dist/main.js:2:2442345

at async Object.unary (/Applications/Cursor.app/Contents/Resources/app/extensions/cursor-always-local/dist/main.js:2:2412282)

at async Object.submitLogs (/Applications/Cursor.app/Contents/Resources/app/extensions/cursor-always-local/dist/main.js:2:1154641)

Hey everyone,

Thank you for sharing these reports and Request IDs. We can see the issue in our monitoring and we are are escalating the issue.

Please check the burned credits, he actually wrote off every request, but in fact did not give an answer)

请求ID:a677d7be-ad25-4b64-9858-7d3f5f07e416