Right Panel Empty in New UI When Using Cloud Agents

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

The right panel (file tree, terminal, Desktop tab, etc.) does not render any content in the new UI when working with cloud agents. The panel appears but remains completely empty.

This makes the new UI effectively unusable for cloud-based agent workflows.

Steps to Reproduce

Case 1 – Opening an existing agent:

  1. Open Cursor’s new UI
  2. Open an agent that was previously created via the web version
  3. Right panel is empty immediately

Case 2 – Switching between agents:

  1. Open Cursor’s new UI
  2. Start a brand new agent directly in Cursor
  3. Right panel displays correctly at this point
  4. Switch to a different agent
  5. Switch back to the original agent
  6. Right panel is now empty

Expected Behavior

The right panel should consistently display its content (file tree, opened files, terminal, Desktop tab, etc.) regardless of how the agent was created or how many times the user switches between agents.

Screenshots / Screen Recordings

Operating System

MacOS

Version Information

Version: 3.0.16 (Universal)
VSCode Version: 1.105.1
Commit: 475871d112608994deb2e3065dfb7c6b0baa0c50
Date: 2026-04-09T05:33:51.767Z
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 25.3.0

Does this stop you from using Cursor

Yes - Cursor is unusable

Hey, thanks for the detailed report with clear repro steps, this really helps.

I see the screenshot with the empty right panel. This is a known issue in Glass UI, the right panel can lose its state during certain transitions between agents. The team is aware and tracking it. Your report with two specific scenarios opening a web-created agent and switching between agents helps with prioritization.

As a temporary workaround, try:

  1. If the panel is empty, close and reopen the Agents Window
  2. Create agents directly in Cursor instead of the web version to avoid case 1

Unfortunately there isn’t a full fix yet, but it’s on our radar. We’ll update here if there are any news.

Thanks for your quick response! I’ll be waiting for the fix.

@love_chaos This should be fixed starting in v3.2.10! Please upgrade and try it out.

Thank you! Yes, I see it works now!