Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
“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.
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.
Steps to Reproduce
Ask the agent to do something that involves the terminal and it will say "My shell path can’t access your repo path right now”
Operating System
MacOS
Current Cursor Version (Menu → About Cursor → Copy)
Version: 1.6.6 (Universal)
VSCode Version: 1.99.3
Commit: 9455eaa4c87f2bad91eda3f2bc9b42b16eae1080
Date: 2025-09-11T01:16:54.096Z (14 hrs ago)
Electron: 34.5.8
Chromium: 132.0.6834.210
Node.js: 20.19.1
V8: 13.2.152.41-electron.0
OS: Darwin arm64 24.6.0
Does this stop you from using Cursor
Yes - Cursor is unusable
