Both of these are known issues tied to a recent update of the Remote SSH extension.
Saved projects failing to connect: The extension update that shipped on May 22 introduced a regression that can break reconnection to previously saved projects. Our team is aware and working on a fix. In the meantime, you can work around this by defining your SSH hosts in ~/.ssh/config (if you haven’t already) and connecting through the config alias rather than the direct user@host format.
Agent history: Your chat history isn’t lost. It’s still stored on disk, just inaccessible when connecting through a different workspace path. Once the fix ships and you can reconnect to your original saved projects, it should reappear.
Disconnect loop: If the reconnect cycle persists, try killing the multiplex-server process on the remote (pkill -f multiplex-server) and doing a Reload Window (Cmd+Shift+P > “Developer: Reload Window”) in Cursor. Our team is actively working on improving SSH reconnection stability.
You may also find this related thread helpful: Bug Report: Remote SSH extension v1.0.51 breaks Connect to Host