Where does the bug appear (feature/product)?
Cursor IDE
Describe the Bug
Hi Cursor Support,
I was actively working in Cursor when my session was suddenly unauthenticated without warning. I was kicked out of my existing workspace/session, and Cursor opened into a different/new window state. It was extremely difficult to figure out how to get back to my previous setup and access Codex again.
This was not a minor inconvenience. I had been working in this environment for months, organized exactly the way I needed them. Losing access mid-work, then being dropped into a confusing state with no clear recovery path, completely disrupted my workflow.
Please investigate why my session was unauthenticated while I was actively working, and please improve the recovery flow so users can easily return to their previous workspace, settings, and agent/tool setup after authentication issues.
At minimum, Cursor should make it obvious how to restore:
- the previous workspace/window
- the prior repo context
- Codex/agent access
- existing settings and session state
This kind of disruption is incredibly frustrating, especially during active development work.
Thanks.
Steps to Reproduce
Steps To Reproduce
I was actively working in Cursor in my established workspace with multiple repos/projects open.
I was using Codex/agent functionality inside Cursor.
Without warning, Cursor unauthenticated my session while I was actively working.
I was kicked out of the current session/workspace state.
Cursor opened into a different/new window state instead of restoring my previous environment.
I had to spend significant time figuring out how to get back to my previous setup and regain Codex access
Expected Behavior
Expected Behavior
Cursor should not unauthenticate an active session without warning.
If re-authentication is required, Cursor should preserve and restore the user’s exact previous state, including:
the previous workspace/window
open repos/projects
Cursor settings
Codex/agent access
prior session/tool context where possible
After logging back in, there should be a clear, obvious path to return to the exact workspace and setup I was using before the authentication interruption.
Operating System
MacOS
Version Information
Version: 3.5.17
VSCode Version: 1.105.1
Commit: d5b2fc092e16007956c9e5047f76097b9e626ca0
Date: 2026-05-20T02:43:31.559Z
Layout: editor
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.5.0
Does this stop you from using Cursor
No - Cursor works, but with this issue