Dear Development Team,
I’m experiencing an unexpected issue with file buttons in Composer when using Windows Cursor IDE connected to a Dev Container (Linux) or via SSH to a project server:
When clicking on file buttons, an error occurs indicating the files “was not found”, despite the files definitely existing.
Technical Details:
- Environment: Windows Cursor IDE
- Connection Type: Dev Container (Linux) or SSH to project server
- Specific Problem: File operation buttons fail to open existing files
Key Potential Causes to Investigate:
- Path resolution differences between Windows and Linux
- File permission discrepancies
- Potential mounting/access issues with remote filesystem
- IDE configuration or path mapping problems
Could you help diagnose the root cause of this file access issue? I’d appreciate any insights or suggestions about what might be causing this unexpected behavior.
Best regards
Hi, can you confirm what version of Cursor you have installed?
1 Like
Hello, 0.44.11 its last version!
And what happens if you click ‘Create File’?
After a bit of research, it looks like this can be caused by a few reasons, most of which seem to be configuration based, and as I haven’t yet seen any other reports of this, I believe it’s not a Cursor bug right now.
When using the AI assistant in Cursor (through Composer), file creation works correctly. However, there’s a specific bug that occurs ONLY when clicking on “files buttons in dialog” and if im clicking the “Create File” button in the IDE interface - in this case, Cursor incorrectly creates files in C:\workspace\app\file instead of the proper container path /workspace/app/file.
This is problematic because:
- The IDE shouldn’t have access to or create files in the host system root directory
- It breaks container isolation principles
- Only happens with the manual “Create File” button action, while AI assistant file operations work correctly
This seems like a path resolution bug specifically in Cursor’s “Create File” dialog/button functionality, while other file operations (including those through the AI assistant) maintain proper container path handling.
Thanks for the information!
We have a new updating coming our to users over the next few days which should improve the stability of Dev Containers, so do let me know if you are still facing this issue once you have updated to 0.45.x
1 Like
I experienced access to version 0.45 briefly about a week ago, but it was quickly rolled back. Since then, I’ve been checking the changelogs regularly throughout the week trying to update to 0.45, but without success. I’m still stuck on 0.45.11, which continues to provide a negative user experience that is both exhausting and time-consuming. I’m really looking forward to the update being released again.
It should be in the next day or two hopefully!
1 Like
Thank you for the update! I’m pleased to inform you that I’ve received version 0.45 and the issue appears to be resolved. As a long-time user who has been with the product since before the IDE even had auto-file writing capabilities, I truly appreciate the continuous improvements being made to the software. Your team’s dedication to addressing user concerns and enhancing functionality is remarkable.
The swift resolution of this issue demonstrates the quality of both the product and the support team. Thank you for maintaining such high standards.
Best regards 
1 Like
