add cursor.sh IDE support to Gitpod

[shaal]

Is your feature request related to a problem? Please describe

cursor.sh (https://www.cursor.sh) provides a full IDE experience in the browser, with support for extensions and theming. It would be great to have this as an option when connecting to a Gitpod workspace.

Describe the behavior you'd like

I would like the option to open a Gitpod workspace using cursor.so as the IDE, similarly to how local IDEs such as VSCode and JetBrains are supported now.

Describe alternatives you've considered

The only alternative is using VSCode, but cursor.so has significant advantages with built-in GPT4 AI support for the whole project's codebase.

Additional context

cursor.so is based on VSCodium so it should be straightforward to integrate it as a connection option. Please consider adding support for this great IDE alternative!

[shaal]

While this issue is not resolved, here's my manual process to connect Gitpod workspace to Cursor IDE -

• Open Gitpod workspace
• Open that workspace in your local VSCode
• In local VSCode - Install Live Share extension
• In Local VSCode - Start a new Live Share session (copy link)
• In Cursor.so - Install Live Share VSCode extension
• In Cursor.so - Join the session (paste link)

[worldofgeese]

I also use Cursor and assumed, since it's built on OSS VS Code, Gitpod integration would just work. Cursor is a game-changer for AI-assisted development. Big ➕ for this feature!

[gtsiolis]

Thanks, everyone! In case it helps decide whether this is possible, re-posting from the README of cursor:

The VSCodium-based version of Cursor is not open-sourced, but we may open up parts or all of it in the future.

[mbrevoort]

@shaal wow, that workaround is involved but clever!

We'll reach out to the folks at Cursor and see if they are interested in making this happen. I would love to see Gitpod expand our IDE support.

[mbrevoort]

Hi @shaal, this still includes some friction but I was able to manually connect over SSH link this:
https://www.loom.com/share/c029b3a942ba4d8f8a1b5707f83b1dcc

We'll see if we can streamline this. :)

[shaal]

@mbrevoort - Thank you for the helpful feedback! To clarify the steps for connecting a Gitpod workspace to Cursor through SSH, here is a streamlined summary:

1. Open the repository in Gitpod and launch the workspace.

2. Click the vertical 3 dots on the right side of the workspace environment, then click "Connect via SSH."

3. Copy the SSH string by clicking the copy icon next to it.

4. In Cursor, click "Open with SSH" and paste the SSH string.

5. Remove ssh from the beginning of the string and the surrounding quotes.

6. Press Enter. The files won't show up yet.

7. Click "Open Folder" and delete /home/gitpod/.

8. Type /workspace/ to see a dropdown of directories. Choose the repo directory.

9. Click OK.

The workspace should now be connected! The Live Share extension is less involved, so hopefully there will be a way to streamline the SSH method too.

Let me know if this helps explain the steps more clearly! Thank you for sharing this solution.

[shaal]

Update to the update: The problem is resolved. I will add explanation on solution in the next comment.

... update from today: the SSH connection between Gitpod workspace and Cursor no longer works for me.

I am back to using Live Share as an alternative. I don't know what changed, I tried starting a new workspace but still no success with SSH.

[shaal]

To allow Cursor to connect through SSH with Gitpod, it is important to NOT have the Remote - SSH extension from Microsoft installed.

As seen in the screenshot below, Cursor has built-in support for SSH, so this Microsoft extension conflicts and cannot be installed alongside Cursor's SSH functionality.

I had originally imported all my VSCode extensions to Cursor, including the devbox by jetpack.io extension. By uninstalling this jetpack extension and reloading Cursor, the conflicting Remote - SSH extension from Microsoft is no longer installed, and the expected Cursor SSH message appears as in the screenshot.

The key points are:

• Cursor has native SSH support, so the Microsoft Remote - SSH extension conflicts
• Uninstalling the jetpack devbox extension removed the Microsoft SSH extension on reload
• The screenshot shows the expected Cursor SSH message after this change

[mbrevoort]

Thanks for the additional details. At the end of the week we were trying to get our extension to work with the open-remote-ssh fork used by cursor. I think we are pretty close to resolving the issues. I agree, it would be great to have cursor just work as a supporter ide.

[shaal]

Thank you!

One additional issue I noticed when connecting to Cursor via SSH is that it does not keep the Gitpod workspace awake.

Typically, Gitpod workspaces will automatically sleep after a period of inactivity. However, I would expect that connecting and interacting with the workspace through SSH and Cursor would reset the sleep timer and keep the workspace active.

This does not appear to be happening at the moment. The workspace still goes to sleep even when connected through SSH, which interrupts ongoing work.

[nhorton]

Related thing to the sleep issue; every few months, it seems like there is a bug that makes that sleep-while-in-use thing happen in Gitpod, including with VSCode. If you would put in something like a timeout countdown in the web page and a button to extend, it would give at least some way to workaround it when it happens.

[shaal]

Is there any update on this feature?

[rosendanew]

Any updates on the issue and it's priority within the gitpod team?

[jeanp413]

We did the required changes on our side, the remaining thing now is that cursor is using an old version of the open-remote-ssh extension, we already send them a message to update it.

[shaal]

@jeanp413 did you hear back from Cursor?

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.