Debug mode frontend logs not showing

Support Bug Reports
1

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Happened to me a while ago when debug mode came out and haven’t used it much snice because of it, but now I really need to get it fixed. When I use Debug mode, if the agent adds logs in the backend to go into debug.log, that works perfectly fine. However if they add frontend logs then none of them show up in debug.log - ever. I have to ask it instead to add console logs and then input the console logs to the chat myself etc. So it successfully adds #region agent log code into my frontend, but when I reproduce the issue, debug.log stays empty if only frontend logs added.

Steps to Reproduce

Not sure since I know others have working Debug mode, but this bug literally happens every time the agent does only frontend logs. But to reproduce for me tis just:

  • explain a bug involving frontend code to an agent in debug mode
  • get debug mode to add ‘#region agent log’ code to the frontend
  • start app locally with an EAS Development build (npx expo start in the frontend)
  • reproduce the bug

Expected Behavior

When i reproduce the bug, debug.log should fill with the frontend logs that the agent added.

Operating System

Windows 10/11

Current Cursor Version (Menu → About Cursor → Copy)

Version: 2.3.34 (user setup)
VSCode Version: 1.105.1
Commit: 643ba67cd252e2888e296dd0cf34a0c5d7625b90
Date: 2026-01-10T21:17:10.428Z
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?

Not model-specific

For AI issues: add Request ID with privacy disabled

c95b2602-bd8b-4a90-9140-1c7aed39654d

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

1 Like
3

hi @user880 the frontend logs depend on the programming language and tool used.

Agent has an option to send frontend logs via http request in some languages. The details may in some cases not go to debug.log and in other cases if the receiving part isn’t running it may not be received.

Could you use Help > Toggle Developer Tools and check if there are requests happening where the Agent has set them in the code. In some cases you may also need to restart your development server for the changes to become active or re-build the frontend / clear frontend cache.

Having said that, usually it works for me in several languages and frameworks (e.g. TS, PHP,…). Ask the agent why the calls are not in logs it should be able to recognize why

4

I’m having the same issue in the Flutter codebase. So now I’ve added a rule file with the following content:

Use instrumentation prefixed print() statements to debug the code.

Do not create the debug.log file because it is not compatible with the framework. Never ever attempt this approach to debug. Use instrumentation with print() whenever required.

I will provide you with the logs manually after performing your said steps.

If anyone has a solution for using this debug.log functionality, please share.