We’ve been looking into it and hoped we had improvements in the last day. Has anyone seen improved behavior?
Glad to hear it - next release will fix here
1 Like
since i deleted C:\Users****\AppData\Roaming\Cursor\User\workspaceStorage**
agents have access to the terminal and operate normally.
thus i cannot tell whether your fix is working, too.
I have to take that back: The error is returning; agent behaves weirdly around terminal calls, finally loses acces. ID 6e673f20-5920-45d3-be69-6e3000cdc6ed
Version: 2.2.8 (user setup)
VSCode Version: 1.105.1
Commit: acdb5a1ab634f13d3d9381161dcb9603f184e670
Date: 2025-12-10T07:03:58.386Z
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
1 Like
It was better this morning, but is starting to show connection errors. This is when the functionality typically starts to degrade. Request ID: c6399d34-f0ef-4f30-ba11-ee3c6724cf85
Terminal still not working!
No output, no able to edits files!
Cursor unusable!
Version: 2.1.50 (system setup)
VSCode Version: 1.105.1
Commit: 56f0a83df8e9eb48585fcc4858a9440db4cc7770
Date: 2025-12-06T23:39:52.834Z
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.26100
2 Likes
How can you say it works? I would not dare let it near my codebase if it cannot check itself (and is just guessing what the code looks like). But that’s just me, I guess.
It seems like terminal can run git commands again, but it still has a problem where it just spaces out and loops forever about 60-70% of the time on something like “git add .” You have to force a message like “continue” to snap it out of whatever it’s stuck in.
1 Like
Updated to Nightly Build.
Version: 2.2.8 (user setup)
VSCode Version: 1.105.1
Commit: acdb5a1ab634f13d3d9381161dcb9603f184e670
Date: 2025-12-10T07:03:58.386Z
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.19045
Running tests in terminal with “Legacy Terminal Tool” + Opus 4.5 is working
Running tests in termina with Opus 4.5 is not working
Running tests in termina with “Legacy Terminal Tool” + Composer 1 is working
In WSL2, the latest Cursor version uses ‘Agent-terminal’ instead of my configured terminal, and it fails to run anything. I don’t know how to set and change the agent terminal to use my terminal
1 Like
Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
For the past few days, the agent has been unable to run any terminal commands. It looks like the terminal either doesn’t execute the commands at all or exits immediately with code 0, without showing any output. This issue makes Cursor practically unusable for me.
I was able to temporarily resolve it by installing an older version, but Cursor keeps auto-updating to the latest version, which brings the problem back.
Steps to Reproduce
Try to run anew PowerShell Command and ask Curser what the output of the command was. Totally blind.
Expected Behavior
The agent should be able to run terminal commands and read the output.
Operating System
Windows 10/11
Current Cursor Version (Menu → About Cursor → Copy)
Version: 2.1.50 (user setup)
VSCode Version: 1.105.1
Commit: 56f0a83df8e9eb48585fcc4858a9440db4cc7770
Date: 2025-12-06T23:39:52.834Z
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
Yes - Cursor is unusable
2 Likes
is this still not fixed???
Hey all, we fixed an instance of this but it appears that some people are still hitting a variant of it. For anyone hitting the “Agent can’t run terminal commands” (not “Agent sometimes stops abruptly”, that is a separate Thing):
- What terminal are you using?
- Do you have the “Legacy Terminals” switch set?
- Please go to the “Output” pane (next to Terminal) and select “Extension Host” - is there anything Interesting in there?
1 Like
Any chance you or the team can ask Open AI to extend the free trial of Codex Max by a week seeing that Cursor was unusable for all but 1 day before it ends for Windows users?
still experiencing the issue ;
Version: 2.2.14
VSCode Version: 1.105.1
Commit: 1685afce45886aa5579025ac7e077fc3d4369c50
Date: 2025-12-11T01:12:35.790Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.1.0
activationEvent: ‘onLanguage:jsonc’
2025-12-10 22:54:25.468 [info] ExtensionService#_doActivateExtension vscode.grunt, startup: false, activationEvent: ‘onTaskType:grunt’
2025-12-10 22:54:25.471 [info] ExtensionService#_doActivateExtension vscode.gulp, startup: false, activationEvent: ‘onTaskType:gulp’
2025-12-10 22:54:25.472 [info] ExtensionService#_doActivateExtension vscode.jake, startup: false, activationEvent: ‘onTaskType:jake’
2025-12-10 22:55:04.940 [info] ExtensionService#_doActivateExtension ms-vscode.js-debug, startup: false, activationEvent: ‘onDebugInitialConfigurations’
2025-12-10 22:55:05.001 [info] ExtensionService#_doActivateExtension ms-python.python, startup: false, activationEvent: ‘onDebugInitialConfigurations’, root cause: ms-python.debugpy
2025-12-10 22:55:05.363 [info] ExtensionService#_doActivateExtension ms-python.debugpy, startup: false, activationEvent: ‘onDebugInitialConfigurations’
1 Like
after being able to interact with the terminal for a couple of turns, the agent then gets stuck interacting with the terminal.
ReqID: fbbdb1b5-8b5b-4639-878b-cfb9f43210ae
Version: 2.2.14 (user setup)
VSCode Version: 1.105.1
Commit: 1685afce45886aa5579025ac7e077fc3d4369c50
Date: 2025-12-11T01:12:35.790Z
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
keep getting this in the dev tools console:
[transport] Connect error in unary AI connect ConnectError: [invalid_argument] Error
at t (workbench.desktop.main.js:12095:457498)
at async Object.getBackgroundComposerChangesHash (workbench.desktop.main.js:585:93853)
at async workbench.desktop.main.js:14762:29769
at async lMo._fetchOptimizedDiffDetailsAndUpdateImpl (workbench.desktop.main.js:14762:30651) {arch: ‘x64’, platform: ‘win32’, channel: ‘stable’, client_version: ‘2.2.14’, service: ‘aiserver.v1.BackgroundComposerService’, …}arch: "x64"causeCode: undefinedcauseErrno: undefinedcauseSyscall: undefinedchannel: "stable"client_version: "2.2.14"code: 3errorDetails: Array(1)0: debug: details: {title: ‘Bad request.’, detail: ‘Cloud Agent has expired’, isRetryable: false}error: "ERROR_BAD_REQUEST"isExpected: true[[Prototype]]: Objectconstructor: ƒ Object()hasOwnProperty: ƒ hasOwnProperty()isPrototypeOf: ƒ isPrototypeOf()propertyIsEnumerable: ƒ propertyIsEnumerable()toLocaleString: ƒ toLocaleString()toString: ƒ toString()valueOf: ƒ valueOf()defineGetter: ƒ defineGetter()defineSetter: ƒ defineSetter()lookupGetter: ƒ lookupGetter()lookupSetter: ƒ lookupSetter()proto: (…)get proto: ƒ proto()set proto: ƒ proto()type: "aiserver.v1.ErrorDetails"value: Uint8Array(47) [8, 36, 18, 41, 10, 12, 66, 97, 100, 32, 114, 101, 113, 117, 101, 115, 116, 46, 18, 23, 67, 108, 111, 117, 100, 32, 65, 103, 101, 110, 116, 32, 104, 97, 115, 32, 101, 120, 112, 105, 114, 101, 100, 32, 0, 24, 1, buffer: ArrayBuffer(47), byteLength: 47, byteOffset: 0, length: 47, Symbol(Symbol.toStringTag): ‘Uint8Array’]0: 81: 362: 183: 414: 105: 126: 667: 978: 1009: 3210: 11411: 10112: 11313: 11714: 10115: 11516: 11617: 4618: 1819: 2320: 6721: 10822: 11123: 11724: 10025: 3226: 6527: 10328: 10129: 11030: 11631: 3232: 10433: 9734: 11535: 3236: 10137: 12038: 11239: 10540: 11441: 10142: 10043: 3244: 045: 2446: 1buffer: ArrayBuffer(47)byteLength: 47byteOffset: 0length: 47Symbol(Symbol.toStringTag): “Uint8Array”[[Prototype]]: TypedArray[[Prototype]]: Objectlength: 1[[Prototype]]: Array(0)at: ƒ at()concat: ƒ concat()constructor: ƒ Array()copyWithin: ƒ copyWithin()entries: ƒ entries()every: ƒ every()fill: ƒ fill()filter: ƒ filter()find: ƒ find()findIndex: ƒ findIndex()findLast: ƒ findLast()findLastIndex: ƒ findLastIndex()flat: ƒ flat()flatMap: ƒ flatMap()forEach: ƒ forEach()includes: ƒ includes()indexOf: ƒ indexOf()join: ƒ join()keys: ƒ keys()lastIndexOf: ƒ lastIndexOf()length: 0map: ƒ map()pop: ƒ pop()push: ƒ push()reduce: ƒ reduce()reduceRight: ƒ reduceRight()reverse: ƒ reverse()shift: ƒ shift()slice: ƒ slice()some: ƒ some()sort: ƒ sort()splice: ƒ splice()toLocaleString: ƒ toLocaleString()toReversed: ƒ toReversed()toSorted: ƒ toSorted()toSpliced: ƒ toSpliced()toString: ƒ toString()unshift: ƒ unshift()values: ƒ values()with: ƒ with()Symbol(Symbol.iterator): ƒ values()Symbol(Symbol.unscopables): {at: true, copyWithin: true, entries: true, fill: true, find: true, …}[[Prototype]]: ObjecterrorDetailsDebug: "{“error”:“ERROR_BAD_REQUEST”,“details”:{“title”:“Bad request.”,“detail”:“Cloud Agent has expired”,“isRetryable”:false},“isExpected”:true}"errorMessage: undefinederrorName: "ConnectError"method: "GetBackgroundComposerChangesHash"platform: "win32"requestId: "not-found"service: "aiserver.v1.BackgroundComposerService"timeoutMs: “undefined”[[Prototype]]: Object
This is what a codex max extry high agent is making out of this dump:
*The stack trace is coming from Cursor’s cloud side (BackgroundComposerService) and it says the “Cloud Agent has expired,” which usually means the remote agent session Cursor spins up for background diff/composer work aged out (TTL) or was killed after idle/resume/network drop. Nothing in your repo caused it.
Quick fixes to try:
-
Sign out and back into Cursor, then re-run the action (forces a fresh cloud agent).
-
Reload Cursor (Developer: Reload Window) or fully restart the app.
-
If available, run the command palette action to restart the cloud/background agent.
-
Update Cursor to the latest build (you’re on 2.2.14 stable) and retry; also check Cursor status for any backend incident.
-
If on a flaky network/VPN, reconnect and try again.*
December 12, 2025 – can I upgrade to the latest Cursor and have Agent work now?
1 Like
same question
1 Like
Would be nice to have some communications to let us know if this is fixed in the latest releases. Keep getting prompted to update and have seen lots of fanfare about 2.2 - but no word on this bug. Can I update? Has it been fixed? Should I risk it? Who knows.