Loading Glass destroyed by workspace

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Decided to follow the prompt and try out Cursor v3, this immediately led to several really upsetting issues.
It seems to have corrupted the workspace entirely. It exists in Glass still as “workspace.json” but the original folder and workspace file do not exist anymore.

When I clicked on my main agent where i do my planning and design, it disappeared , or seemed to. It disappeared from the view anyway. I figured out how to display archived conversations and none of my archived conversations are present.

So I switched back to “Editor” and this is when I discovered that the workspace was no longer going to load. I opened other recent workspaces and they were fine, but my primary is gone.

Switched back to glass, I was able to have cursor hunt down the actual conversation file, but Glass does not appear to have a way to directly load a workspace.

All in all, not happy or impressed. Why is this an improvement?

I’m also finding opening files really challenging, each time I switch conversations it loads a new file view so I don’t have consistent ability to drag and drop files between conversations.

Steps to Reproduce

Two finer click on a laptop to pull up right click menu on a conversation. That trigger some kind of hide function.

Open a file folder in one conversation, switch conversations open files, it will not persist.
Go to a new conversation, the open folder view does not persist.

Expected Behavior

Not corrupt the worksppace

Operating System

Linux

Version Information

Version: 3.0.9
VSCode Version: 1.105.1
Commit: 93e276db8a03af947eafb2d10241e2de17806c20
Date: 2026-04-03T02:06:46.446Z
Layout: glass
Build Type: Stable
Release Track: Default
Electron: 39.8.1
Chromium: 142.0.7444.265
Node.js: 22.22.1
V8: 14.2.231.22-electron.0
OS: Linux x64 6.17.0-19-generic

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

I noticed this as well, it’s kind of annoying that each agent / chat view is considered its own environment where there’s no consistency between each of them.

I guess this is the point of the Editor view, since its focus is more on your file structure, files open, etc. — whereas the goal with each agent / chat is to make each session a stable environment where you can return to the files + tabs you had open for that session so it’s all relevant.

Honestly, I think it’s faster to type @ and begin typing the filename so I can reference it in chats, than it is to drag files; but there are times when dragging makes more sense (especially if you aren’t working on a saved file, but an Untitled scratch pad with random text in it).

6

I dislike the lack of continuity feeling of having a file I’m working on that I intend to use in a different chat. I switch to that chat, and my file is gone. So I have to go through multiple additional steps to get it back in front of me. It’s added friction that didn’t used to be there. Probably a simple oversite, if it’s intentional it’s a real negative for my style.

1 Like
7

I almost want to see an option like: “New chat with current view” or simple a “New context window” or something like that, since the benefit of new chats / agents is having that fresh window if you’re still working on a specific group of files, browser views, etc.

8

For me it’s more about how I organize into a Prime or Main chat, and then fork sometimes, and sometimes start a fresh agent.
I don’t find the subagent command quite up to my needs most of the time, and tend to start a new agent with a handoff.

I did find the @ an acceptable solution for this specifically.

It doesn’t help with my desire to drag and drop a file and have a consistent view of my file tree. Maybe a pin option for that pane?

10

Hi @Drakosfire

First, the good news: your workspace is almost certainly not corrupted. Your files are still on disk. What’s happening is that Glass uses a different workspace model than the Editor layout. Glass organizes around individual project folders and git repos, and doesn’t natively open .code-workspace multi-root workspace files the way Editor does. When you see it listed as “workspace.json” in Glass, that’s Glass’s internal reference — not a replacement of your original workspace file.

To get back to your workspace, switch to the Editor layout (you can do this from the layout toggle) and open your workspace from File > Open Recent or File > Open Workspace from File. Your workspace file should still be at its original location on disk.

For the conversation that disappeared — based on your description (“two finger click triggered some kind of hide function”), it sounds like the trackpad gesture accidentally triggered the Archive action from the right-click context menu. You can find it by toggling the “Include Archived” filter in the sidebar. If it doesn’t appear there, it may have been hidden rather than archived.

Regarding file views not persisting between conversations — this is currently by design in Glass. Each conversation maintains its own workspace and file context, so switching between them reloads the file view for that session. As @munchkin mentioned, using @ to reference files is the fastest way to bring files into a different conversation. The team is aware of the friction here and exploring improvements.