First of all, your core AI coding functionality is already fantastic. That’s the main reason we love and rely on Cursor every day.
However, the constant UI and layout redesigns are becoming extremely frustrating for daily workflow. As developers, we don’t need a fancy or flashy interface—we need a stable and familiar environment so we can dive straight into coding without distraction.
Coming in every morning to find a different layout forces us to re-learn, re-adapt, and search for where basic tools or repositories have moved. We simply don’t have the time or energy to constantly adjust to arbitrary interface overhauls.
Please focus your efforts on refining and perfecting the core coding capabilities, and leave the UI layout stable (or at least provide settings to keep the classic view).
We hear you on wanting a stable, familiar layout. The classic editor is still fully supported: Command Palette → Open IDE, or from the Agents Window use Cmd/Ctrl+Shift+N. You can also set Cursor Settings → General → Window Restoration to Last Used Windows so Cursor restores whatever you had open last (keep the editor as the last window you close, and it should come back that way). More on switching surfaces: Agents Window.
As @Artemonim noted, a couple of screenshots of what shifted for you day-to-day would help - startup window vs a specific panel move are different fixes.
Thank you for the information. I would appreciate it if the Cursor team could ensure the IDE layout remains saved permanently, particularly for the mobile and desktop views. This would allow us to maintain our focus on core coding without frequent UI adjustments.
hi Cursor and Mohit:
can I pls report a issue with you?
if it is possible pls help. If I got the wrong person, pls let me know where can I report this thank you much!
Request ID: 71035069-1d2b-4d5a-a317-8d7d6c030d76
[invalid_argument] Failed to resolve request context blob
RetriableError: [invalid_argument] Failed to resolve request context blob
at oOg (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9045:7773)
at f3s (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9045:6271)
at EOg (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9046:12878)
at Object.classify (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9046:17450)
at _Og (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9046:5856)
at async D3s.run (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9046:16802)
at async Eoe.runAgentLoop (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:11717:15420)
at async gdo.streamFromAgentBackend (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:15632:15607)
at async gdo.getAgentStreamResponse (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:15632:31596)
at async OTe._submitChatMaybeAbortCurrent (vscode-file://vscode-app/Applications/Cursor.app/Contents/Resources/app/out/vs/workbench/workbench.desktop.main.js:9241:2568)
Hi @WonRxpnoe Thank you for the post. We’re currently investigating a widespread issue affecting Cursor. Please follow status.cursor.com for live updates. We’ll post there as we learn more and when service is restored. Sorry for the disruption.