# Unable to edit files in the virtual workspaces

**URL:** <https://forum.cursor.com/t/unable-to-edit-files-in-the-virtual-workspaces/151036>\
**Category:** Bug Reports\
**Tags:** installation\
**Created:** [February 6, 2026, 9:44am UTC](https://forum.cursor.com/t/unable-to-edit-files-in-the-virtual-workspaces/151036 "2026-02-06T09:44:38Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![COOPER-DENG](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/cooper-deng/32/97431_2.png) [@COOPER-DENG](https://forum.cursor.com/u/COOPER-DENG)\
**Post date:** [February 6, 2026, 9:44am UTC](https://forum.cursor.com/t/unable-to-edit-files-in-the-virtual-workspaces/151036/1 "2026-02-06T09:44:38Z")

</div>

### Where does the bug appear (feature/product)?

Cursor IDE

### Describe the Bug

The previous versions (2.3.21 and earlier) could read and edit files in the virtual workspace, but versions 2.4.X (specifically from 2.3.23 to the latest 2.4.28) can only read files in the virtual workspace, but cannot successfully edit them. It only creates a local copy and applies the edits to that copy. This makes me hesitant to upgrade to the latest version, because I need to manually copy the changes from the local copy back to the file opened in the virtual workspace. Compared to before, this experience is terrible. I need to go back to the previous version, where I could directly read and successfully edit files in one step.

I suspect the file editing tool might have undergone some adjustments. Why could I successfully edit files in so many previous versions, but not in later ones? Please help me solve this; this problem is very important to me. Thank you! Otherwise, I might not be able to use Cursor in a few months. @deanrie

### Steps to Reproduce

When connecting to the server via a virtual workspaces

### Expected Behavior

When those older, available versions are no longer supported, the cursor can no longer be used.

### Operating System

Windows 10/11

### Version Information

Version: 2.4.28 (user setup)  
VSCode Version: 1.105.1  
Commit: f3f5cec40024283013878b50c4f9be4002e0b580  
Date: 2026-02-03T00:56:18.293Z  
Build Type: Stable  
Release Track: Default  
Electron: 39.2.7  
Chromium: 142.0.7444.235  
Node.js: 22.21.1  
V8: 14.2.231.21-electron.0  
OS: Windows\_NT x64 10.0.19045

### Does this stop you from using Cursor

Yes - Cursor is unusable

---

<div class="post-metadata">

**Author:** ![deanrie](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/deanrie/32/1263_2.png) [@deanrie](https://forum.cursor.com/u/deanrie)\
**Post date:** [February 6, 2026, 12:18pm UTC](https://forum.cursor.com/t/unable-to-edit-files-in-the-virtual-workspaces/151036/5 "2026-02-06T12:18:44Z")

</div>

Hey, this is a known issue with virtual filesystem support in Cursor.

Here’s a similar thread: [Cursor Lacks Access to Virtual Filesystem](https://forum.cursor.com/t/cursor-lacks-access-to-virtual-filesystem/148127). With the current architecture, this is a technically hard fix. The team is aware, but there’s no timeline yet.

To better understand your case:

- Which virtual filesystem provider are you using? (Remote SSH extension, Dev Containers, or something else?)
- Can you share the Request ID when you try to edit? (Chat menu top right \> Copy Request ID)

Workaround: For now, please stay on 2.3.21. It’s the only working option for virtual workspaces.

I’ll let the team know this is critical for you. Your report helps us prioritize.

---

<div class="post-metadata">

**Author:** ![system](https://sea3.discourse-cdn.com/cursor1/user_avatar/forum.cursor.com/system/32/99069_2.png) [@system](https://forum.cursor.com/u/system)\
**Post date:** [February 28, 2026, 12:19pm UTC](https://forum.cursor.com/t/unable-to-edit-files-in-the-virtual-workspaces/151036/6 "2026-02-28T12:19:32Z")

</div>

Closed on February 28, 2026, 12:19pm UTC

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.