C++ Jump to Definition and Context Menu Incomplete on SSH Remote (CentOS 7)

Bug Reports
1

Describe the Bug

When using Cursor’s SSH Remote feature to connect to a CentOS 7 server for C/C++ development, the right-click context menu shows very few options. Even though the “Jump to Definition” item is visible, most symbols fail to resolve — I get a “No definition found” message.
This behavior differs from my local macOS 15.5 environment, where the right-click menu is fully populated and most symbols can jump to definitions successfully. Interestingly, even for some symbols that fail in Cursor, VSCode’s regular C++ extension resolves them just fine.

Steps to Reproduce

  1. Connect to a CentOS 7 server using Cursor via SSH Remote.
  2. Open a C/C++ project.
  3. Right-click on various symbols in the code.
  4. Notice the limited context menu options.
  5. Try “Jump to Definition” on various symbols.
  6. Observe that most of them do not resolve (unlike on local macOS).

Expected Behavior

The C++ extension should work the same across both local and SSH Remote environments: the right-click context menu should be fully populated, and “Jump to Definition” should resolve most symbols correctly.

Operating System

Linux

Current Cursor Version (Menu → About Cursor → Copy)

Version: 1.1.3 (Universal)
Commit: 1.96.2
Date: 979ba33804ac150108481c14e0b5cb970bda3260
Electron: 2025-06-15T06:37:17.379Z
ElectronBuildId: 34.5.1
Chromium: undefined
Node.js: 132.0.6834.210
V8: 20.19.0
OS: 13.2.152.41-electron.0

Additional Information

I followed the setup guide from this thread: New In-house Extensions (C++, C#, SSH, DevContainers, WSL, Python).
Despite that, the C++ extension behaves inconsistently across environments.
I sincerely hope the C++ extension can work properly in both local and SSH remote scenarios.

Does this stop you from using Cursor

Sometimes - I can sometimes use Cursor

3

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