Adding a macOS reproduction with additional symptoms not covered above. This is blocking workspace management for multi-repo setups.
Environment
- OS: macOS (darwin 24.6.0)
- Layout: Agent Window / Glass multi-root workspace
- Workspace config path:
~/Library/Application Support/Cursor/glassMultiRootWorkspaces/供票系统全栈.code-workspace
- Folders: 4 repos on external exFAT volume
/Volumes/移动硬盘/...
Symptoms (beyond rename not sticking)
1. Save fails with explicit error
Click Edit Workspace → change name → Save shows:
Could not save this workspace. Try again.
This is worse than Save being disabled — the UI accepts input but persistence fails.
2. Edit dialog shows WRONG auto-generated name (not the saved filename)
- Actual filename on disk:
供票系统全栈.code-workspace
- Edit Workspace dialog shows:
echain-cloud-featu-个人知识库-plus-2
The dialog does not read the .code-workspace filename. It auto-generates a name from folder list:
- first folder truncated + second folder +
-plus-N for remaining folders
So users see three different names: sidebar label, edit dialog, and filesystem — with no single source of truth.
3. .code-workspace has no name field
File only contains folders[] with fragile relative paths like:
"path": "../../../../../../Volumes/移动硬盘/代码库/git/echain-cloud-feature-chuantou-drill"
Display name is entirely derived from filename, but Edit UI ignores it.
Steps to Reproduce
- Create multi-root workspace (4 folders) via Agents Window, name it e.g.
供票系统全栈
- Open workspace later → Edit Workspace
- Observe name field shows auto-generated
echain-cloud-featu-个人知识库-plus-2 instead of 供票系统全栈
- Change name to anything → click Save
- Result: red error “Could not save this workspace. Try again.”
Workaround (manual only)
Quit Cursor → rename .code-workspace file in glassMultiRootWorkspaces/ manually → reopen.
Severity
High — workspace rename/edit is completely broken on macOS for glass multi-root workspaces. Users cannot manage workspace identity without filesystem hacks. Combined with external-volume path validation, this makes multi-repo Agent workflows unreliable.
@Colin — happy to provide screen recording if needed. This appears related to #169054 but the save failure + name desync are distinct regressions worth tracking separately.
— LingQi_Meng
UPDATE — Clarification (rename succeeded, UI display is wrong)
After further investigation, the root issue is refined:
What actually works
- Workspace was named
供票系统全栈 at creation — this saved correctly
- Verified on disk:
glassMultiRootWorkspaces/供票系统全栈.code-workspace exists
workspaceStorage/.../workspace.json correctly points to this file- Workspace functionality (folders, agents) works fine under the correct name
What is broken (the real bug)
This is primarily a UI display desync, not a failed rename:
- User sets name to
供票系统全栈 → file on disk is correct
- Re-opening Edit Workspace still shows auto-generated
echain-cloud-featu-个人知识库-plus-2 instead of reading the filename
- User thinks rename failed, tries to save again → may get “Could not save this workspace” even though the name is already correct
- Sidebar / edit dialog can show different names for the same workspace
Revised severity
Medium-High (UX / misleading UI) — persistence at creation works, but the Edit Workspace UI never reflects the saved name. Users cannot trust or manage workspace identity through the UI.
Suggested fix
Edit Workspace should read display name from the .code-workspace filename (or a dedicated name field), not auto-regenerate from folder list on every open.
