We are looking into remote SSH performance.
1 Like
Is it just me or anyone else have this issue? It doesn’t let me pass any input or even ctrl+c but if I run the command myself, terminal isn’t read-only.
2 Likes
Thank you, I’ve found the reason why I couldn’t understand how to use the Agent Window.
When I open the agent window from the chat panel, there is nothing on the sidebar of the agent window. When I collapse and reopen the agent window‘side bar again, the chat list appears at this time.
I think this should be a bug.
1 Like
@Usor_Ufork which OS do you use?
@tangjun does the sidebar of Agent Window not have this button when you open it? Kindly share your screenshot.
Using M2 macOS Sequoia 15.6.1
1 Like
@Usor_Ufork we are looking into it.
1 Like
”My shell path can’t access your repo path right now”
Since 1.6, I’m repeatedly getting this when I try to get the agent to perform basic actions in the chat terminal, like Git commands and running tests. Does anybody know what’s going on?
I’m using GPT-5 High and GPT-5 Mini in agent mode.
3 Likes
@dvv101111 For emacs keybinding users, CTRL-E is mapped to move to end of line. Why does cursor keep releasing updates that overrides existing keymaps? What would it take cursor to release updates that don’t break things that are working? IntelliJ IDEA is so much better at respecting user choices with things like this.
2 Likes
Oh, thank god, I thought it was just me.
1 Like
hi @omerba @G4Q4 thank you for reporting the issue. Could you post a full separate Bug Report with more info so we can debug the issue? Create Bug Report
I like the request queuing, seems to inject at the right moment, nice.
Would enjoy this one for parallel work with other agents, should be easy:
1 Like
-
For ~24 hours the Cursor agent running in my workspace has been unable to run shell commands against the mounted project. Commands fail with errors like:
-
“my shell path can’t access your repo right now”
-
no such file or directory: /path/with/escaped/spaces (observed backslashes in the logged path)
-
This prevents the agent from running tests, checking out commits, or reading files inside the workspace.
Observed symptoms (concrete examples)
-
Agent attempts to cd into the workspace fail with no such file or directory, and the error text shows backslashes or other escaped characters in the path (e.g., Some\ Path\ With\ Spaces/…), which suggests incorrect escaping or a broken mount.
-
Git commands invoked by the agent fail because the working tree is not reachable from the agent runtime.
-
The agent was able to run once previously (so the mount was accessible before), then later attempts consistently fail with the same no such file or directory error.
Why these look like the same root problem
- Both failures (inability to cd and failing git operations) are consistent with either:
-
The agent’s workspace mount being lost or having incorrect permissions; or
-
A quoting/escaping bug that causes paths to be passed incorrectly to the shell (double-escaping or literal backslashes).
- Either way, the agent cannot access repository files or execute repo-local commands, producing identical downstream failures.
What I tried (useful debug info)
-
Ran the test wrapper and other npm scripts via the agent; the agent reported no such file or directory when trying to access workspace paths.
-
The agent produced test logs earlier (confirming it could access the repo once) and then later could not access the same paths.
-
The failing shell output includes escaped spaces/backslashes in the logged command, indicating a possible escaping problem.
1 Like
@G4Q4 thank you so much for the detailed bug report!
1 Like
No problem.
Has anyone internally noticed this bug yet? Or does it seem to be a bit of a niche edge case?
And do you think if I revert it back to 1.5, I would still encounter this bug?
I use same OS and Cursor version but can’t reproduce it, though team may have more other feedback as well.
For 1.5 if you did not have any other terminal issues you can install 1.5 and set it to release channel Default to prevent Early Access updating over it, but you will get the 1.6 release once it goes public.
Do I need to disable early access, delete Cursor then reinstall it to get back to 1.5, or is there an easier way to do it?
Yes you do need to disable Early Access in Settings > Beta > Update access, delete Cursor app (in Applications), then download 1.5 and install it. No other folders need to be changed or removed.
1 Like
You can also access any Cursor version download here: