I currently have no workspace folders

Support Bug Reports
, ,
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

gpt 5.2 often says
I currently have no workspace folders. Please re-open the ... workspace (or confirm the new root path) so I can read ... and .....

Steps to Reproduce

ask to plan or in agent to edit files

Expected Behavior

should do the plan or just edit files

Operating System

Windows 10/11

Version Information

Version: 2.4.21 (system setup)
VSCode Version: 1.105.1
Commit: dc8361355d709f306d5159635a677a571b277bc0
Date: 2026-01-22T16:57:59.675Z
Build Type: Stable
Release Track: Early Access
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

GPT Codex 5.2
GPT 5.2

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

3

Hey, thanks for the report. This is an interesting issue: the GPT 5.2 model can’t see the workspace even though it’s open.

I’ll need a bit more info to troubleshoot:

  1. Confirm the workspace is open: In Cursor IDE, bottom left, does it show the folder or project name?

  2. Request ID: Next time you hit this error, in the chat on the right, click the three dots in the top right > Copy Request ID. Send it here.

  3. Other models: Try Opus 4.5 or Sonnet 4.5 in agent mode with the same request. Do they have the same problem?

  4. Specific project: Does this happen in just one project or in all projects?

Let me know what you find, it’ll help narrow down what’s going on.

4

Happens again

request ID : 6f32f065-aa9b-4a9e-af81-651686efadbd

Version: 2.4.28 (system setup)
VSCode Version: 1.105.1
Commit: f3f5cec40024283013878b50c4f9be4002e0b580
Date: 2026-02-03T00:56:18.293Z
Build Type: Stable
Release Track: Early Access
Electron: 39.2.7
Chromium: 142.0.7444.235
Node.js: 22.21.1
V8: 14.2.231.21-electron.0
OS: Windows_NT x64 10.0.26200

Screenshot 2026-02-05 184130
Screenshot 2026-02-05 184130560×237 5.69 KB

5

Thanks for coming back with the request ID. That’ll help the engineers see what exactly happened with this request.

To dig deeper, I need the info from my previous message:

  1. In the bottom-left in Cursor, does it show the folder or project name? A screenshot would help.

  2. Try Opus 4.5 or Sonnet 4.5 with the same request in agent mode. Do they also not see the workspace, or is it only GPT 5.2 messing up?

  3. Is this happening in one project or across all projects?

This info will show whether the issue is with the GPT model itself or something broader. Let me know what you find.

6

I don’t have the answer for your 3 questions : but it happens on the same workspace with 3 added folders