Cmd + click is not working as "Go to definition"

[anovi (Aleksei Novichkov)]

Where does the bug appear (feature/product)?

Cursor IDE

Describe the Bug

Cmd+click stopped to work as “Go to definition” in the editor. It stopped serveral days ego. Probably after an update.

Steps to Reproduce

I just open a TS or JS file and try to cmd+click on a method call.

Expected Behavior

Editor should jump to definition

Operating System

MacOS

Version Information

Version: 2.6.14
VSCode Version: 1.105.1
Commit: eb1c4e0702d201d1226d2a7afb25c501c2e56080
Date: 2026-03-08T15:36:54.709Z
Build Type: Stable
Release Track: Default
Electron: 39.6.0
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Darwin arm64 24.6.0

Additional Information

What I have tried so far:

• disabled all extensions
• downloaded previous versions 2.6.*

Still does not work.

Does this stop you from using Cursor

No - Cursor works, but with this issue

[deanrie]

Hey, this is a known issue. A few users have reported the same behavior.

A couple things to try:

1. Open the command palette Cmd+Shift+P and run “TypeScript: Restart TS Server”. This often fixes it.

2. Check what the TypeScript language server is doing. Go to View > Output, then select “TypeScript” in the dropdown. Do you see any errors?

3. Make sure the built-in TypeScript Language Features extension is enabled in the Extensions panel.

Since disabling all extensions didn’t help, the Output log would really help narrow this down. Can you paste what it shows after you open a TS file and try Cmd+click?

The team is aware of this issue, and your report helps with prioritization.

[anovi (Aleksei Novichkov)]

The output from typescript:

2026-03-10 11:58:43.097 [info] Killing TS Server
2026-03-10 11:58:43.097 [info] Starting TS Server
2026-03-10 11:58:43.097 [info] Using tsserver from: /Applications/Cursor.app/Contents/Resources/app/extensions/node_modules/typescript/lib/tsserver.js
2026-03-10 11:58:43.097 [info] <syntax> Forking...
2026-03-10 11:58:43.097 [info] <syntax> Starting...
2026-03-10 11:58:43.097 [info] <semantic> Forking...
2026-03-10 11:58:43.097 [info] <semantic> Starting...
2026-03-10 11:58:43.097 [error] TSServer exited. Code: null. Signal: SIGTERM

[deanrie]

The log is really helpful. It shows that TSServer crashes right after launch with a SIGTERM signal. That explains why Go to Definition doesn’t work. The TypeScript language server doesn’t even get a chance to start.

A couple things that can help narrow it down:

1. Does Go to Definition work in VS Code (not Cursor) with the same project? This helps confirm the issue is specific to Cursor.

2. Try a full reset of Cursor state. Delete the ~/.cursor folder (back up settings.json first if you need it), then start Cursor again. Sometimes local state breaks the TS server between versions.

3. If that doesn’t help, try launching Cursor from the terminal with --verbose and check whether there are extra errors in stdout or stderr when you open a TS file.

The team knows about this bug. Your SIGTERM log is a useful data point for debugging. Let me know what you see after the steps above.

[anovi (Aleksei Novichkov)]

VS Code works fine with the same project.

VS Code version info:

Version: 1.111.0 (Universal)
Commit: ce099c1ed25d9eb3076c11e4a280f3eb52b4fbeb
Date: 2026-03-06T23:06:10Z (4 days ago)
Electron: 39.6.0
ElectronBuildId: 13330601
Chromium: 142.0.7444.265
Node.js: 22.22.0
V8: 14.2.231.22-electron.0
OS: Darwin arm64 24.6.0

I created a new project via npm create vite@latest with TS and no frameworks. There are no .cursor or .vscode folders.

I opened the project in VS Code and Cursor with --verbose option.

VS Code

Go to definition works.

Cursor

Go to definition does not work.

There are two files that include content from the terminal and from the Output > Typescript console.

cursor-verbose-terminal-log.txt (39.8 KB)
cursor-output-typescript-log.txt (24.0 KB)

[anovi (Aleksei Novichkov)]

I have tried deleting /Users/{USER}/Library/Application Support/Cursor/User/settings.json. It did not change the result.

[anovi (Aleksei Novichkov)]

I have found the problem.

Somehow, the “Editor: Multi Cursor Modifier” setting was set to ctrlCmd and it caused the editor to switch to alt modifier when clicking:

I don’t know what changed this setting—I don’t remember touching it. I tried to reproduce by enabling extensions, but didn’t get the same result. Possibly, because I deleted some of the extensions.