Setting up a new workspace causes memory leak

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Since the launch of workspaces on the new agent editor I’ve noticed that I haven’t been able to create a new workspace because it completely lags my computer, can only guess this is a memory leak of some sorts.

Steps to Reproduce

Literally just creating a new workspace with 2 or more folders.

Operating System

MacOS

Version Information

Version: 3.2.16
VSCode Version: 1.105.1
Commit: 3e548838cf824b70851dd3ef27d0c6aae371b3f0
Date: 2026-04-28T21:07:47.682Z
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: Darwin arm64 24.0.0

Additional Information

Context: MBP 14" 2021, 16GB RAM 500GB storage

Does this stop you from using Cursor

Yes - Cursor is unusable

This is a known issue with Glass (the Agents Window) and multi-root workspaces. When a workspace contains multiple folders, several Glass components scale with the number of roots, which can cause significant lag on lower-RAM machines like yours (16GB).

Our team is working on multi-root performance improvements for Glass. No ETA to share yet, but it’s actively tracked.

Workarounds for now:

  1. Switch to the Editor layout temporarily: Cmd+Shift+P > search “Toggle Editor Layout.” Several users have reported that switching from Agents Window back to the Editor Window resolves the lag immediately.

  2. Use single-folder workspaces instead of multi-root — open each folder in a separate Cursor window rather than combining them into one workspace.

  3. Restart Cursor periodically (Cmd+Q then relaunch) if you notice lag building up over time.

If you’re able to capture a Process Explorer snapshot when the lag occurs (Cmd+Shift+P > Developer: Open Process Explorer), that would help us understand which process is consuming the most resources. Let me know if switching layouts helps or if you run into anything else.