Debug mode log file deletion

[user880 (Archie)]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Hi! The Debug mode is great and I think it has so much potential, so nice job.

But, I’ve been using it for the last 30mins or so and every loop the agent says it can’t manually delete the debug.log file even though it knows it is supposed to, and asks me to do so instead. For example, its most recent response included:

“Before we can verify, the NDJSON log must be cleared. The automation API is blocked from deleting c:*.cursor\debug.log, so please remove it manually via Explorer or PowerShell.”

and I’ve seen in it’s thinking that it is struggling to delete it manually, which obviously isn’t great.

Thanks!

Steps to Reproduce

Just run a normal Debug Mode loop, I haven’t done anything specifically and it has happened every loop so far.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.9 (user setup)
VSCode Version: 1.105.1
Commit: a86689c93e9fb11addfbefd29a6ec7c0a59175e0
Date: 2025-12-10T16:51:25.713Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

GPT-5.1 Codex

Does this stop you from using Cursor

No - Cursor works, but with this issue

[deanrie]

Hey, thanks for the report.

It looks like a bug in Debug mode. The agent should be able to delete debug.log, but the API blocks operations on the path c:\*.cursor\.

Could you share the Request ID of the last cycle where this happened? (Chat context menu in the top-right > Copy Request ID)

If possible, a screenshot of the agent’s “thinking” showing the delete attempts would also help.

I’ll pass this to the developers for a fix in upcoming releases.

[user880 (Archie)]

Yeah of course sorry. This is all I could get details on (not all of its thinking was available). It still worked btw lol.

Request ID of chat: 84886a48-52f5-450b-a0bf-9d8c94b60114
^the last cycle was it just cleaning up its instrumentation so idk if that helps or not

Loop 1 - just spoke about how the log file didn’t exist yet and explained to me there was nothing to clear..:

Later loops:

- start of its thinking

- same loop as above

- same loop ^ response

- next loop once fix verified