Hey, thanks for the report, and it’s good you already found a workaround.
You’re right about the version. This is a known Remote-SSH issue after updating the client to 3.15.x. On older Linux remotes with legacy glibc like CentOS/RHEL 7, Debian 9, Amazon Linux 2, the remote extension host crashes during activation, so the SSH agent just hits a timeout even though everything works locally. This isn’t related to Cursor servers or your setup.
The workaround is to roll back the client to a version before 3.15. You rolled back to 3.13 and that works. In a nearby thread, users also confirmed 3.14.27 as the last stable one. Details and discussion here: Regression in Cursor 3.15.6: Remote SSH Extension Host crashes with SIGSEGV on Debian 9 (linux-legacy-x64)
We’re tracking this issue. I can’t share an exact timeline yet, but I’ll post in the thread as soon as there’s an update.
@designers-prescripti, your case (CentOS 7.9, glibc 2.17, SIGSEGV in the remote extension host) is the same class of issue. Thanks for the detailed breakdown with commits. If you can, please paste excerpts from remoteagent.log and remoteexthost.log here and I’ll pass them along. For now, the workaround is the same: roll back the client to 3.14.x.