--classic and cursor editor do not bypass Glass CLI folder routing (3.5.38)

Describe the Bug

On Cursor 3.5.38 with Layout: glass, CLI folder opens are hijacked by Glass/Agents routing even when using documented workarounds (–classic, cursor editor). This breaks the core cursor . workflow for opening a repo in the classic VS Code-style editor.

All of these open (or refocus) the Agents/Glass window instead of the classic editor with the folder loaded:

  • cursor /path/to/repo
  • cursor /path/to/repo --classic
  • cursor editor /path/to/repo
  • open -na Cursor --args --classic /path/to/repo

The “Editor Window” button often opens a blank/unrelated window or refocuses Agents instead of opening the same folder in the editor.

Steps to Reproduce

On Cursor 3.5.38 with Layout: glass, CLI folder opens are hijacked by Glass/Agents routing even when using documented workarounds (–classic, cursor editor). This breaks the core cursor . workflow for opening a repo in the classic VS Code-style editor.

All of these open (or refocus) the Agents/Glass window instead of the classic editor with the folder loaded:

  • cursor /path/to/repo
  • cursor /path/to/repo --classic
  • cursor editor /path/to/repo
  • open -na Cursor --args --classic /path/to/repo

The “Editor Window” button often opens a blank/unrelated window or refocuses Agents instead of opening the same folder in the editor.

Expected Behavior

Per Cursor staff guidance on the forum, cursor . --classic should open the classic Editor window with the folder loaded, skipping the Agents/Glass window.

Operating System

MacOS

Version Information

Version: 3.5.38
Commit: 009bb5a3600dd98fe1c1f25798f767f686e14750
Layout: glass
Build Type: Stable
Release Track: Default
OS: Darwin arm64 26.5 (25F71)
CLI: /usr/local/bin/cursor (app install), ~/.local/bin/cursor (shim)

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey @Nathan_Reynolds!

Agreed, it’s annoying our devs too.

I use glass most of the time but when i open from a terminal it means i want to explore the codebase in an ide and its always a dance to get there

We’re fixing it.