Hey there! Stay on Cursor 3.14.x with auto-update off for now. That is the working setup for CentOS 7 / glibc 2.17 hosts on 3.15.x.
The extension host crash isn’t something you misconfigured. We’ve let the team know and this is an issue we’re tracking, same as this thread. No timeline yet, but I’ll post here when there’s an update.
One clarification: the linux-legacy server package is published for 3.15.19. Your install log saying it wasn’t found is a host-side check failing open (often TLS inspection / egress filtering on the box). Even a successful legacy download still hits the same crash on 3.15.x, so pinning 3.14.x remains the right move. If you can share the full Remote - SSH output log (View > Output → “Remote - SSH”), I can look at why that check failed.
Regular remote needs glibc 2.28+; 2.17–2.27 is meant to use the legacy server automatically. I’ll pass along the ask to document that publicly.