"View: Toggle Maximize Editor Group" command not working

Describe the Bug

There is some discussion here but it is locked instead of being solved:

I can’t even do this using command palette, so could the team fix it a bit? This is really annoying here.

Steps to Reproduce

As above, type in command palette

Expected Behavior

The editor group is maximized

Operating System

MacOS

Version Information

Version: 2.6.14
VSCode Version: 1.105.1
Commit: eb1c4e0702d201d1226d2a7afb25c501c2e56080
Date: 2026-03-08T15:36:54.709Z
Build Type: Stable
Release Track: Default
Electron: 39.6.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Darwin arm64 25.3.0

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

Hey, thanks for the report. This is a known issue. The Toggle Maximize Editor Group command has a precondition that requires 2+ editor groups, and in Cursor’s current layouts, especially with Agent mode, it often stays disabled, even from the Command Palette.

The team is aware of the bug. There’s no specific ETA for a fix yet, but your report helps with prioritization.

As a temporary workaround, you can try opening a second editor group manually (split the editor). Then the command should become available, at least for the main group.

Let me know if there’s anything else.

1 Like

“View: Toggle Maximize Editor Group” command not working only on the left editor group :frowning: .

Also when quiting Cursor, Am getting this error.

Illegal state: service accessor is only valid during the invocation of its target method

Anything being Deployed?

2 Likes

Hi team, thank you for the quick reply, I current multi-root workspace has 4 or more editor groups, and I don’t think >=2 editor groups will make the issue go away after several trials. I think I can give more context why I need it.

when an IDE agent / CLI agent finishes the current editing file, since I’m a heavy keyboard shortcut user, so I usually just switch to what file it has edited, and maximize it so I get the full picture and decide to keep it or not (I’m not using cursor native file review here).

So this kind of a quality-of-life issue, so probably this can help the team to put it into high priority. I know the team have done a lot of UI tweaking these days, but if the original feature on top of vscode continuous break, it will not be a good experience for new users. Thanks!

Taking a look at this today, this one right?

Yes! Thx for taking time for this issue!

Fixed in tomorrows nightly and the next point release. Sorry about this!

1 Like

Thx! looking forward to it!

Should this have been resolved on the latest version? I’m still experiencing the issue after updating

are you on nightly?

Still not working.

Information

Version: 2.6.21 (Universal)
VSCode Version: 1.105.1
Commit: fea2f546c979a0a4ad1deab23552a43568807590
Date: 2026-03-21T22:09:10.098Z
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.6.0

Not working on the latest version as well

Version: 2.6.22
VSCode Version: 1.105.1
Commit: c6285feaba0ad62603f7c22e72f0a170dc8415a0
Date: 2026-03-27T15:59:31.561Z
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