Debug mode, log file not found

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Very frequently, during the Debug Mode, the log file generated by the debug ingest server—typically located at .cursor/debug-hash.log—is not automatically detected by the agent. This issue does not appear to depend on the model, as it occurs even when using Premium models such as GPT-5.3-codex, GPT-5.4, Sonnet 4.6, Opus 4.7, and Composer 2.

Additionally, in many of these cases, the agent does not use tools like grep or the terminal to search for the log file.

Steps to Reproduce

  1. Ask the agent about any issue and allow it to generate the log file.
  2. Click the Proceed button.
  3. Observe whether the agent searches for the log file.

Expected Behavior

The agent should automatically locate and read the log file, or at least actively search for it using available tools.

Screenshots / Screen Recordings

1.txt - caab-markeplace-and-city-logistics (Worksp.png
1.txt - caab-markeplace-and-city-logistics (Worksp.png393×381 8.92 KB

Operating System

Windows 10/11

Version Information

Version: 3.1.15 (user setup)
VSCode Version: 1.105.1
Commit: 3a67af7b780e0bfc8d32aefa96b8ff1cb8817f80
Date: 2026-04-15T01:46:06.515Z
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: Windows_NT x64 10.0.26200

For AI issues: which model did you use?

Premium that defults to GPT-5.3-codex, GPT-5.4, Sonnet 4.6, Opus 4.7, Composer 2

For AI issues: add Request ID with privacy disabled

Request ID: 81436841-4589-413e-9060-fe95870ce1ff

Additional Information

I suspect the issue may be caused by adding **/*.log to the .gitignore. In this case, the .gitignore rule should be ignored, allowing the agent to access the log file.

Does this stop you from using Cursor

No - Cursor works, but with this issue

5

I am also having this issue on the most recent update of Cursor:

Version: 3.1.15 (system setup)
VSCode Version: 1.105.1
Commit: 3a67af7b780e0bfc8d32aefa96b8ff1cb8817f80
Date: 2026-04-15T01:46:06.515Z
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: Windows_NT x64 10.0.26100

As a workaround, I have been clicking on the debug file in chat to open the file in the editor, then I can drag the file name near the top of the tab over to the “Enter additional context about the issue” text entry. This adds that file as context to the reply, so that the chat knows where to find it. I enter any other notes about the debug interaction, and then instead of clicking “Proceed” or “Mark as fixed”, Click the submit arrow button in the chat, or press Enter.

10

@Neting_Srl @Leland_Hepworth Thanks for reporting and for sharing the workaround! We’ve got a bug report raised, and we’ll let you know any updates.

The workaround is a great option in the meantime.

11

Replying to keep the post open; otherwise “This topic will close 22 days after the last reply.”

I had this issue once again since my last reply, but most of the time I remember to manually add the debug log as context.

@kevinn do you have any update on the situation?

12

Hi @Leland_Hepworth We still have the bug ticket open and I don’t have an ETA. The workaround is a great option to continue to use while this still exists.

You don’t have to worry about the thread closing automatically … even if it does “close” we will still respond with an update when the issue is fixed.

13

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

This is a very old bug that still happens and annoys me a little, almost always the debug agent cannot find the generated logs by itself. The logs are generated and I can see them in the log preview inside the agent, but the agent simply says “I can’t find the logs, so they are not being generated” and replace everything with a console.log. So I always need to stop the agent and copy and paste the logs in the chat so the agent can find the file the logs are.

Steps to Reproduce

Use debug mode and generate logs.
Ask to proceed, and the agent will not find the logs it just created

Expected Behavior

It should find the logs as they exist

Operating System

Windows 10/11

Version Information

Version: 3.3.30 (system setup)
VSCode Version: 1.105.1
Commit: 3dc559280adc5f931ade8e25c7b85393842acf30
Date: 2026-05-09T18:28:42.332Z
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: Windows_NT x64 10.0.26200

Does this stop you from using Cursor

No - Cursor works, but with this issue