Skip to lesson
Exit
Debugging & Troubleshooting Method1 / 2

1 min lesson

Reading logs, traces & diagnostics

Match each case in "Reading logs, traces & diagnostics" to the signal and response that fit it.

Step 1 of 2

Logs are where a vague complaint becomes a specific cause. The skill isn't reading every line - it's knowing where Cursor writes the signal and which line is the first one that's actually yours.

Cursor is a VS Code fork, so it inherits VS Code's diagnostic surfaces while adding its own. Know the three places it surfaces problems and how to reach them.

Developer Tools console

Help → Toggle Developer Tools

JS errors, renderer crashes, failed requests

Same DevTools you know from Chrome

Output / log panels

Output panel, channel dropdown

Per-feature logs: indexing, extensions, agent

Command Palette → set log level to trace

Log files on disk

Command Palette → Open Logs Folder

Persist across restarts for attaching to a ticket

Paths differ per OS (see below)

Learn more

Full explanation

Full explanation

Typical log directory by OS (verify the exact path in-product; Cursor inherits VS Code's layout)
macOS:    ~/Library/Application Support/Cursor/logs/
Windows:  %APPDATA%\Cursor\logs\
Linux:    ~/.config/Cursor/logs/