Hello Cursor team,
This message is to formally express our dissatisfaction with the current state of SSH and remote computer workflows in Cursor.
These capabilities were not optional for us. They were essential. We used them to connect to systems, inspect behavior directly in the target environment, and diagnose issues efficiently. With the current restrictions, regressions, or broken behavior, that is no longer possible in a practical way.
As a result, we are now unable to troubleshoot bugs effectively. We cannot connect to the systems we need, cannot inspect problems where they actually happen, and cannot rely on Cursor during real debugging workflows.
Frankly, this undermines one of the most natural expectations from an AI coding tool: if Cursor helps write the code, it should also be able to help follow that code into the real environment and support analysis on the actual system. Anything less turns it into a partial tool instead of an end-to-end engineering assistant.
If this capability is not restored, we will have to move away from Cursor. This is not a threat for effect; it is a practical decision based on workflow impact. A tool that cannot support SSH / remote investigation is not sufficient for our needs.
We need a direct answer on the following:
-
Was this capability intentionally reduced or restricted?
-
Is this a temporary bug or a product direction?
-
Will full remote troubleshooting support be restored?
Please escalate this appropriately.
Regards,