Debug.log created for all chats regardless of mode

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Bug report details:
Issue: Cursor creates .cursor/debug.log even when not in debug mode
Cursor version: 2.2.44 (20adc1003928b0f1b99305dbaf845656ff81f5d0, arm64)
OS: macOS (darwin 25.2.0)
File location: .cursor/debug.log in the project root
File contents: JSON logs with “sessionId”:“debug-session” from provider.go:61 (SQL query logging)


This happened soon after switching which model I was using. The agent itself appears to have no idea how it’s being created outside of being built-in cursor instrumentation.

Steps to Reproduce

Chat in any mode.

Expected Behavior

Only produce a log in debug mode, once there’s instrumentation in place to solve a problem in code.

Operating System

MacOS

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.2.44 (Universal)
VSCode Version: 1.105.1
Commit: 20adc1003928b0f1b99305dbaf845656ff81f5d0
Date: 2025-12-24T21:41:47.598Z
Electron: 37.7.0
Chromium: 138.0.7204.251
Node.js: 22.20.0
V8: 13.8.258.32-electron.0
OS: Darwin arm64 25.2.0

For AI issues: which model did you use?

Any model

Does this stop you from using Cursor

No - Cursor works, but with this issue

Hey, thanks for the report. This looks like a new bug in version 2.2.44. debug.log shouldn’t be created outside Debug Mode.

I can confirm the issue and I’ll pass it to the dev team. Based on what’s in the file (provider.go:61 with SQL request logging), it looks like internal Cursor logging that’s being enabled by mistake.

As a temporary workaround, you can:

  • Add .cursor/debug.log to .gitignore so these files don’t get committed
  • Delete the file manually from time to time

The team should fix this in a future update. I’ll keep you posted if a fix comes out.

This topic was automatically closed 22 days after the last reply. New replies are no longer allowed.