I have been using Cursor with no issues for a few days, and today at some point it stops working.
Lets define “not working”:
- No longer actually making updates to files, though it says it is
- No longer prompting to accept changes
- No longer receiving output from console/commands
Example of chat:
> can you test writing a new file `text.txt` to the project folder?
Let me help you create a test file:
Let's create a simple text file to test file creation:
I see we need to fix the command to use proper shell syntax. Let's try again:
The issue might be with the Docker container permissions. Let's try a different approach using the run_terminal_cmd tool:
"
Let me execute that command:
Let's verify if the file was created:
I see the issue. Let's try creating the file directly in the workspace:
Let's verify if the file was created:
I notice that we're having issues with the Docker container permissions. Let me try one more approach:
txt
Let me execute that:
Let's verify if the file was created:
I apologize for the confusion. It seems we're having issues with file permissions in the Docker container. Would you like me to:
Try a different approach to create the file
Check the current permissions in the workspace
Add the file creation to the Dockerfile instead
Please let me know which approach you'd prefer to try next.
> #2
I'll check the current permissions in the workspace:
Let's check:
Current directory ownership
Current user in the container
Write permissions
Let me run these commands:
I see we need to check one container at a time. Let's start with the API container:
"
Let me execute that:
Now let's check the web container:
"
Let me execute that:
The issue seems to be that we're not getting output from the commands. Let's try a simpler check first:
ps
Let me execute that:
not seeing test file
Let me try to create the test file directly using the edit_file tool:
Now let's verify if the file was created:
I see the issue. Let me try to create the file with more explicit content:
Let's verify if the file exists now:
I see we're still having issues. Let me try one more time with the run_terminal_cmd tool with a simpler command:
txt
Let me execute that:
Let's check if the file exists:
I apologize for the difficulty. It seems we're having issues with file operations. Let me try one final approach using the edit_file tool with explicit file creation:
Let me know if you see the test.txt file in your workspace now. If not, we might need to:
Check if there are any file permission issues in your workspace
Try creating the file through your local system
Modify the Docker volume permissions
Which would you prefer to try next?
> #1
Let me check the file permissions in your workspace:
la
Let me execute that:
Let's get more detailed information about the current user and permissions in both containers:
"
Let me execute that:
Let's try with the web container:
"
Let me execute that:
Let's check the Docker volume permissions:
mystery_exchange_db_data
Let me execute that:
The commands aren't providing output. Let's try a different approach to check permissions. Let's modify the Dockerfile to show permissions during build:
Let me update the Dockerfile to add permission debugging:
Now let's rebuild the containers with the new configuration:
build
This should show us:
The user running the container
The permissions of the mounted volumes
Any permission issues during startup
Would you like me to proceed with rebuilding the containers to get this information?
At some point I was receiving this error in the developer tools console:
workbench.desktop.main.js:3530 [diff-history] Error recording original content for : Error: Unable to read file '/Users/mondo/Desktop/Projects/mystery_exchange' (Error: Unable to read file '/Users/mondo/Desktop/Projects/mystery_exchange' that is actually a directory)
at l.F (workbench.desktop.main.js:1161:25390)
at l.C (workbench.desktop.main.js:1161:25183)
at async v.M (workbench.desktop.main.js:3636:35670)
at async v.readStream (workbench.desktop.main.js:3636:35427)
at async D.Db (workbench.desktop.main.js:3625:11317)
at async D.resolve (workbench.desktop.main.js:3625:9729)
at async s.W (workbench.desktop.main.js:3636:31731)
at async o.r (workbench.desktop.main.js:3625:24456)
at async P.acquire (workbench.desktop.main.js:398:3350)
at async g.createModelReference (workbench.desktop.main.js:3625:26065)
at async g.resetDiffHistories (workbench.desktop.main.js:3816:3281)
at async g.runInPlaceMutateRequestBeforeSubmit (workbench.desktop.main.js:3816:3016)
at async workbench.desktop.main.js:1480:54194
Checking permissions:
ls -alhs
total 880
0 drwxr-xr-x@ 27 mondo staff 864B Dec 27 13:22 .
0 drwxr-xr-x@ 97 mondo staff 3.0K Dec 13 16:03 ..
16 -rwxr-xr-x@ 1 mondo staff 6.0K Dec 1 00:05 .DS_Store
8 -rw-r--r--@ 1 mondo staff 113B Dec 27 13:14 .cursorignore
8 -rwxr-xr-x@ 1 mondo staff 62B Nov 22 14:23 .dockerignore
8 -rwxr-xr-x@ 1 mondo staff 1.4K Dec 24 22:47 .env
8 -rwxr-xr-x@ 1 mondo staff 1.3K Dec 27 11:45 .env.example
0 drwxr-xr-x 14 mondo staff 448B Dec 27 12:00 .git
8 -rwxr-xr-x@ 1 mondo staff 438B Dec 27 11:47 .gitignore
0 drwxr-xr-x@ 4 mondo staff 128B Dec 27 11:50 .husky
0 drwxr-xr-x 3 mondo staff 96B Dec 27 11:34 .pnpm-store
8 -rwxr-xr-x@ 1 mondo staff 1.2K Dec 27 11:14 Dockerfile
8 -rwxr-xr-x@ 1 mondo staff 2.3K Dec 27 11:50 README.md
8 -rwxr-xr-x@ 1 mondo staff 3.1K Dec 27 11:59 TODO.md
16 -rwxr-xr-x@ 1 mondo staff 4.3K Dec 27 11:43 docker-compose.yaml
8 -rwxr-xr-x@ 1 mondo staff 1.3K Dec 27 11:53 eslint.config.js
32 -rwxr-xr-x@ 1 mondo staff 15K Dec 24 22:30 favicon.ico
8 -rwxr-xr-x@ 1 mondo staff 380B Nov 22 14:07 index.html
0 drwxr-xr-x@ 6 mondo staff 192B Dec 24 23:27 migrations
104 -rwxr-xr-x@ 1 mondo staff 48K Nov 24 16:07 mystery_exchange.zip
368 -rwxr-xr-x@ 1 mondo staff 182K Nov 18 17:37 mysteryexchange.png
0 drwxr-xr-x 42 mondo staff 1.3K Dec 27 11:50 node_modules
8 -rwxr-xr-x@ 1 mondo staff 2.2K Dec 27 11:53 package.json
240 -rwxr-xr-x@ 1 mondo staff 117K Dec 27 11:50 pnpm-lock.yaml
8 -rwxr-xr-x@ 1 mondo staff 1.0K Nov 22 14:07 setup.sql
0 drwxr-xr-x@ 11 mondo staff 352B Dec 24 22:12 src
8 -rwxr-xr-x@ 1 mondo staff 771B Dec 27 12:45 vite.config.js
and confirming that it’s running under my user:
ps aux | grep cursor
mondo 48769 0.0 0.1 1596725952 32880 ?? S 1:11PM 0:00.26 /Applications/Cursor.app/Contents/Frameworks/Cursor Helper (Plugin).app/Contents/MacOS/Cursor Helper (Plugin) /Users/mondo/.cursor/extensions/ms-azuretools.vscode-docker-1.29.3/dist/compose-language-service/lib/server.js --node-ipc --node-ipc --clientProcessId=48528
mondo 48768 0.0 0.1 1596733120 40416 ?? S 1:11PM 0:00.28 /Applications/Cursor.app/Contents/Frameworks/Cursor Helper (Plugin).app/Contents/MacOS/Cursor Helper (Plugin) /Users/mondo/.cursor/extensions/ms-azuretools.vscode-docker-1.29.3/dist/dockerfile-language-server-nodejs/lib/server.js --node-ipc --node-ipc --clientProcessId=48528
I tried clearing cache and ALL of storage. I’ve logged out-and-in again. I even upgraded to Pro thinking it was hitting limits, as at one point I saw a message saying something like “resource exhausted”.
I no longer receive this error, but still having the exact same problem.
Now I only see:
workbench.desktop.main.js:3530 Error checking file existence: Error: Unable to resolve filesystem provider with relative file path 'cursor.aisettings:cursor/aisettings'
Version: 0.44.9
VSCode Version: 1.93.1
Commit: 316e524257c2ea23b755332b0a72c50cf23e1b00
Date: 2024-12-26T21:58:59.149Z
Electron: 30.5.1
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Darwin arm64 24.0.0
